01
Marketing & brochure sites
Pages, a content editor a non-technical colleague can actually use, and forms that reach a human. Weeks, not quarters.
- cms
- blog
- multilingual
- lead_forms
- catalog
[ product studio · web, mobile, integrations ]
We build custom applications and then keep them running. No discovery phase you pay for twice, no fixed bid that quietly becomes a change order. You get a scope, a number, and the person who wrote both.
40+ builds shipped 14 wks median engagement 9 engineers, no bench
$ scope ./brief.md reading brief ....... ok project type ........ web application features ............ 6 selected integrations ........ 3 systems platforms ........... web, ios design .............. wireframes only timeline ............ normal → estimate ............ $69,500 → planning range ...... $59,000 – $83,000 $
[ what we build ]
Most briefs are one of these. They differ less in the technology than in what has to be true on the day it ships — which is why they are priced from different starting points.
01
Pages, a content editor a non-technical colleague can actually use, and forms that reach a human. Weeks, not quarters.
02
Accounts, permissions, dashboards, search across your own data, and an audit trail that answers who changed what and when.
03
Built for both stores. Offline-first where the network is not a given; camera, location and push where the product genuinely needs them.
04
Two systems that have to keep agreeing with each other. Sync, single sign-on, webhooks, and scheduled jobs that alert when they fail.
[ capabilities ]
We pick tools for how well they age, not for how new they are. The specific stack is a conversation for the kickoff; these are the categories every build of ours has.
[ pricing ]
Effort scales with three things: how many features the thing has, how many other systems it has to talk to, and how many platforms it has to run on. Everything else is rounding.
So we do not quote a range and defend it later. We start from a base for the kind of project, add a figure per feature, add a unit per integration, add a surface per extra platform, and show you the stack. If you remove a feature, the number goes down while you watch.
The scoping form asks exactly the questions that move this total — and nothing else. It does not ask what your budget is.
estimate — worked example
Illustrative figures for a fictional project. Your own stack is assembled by the scoping form, one answer at a time.
[ engagement ]
Pick the one that matches what happens after launch. Changing your mind later is a conversation, not a renegotiation.
[ one-time build ]
A defined scope, a fixed team, and a handover that includes the repository, the runbooks and a walkthrough with whoever inherits it. Right when you have engineers of your own to take it on.
[ ongoing retainer ]
A standing share of the team, a roadmap reviewed monthly, and a named engineer who answers when something breaks at an inconvenient hour. Right when the software is the product.
[ contact ]
Write it the way you would write it to a colleague — a paragraph is plenty. The form reads it, works out which questions still apply, and prices the shape of the work as you answer.
$ the scoping form opens on its own in a moment — or press “Scope my project” in the corner whenever you are ready.
Tell us your trade and town. We’ll stand up a branded instant-quote flow and email you the link — no sales call required.