How we work, in four steps and no ceremony.

The actual process, including the parts that are inconvenient for us.

If any of it does not fit your organisation, say so in the first week rather than the last.

Discovery, one week
We interview whoever knows the problem best, write down what success means in one sentence, and produce a scope with an explicit list of what we are not building. You can walk away at the end of this with the document and no further obligation.
A prototype before a plan
The riskiest assumption gets built first, roughly, so it can be wrong cheaply. A prototype that dies in week two has done its job better than a specification that survives to launch untested.
Weekly shipping
Work lands on a preview URL continuously and you see it every week. There is no phase where we disappear for a month and come back with a reveal, because that is where projects quietly go wrong.
Handover you can use
Typed code, a README that works on a machine that has never seen the project, deploys running in your own accounts. If you never call us again, nothing breaks.

What we will not trade away.

Cut scope before cutting quality. A smaller thing that works beats a bigger thing that almost does.
Boring technology on purpose. Novelty is a cost that someone pays at three in the morning.
Say the uncomfortable thing early. A hard conversation in week one is cheaper than a rescue in month four.
Measure instead of assuming. Performance, accuracy and usage all get numbers, not adjectives.

If it does, the next step is a short call about scope. If it does not, we would rather find that out now than three months in.