Four gigs
AI agents, automation, web and mobile, Salesforce and AWS — see all four
ABOUT
WHAT I DO, AND WHO IT IS FOR
— NO AGENCY, NO HANDOVER CHAIN.

HOW I WORK
No account manager relaying your brief to someone you never meet. The person who scopes the work writes the code and answers when something needs attention a month later.
What is being built, what it connects to and what is deliberately excluded — agreed in writing with a fixed price attached. If the scope changes, we agree the change and its cost first.
Duplicate records, failed steps, the enquiry that arrives at 2am. Automations are tested against what actually happens, not just the path where everything behaves.
Documentation, a handover session and credentials that live in your accounts. Continuing support should be a choice you make, not a dependency a thin handover created.
WHAT YOU GET
What is being built, what it connects to and what is out of scope — with a fixed price attached, before any work begins.

Written updates at agreed check-ins and working software you can try, rather than silence punctuated by a demo at the end.

How it works, what it connects to, which credentials it uses and what to do when something breaks — walked through with whoever will own it.

Seven days on Basic, fourteen on Standard, thirty on Premium. Longer arrangements are available, but the handover is meant to make them optional.

WORKING TOGETHER
Communication, access, documentation and what happens when something breaks.
Still have a question? Get in touchI do, start to finish. There is no agency behind this and no team the work gets passed to. The person you discuss the problem with is the one who writes the code and the one who answers when something needs attention three months later.
Written updates at agreed check-ins, plus calls scheduled to suit your hours. Everything between check-ins runs asynchronously, so neither of us is waiting on the other to be awake. If something slips, you hear about it when I know — not at the deadline.
A conversation about the problem, a look at how the work happens today, and access to the relevant tools when we reach that stage. It also helps to know who will own the system day to day once it is live, because that shapes how it is built and documented.
You will hear that before work starts rather than after. Sometimes the right answer is smaller than expected, and occasionally automation is not the answer yet. Saying so early costs me an invoice and saves you a system nobody uses — that trade is worth making.
Yes to both. An NDA is fine before we discuss anything sensitive, and every project runs against a written scope that covers deliverables, timeline, price and what happens if the scope changes.
Tell me what you want to build or make easier. I’ll help you find the right next step.
01 / Clear from the start
Fixed scope. Upfront pricing.
02 / Direct to me
A reply within one business day.