Process

How a project runs.

Five steps, fixed scope, one person accountable at every one of them. The same shape whether it’s a voice agent or a one-week automation.

1. 01

   Discovery

   A short call or a WhatsApp thread. You describe the workflow exactly as you run it today; I ask the awkward questions — edge cases, volumes, failure paths, and the tools you already pay for.

   You get — A plain-language summary of what we’re actually building

2. 02

   Scope

   Everything in writing before any money moves: what’s in, what’s explicitly out, the tools, monthly running costs, the price, and the timeline. If it isn’t in the scope, it isn’t assumed.

   You get — A fixed quote — no hourly meter, no surprises

3. 03

   Build

   I build it myself — no handoffs to a team you’ve never met. You get demo links as it takes shape, so course corrections happen mid-build, not after delivery.

   You get — Working demos, not status reports

4. 04

   Deploy

   Shipped into your accounts with error handling, retries, and logging from day one. When something fails, it fails loudly — you find out from an alert, not from a customer.

   You get — A system that tells you when it breaks

5. 05

   Handover

   Code, exports, credentials, and docs handed over with a walkthrough. Then I remove my own access — ownership means you don’t need me to keep it running.

   You get — Full ownership · no lock-in