Discovery & Scoping
A paid, fixed-fee stage that turns an idea into a written scope and a price you can take to any team.
Software development solutions
You are about
to buy something
you cannot inspect
So here is the whole engagement, drawn to scale — what it costs, how long it runs, and every point where you can walk away.
What we build, and what moves the price
What we build.
These are not peer options to pick from. Discovery produces the scope, the build works against it, and operations keeps it running after everyone has gone home.
Web Development
Custom web applications, typed end to end and deployed on infrastructure your team can operate. Greenfield builds, replatforming, or joining an existing codebase.
E-Commerce
Online stores and checkout flows, including payment, inventory, and fulfilment integrations. Built on a platform you can staff for, not one only we understand.
UI/UX Design
Interface and interaction design done alongside the build rather than thrown over a wall — screens, flows, and the design system that keeps them consistent as the product grows.
Search & Performance
Technical SEO and page performance treated as engineering: crawlable markup, fast loads, structured data. Not content marketing or link building.
Launch & Operations
Getting it live and keeping it up — monitoring, backups, and a runbook written in plain language.
How an engagement runs
Four stages, and an exit at every boundary.
1–2 weeks • Paid, fixed fee
The paid stage that follows the free call, where a rough range becomes a fixed price. We ask questions until we can describe your business back to you, then write down what the software has to do and where the hard parts are.
You get: A written scope, a fixed price, and a plan you can take elsewhere.
2–4 weeks each • Per stage, approved in advance
Work runs in stages of two to four weeks. You approve each one before it starts and see working software at the end of it — not a status report describing software.
You get: Working software at every boundary, in your repository from the first commit.
1 week • Included in the build
Deployment, monitoring, alerting, and backups are part of launch rather than a later upsell. When something breaks at three in the morning, someone is paged and there is a written procedure for what to do.
You get: A live system, monitored, and a runbook in plain language.
Monthly • Rolling, cancel anytime
Ongoing operation and change, month to month. No lock-in and no proprietary framework you would have to pay us to maintain — including when an in-house team replaces us.
You get: A system you can hand to whoever comes next.
Six questions to ask any team
Ask us these before you ask for
a proposal.
01Who actually writes the code?
Agencies routinely sell you the senior people you meet and staff the work with juniors you never meet.
The people in the first call are the people who build it. We are a senior-only team, which is also why we are small and why we will tell you when we are full.
02Can we see previous work?
Most of our work is under NDA, and a portfolio of screenshots proves less than it appears to anyway.
Often not, and we will say so rather than show you something we did not build. What we can do is walk you through a technical decision in detail — which is the thing a portfolio is a proxy for.
03Who owns the code?
Some shops keep the repository until final payment, or build on tooling only they can operate.
Your repository, your accounts, from the first commit. No proprietary framework you would have to pay us to maintain.
04How do you handle scope changes?
A quote with no stated assumptions is a number, not an estimate. Ask what it depends on.
We name the assumptions in writing and price per stage rather than per hour, so the incentive to work slowly is removed. A change that grows the scope gets its own stage and its own price.
05What does "done" actually mean?
Without a written definition, "done" is whatever the vendor says it is on the day they want to invoice.
Done is defined in the scope before the stage starts: what it does, what it explicitly does not do yet, and what has to be true for it to ship.
06What happens when something breaks after launch?
Most proposals cover building the thing and go quiet about operating it.
Monitoring and alerting are part of launch, not an upsell. You get a runbook written in plain language, and you can stop at any stage boundary.
When we are the wrong team
Three situations where you should hire someone else.
We would rather say this now than three weeks into a project.
You need forty people by next quarter.
We are small on purpose and will stay that way. Scale like that needs a different kind of firm, and we would rather name one than pretend.
You want the cheapest quote.
We are not it. The cheapest quote is rarely the cheapest project, but if price is the deciding factor you should buy on price and not on this page.
You need it live in three weeks with the scope already fixed.
One of those has to move. We will tell you which one before you have paid us anything, not three weeks in.
Bring us the thing you have been told and do not understand.
The first conversation costs nothing. You will leave with a rough range, an honest read on whether we are the right team, and no obligation to go further.
Talk to us