Typical Project Process

We're fans of simplicity, and we don't like things that slow us down - this includes cumbersome documentation and administration. Here's our typical workflow when you hire us:


Timeframe: 1-2 days
We'll want to meet with you and find out how you work, what you need, and what we can do for you. After that we'll prepare a one page proposal document that outlines what we discussed and what we're going to build, with budget and schedule.


Timeframe: About a week
Once you give us the green light, we get started immediately. We'll meet again, and fully discuss the new project. We'll then prepare a design document, which is a detailed feature sheet of everything the system should contain, how it will function, how it will interact with users of the software, etc. It's the skeleton for the application and we want to nail everything down early. That's not to say we can't make changes as we go along, but the more we clarify and discuss the major components of the system early, the better able we are to manage complexity and scope change later on. This usually takes between 5 and 7 days.


Timeframe: Project-specific
Once we've all got a good idea of the whole system, the construction phase begins. It is at this point we add screens, user interface components, and bells & whistles. You'll begin to see the application take shape, as we quickly get a working version going, and incrementally improve it as we go. We'll want your feedback, so we will continuously release new versions to you to go over.


Timeframe: 1-2 days
After we've finished the work, and the software is functional and feature-complete, we'll ask you sign off on it as such. At that point, your warranty period will kick in, where we're available for 60 days to fix minor bugs that weren't discovered during development (no software is perfect), as well as assist your team with integration into your existing systems (if required), familiarize your users with the software, etc.
"Fresh Coffee, Great Software"