The number comes before the build.
Fixed price for anything we can scope, monthly for work that is genuinely open-ended, and a flat hosting fee after launch. No hourly meter, no invoice that arrives larger than the estimate.
Get a fixed priceLaunch
from $4,500
fixed · 3 to 4 weeks
Best when: A marketing site or landing pages that need to work hard
- Up to 8 pages, designed and built
- Content model you can edit without us
- Analytics, pixels and conversion tracking
- Performance and accessibility pass before launch
- 30 days of changes after go-live
Product
from $18,000
fixed, per phase · 6 to 12 weeks
Best when: A web or mobile app with users, accounts and data
- Discovery, design and a working v1
- Auth, roles, payments and admin
- Integrations with the systems you run
- Test suite and deployment pipeline
- Handover documentation, or we keep running it
Embedded
from $6,000
flexible, per month · Rolling, 30 days notice
Best when: Continuous work when the roadmap is longer than one project
- A named engineer and designer on your team
- Weekly shipping against your priorities
- Scope changes without a change order
- Direct access in your Slack
- Pause or stop with 30 days notice
What it costs to keep it alive.
Every plan includes hosting, certificates, backups, monitoring and patching. The difference is how much change is included and how fast we answer.
Essential
$99/ month
Best for: Marketing sites
- Managed hosting on a global edge network
- SSL, backups and uptime monitoring
- Security and dependency patching
- Up to 1 hour of content changes a month
- Next business day response
Standard
$349/ month
Best for: Sites and apps that keep changing
- Everything in Essential
- Staging environment and release process
- Up to 4 hours of changes a month
- Performance and error monitoring with alerts
- Same business day response
Scale
$899/ month
Best for: Revenue-critical products
- Everything in Standard
- Up to 12 hours of changes a month
- 99.9% uptime target with incident response
- Quarterly performance and security review
- Named engineer, 2 hour response in business hours
Hosting is optional and month to month. Cancel and we hand over the code and the infrastructure, documented, with no exit fee.
Six things that change a quote.
So you can tell roughly where you sit before we speak.
How many user types it serves
One kind of user is a build. Customers plus staff plus an admin is three interfaces, three sets of permissions and three sets of edge cases.
Whether money moves through it
Payments, subscriptions, refunds and invoicing bring tax, reconciliation and failure states that have to be handled properly rather than optimistically.
How many systems it integrates
Each integration is its own small project, and legacy systems without APIs cost more than modern ones with good documentation.
Whether content changes without us
A site your team edits needs a content model, an editing interface and preview. Cheaper to build in at the start than to retrofit.
Compliance and data residency
Health, finance and public sector work carry audit, retention and residency requirements that change the architecture, not just the paperwork.
How fast you need it
A normal timeline is cheaper than a compressed one. If a date is fixed, we scope to the date rather than pretending everything fits.
Before you enquire.
Fixed, for anything we can scope. You get the number and the date before we start, and a change of scope gets its own written price rather than appearing on an invoice. The embedded option is monthly instead, for work that is genuinely open-ended.
No. Everything we build can be handed over to run wherever you like, with documentation. Most clients stay because patching, monitoring and small changes are the part nobody wants to own, not because they are locked in.
You do, on day one. It lives in your repository and your cloud accounts, and it stays yours whether or not we keep working together. No per-seat licence, no platform you can only leave by rebuilding.
For a brochure site with no integrations, it often is not, and we will tell you that. The difference shows when you need real data, logins, payments, an integration with the system you run, or performance that survives a traffic spike.
Yes, and it is a common start. Two weeks produces a written assessment of the codebase, the infrastructure and the risk, with a plan to stabilise it. You keep the assessment either way.
Then you are talking to the right people. Most of what we build ends up connected to the automation side: the app collects the work, the automation does it. We scope both together so they are not two projects that meet awkwardly later.