How we deliver on our promises...

We love building systems together (and have for several years). In this industry, few developers stay together long enough to achieve our level of teamwork. We deliver on our bold promises together.

We leverage not only our vast library of proven code but the universe of existing libraries and tools to generate stable systems quickly. We don't build systems from scratch so our full efforts are directed at solving your particular problem and not monkey-coding and re-inventing wheels. We build as little as possible to achieve a new system; re-use is faster, cheaper, and less risky than construction. Our systems therefore have less original code which makes them easier to hand-off to your maintenance team and less cost for them to change.

We invest in excellent equipment and software so our infrastructure supports continuous iteration. Standard scripts drive our builds, document generation, testing, and deployment packaging. This ensures we have thorough documentation and continuous testing of all incremental changes (a necessary feature for rapid development).

Even when physically separated between our offices and yours we use real-time collaboration and shared virtual computers; when working we always enjoy quiet private offices and none of the distractions that steal time. We work together in person and apart.

We visit your groups who will run the new system to establish requirements. Uncertain and changing requirements are not a problem; we expect changes because that's business! Development is exploration. Even when the requirements seem obvious revelations occur running intermediate versions.

These rapid cycles drive our process; both teams (ours and yours) learn more each iteration and the versions improve continuously. The changing requirements pass into new versions and the resulting system shines.

We use appliances (via VMWare virtualization) for our deployment of versions to ensure that the environment the software runs in is not a factor during development. The final version can include installation automation for an integration to existing systems if requested; in many cases the appliance is sufficient for production use on its own.