How we'd work together

No open-ended retainers and no surprise invoices. Work gets broken into pieces, each piece gets a price before it starts, and you decide whether to keep going after each one.

The process

1. A call

Thirty minutes, free. You describe the problem. I ask questions and tell you honestly whether it's something I can help with.

2. A written scope

I write down what I understand you need, broken into chunks, with a price and a rough timeline for each. Nothing starts until you've read it and agreed.

3. Build, in the open

I work in chunks and show you progress as it lands, not at the end. If something turns out harder than quoted, you hear it immediately.

4. Handover

You get the code, the deploy pipeline, and documentation good enough for the next developer. No lock-in and no dependency on me.

How pricing works

I price per chunk of work, not per hour, and the price reflects complexity and risk. A well-understood piece of work with a clear answer is cheap. Something genuinely uncertain — where the honest answer is that it needs investigation before anyone can estimate it — costs more, and I'll tell you which one you're looking at.

This means you're never buying an open-ended commitment. You approve one chunk, you see the result, and you decide whether to approve the next one. If you want to stop, you stop, and you keep everything built so far.