Our process

Many of our customers have never worked with a developer before and aren’t sure what to expect. We get that, and we want to make it easy for you to imagine what it’s like to work with us. (It’s pretty fun – we promise.) This is the whole breakdown, from that first phone call to the project finish.

  1. First Contact
    Every project starts the same way: you pick up the phone and tell us all your troubles. We tell you that your troubles sound pretty rough, but we’re pretty sure we can make them better. You say that sounds pretty good. We say great, are you free for a meeting on Tuesday? (Or whenever. It doesn’t have to be Tuesday. We’ll coordinate.)
  2. Initial Assessment
    In this first meeting, we’re going to ask a lot of detailed questions about what you’d like this solution to do for you. We’ll come up with an initial list of features you want, problems that need solving, and keys to how your business works. We’ll define what you need, get to know one another, and decide if we all agree that we can make this project work together.
  3. Quote
    After the initial assessment, we’ll come up with an initial quote, as well as the estimated value of this app to your company. Which is to say, we’ll explain what it will cost you, but also how it will benefit you monetarily. If you think the amount of money you’ll save and earn is well worth the amount of money you’ll invest (and we think you will) we’ll sign an official agreement to work together.
  4. Planning
    This is where all our best-laid plans tend to go up in the air. This is completely normal and expected for software development. We’ll discover new requirements, you’ll decide on new features – in short, things will change. We’re breaking new ground here, and we’re inventing as we go. We’ll always run by changes in scope with you before we begin, but you should know that the planning process is always in flux.
  5. Documentation
    Once we have a system mapped out, we’ll start documenting the information that needs to be tracked and accessed within the system. This is tedious for us, but doesn’t require much input from you, so you get to take a break during this stage.
  6. Mock-Ups
    This is where the fun really starts. We start creating mock-ups to show you what your system will look like, letting you give your feedback, make tweaks, and ask for new elements. Expect lots of brainstorming and hand-waving and general melee.
  7. System Build
    We put our tech geekery to work. We start incrementally building the system one piece at a time, letting you test it at various stages to be sure you like how it’s coming along. Once all your functionality has been implemented, we’re going to have a real working model of your system. We have created a real thing from mere ideas! This is where we beat on our chests and holler our triumph. You can join in if you like.
  8. Testing
    This is where we find out our triumph was premature. It is utterly unheard-of for any initial prototype to not show some bugs and kinks and hiccups in the first testing phase, but we always seem to forget this and sigh heavily when it happens. We’ll go through several rounds of testing until all those kinks are worked out, and then we’ll beat our chests some more.
  9. Going Live
    It’s time for the real deal: all the bugs are gone and your system’s ready to go. We’ll launch it in a blaze of glory, and raise a glass to a brave new world.
  10. Standing By
    We make sure your live version is ready to go, but sometimes issues do crop up over time, or you decide you’d like to add new features or change the functionality. That’s no problem. We don’t just abandon your new solution once we launch it. We’ll always be a phone call away, whenever you need us.