You know AI could help. You don't know where. I work that out with you, set up the right tools, and build the ones that don't exist. Costs shown up front. You own everything. Support whenever you need it.
What I’d set up and build for a business like yours
Examples and case studies. Much of this is showing you tools you haven't tried, and what the ones you already pay for can do once AI is connected to them: meeting notes that file themselves, a CRM that fills itself in, a question about last week answered in Telegram. Each one is scoped and priced on the call. The case studies are already built.
ExampleTelegram · Shopify · Xero · Gmail
Ask your business a question in Telegram
For
Any owner who wants the answer without opening five tabs.
What it does
A chat line to your own business. Ask "how did last week go?", "who owes us money?", "what did we agree with Sarah?" It reads your store, your accounts, your email and your notes, answers in a sentence with the figure in it, and if you say "chase them" it drafts the emails for you to send. It remembers what you asked, so next week it knows what you care about.
Your part
It answers on its own. Anything it drafts waits for your yes.
Example · Scoped and priced on the call.
Telegram · Shopify · Xero · GmailExample
how did last week go?
Sales £4,120, up 6%. Two invoices overdue, £1,850.
chase them
Two nudges drafted, in your voice. Send?
It answers on its own. Anything it drafts waits for your yes. · Illustrative
Pick a card. 1 / 16
What we do
First we work out where AI helps. Then we set it up and build what’s missing. Most of the value is in the first two steps.
01
Understand
A half-day workshop, or a walk through your business on a call: what AI can and can't do for you, the tools you haven't heard of, what the ones you already pay for can do once AI is connected, and how to prompt them for your work.
A shortlist, a cost per item, and what to do first.
02
Set up and integrate
ChatGPT, Claude or Gemini, whichever you already pay for, set up properly and connected to Shopify, your CRM, Gmail, Slack, your accounts. Plus the tools you haven't met: Granola or Quill for meeting notes, Fastlane for short videos made, scheduled and posted. Training for the team, and your Playbook: the repeatable tasks written down once, so they run the same way every time.
You leave with your Playbook: how you work, the jobs written down, the rules it works within. Every correction you make goes in, so it is constantly learning and improving.
03
Build
When nothing off the shelf does it: a bespoke service (an agent) that runs the job, or a small internal tool built the same way, a dashboard, a stock view, a booking form, a website. Weeks, not months.
Working in about two weeks, on your real data. Nothing it drafts goes out until you approve it.
04
Run
Every build comes with its monthly running cost shown before we start, handover notes you can follow, and 30 days of support while it beds in.
You own the code. No platform fee, no lock-in.
Or tell me about your annoying manual process. If it repeats and has a clear input and output, it can probably run itself. Tell me about it
Who this is for
For people who run a small business and want to get more done without taking on more staff.
A good fit if
You know AI and better tools could help, but nobody has shown you where, and there's no time to work out which ones actually matter for your business.
You've used ChatGPT and got something out of it, but it's still a tab you open, not something the business runs on. You want it built in, and you want to be the one who knows how.
You're still the one doing the emails, the chasing, and the reports nobody has time to pull together.
Something in the business repeats every week, and you'd rather it ran itself.
Probably not if
You want a chatbot on your website. That's a different product and there are cheaper ways to get one.
You want a strategy document. I build things, then show you what they cost.
You need enterprise procurement, SLAs and an account manager.
How it works
A free call, a half-day workshop, then it’s yours to run.
I
A 30-minute call
You describe the business: what you sell, how the work flows, what repeats, what takes the time. I show you where AI can already do more for it than you'd expect: the jobs it can take off you, the ones it can do faster and better, and the value it can add that you didn't know was there. And roughly what that costs.
Free. Thirty minutes, nothing to prepare.
II
A half-day workshop, on your real work
In your office or on a call. We write down how you work, set up ChatGPT or Claude properly, connect them to your email, calendar, notes and the tools you already pay for, and run your first jobs together.
You leave with your Playbook, in your own accounts.
III
Yours to run
You and your team run it day to day. When a job should run by itself, I build the service that does it and hand it over with notes you can follow. Support whenever you need it, and most people need very little.
It asks before it acts: it drafts, you approve.
When a job should run by itself
Built for real businesses. Running today.
Most businesses get what they need from the workshop. These are the jobs that were worth building a service for. Each runs on a schedule, on a known monthly cost, and asks a person before it acts. The status is real: if one is paused or not built yet, it says so.
6 live, on a schedule1 in buildEvery one asks before it acts
1 / 7
Live
Four sweeps a day
Alert triage
Groups the error alerts, investigates each group against the logs and the code, and posts a diagnosis. Nothing is filed until someone approves it.
Runs
Four sweeps a day, on a schedule.
Reads
The alerts channel, then the logs and the code for each cluster.
Guardrail
Proposed tickets wait for approval. If nobody approves one, it is dropped.
For
A SaaS startup, live production alerts.
Discord · GitHub · Claude
Live
07:00 daily
Social post drafter and scheduler
The day's posts and replies drafted and queued for the company account. A separate, approved step is the only thing that ever posts, each at its time.
Runs
07:00 daily for the posts, always-on for replies.
Writes
The day's posts and replies, in the company voice.
Guardrail
A separate poster is the only process allowed to write to X, and every post carries an explicit approval.
For
A SaaS startup's company account.
X · Claude
Live
Always on
Ticket intake
Watches the support channel, turns each real problem into a ticket with the details filled in, and skips the chatter.
Runs
Always on.
Watches
The support channel, one thread per report.
Guardrail
Only an approved list of actions. A reaction shows the status of each.
For
A SaaS startup, support channel.
Discord · GitHub · Claude
Live
Weekly
Meeting notes and a weekly team update
Quill records and writes up every call. Once a week a small service reads the notes, pulls out the decisions and action points, and sends the team one update.
Runs
Once a week, after the week's calls.
Reads
The notes Quill wrote, one per call.
Guardrail
Read-only. It writes one update to the team and nothing else.
For
A SaaS startup.
Quill · Claude
Live
Mondays at 09:00
Your industry's YouTube, read and sent to Telegram
Pulls founder interviews from YouTube, writes a note per episode on what worked and the tools used, and builds a weekly digest. Next: the digest lands in Telegram, and you can ask for more.
Runs
Mondays at 09:00, unattended, on a schedule.
So far
26 founder interviews read and written up, one note each.
Next
The digest sent to Telegram, with "more on that" and "save it" replies. In build, November 2026.
Guardrail
Read-only. It writes notes, a digest and messages to you, nothing else.
YouTube · Telegram · Claude Code
Live
Set up, in use
Short videos made, scheduled and posted
Granola and Fastlane set up for an online store: meeting notes taken for them, and short videos made from products and trending clips, scheduled and posted.
Status
Set up and in use at an online store.
Does
Short videos made, scheduled and posted to TikTok, Reels and Shorts.
Guardrail
The owner picks which videos go out. Nothing posts without a yes.
Saves
The hours that went on making, scheduling and posting content.
Fastlane · Granola
In build
Weekly, in build
Competitor watch
Reads the competitors' sites, changelogs and pricing every week, reports what shipped and what it means, and raises a ticket for anything worth building. Tickets wait for approval.
Status
In build for a SaaS startup, September 2026.
Reads
Competitors' sites, changelogs and pricing pages, once a week.
Writes
A weekly report on what shipped and what it means, and a ticket per thing worth building.
Guardrail
Read-only on the web. Every ticket waits for approval, and unapproved ones are dropped.
Competitor sites · GitHub · Claude
Getting the most out of ChatGPT or Claude
The difference isn't the tool. It's the context, structure and rules around it.
Most people type what they want into ChatGPT, get something nearly right, and type it all again tomorrow. It only knows what is in front of it. So give it context, structure and rules: a folder of plain-English files it reads every time, and every correction goes back into them, so you only ever fix a thing once.
01
How we work
The brief on your business: what you sell, to whom, how you sound, the words you use. Read first, every time.
02
Jobs
Each repeatable task as a procedure: inputs, outputs, and the checks it runs before you see the result.
03
Rules
The guardrails. What needs sign-off, what it never says, what it never touches, when it must ask first.
04
Issues
Every failure logged as asked, got, expected. Fixed in the job, with a check so it cannot come back.
05
Decisions
What was chosen and why, dated, so nobody re-argues it.
Your Playbook, as a folder
your-playbook/
how-we-workHow we work
jobs/Jobs
weekly-report
quote-reply
newsletter
rulesRules
issuesIssues
decisionsDecisions
This is the Playbook. It is what you leave the workshop with, set up in ChatGPT or Claude, in your own account.
How to work with it, day to day
The files are half of it. The other half is method: how good software teams work with AI, translated for a business that has never written a line of code.
01
Have it interview you first
Before the brief, it asks the awkward questions: what happens when the data is missing, who signs off, what must never happen. Five minutes of questions saves an hour of fixing.
02
Define done, then check it
Every job carries a short list of checks it runs before you see the result: the figures add up, every row is filled, nothing goes to the wrong person. A job with no checks isn't finished.
03
Examples, not adjectives
Three real emails you were happy with beat 'friendly but professional'. It copies what it can see.
04
Log problems like faults
What you asked, what came out, what you expected, in a list it can read. Fixes go into the job, and the list shows you what keeps going wrong.
05
Small steps, tight loops
The faster you can check, the faster it improves. One step, looked at, then the next. Big asks get big mistakes.
06
A note at the end
What changed, what was decided, what to do next time, written where it will read it tomorrow. That is how it gets better week on week.
Habits I run every day and coach my clients on.
Who's building it
I'm Rory
Software engineer, now AI engineer · UK
I'm a software engineer. For eight years I've built and run the things businesses depend on day to day, from the screens people use to the systems behind them.
Then I built a SaaS startup, end to end. That's where I worked out how to make AI genuinely work for a business: not a chatbot in a tab, but a proper system. Everything written down, every job with its own checks, every service asking a person before it acts. It runs the routine work of that company every day, and it gets better every week, because every correction goes back in.
AI is moving fast. New tools come out every week, the good ones genuinely save hours, win sales and help a small team do more, and keeping up with it all is a job in itself. That's the hat I wear so you don't have to. I follow what's new, try it on real work, and know what these models can do this month and what to keep them away from.
So when I look at your business I'm not selling AI. I've built a company that runs on it. What I bring is the system behind it: the structure, the checks and the habits that turn a clever tool into something your business can rely on, and that keeps getting better the longer you use it.
Built a SaaS startup
Developer, 8 years
UK · remote
Pricing
Three ways to work with me, each with the cost up front.
Most people start with the workshop. Fixed prices, agreed before we start, and every build comes with its running cost shown up front.
01
Start here
Workshop
Where most people start
Half day
In person or on a call
£750
Full day
The half day, plus a first service built live
£1,200
Hands-on, on your real work. You leave with your Playbook set up in ChatGPT or Claude and your first jobs running your way. The full day also builds your first bespoke service with you in the room.
Built around your own tasks, in your own accounts
Your Playbook: how you work, your first three jobs written down, and the rules it works within
For after a workshop or a build, when you want it to stick and keep growing. I stay on, keep what we built running, and keep finding the next hour to give back. The price depends on how much of my time you need each month: how many sessions we do, and how many services I keep running for you.
Two working sessions a month, on your real work
Your services kept running: monitoring, fixes, small changes
New tasks added to your Playbook as they come up
Priority line between sessions, and new starters trained
Prices exclude VAT. Running costs are the real monthly bills for the AI tools and hosting, shown up front.
Questions
Questions people ask before they book a call.
I don't know what I need. Is that OK?
That's most people, and that's what the call and the workshop are for. Describe the business and the annoying bits; I'll tell you what's worth doing first, and what it costs.
I already use ChatGPT or Claude. What would be different?
Using it for the odd email is a good start, and most businesses stop there. It's almost never the model that's the problem. It's that nothing is written down, so every conversation starts from zero and every correction is lost by tomorrow. The workshop sets up your Playbook: who you are, how each job is done, what it must never do, and connects it to your inbox, calendar and the tools you already pay for. After that, it reads the Playbook every time, and when you correct it, the fix stays.
Do I need to be technical?
No. I do the connecting and the setting up. You learn where the buttons are, what to glance at each week, and how to change the instructions when the business changes.
What does one of these actually cost to run?
Typically £10–30 a month for the AI tools and hosting behind it, and sometimes nothing: a lot of the best tools are free and open source, and where a free one does the job, that's the one I'll use. I'll give you the number before we start, and the handover notes show you where to check it.
What if it makes a mistake?
Everything I build asks before it acts. It drafts, you approve. Nothing gets sent, posted or filed without a person saying yes, and if nobody says yes, it's dropped. Silence means no.
Do I need a developer to keep it running?
No. The instructions are plain text files you can edit yourself, and the handover notes cover the routine things. You get 30 days of support after handover, and I am a message away after that.
Do you do Shopify?
Yes. I've rebuilt several stores and built the reporting behind them, so store digests, listing writers and customer email triage are the builds I know best.
Which tools would you actually set up?
Two kinds. Tools you may not have met: Granola, or Quill which is free, to take your meeting notes for you; Fastlane, which makes short videos for a store and posts them; Claude or ChatGPT set up for your business with your Playbook, rather than a blank tab. And the tools you already pay for, connected to AI so they do more: your CRM kept up to date from your calls and emails, your meeting notes filed where the team can find them, your accounts package drafting the invoice chasers. Most businesses I meet are using a fraction of what their tools can already do.
Do you build websites and apps too?
Yes, when they're the right answer. With AI in the loop, a dashboard, an internal app or a website rebuild takes days rather than months, so it's often the quickest way to give a business the tool it's missing. I don't take on big software projects, and I'll say so on the call if that's what you need.
Can it work with my CRM?
Yes. HubSpot, Pipedrive, Zoho, Salesforce and most of the others let tools like this read and write to them, so notes, deal stages and follow-ups can be kept up to date without anyone typing them in. If your CRM is a spreadsheet, that works too.
Not sure where to start? That's what the call is for.
Book a 30-minute call. I'll show you where AI can already do more for your business, what it costs, and what to do first.