One workflow, off your plate. And still work you’d put your name to.
You already know some of what you do could go to AI tomorrow, and some of it never should. Telling the two apart is the hard part, and in a business of one, there’s nobody to check your thinking with.
The Read is a one-to-one look at the whole of your practice, for consultants, advisers, coaches and trainers whose clients pay for their expertise. We narrow down which workflows are worth changing, you choose the one to start with, and I build it around the line between what AI can carry and what stays with you.
So the next time it comes round, less of it lands on you.
You bring the week you actually have, I tell you what I see in it, and the honest next step follows, even if that is nothing yet.
Let’s look at your week togetherIt stops in the same places every week.
Your week has a shape to it. Chasing the work, writing the proposals, the client delivery itself, and the follow-up that always seems to land at nine in the evening.
You’ve put AI to some of it already.
It gets close every time, and stops in the same two places.
It drafts the proposal and misses why this client would say yes. It cuts the report down and sounds equally sure about the line that’s wrong.
So now you check all of it, including the parts that were fine.
That checking is your judgement doing its job. It has nowhere to sit yet, so it costs you an evening instead of giving you one back.
An evening spent checking is one that doesn’t go to a client, a proposal, or work you’d actually charge for.
The problem isn’t that AI can’t do enough of the work.
It’s that nobody has decided where your judgement comes in, so it comes in everywhere.
We give your work a shape AI can follow.
In practice, it’s a workflow built once around the way you actually work. AI runs the parts you’ve handed it, and wherever a decision is yours, it stops and waits for you. Your judgement finally has somewhere to sit, and the evening goes back to being yours.
The question isn’t “What could AI automate?”
A long list of things AI could do in your practice is easy to make.
And the loudest job in your week isn’t always the one to start with.
The harder question is:
Which one is worth changing?
A monthly client report might take three hours and leave you exhausted.
The first reply to a new enquiry might take twenty minutes.
But the twenty-minute job may matter more to the business than the three-hour one.
So for every workflow I weigh two things.
What you get back.
The hours it takes, how often you’re spending them, the wear it leaves, and what having less of it on your plate would change.
And what it costs if AI gets it wrong.
Your name on the work, how far a bad output travels, and how sensitive the material is.
The point isn’t to automate as much as possible. It’s to find the place where AI can take real weight off you without taking the part your clients pay you for.
You don’t have to arrive knowing what should be automated.
About an hour of your work up front. Then I do the reading, comparing and building; we use the conversations for the decisions only you can make. From the intake to the set-up session, it takes about five to six weeks.
You show me the work.
The intake form covers six areas of your practice: what happens in each, how often, and how much of your month it takes. Sixty to seventy-five minutes, and you can do it in pieces.
That hour is why the first call isn’t me gathering facts.
We spar over it.
The Calibration Call, about an hour. I come having read everything, with questions of my own and workflows on your list I’d challenge.
Push back where you see it differently. Most of the useful conversations start there.
I take the whole thing apart.
About a week. I work through all your workflows and set them against each other. What would change if each one ran better? What would it cost if AI got it wrong?
Then I go back over my first read before I trust it.
You see where I’d start.
The decision call, ninety minutes. You get the whole of your practice on one page, ranked, with the reasoning next to each. Out of that comes a shortlist, and I tell you which one I’d start with and why. You’re welcome to disagree, and then you choose, because it’s your practice.
I build the one you chose.
Two to three weeks. I’ll have questions as the detail comes up, and I test it on your work before it reaches you, written out and ready to run.
I build it in my own account, in Claude or ChatGPT, whichever you already work in. Your material stays confidential throughout.
Real use can still show us things a test can’t, which is why the thirty days of email support start at the set-up session, when the workflow reaches you.
We put it into your tools together.
The set-up session, ninety minutes. You share your screen and do the clicking in your own account, and I guide you through every step. I never need your login.
Before we finish, you run one of the jobs it was built for, while I’m still there. You bring a copy of the material with your clients’ names replaced, so nothing confidential ends up in the recording.
This is where I hand the workflow over, and your thirty days of email support begin.
Then we look at what happened.
The follow-up call closes the thirty days: what worked, what didn’t, what changed once the workflow met a real week, and where you go from here.
Founding clients get one more call at ninety days.
Something tangible: a workflow you can actually use.
Your blueprint.
The workflows that come round every week or month and carry real weight in your practice, ranked, with the reasoning behind each.
So you stop wondering where AI belongs. You can see where it could give you time back, and what isn’t worth handing over at all.
Your tested build.
The workflow itself, tested on your own material, and running in your own tools by the end of the set-up session.
So what reaches you is something already built around your work, rather than another AI experiment to find time for.
Your recipe.
The written system behind your workflow: what you set up once, what you run each time, and the check before anything leaves your desk. It also holds the decisions that stay yours, what makes your writing sound like you, and what can safely go into the tool.
With it comes a short how-to: how it runs, and what to check on a day it stops behaving.
So the next time the work comes round, you don’t decide it all again. You decided once.
Your first thirty days, with me in them.
They ask for your attention rather than your evenings.
A short plan that ties the workflow to jobs already in your diary, and me on email from the set-up session.
Real work finds the things a test never does: a step that misfires, an instruction that needs sharpening, a place where the workflow and your week don’t quite agree. Send it over, and if it’s in the workflow we built, I adjust it.
I also come to ask how you’re getting on, because a new way of working is often the first thing to disappear in a busy week.
Then it’s yours.
Nothing keeps running through me, and there’s no monthly retainer. The workflow is written down so you can see what is happening and why. If a tool changes or its price moves, you still have the steps, the reasoning and the handover points rather than having to work the whole thing out again.
The tool-specific part may need adapting. The workflow itself doesn’t disappear with it.
Every call is recorded, for you.
It runs the steps. It doesn’t decide them.
You’ll have met the word agentic. This is the bit I care about more than the word.
An agentic workflow can run a sequence of steps for you.
The question is:
Who decided what those steps are?
Left to itself, AI works that out as it goes. You can ask it to pause where you’d want it to, and mostly it will. With your name on the work, mostly is the problem.
So in The Read, we decide the steps: what goes in, what AI does with it, what it isn’t allowed to decide, and the point where the work comes back to you.
So the workflow might read the material, sort it, draft it, compare it, or prepare the next step. But the judgement that belongs to you stays yours.
AI runs the steps. You keep the decisions.
AI doesn’t carry your name. You do.
Most of this field can show you what AI can do. Rather fewer have had to stand behind the result in a room where it cost real money.
Thirty years of mine went on exactly that, twenty of them negotiating and defending contracts for international groups across aerospace, defence and security, transport, commodity and biopharma. Work where the value isn’t just in producing something.
It’s in knowing what to notice and what to question. What you can stand behind when your name is on the page. AI hasn’t changed that. It has just made sounding certain much easier.
I got that wrong myself at the start, and handed AI a piece of work that was mine to keep. So The Read starts with what this work is worth and where your judgement belongs inside it, rather than with what we could automate.
You don’t need to become an AI engineer.
But you need to know where AI earns its place in the work you already do.
More about me →You’re good at the work.
It’s the repeated parts that
are getting expensive.
You’ve been at this for years, as a consultant, adviser, coach or trainer.
A business still finding its feet is too early for this one.The same work keeps coming round. Month after month, and enough of it that there’s a pattern to find.
Clients come to you for your expertise or judgement. They’re paying for what you can see, rather than for how much you produce.
You can already name the parts of the week you’d happily have less of.
The work matters. It just doesn’t need this much of you.You’ve used Claude or ChatGPT, and that’s enough. You know they can be useful, and you still check everything that matters.
You don’t mind me seeing it untidy. The parts you’d tidy first are usually the ones worth reading.
And you’d rather have one workflow that earns its place than ten clever things you tried once.
If you’re wondering whether The Read fits your practice, bring me the week you actually have. We’ll look at it together.
Free. Forty-five minutes. No obligation.
- a straight read on what I see
- a fair idea of whether The Read can help
- whether the two of us would work well together
Then a short written note from me a day or two later, with the main findings.
Eight practices, and the method takes shape on yours.
I’m taking eight women through The Read at the founding price, one at a time.
What you get is a workflow made for your practice and nobody else’s, because being first means there’s no ready-made version waiting to be adapted.
What I get is eight real runs through The Read, and the chance to see what holds once each one meets a real quarter. Your work helps shape the method before I take it further.
The first thirty, and the full ninety
The follow-up call closes your first thirty days: what real use has shown us, what needed adjusting, and your next best step for putting AI to work for you.
The ninety-day call gives us a second look after a real quarter: did the workflow survive the busy month, the awkward client, the job that turned out nothing like the others?
Either way, if the workflow has stopped doing what we built it to do, I take another look at the build and adjust it where needed.
At the end I’d like a named testimonial from you. Saying no costs you nothing, and the price is the same either way.
The founding price is EUR 627.
After the eighth place,
it’s EUR 1,197.
It’s the price of being one of the first eight. What you’re paying for is a result: one piece of repeated work that asks less of you, set up and running in your own tools.
At the decision call, I put a number on it: roughly how many hours a month that workflow should give back, worked out from your own intake. So you know what it’s worth to you before I build it.
That work comes round every week or month of your year. Each time it does, those hours should come back to you.
You also get the rest of your map: all the workflows worth doing, the ones to leave well alone, and the reason for each.
The Read is a business service, bought for your own practice. Prices are net. VAT where it applies.
If paying in one go doesn’t suit you, we can talk about instalments when we speak.
You don’t buy The Read from this page. We talk first, and nothing is decided in it.
The conversation is free. The Read is the work that follows it.
When we look at my week together, is that already The Read?
No. That’s the conversation: forty-five minutes, free and online, and we spend it on your week rather than starting the work.
We’ll talk about what’s in that week, what you’ve already tried with AI, and where you’re getting stuck. You’ll leave knowing whether there’s a sensible next step and whether The Read fits, including if the answer is no.
Do I have to know which workflow I want?
No. You might have one in mind already, and you might even be right.
But I want to see the rest of your practice before you decide. That’s the point of The Read.
Couldn’t I work this out myself?
Probably. You know your practice better than anyone, and you’ve used AI enough to know where it helps and where it starts making more work.
The question is how much more of your own time you want to spend testing it.
The Read gives you a second pair of eyes across the whole practice, a way to weigh the options against each other, and one workflow built and tested rather than another thing to try when you get a quiet evening.
What if the workflow I pick turns out to be the wrong one?
Sometimes the workflow is right, but real use shows us something that needs adjusting. That’s what the thirty days of email support are for.
And sometimes you may realise you’d rather have chosen a different workflow altogether. If that happens, a different workflow would mean a new build, so we’d treat that as new, paid work. It comes with its own thirty days of support, and the workflow you first chose is still finished as agreed.
How does the set-up session work?
You share your screen and do the clicking in your own account, while I guide you through each step. We make the settings it needs, connect what it should reach, and get it running. I never sign in to your account.
Then you run one of the jobs it was built for, on a copy with your clients’ names replaced, so nothing confidential lands in the recording. You pick which job on the day.
Two working days before, I send you a short list of what to have ready: your login, access to any tool the workflow connects to, and that copy. Your thirty days of email support begin at the end of the session.
How does paying for it work?
You pay in full before we start, and then the intake form comes over to you.
It’s a straightforward invoice from me, paid by bank transfer. Prices are net, with VAT added where it applies.
If paying in full doesn’t suit you, tell me when we speak and we can talk about payment in instalments.
How much of my time does this really take?
Allow sixty to seventy-five minutes for the intake form.
Then there are three calls and the set-up session: an hour, ninety minutes, ninety minutes for the set-up, and a shorter call at the end. While the founding places last, there’s one more call at ninety days.
I’ll have a few questions for you while I’m building.
Afterwards, you have email support when something comes up in real use.
Do I need to be technical?
No.
In the set-up session, you do the clicking and I tell you where. Depending on what we’ve built, that means loading the workflow and making a few settings. I show you what applies to yours.
Can it run on its own?
Where the workflow suits it, yes. It can run on a schedule, check tools you’ve already connected, and tell you when something has changed.
What I don’t build is the separate automation layer that makes a workflow start instantly when something arrives.
Without that layer, the workflow checks at set intervals rather than being triggered the moment something happens. So there can be a gap between something changing and the workflow seeing it.
What about confidential client work?
Anything you share with me while I build the workflow is treated as confidential and handled under the data-protection obligations that apply to my work.
For the workflow itself, your confidentiality rule becomes part of the workflow: what can go into the AI tools you use, what counts as sensitive, and a check before you put confidential material in.
You remain responsible for deciding what client information you can put into those tools, and for meeting the GDPR, confidentiality and other requirements that apply to your practice. I don’t advise you on those requirements; I build your rules into the workflow, so there is a clear point to stop and check before sensitive material goes into a tool.
What if my tools change, or a price goes up?
The workflow is documented, so the part that matters stays readable whatever happens to the tools.
The tool-specific part may need adapting, with the workflow, instructions or settings changed to fit the new tool.
Prices are theirs to set, and I’ll tell you where that stands when we speak rather than promise you where it will stand next year.
What if I get to the decision call and I’m not sure?
Then you don’t decide on the spot.
If the one you came in sure about isn’t the one I’ve put first, say so. We can talk through why, or you can take it away and think.
You don’t have to agree with me because we’re on a call. You have three working days afterwards to confirm your choice by email. If you need more time, tell me.
Still wondering whether The Read
fits your practice?
Bring me a week of your actual work. We’ll look at it together.