10Packages4 tiers

Fixed scope. Fixed date.

Some work is knowable in advance. For that work, the scope and the schedule are on this page, and the quote follows within a day of a short call. Everything else goes through discovery, because guessing at a number helps nobody.

Launch Page

One page, live in a week.

Timeline1 week

QuoteSame day

You need a credible presence at a real domain before a launch, a raise, or a conference — and you need it this week.

A single, well-built page: your positioning, what you do, and one clear action. Built on the same stack as everything else we ship, so it is a foundation rather than something to throw away when the real site happens.

Included

One page, up to six sections
Copy edit of text you supply
Mobile, tablet and desktop layouts
Contact form wired to your inbox
Analytics and search-console setup
Deployed to your domain with SSL
One round of revisions

Not included

Original copywriting from a blank page
Custom illustration or photography
A CMS — content changes come back to us
Multiple pages or a blog

A live one-page site at your domain

Get a quote

Marketing Site

A full site you can edit yourself.

Most chosen

Timeline3 weeks

QuoteSame day

You have a product and a story, and you need a site your team can keep current without a developer in the loop.

Five to eight pages on a headless CMS, so your marketing team publishes without a deploy. This is the tier most companies actually need, and it is the one we recommend by default.

Included

Up to 8 pages, designed not templated
Headless CMS your team controls
Blog or case-study collection
Design system: type, colour, components
SEO: metadata, sitemap, structured data
Performance budget, enforced at build
Analytics and conversion tracking
Two rounds of revisions
A handover session with your team

Not included

E-commerce or payments
User accounts or gated content
Migrating an existing blog archive
Copywriting beyond editing what you supply

A live site plus a CMS your team owns

Get a quote

Product MVP

Your app — or web product — live in eight weeks.

Timeline8 weeks

QuoteSame day

You need something real in users' hands to validate demand, run a pilot, or show an investor — most often a mobile app, sometimes a web app. One platform, done properly, not a prototype that stops at the login screen.

A genuine product on one platform of your choosing: a Flutter app shipping to both stores, or a web app at your domain. Eight weeks is achievable because the scope is one platform and one core workflow — build both surfaces, or widen the workflow, and it becomes Custom Build. Most clients start with the app; the web option is the same engagement pointed at a browser.

Included

One platform: a Flutter app (iOS + Android) or a web app — your choice
Authentication and user accounts
One core workflow, end to end
Payments via Stripe or Razorpay, if needed
Admin view for your team
Push notifications (app) or transactional email (web)
Production deploy — store submission, or your domain
Weekly build you can open, from week two
Source in your repository from day one

Not included

The second platform — one product surface, app or web, not both
More than one core workflow
A backend built from scratch — this assumes an API exists
Offline-first sync with conflict resolution (that is Custom Build)
Compliance work (HIPAA, SOC 2, PCI)
Migrating data from an existing system

A live product — your app in both stores, or your web app at your domain

Get a quote

Custom Build

When the problem is bigger than a package.

Timeline3–9 months

QuoteAfter discovery

Offline-first apps, platform re-architecture, migrating off existing native codebases, anything regulated — the work our case studies are made of.

Everything above is fixed scope because the scope is knowable in advance. Most interesting work is not. This starts with a discovery sprint that ends in a written plan and a costed roadmap, and roughly a third of them end with us recommending you do not build the thing yet.

Included

Discovery sprint before anything is costed
Cross-disciplinary team, two-week increments
Offline-first sync and conflict resolution
Migration off existing native apps, without a cutover
Platform architecture and backend build
Compliance and audit requirements
Ongoing support after launch

Not included

An estimate before discovery — we will not guess
Native games or embedded firmware
ML research

Scoped in discovery, costed before you commit

Book a discovery call

How a fixed-price build runs

A fixed price is only worth anything if the process behind it is legible. This is the whole of it.

A 30-minute call

You describe what you need. We tell you which tier fits, or that none of them do — the ladder is not a funnel and pushing you into the wrong tier costs us more than it makes.

A written scope and a quote

You get a document listing every deliverable and every exclusion, with a fixed price against it. Nothing is open-ended and nothing is billed by the hour — you approve a number before any work starts.

Half up front

50% to start, 50% on delivery. The clock starts the day we have your content and access, not the day you pay — so a slow week on your side does not eat your timeline.

Build, with the work visible

A staging URL from day one, updated as we go. You watch it happen rather than waiting for a reveal, and course corrections cost hours instead of weeks.

Handover

Source in your repository, deploy pipeline you control, and a session walking your team through it. No dependency on us afterwards unless you want one.

Questions

Why aren't there prices on this page?

Because a number on a page is a number without a conversation attached, and it is wrong in both directions — too high for a simple job, too low for a complicated one wearing the same name. You get a fixed quote in writing after a 30-minute call, before any work starts. What is published here is the scope and the schedule, which is the part that does not move.

So how quickly can you tell me what it costs?

Same day for any of the fixed-scope tiers, usually within an hour of the call. Custom Build needs a discovery sprint first, because a number produced without one is a guess we would both end up regretting.

What happens if it takes longer than the timeline?

The price does not change. That is the point of agreeing a scope and a quote up front — we absorb the risk of estimating badly, which is the correct place for it to sit, because we are the ones doing the estimating. The exception is scope you add mid-build, which we quote separately before starting.

What if I want something that is not in the list?

Say so on the call. Small additions are usually absorbed; larger ones get quoted as a separate line before work starts. What we will not do is agree to it vaguely and argue about it in week three.

How is a Product MVP eight weeks when your case studies run months?

Because those are not the same job. The utilities field app was offline-first sync with conflict resolution across 400 devices, and the telemetry platform was a multi-tenant rewrite holding 40,000 events a second — both carry scale, sync and migration the MVP tier explicitly excludes. Eight weeks buys one platform — a Flutter app or a web app, not both — and one workflow, against a backend that already exists. If any of that is untrue for your product, it is Custom Build and we will say so on the call rather than in week six.

Do you write the copy?

We edit what you supply and will push back hard where it is unclear. Writing from a blank page is a separate engagement — good copy takes longer than the Launch Page tier exists for, and pretending otherwise is how one-week projects become six-week ones.

Can I start with a package and grow into custom work?

That is the intended path and the most common one. Everything is built on the same stack, in your repository, so a Launch Page becomes a Marketing Site becomes an application without anything being thrown away.

What do you need from me?

Content, brand assets if you have them, domain and hosting access, and one person empowered to make decisions. The last item is the one that most often slips a timeline — a fixed date needs a decision-maker who is actually available.

Not sure which one fits?

Describe what you need and we’ll tell you which tier it is — or that none of them are right, which happens often enough to be worth saying.

Start a project See what we’ve built