Process

How custom projects run

Bigger builds with a fixed scope follow these steps. You see the research behind each decision, a flat price before work starts, and something working at the end of each step.

1. 01

   Discovery

   We start with what's slowing you down, not a feature list. Most briefs I see are wishlists. That's fine, but the answer to most of the list can be "not yet".

   I leave the call with three things: the one or two problems worth fixing first, the hard requirements (a tool you must keep, a vendor you rely on, a date), and the questions I still need answered.

2. 02

   Research

   Before I write code, I read the docs, pricing and limits of the tools you already pay for and the alternatives. Often the fix is a setting or a tool you already own.

   When something has to move, like a booking system, I research the move itself: what data comes over, how long it takes, and what can go wrong. You get the findings with sources, and I mark anything I couldn't confirm.

3. 03

   A recommendation

   You get one recommendation, not a menu. It's the smallest change that fixes the main problem, split into steps that each work on their own.

   I also tell you what I'd leave out, what you could do yourself, and what would make me change my mind.

4. 04

   A checked plan

   Before a plan or quote reaches you, I check it for missing costs, promises I can't keep and dependencies outside my control, like a vendor's approval. I use AI tools to help me look for gaps, and I verify every one against the real docs.

   What's left is a plan I can stand behind.

5. 05

   A flat quote

   Each step has a flat price and a timeline. You pay per step and can stop after any one of them and keep what's done.

   The quote also says what's not included and which outside dates, like a vendor's approval, could move the timeline.

6. 06

   Build in small steps

   I build one step at a time and show you each one working before the next starts. Every change is tested before it reaches you.

   You get a private project page with the plan, the research, the decisions and a live tracker, so you never have to ask where things stand.

7. 07

   Launch and care

   Launch includes training and 90 days of bug fixes. After that, care is optional: monitoring, updates and small edits for the parts I built.

   You own every account from day one. If you stop care, I hand over everything and remove my access.