Jesse was wearing every hat in his business, with a hundred things competing for his attention. He knew AI mattered — he could see people all around him accelerating with it — but with so much to prioritise, he simply did not know where to begin.
Over the years, Jesse had quietly built all sorts of processes, operational systems and sales and marketing collateral — much of it genuinely detailed, but a lot of it never seeing the light of day.
He wanted to get on the front foot with AI and learn it quickly, so he could clean things up and build — and actually implement — new systems and processes fast.
Two weeks earlier I ran a discovery call with Jesse, and he shared a huge amount about his business. The thing I picked up on most was a real need to better qualify his inbound leads — that, and a stack of software subscriptions, maybe half of which were genuinely being used or adding value.
So we built the day around two things: getting Jesse genuinely confident and self-sufficient with AI in the morning, then putting it straight to work on a real problem in the afternoon.
Got both up and running, side by side, so Jesse could see the landscape and where each fits.
Set up Claude Projects with standing instructions — the engine room that makes every chat smarter.
Let Claude write its own instructions from a rough draft, then refined it. The AI optimising its own brief.
Plugged Claude into Jesse's own world. We even troubleshooted live on his iPhone using screenshots — which leads to the rule of the day…
A quick, fun win to show what's possible visually.
Used Claude to begin shaping the bigger picture — loading Jesse's own documents in via the Drive connection so it worked from his real context.
About four and a half hours in, Jesse was confident and ready to build. We moved into Claude Code to create his first real tool.
The first code project kicked off in GitHub at 3:03pm. By 5:30pm his very own tool — a lead enquiry form, aimed squarely at his number-one need of qualifying inbound leads — was built, deployed and running live, ready to use the very next morning.
The tool we built needed a proper little stack — all set up on the day:
The end-of-day whiteboard — everything we covered.
Jesse was supercharged. We hit a few first-time roadblocks in the setup — GitHub, Vercel, Supabase and Resend (the tool we chose needed all four) — but those are one-off hurdles he will not face again.
"I felt really good about the day and learnt SOOOO much — I didn't think we would cover off on so many things in the one day together. I was absolutely stoked to have my first functional and valuable tool to go away and implement ASAP. Mark was great; he didn't end the day until we had it ready, and was even willing to help me tie off a few more items the following day."
Mark with Jesse at the end of Day One.
"Yes, definitely! This is perfect for anyone like me who is so busy. Spending a day out of my business learning the theory of this would have frustrated me even more — I'd have to go back and then find time in my business to implement it."
Not everything belongs in one day, so we deliberately "parked" the bigger projects for another time:
Here is the real shift, though: these are no longer daunting unknowns sitting on a someday list. Jesse now has the tools, the foundations and — most importantly — the confidence to power through them himself, with AI working alongside him every step of the way.
Take the free AI assessment — a few quick questions, and I'll come back to you personally.
Take the Free AI Assessment →