Skip to content

Services

Build the thing, then make sure it lands.

Most software fails somewhere between “it works on my machine” and “a stranger paid for it and it worked.” That whole stretch is the job.

Engagements

Three ways to work together.

Fixed-scope project

A defined thing with a defined end: an application, a site, an automation. Written scope, fixed price, agreed delivery date. The default, and the right shape for most work.

Discovery first

When the problem is clear but the solution isn't. A short paid engagement that produces a technical plan, a cost estimate and a recommendation — including, sometimes, don't build this. Yours to take elsewhere.

Ongoing retainer

A set number of days a month for continuing work on something already built. Only offered after a project, because it needs shared context to be worth the money.

Process

What actually happens.

1

Conversation

Half an hour, free, no deck. What you're trying to do and what's in the way.

2

Written scope

What's included, what's explicitly excluded, the price and the date. You can take this to another developer — it's a specification, not a trap.

3

Build

Working software early and often, in an environment you can click through. Feedback changes direction while that's still cheap.

4

Handover

Source, deployment, accounts and documentation, all in your name. Support afterwards is optional and separate.

What does it cost?

Honestly: it depends on what you need, and quoting a number before understanding that would be theatre. Every project is priced fixed after a written scope, so you know the figure before committing — and the conversation that gets there is free.