For agencies · White-label · UK-based
Turning the work down costs you the account. Hiring for it costs more than the project is worth. I build the AI feature behind your brand, on a fixed price and a fixed date, and your client never needs to know a subcontractor was involved.
The default is that I’m invisible. Everything below can be relaxed if you’d rather I weren’t.
You quote the client, you own the relationship, you invoice. I deliver to you. Nothing I build is published as my case study, and this site never names your clients.
Signed before I see a brief, a repository or a client name. Yours or mine, whichever your process prefers.
I work through you, in your Slack or by email. If you’d rather have a technical person on the call, I’ll join under your agency’s address as part of your team.
Code in your repository, in your stack conventions, with a walkthrough at the end. You’re not locked into me for the next change.
Features that sit inside a product you’ve already built or are building.
Support assistants, internal knowledge tools, product guides. Not a generic wrapper. It is grounded in their documents so the answers are theirs. Working demo.
Semantic search across a client’s document set, or structured data pulled out of invoices, CVs and contracts. See how it works.
Classification, summarising, routing and drafting wired into the tools the client already uses, rather than another system to log into.
OpenAI, Anthropic or Azure OpenAI added to a Next.js, React or TypeScript codebase, including the parts teams underestimate: streaming, rate limits, cost control and failure states.
Built so you can quote your client with a date you’ll actually hit.
The template below is enough. If the client’s request is still vague, send it vague, because pinning it down is part of the call.
30 minutes. You get a fixed price and a delivery date you can put in your own proposal, plus an honest answer if I think the feature is the wrong thing to build.
Working in your repository on a branch. Progress visible as it happens, so you’re never guessing what to tell the client on a Thursday.
Merged, documented and walked through with your developers. You present it to the client as your own work, because as far as the contract is concerned, it is.
No email required, no download form. Copy it, put it in your own doc, use it with any developer you like.
Most AI briefs that arrive from agencies stall on the same three unknowns: where the data lives, what “good enough” means, and who signs off. This template asks for those up front, which is usually the difference between a same-day fixed quote and a fortnight of back-and-forth.
AI FEATURE BRIEF 1. THE CLIENT'S ASK In their words, not translated into technical language: What they said they want: What we think they actually need: 2. WHERE IT LIVES Existing product, or something new? Stack (framework, language, hosting): Repository access possible? (yes / no / staging only) 3. THE DATA What the feature reads from (documents, database, API, user input): Roughly how much of it: Where it currently sits: Anything sensitive in it? (personal data, client-confidential, regulated) 4. WHAT "WORKING" MEANS The one thing it must do to be signed off: How the client will judge quality: What is explicitly out of scope for this round: 5. CONSTRAINTS Date the client has been promised (if any): Budget range or the fee already quoted: Anything that cannot change (design system, vendor, hosting, compliance): 6. PEOPLE Who signs off on delivery: Who at your agency I work through: Should I be visible to the client, or stay behind the scenes? 7. WHAT YOU HAVE ALREADY TRIED Prototypes, prompts, tools tested, or a previous attempt that stalled:
Sections 3 and 4 are the ones worth spending time on. If you can answer those two, most AI features can be quoted properly on the first call.
Two production AI products, both built end to end, both live and commercial.
An AI reading platform for UK primary school children: personalised story generation, comprehension tools and progress tracking. Built and run by me, used by real schools and families.
See the build →An AI recruitment platform doing CV analysis and candidate matching at volume, the same extraction and matching work agencies most often need for their own clients.
See the build →Next.js, React and TypeScript, with OpenAI, Anthropic, Azure OpenAI and Supabase. The person you brief is the person who writes the code, which is why a seven-day sprint is possible at all.
Not unless you tell them. I work behind your brand: no direct client contact unless you invite it, nothing published as case study material, and an NDA signed before any code or brief changes hands.
Fixed price per sprint, from £750, quoted once the brief is agreed. You mark it up however you like, and most agencies quote their client a project fee and keep the margin. Day rates are set out on the AI consulting cost page.
Yes, if you want a technical person in the room. I use your agency’s email address and introduce myself as part of your team. Plenty of agencies prefer I stay invisible, which is equally fine.
Small corrections within scope are part of the sprint. Anything genuinely new is quoted as a follow-on sprint. Retainers are available if you want ongoing availability without re-quoting every time.
You do, and by extension your client. Code is handed over with a walkthrough so your own developers can maintain it. No dependency on me after handover.
The brief above, repository or staging access, and a named person at your end who can make decisions. Same-day replies are plenty, and I do not need hours of anyone’s time.
Yes, and it is often the better moment. If you are pitching and need a realistic scope, price and timeline to put in the proposal, I will help you build that estimate without charging for it.
Send the brief, or just describe what the client asked for. You will get an honest scope and a fixed price, or a straight answer that it is not worth building.