1:1 · 90 minutes · Two sessions a week
Ninety minutes, one to one, on how you actually work with AI.
Bring a codebase, a project you are planning, or an agent setup that keeps going wrong. We work on it together on a screen-share — I change things while you watch, rather than describing what you should change. You leave with a written plan.
If I can't help you, I'll say so in the first 15 minutes and refund you in full. No argument, no forms. Reschedule free up to 24 hours before. Inside 24 hours the slot is used.
How it works
01
Book and tell me what to look at
You get a form when you book. One sentence on what you want to work on, one on what you have already tried. A repo link if you have one — useful, not required. That is the whole prep.
02
Ninety minutes on the real thing
Screen-share, and we work on your situation rather than an example one. If there is a repo we get into it; if there is not, we work on the setup, the plan, or the decision in front of you.
03
Leave with the plan written
The action plan gets typed during the call in a doc you keep. Nothing is promised for later, because things promised for later do not arrive.
What you get
- Ninety minutes on a screen-share, working on your actual situation — not a talk about workflows in general.
- If you bring a repo, we work in it: context files, agent instructions and review loop rewritten live, by me, while you watch.
- A written action plan typed during the call, in a shared doc you keep.
- The recording, if you want it.
- One follow-up email a week later if something we changed did not hold up.
What this is not
- I do not write your feature for you. We fix how the work gets done, not the backlog.
- No ongoing retainer, Slack access, or "unlimited questions" afterwards.
- Not a code audit. Ninety minutes is not enough to responsibly review a whole codebase for security or architecture.
- Not a tutorial. If you have never used an agent before, install OpenAgents Control and use it for a week first — you will get far more out of the session afterwards.
Founding rate for the first ten sessions. It goes up after that — the sessions do not get worse, I just stop needing the first ten write-ups.
Book this if
- You already use Claude Code, Cursor, OpenCode or similar — or you are about to and want to start properly.
- You are working on something real: a codebase, a project you are planning, or a setup you want to get right.
- The tools work in demos but drift on your actual work.
- You spend longer reviewing generated code than writing it would have taken.
Do not book this if
- You want someone to build the thing for you. That is contract work, not this.
- You are choosing between tools and want a recommendation. That is a free video, not £150.
- You want a general lecture on AI coding. Bring something specific — a repo, a setup, a decision you are stuck on — or ninety minutes will drift.
- You are brand new to programming. This assumes you can already read code.
Who you are booking
I am Darren. I make DarrenBuildsAI, where I work through AI coding tools on real projects rather than demos — and show the parts that do not work as well as the parts that do.
I build and ship with these tools every working day. That is the only reason the advice is worth anything, and it is why the sessions stay capped at two sessions a week — the moment this becomes the job instead of the thing beside the job, the advice goes stale.
I also build OpenAgents Control, an open-source agent framework with 4,800+ stars on GitHub. It exists because I kept hitting the same problem you probably have: agents that run off and produce a diff nobody can review. Most of what we do in a session is the same thinking, applied to your situation instead of a general one.
If you want to judge before spending anything, watch a couple of videos first. The session is the same person, working on your problem instead of mine.
Questions people actually ask
Do I need to bring a repo?
No. Bringing one makes the session sharper, but plenty of good sessions are about a setup you are planning, an agent config that keeps misbehaving, or a decision you are stuck on. What matters is that you bring something real rather than a general question.
My code is private or under NDA. Does that rule this out?
Not at all. Most people screen-share rather than send anything, so nothing gets cloned or kept. If even screen-sharing is off the table, we can work on a redacted branch, a reproduction, or just your setup and your approach — and it is still a useful ninety minutes.
What if my problem is not one of the ones you list?
Send it to me before booking. If it is not something I can help with, I will say so and not take the money — that is easier for both of us than finding out fifteen minutes in.
What actually happens in the ninety minutes?
The first fifteen are you showing me the thing that is breaking. Then we work on it — I drive as much as you do, and I change files. The last ten minutes we write down what you are doing next. There is no presentation and no prep deck.
Why £150?
It is a founding rate for the first ten sessions, and the trade is that I get to write up what we found. It will go up. If you think it is cheap because I have no track record, watch a few videos first and decide from that rather than from the number.
What if it is not useful?
Then you get your money back. I will tell you inside the first fifteen minutes if I do not think I can help, and refund you in full. If it goes the distance and still misses, email me and I will refund you anyway — I would rather that than have you tell people it was a waste.
Why only two a week?
Because I still build and ship with these tools daily, and that is the part that makes the advice worth anything. If the calendar is full, it is genuinely full rather than a countdown timer.
Do I get a recording?
If you want one, yes. Say so at the start of the call and I will record it and send it over afterwards. It is your call, not the default.
What happens after the session?
You leave with the written plan and go do it. A week later I will email once to ask whether the changes held up. If you want more sessions after that, we can talk about it then — there is nothing to sign up for now.
Two sessions a week. That is the cap.
If the calendar is full, it is genuinely full — there is no timer on this page counting down to a fake deadline. If I can't help you, I'll say so in the first 15 minutes and refund you in full. No argument, no forms.
Book a Workflow Review — £150