icon picker
Think it Build it Studio


Fast, high quality product development for businesses who want to ship quickly, learn fast and deliver products that make a mark in their industry.

Helpful terminology

Before we embark on this crazy journey we call “App Development”, it would be helpful to establish a shared dictionary of somewhat jargony yet useful words:
Backlog: Where all tasks live before we decide to build them.
Feature: This could represent some new functionality or improvement to the app, or more of a behind-the-scenes update to improve performance, security, or reliability moving forward. At its core, this is simply some change that’s going to happen to the application.


Picking a plan

Before we start work you’ll decide how much developer capacity you want to reserve for the upcoming month. This works just like your mobile data plan: you get a certain amount of capacity to use on whatever you want. Of course, some things use up more capacity and some less. How much capacity is appropriate is something we can help you with but ultimately it boils down to how many features you want to prioritise getting done.
Below you can see an outline of your capacity options.
Monthly plan options
There are no rows in this table


Planning each month’s work happens in three distinct steps:
You’ll add all the features and updates you want done to the Backlog
We’ll then give an estimate for how many credits we think each one will take. We might ask some clarifying questions. We’ll include the uncertainty and risk in our estimate.
Finally, we’ll have a conversation with you about what takes priority. This is just a triaging of the tasks where we decide that adding in that integrating with your CRM is a must have for this month while adding in that new admin view can wait.
Please note that while we’ll always endeavour to make our estimates as accurate as we can, there is often unforeseen complexity and unknowns that make truly spot-on estimates nigh on impossible (if that wasn’t the case, a robot could do our job. Maybe one day....).
This is especially true as an app gets more complex. Each additional change has to take into account a wider range of touchpoints. Even a simple new search dropdown might warrant a database structure change, refactoring, bulk updating of existing data, and an hour or two of tests and bug fixing.
All that is to say, we may occasionally get features which take less or longer than our estimate, but as mentioned , we’ll do our best to communicate this timely and adjust our planning accordingly.


During the month we’ll work our way through the queue in order or priority. We’ll communicate largely a-sync but can schedule live calls for hairy topics we need to hash out live.
If it looks like we’re going to need more hours than we estimated, we’ll let you know as soon as we’re able. In this scenario, you can either:
Purchase additional hours for use within the month at $165/hr
Do nothing, in which case development will simply pause once we’ve exceeded our hours and resume once the next month starts.
If we finish all features in the month with time to spare, we’ll start working on tasks from the backlog. It’s worth noting that unused credits do not carry over to the next month. To reduce the chances of this happening (working as efficiently as possible!) we always want to have enough features in the backlog that we can pull into the month if we’re able.
Towards the end of the month we’ll re-do the stage for the subsequent month.

Changing your plan

We ask for a minimum of one weeks notice for any plan change; this includes starting a new plan, moving to new plan with more or less capacity, or cancelling a plan.

Plan billing

Payment for each month is due before the month’s start date.
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
) instead.