Our development processes are structured and orderly. We follow a three stage waterfall model, utilizing development, staging, and production server platforms. We use well-supported, proven toolsets, storing code and static content in the Subversion source code control system, and logging issues, change requests as well as project documentation utilizing Trac.

We closely adhere to the principles of KISS and DRY in our development, in an effort to maximize the simplicity and intuitiveness of the user interface and to reduce the introduction of extraneous errors, as well as reducing time to delivery. Following these principles and employing these tools allows us to deliver a more robust and resilient product.

We have developed a number of complex, interactive web-based systems for both customer-facing and internal audiences. These include systems that serve as customized ERP solutions, community-centric portals, timeclock/time accounting systems, database-driven customer sites, among many others.

In our efforts to provide robust and responsive solutions, we’ve found more comfort over the years utilizing Open Source Software. Since you have access to the source code, and more often than not, a large group of people sharing their experiences with it on the web, you can typically solve any problem that comes up pretty quickly. The web has made this extraordinarily easy. Contrast this with using a closed source, proprietary system, where you are dependent upon that one provider. If you come across a roadblock in your development due to a bug in the system, or an incompatibility, you are typically at the providers mercy. With an open source solution, you can modify the source code to fix the bug, or eliminate the incompatibility, and then move on.

Shall we begin?