Bring the problem. We'll pick the tools.
Most businesses don't come to us asking for an app. They come with a till that stops when the Wi-Fi drops, branch numbers that never match head office, or an app that stalled before launch. These four services are how we fix it, and most projects need two or three.
What it costs.
It depends on what you're building. Here's how we price it, so the number you get is one we can keep.
How much does it cost to build an app?
Three things drive the price: how many screens and user roles there are, how many other systems it connects to (payments, printers, outside services), and whether it has to work offline. We start by mapping what you need and finish that step with a written estimate, so the number is for the thing you actually need.
Fixed price or hourly?
A fixed price for the first build, so you know the number up front. Most clients then keep us on a monthly retainer, because the version that matters is the one people use after launch.
What makes a project more expensive?
Connections, more than screens. Payments, receipt printers, live updates and anything that must work offline add work you can't see in a mockup. A catalogue with ten screens costs less than a checkout with three.
Do we pay before we see anything?
You see every screen in Figma before the build starts, and from the first week there's always a working version to try.
Can you work with a small budget?
Sometimes. The better move is to build less, well, than everything badly. We'll tell you what we'd cut and what we wouldn't.
Let's make it work.
Tell us what's broken or what you want to build. We'll reply with what we'd make and what it would take.
How we work →