Pricing

04
Pricing

How pricing works, in words, not numbers. Every part of it traces to a commitment already on the site: the feasibility report first, the fixed quote before any build, and requirement changes tracked for the next version.

You find out the cost before you spend on the build

Before anything is built you get a written feasibility report: the direction I'd take, what it involves, and an honest cost. It's a paid service, priced at a fraction of what starting the build without it would cost, and it can just as easily point you at a leaner version, a different route, or away from the build altogether. That honest verdict is worth paying for even when it spares you a build you didn't need.

The first conversation and the scoping that frames the report are free; what you pay for is the written recommendation. That is the point of doing it first: you decide whether to commit to the build knowing what the work really takes, not on a guess.

src: How I work · step 03

A fixed quote, not an open meter

After the feasibility report you get a fixed quote, before any build begins. The number reflects work I've actually scoped, not a hopeful estimate, so the cost is settled before you commit rather than climbing as the build goes on.

The quote follows the report because that is the point where the work is actually understood. There is no open meter running while I figure the project out.

src: How I work · step 04

Changes go to the next version, not a silent bill

When requirements change mid-build, they don't quietly expand the scope and the cost. A change goes to a ledger for the next version instead, so you always know what you're paying for and when it lands.

That keeps the agreed quote meaning what it said, and keeps a new requirement an explicit decision you make rather than a surprise on an invoice.

src: FAQ · how changes work

The billing stance

Pending

The wider billing stance (how small changes and ongoing work are priced, and the reasoning behind fixed versus hourly) is mine to set and designate. Until then it stays off the page rather than appear as a guessed figure or policy.

Not sure it's even possible? That's what the first conversation is for.

You get a written feasibility report and an honest cost before you commit to the build. src: How I work · step 03

Start the conversation