FLATMAP

How it works

How a project actually goes.

No mystery and no agency theatre. This is the whole thing, start to finish, including the parts most people do not tell you about.

Start to finish

Five steps. None of them are a surprise.

  1. 01

    We talk

    Thirty minutes, no charge, no obligation. You tell me what you want and why. I ask a lot of questions — often the useful outcome of this call is realising the thing you need is smaller than the thing you asked for.

    You know what it would take before you commit to anything.

  2. 02

    We agree what we are making

    I write down what you are getting, what it costs and roughly when, in plain language, on about one page. You agree to that. There is no forty-page contract nobody reads.

    One page you can actually read, and a price that does not move.

  3. 03

    I build it, where you can see it

    You get a link, and the thing behind it grows week by week. You do not wait until the end to find out I misunderstood you. When something is wrong we fix it then, while fixing it is cheap.

    No six-week silences.

  4. 04

    It gets checked properly

    Every time I change something, a set of automatic checks runs over the whole thing to make sure I have not broken anything that already worked. This is the boring habit that separates software that lasts from software that falls over three months in.

    It works before you ever see it.

  5. 05

    It goes live, and it is yours

    I handle hosting, the domain, the certificates and the search-engine side. Then I hand over the keys — the code, the accounts, all of it. I am happy to keep looking after it, but you are never stuck with me.

    Yours to keep, or to hand to somebody else.

One more thing

Yes, I use AI. Here is exactly how.

You have probably seen websites that were obviously churned out by a machine — generic, slightly wrong, clearly nobody cared. That is not this, and I understand why you would worry about it.

I use AI agents for the parts of the job that used to be slow and repetitive: writing routine code, checking my work, running the tests, publishing releases. They work inside rules I wrote for your project specifically, and nothing reaches you without passing checks I set up and without me reading it.

What that means for you is simple. The thinking, the design and the judgement are mine. The tedium is automated. That is why a properly built thing now takes weeks instead of months — and why I can take on projects that would once have been too small to do well.

Limits

What I never leave to a machine.

Anyone who cannot tell you where the line is has not thought about it. Here is mine:

  • Deciding what to build, and what to leave out. Most of the value in a project is in the things you decide not to do.
  • Anything touching money or personal information. I read every line of that myself, every time.
  • Talking to you. You get me in the conversation, not a summary of me.

Talk to me

Still sounds like a fit?

Tell me what you are trying to make. Thirty minutes, no charge.

Start a project