Notes for people buying software.

Short, practical guides on the decisions that matter before a project starts: what to build, how to scope it and how to brief a studio.

React Native vs native apps: which should you build?
When one codebase for iPhone and Android is the right call, when separate native apps are worth it, and what to ask before you decide.
2 min read
Read the guide: React Native vs native apps: which should you build?
How custom software projects are scoped
The steps that turn a rough idea into a written scope you can approve, and why doing this before any code is written saves everyone trouble.
2 min read
Read the guide: How custom software projects are scoped
What a project brief should include (with a template)
A short checklist and a copy-and-paste template for writing a brief that gets you a useful answer from a studio the first time.
2 min read
Read the guide: What a project brief should include (with a template)

Tell us what you're building.

A clear brief is all we need to start. We will tell you plainly whether we can help and what a sensible next step looks like.

You send a brief
A few lines on the problem and the outcome you want.
We reply within a business day
With questions, or an honest view on whether we are the right fit.
We talk it through
A short call to understand scope, constraints and priorities.
You receive a written proposal
Scope, approach and cost in writing, before any code. There is no price list: the proposal is the price.