The success of any new software project is critically dependent on the initial “discovery” or “requirements analysis” phase of the project.

Here are some reasons requirements analysis is often treated as a separate project—distinct from design and implementation of a software system:

• More accurate cost estimate. It’s far easier to accurately estimate a development project after the requirements have been clearly established.
• Better evaluation of the project. With an accurate estimate of cost and completion date, it is much easier to evaluate cost vs. benefit and to position the proposed system in a company’s overall strategic plan.
• Higher-quality bidding from vendors. If you want competitive bids from software development companies, a good requirements study is essential. Bids will be more accurate because potential vendors have clear information on which to base their proposals. In addition, because all bidders will be responding to the same written request, your evaluation of their responses can be on a more “apples to apples” basis.
• Leapfrog a generation of development. A well-executed requirements analysis often reveals opportunities to streamline or evolve existing business practices. Sometimes one or two rounds of requirements analysis followed by a re-evaluation of objectives can help you to skip a generation in-house development—so you ultimately end up with “version 2” of the desired system instead of version 1, saving considerable cost and time.

We believe in the extraordinary efficacy of well-executed discovery and requirements analyses. And we know that “well-executed” means going well beyond the obvious—working with you to reach the point where the goals for the system are rooted in the true operational, competitive and economic realities of your business.

We also understand that you “hold the reins.” We can go deeply into requirements for complex systems and organizations—but we equally understand there are times when simplicity and quick conclusions are desired. You call the shots and we do the work.

Discovery and requirements analysis are part of every software project we undertake. Having seen so many projects through to completion, we understand not only how to do requirements analysis well, but also how important it is to the final outcome of a project.

When stakeholders understand the significance of requirements and discovery, they gain a better perspective of the great importance of their role—up front, at the beginning of the project—leading to a spirit of cooperation and enthusiasm based on shared vision of a high-quality result from the project.

• We care about the quality of our work—not just from the “technical” point of view, but also from the standpoint of benefits you can receive, and the cost-effectiveness of the work we do.
• We know that software can be even more effective and easier to use than you hoped at the beginning of the project—and that this begins with well-executed discovery and requirements analyses. We know how to make that happen.
• We always stand behind our work. Every project has a two-year warranty.
• We have proved that our work is consistently of the highest quality. Scores of clients and hundreds of successful software applications attest to that.
• We are easy to work with, flexible in organizing projects so they will be compatible with your specific goals and ways of doing business.