Using AI to turn your existing service process into a…

You know that feeling when a new client emails you the same three questions you answered for the last client — and the one before that — and you're typing the same reply for the fifteenth time wondering if there's a better way? This post shows you how to explain your process to clients before a project starts, using AI to turn your existing workflow into a clean, client-facing document that answers those questions before they're even asked. And if writing about your own work makes you want to stare at a blank page forever, don't worry — there's a trick for that too.

What you need before you start

ChatGPT{:target="_blank"} or Claude{:target="_blank"} — both are AI tools you type questions and instructions into, like texting a very capable assistant. ChatGPT (from OpenAI) and Claude (from Anthropic) both have free tiers that work fine for this task. If you want more speed and longer documents, paid plans run around $20/month for each.

Google Docs{:target="_blank"} or Notion{:target="_blank"} — somewhere to paste and polish the draft once it's ready. Both are free.

Time required: About 45 minutes the first time — maybe 20 minutes of that is just you thinking through your process. It gets faster.

Skill level: If you can write an email, you can do this. Seriously.

Why Clients Keep Asking the Same Questions (and What It's Costing You)

Before we build anything, let's name the problem clearly.

Most service businesses — designers, consultants, coaches, contractors, bookkeepers, photographers — field the same 5 to 10 questions at the start of every single project. How long will this take? What do you need from me? When will I see a draft? How many revisions do I get? When's the invoice due?

These aren't bad questions. They're anxious questions. A new client is handing you money and trust at the same time, and they don't know how things work yet. The questions aren't about you specifically — they're about uncertainty in general.

Here's the part that should make you put down your coffee: the average small service business owner spends an estimated 3 to 5 hours per new client just answering pre-project clarification emails and calls. Multiply that by 10 or 15 clients a year and you've got a part-time job made entirely of email you didn't need to write.

A well-built client onboarding explainer doesn't eliminate the relationship. It starts it better.

What a Client Onboarding Explainer Actually Is — and What It Isn't

A client explainer is not your contract. It's not your proposal. It's not a scope of work.

Think of it like the orientation packet you got on your first day at a new job — before the actual work started. It tells you how things work around here, what to expect this week, who does what, and where to go if you have a question. It reduces anxiety. It creates a shared language.

The best ones follow a simple structure that mirrors how clients actually think: What am I getting? How does it work? When does it happen? What do you need from me? That's it. Four questions, plain answers, written for the person on the other side — not for you.

The most common mistake people make writing these? They write it from their own perspective. They explain the process in the order it makes sense to them, not in the order it matters to the client. AI is genuinely useful here, because you can ask it to flip the perspective.

How to Gather Your Raw Material in 10 Minutes

Don't open a blank document and try to write your process from scratch. That's the hard way.

Instead, do a brain dump. Here's how:

Open a notes app, Google Doc, or even your email drafts.
Set a 10-minute timer and write down every question a client has ever asked you before a project started. Don't organize it. Don't polish it. Just list them.
Add a rough description of how your project actually runs — phases, steps, handoffs, whatever you'd say out loud if someone asked "so what happens after I pay you?"
Jot down anything your clients need to send or do before you can start — files, logins, decisions, approvals.
Note your preferences: how you like to communicate, how quickly you reply, what happens if a deadline slips.

That messy document? That's your raw material. The AI doesn't need it to be pretty. It needs it to be real.

How to Explain Your Process to Clients: The Exact Prompt Sequence

Now, open ChatGPT or Claude and paste this prompt first. This is the "interview yourself" technique — instead of asking AI to write from nothing, you're letting it ask you the right questions and then build from your answers.

This prompt works because it treats the AI like a smart colleague who needs to understand your business before they write anything about it.

I run a [type of business] and I want to create a one-page client onboarding explainer that I send to every new client before a project starts. The goal is to reduce the back-and-forth emails by answering their most common questions upfront. Before you write anything, please ask me 8–10 questions about my process, my clients, my typical project timeline, what I need from clients, and my preferred communication style. Ask them one at a time and wait for my answer before continuing.

Answer each question honestly, in plain language, the same way you'd explain it to a friend. Don't overthink it.

Once you've answered all the questions, use this follow-up prompt:

Now use everything I've told you to write a friendly, clear client onboarding explainer. Structure it using these four sections: "What you're getting," "How the process works," "What to expect and when," and "What I need from you." Write it for the client — not for me. Use a warm, professional tone. Avoid jargon. Keep it to one page if possible.

You'll have a first draft in under five minutes. It won't be perfect — it'll need your voice and a few tweaks — but it'll be 80% of the way there on the first pass.

If the tone feels too stiff or too casual, add one more prompt:

Please rewrite this in a [friendlier / more professional] tone. My clients are [describe them briefly — e.g., small restaurant owners who are not very technical].

What a Finished Explainer Looks Like

Here's a quick before-and-after based on the kind of raw notes a freelance web designer might have:

Before (raw brain dump): "Projects take 4–6 weeks. I need logo files and brand guidelines. Clients get 2 rounds of revisions. Payment is 50% upfront. I check email Mon–Fri."

After (AI-assisted explainer excerpt):

How the process works After you send your deposit, I'll reach out within one business day to confirm your start date and send a short checklist of files I'll need from you (usually your logo and any brand guidelines you have). From there, most projects move through three phases: discovery, design, and revisions — usually over four to six weeks total.

What to expect and when You'll see your first design concepts at the end of week two. From there, you get two rounds of revisions to get everything just right. I'm available Monday to Friday and reply to emails within 24 hours during the workweek.

Same information. Completely different experience for the client reading it.

Where to Put It and When to Send It

Timing matters as much as content. Send the explainer after someone says yes but before the kick-off call. That's the window where anxiety is highest and questions multiply fastest.

Drop it in a Google Doc or a Notion page and share the link in your confirmation email. Keep the email short:

"Excited to work together! Before our call, here's a quick overview of how I work — it'll answer most of the questions that usually come up. See you [date/time]."

That's it. You're not asking them to sign anything or study anything. You're just giving them a map before the trip starts. Service businesses that do this consistently report that their kick-off calls run shorter and stay focused on strategy instead of logistics. Worth it.

How to Update It as Your Process Changes

Your process will evolve. Prices change. Tools change. You stop offering certain things or add new ones.

Don't rewrite from scratch. Keep your original brain dump notes in a document alongside the explainer. When something changes, update the notes and paste both into a new AI session with this prompt:

Here is my original process explainer [paste it] and here are my updated process notes [paste them]. Please update the explainer to reflect the changes in my notes. Keep the same tone and structure.

Done in five minutes. No starting over.

What to Do Next

The natural next step is getting this document into a workflow — so it goes out automatically every time someone becomes a client, without you having to remember to send it. If you want to take this further, Owen wrote a walkthrough on automating your client welcome sequence without any coding.

FAQ

Does this replace my contract? No — and it shouldn't try to. The explainer is a relationship document, not a legal one. It reduces anxiety and sets expectations. Your contract handles scope, payment terms, and what happens if things go sideways. You need both, and they serve completely different purposes.

What if I don't have a very defined process yet? Good news — this exercise will help you build one. The brain dump step forces you to articulate how projects actually run, even if you've never written it down before. A lot of business owners come out of this step with a clearer sense of their own workflow, which is useful beyond the document itself.

How do I reduce client questions before a project starts? The fastest way is to send a short onboarding explainer immediately after a client says yes — before the kick-off call. It doesn't need to be long. One page covering what they're getting, how the process works, what happens when, and what you need from them will eliminate most of the back-and-forth before it starts.

Can I use the same explainer for every client? Mostly yes, with small tweaks. The core structure stays the same. You might swap out a detail or two for clients with different project types, but the AI makes that quick — just paste the base doc and say "adjust this for a client who is [different situation]."

What if I try this and the draft sounds nothing like me? That's a normal first pass. Add one prompt: "This sounds too formal/too casual. Here are three sentences from an email I actually sent to a client: [paste them]. Please rewrite the explainer in that same voice." AI is excellent at matching a tone when you give it a real example to work from.

Do clients actually read these things? More than you'd expect — especially if you keep it short and send it at the right moment. Research from Wyzowl{:target="_blank"} found that 86% of people say they'd be more loyal to a business that invests in helping them understand the process. A one-page document that took you an hour to build is a low-effort way to make a good first impression that lasts.

Using AI to turn your existing service process into a simple client-facing explainer that reduces questions before they start