Software Development

Software development is our passion. After we go through the design process, it’s time to start developing your product in actual code. We love to see it when an entrepreneur is able to touch their idea for the first time in real code, it’s like watching a father hold a newborn child and what’s even more exciting is the first time it is held in the hands of real users. On this page we describe how we do it.

How It Works

At Approachable Geek we develop our software in two week intervals. The first week we write code, the second week we spend the Monday internally testing it with our developers, on Tuesday we have non technical people test it, on Wednesday we demo it for you, the client, and send you a build of the app that you can test and request revisions on. Then Thursday through Friday we implement your revisions and send you a completed two weeks worth of code.

This process allows us to give you solid code that is rigorously tested, and provides clear touch points throughout the development of the app for communication and adjustments.

work steps

Your Team

Throughout the development process we have a project manager who serves as your point of contact with Approachable Geek helping to schedule meetings, inform you of progress, and communicate adjustments during the process. You’ll also have a team lead who represents the developers in helping resolve technical issues and show you the development of the app. The team lead has a few other developers that work with them.

teams involved


Everything we do with our process of software development at Approachable Geek is aimed at delivering great code and helping you, as the client, have a great experience working with us. We believe in the old adage, “Measure twice, cut once” and that ethos is infused into everything that we do.

We do test-driven development and spend a full week on testing and revisions for every week of coding because we build our software for the long haul. There are cheaper and quicker ways to do it in the short term, but it doesn’t produce the same stability of software or ease of use for your users.