The Half-Built Audit
Four half-built AI things. One page to decide what stays.
“I started with AI and it got away from me.”
Teacher by qualification and character. Builder by nature.

Better systems. More capable people. More room for human work.
I work with people and small organisations whose value comes from what they know. Sometimes that’s one person changing how they work. Sometimes it’s a whole team that has to change together.
I’m Rachel. I look at where your people are actually at, whether your systems work in real life and where the real value sits, then we build around that. And I care whether you can still use it when I’m not in the room.
Not sure what needs fixing first? That’s exactly what a Read is for.
In plain English
What I do
I help you work out what should change, then we build the useful version, with you or for you. AI working setups, workflows, interactive tools, learning experiences, websites. The method stays the same. The build fits you.
Who it’s for
Solo founders, coaches, course creators, membership owners, consultants, educators, professional services and small expertise-led teams. If your value comes from what you know, this is for you.
What changes
The repetitive work that doesn’t need you gets lighter, your people get more capable, and there’s more room for the work that does need a human: judgement, relationships, teaching, care.
Sound familiar?
Professional services owners
“We have ChatGPT. The staff need to use AI.”
They told the team to play with it. Nobody got the output they wanted, so everyone quietly stopped. Giving somebody access to ChatGPT isn’t adoption.
What “this worked” looks like: the team are using it and asking questions.
Bring me in →Experts and their communities
“You don’t need to keep up with AI. That’s my job.”
You need to know what it changes for yours. You know your field. I bring learning, change, systems and technology, and we turn your expertise into something that travels further.
Sometimes that’s a tool your members use. Sometimes it’s one you can charge for.
See the pathways →Working together
You don’t need to know which tool or package you need. You need to know where you’re stuck, and how much of the build you want to hold.
Work out what to fix first
“I’m not even sure what the right problem is yet.”
Buy the diagnosis before you buy the build.
Works out which mode fits
Start with a Read →Done with you
“I know what I want and I want to build capability while we make it.”
You drive. I guide. Build the thing. Build your capability at the same time.
We do
Build it with me →Done for you
“I know what I want and I want Rachel to make it.”
I build. You approve. I can build it for you without building a black box you can’t use without me.
I do, with a handover you can own
Hand it over →For teams, memberships and communities
“My team, members or community need to come with me.”
Don’t just give your people AI tools. Build their capability to use them well.
All three, across a team or community
Bring me in →Keep Me Close. Built the thing? Keep me in your corner while you use it. Ongoing access for questions, decisions and refinement.
How it works →What we might build
Context, voice, skills, recurring work and repeatable ways of working that make AI useful.
The repetitive process or admin job that keeps eating attention.
Calculators, self-assessments, scorecards, decision trees, quizzes and action-plan builders.
Courses, memberships, resources and onboarding designed around application.
What you know, turned into a repeatable resource, tool, programme or internal system.
Clearer, easier experiences from the customer’s side of the screen.
Landing pages, websites, resource hubs and bespoke tools.
Ways to capture and reuse your thinking without flattening your voice.
Got something weird? Good. Show me. Any of these can happen through Build It With Me or Hand It Over.
Free guides
We don’t have a knowledge problem.
Almost anything you want to know is a search away. Knowing it and changing how you work are two very different things. So all 12 guides are complete and free, and each one ends with one thing to try this week.
Four half-built AI things. One page to decide what stays.
“I started with AI and it got away from me.”
Adjectives don't make it sound like you. One file does.
“Everything it writes sounds like a press release.”
Downloads aren't leads. Build the version that asks back.
“People grab the download and never open it.”
How I look at a problem
Most tech problems aren’t just tech problems. Before anyone picks a tool, I want to know what’s actually happening.
People
Ready to change is one question. Willing to change is another. I read both before designing anything.
Systems
Systems are more than software. The system plus the habits of the people using it is what actually happens.
Expertise
Your judgement, your pattern recognition, the bit only you bring. We build around that. We don’t automate it away.
The system has to fit the people and create more room for the expertise.
Not this
Everyone gets ChatGPT, the team is told to play with it, and by next month nobody opens it.
This
The team are using it and asking questions, because they’re actually using it.
How I work
Every pathway runs on the same method. The project changes. The thinking doesn’t. And the capability moves across as we go: I do, we do, you do.
What should be different when we’re done? “Can we automate this?” isn’t the problem yet.
Who has to use this on Monday, what they already know, and what makes the change hard.
The smallest change that makes the biggest difference. Sometimes that’s removing a step, not automating it.
Do the thing while the support is still in the room.
It isn’t finished because it’s built. Can the people who need it use it, own it and keep using it when I’m not there?
I wondered if this would work, so I built it
This is a live build, the same kind that goes inside client courses and communities. Eight questions, and it tells you which digital asset moves your business most.

Why this comes from a teacher
Teaching was never just delivering information. It was working out where someone was starting from, what the next achievable step was, and why something wasn’t landing. I was an early adopter the whole way through, including helping colleagues through a learning management system change. The learners changed. The tools changed. The work underneath it didn’t.
Curious enough to try early. Experienced enough not to confuse new with better.
Booking, not buying?
A lot of my work starts after someone hears me speak. Booking for a conference, chamber, team day or community? A brand, or a podcast after a guest? Tell me which and I’ll ask the right questions.
You’ll get a straight answer either way, within a business day or two.
Before we add another tool, let’s work out what’s actually getting in the way.