Less is more—We won't clutter our applications with too many buttons, colors, fonts or complexity. A custom software application is best when it requires a very, very light instruction manual.

Do it right the first time—Good software begins with the thorough gathering of requirements and a complete, written design. We won't proceed with a project without clear written direction so that all stakeholders know what is to be built. This avoids costly rework, missed deadlines and an upset client.

Give the customer what they want: no more, no less—Bells and whistles are fun and interesting, and sometimes the client even likes them. Usually, though, adding them comes at a cost to the budget or schedule. We strive to build applications that conform exactly to the customer's specifications. If a customer wants to add a feature to a project mid-stream, all stakeholders will be made aware of the effect on the budget and schedule before we move on the change. This may seem pedantic, but in our experience it actually saves time, money and avoids confusion in the long run.

Make the customer’s data work for them, not the other way around—Whether a client is moving from a paper-based system to a digital one or is revamping an existing software application, our goal is to come up with meaningful and creative ways to allow customers to view, report on, graph, manipulate and otherwise use their valuable data in the most powerful yet easy-to-use way possible.

Build software that makes users smile—This is the part that we find the most fun...coming up with ways to make a client's employees' experience while using our software fun. This takes a simple graphical user interface (GUI) design as well as listening to the needs of end users.

Strive to build software that cuts work time in half—By following our own strict software development standards in combination with the client's knowledge of their business and our years of experience in developing streamlined, integrated software applications, we hope to make your work happen faster and be simpler to perform.

Use the right tool(s) for the job—We will never push any particular software or hardware technologies on our clients. We will make recommendations, but we will use that combination of technologies that we know best and that best suits the client's needs, the project and the budget.

Manage the project to the triple constraints—Imagine the three main components of a project as a triangle with budget, schedule and customer requirements as the three sides. Any change to one side may have an effect on the other two. Therefore, if any changes are to be made to a project, the significance of the change is thoroughly discussed and then planned before we integrate it into the master project plan. Also, all stakeholders are made aware of the effect of the change before it is approved.

There are no stupid questions—While it sometimes takes a bit more of everyone's time, we insist that our analysts ask as many questions of their client contacts as they need to in order to get the information they need to complete their work to the customer's specifications. Our idea is that a few more questions up front, even if it seems bothersome, can avoid later cost and budget overruns or software that doesn't work quite right.

Walk, don't run—We are careful planners and will do no work without consise written specifications. We also have more project meetings throughout the course of a project than many other firms do—usually there's one at least once a week—but, again, we feel this saves negative cost and schedule effects from happening long term. Also, we try to have every line of code reviewed by at least one other analyst to ensure that our work is of the highest quality, is error free, and, of course, does what the customer wanted it to do in the first place.