A Day 1 CEO Kit field guide
How to Turn a Messy Client Intake Process Into an Automation-Ready Workflow
By Charley Ellis
A client emails you. Someone else sends a message. You jot down a deadline, then spend ten minutes hunting for it later. If that sounds familiar, start here: give those inquiries a clear path before you ask a tool to handle them. You can map it in a plain note. No fancy software needed.
Before and after: give every inquiry a next step
- Before: the inbox does all the remembering
- Details sit in email threads, messages, and sticky notes. You ask the same questions twice, rewrite the same replies, and rely on memory to know who is waiting. A helper cannot tell whether an inquiry is ready, missing details, or already answered.
- After: one record, one owner, one clear status
- Each inquiry lands in a shared intake list with the details you need. Simple rules flag missing information and prepare the next action. A named person reviews the response before it goes out. You can see what is waiting and recover if a step fails.
That is what automation-ready means here: someone else could follow your instructions without guessing. It does not mean every step needs AI. Capturing a form or assigning a status may only need a simple rule. AI might help draft a summary of a longer inquiry, with a person checking it against the original.
Your six-step client intake checklist
Grab one recent inquiry and follow it from arrival to the first useful reply. Copy these six prompts into a note and adjust the example answers to match how your business works.
1. Trigger
Choose one event that starts intake: a new inquiry form arrives, for example. Decide how email or phone inquiries reach the same starting point so they do not disappear into a second queue.
Write something like: Start when a new inquiry is recorded in the intake list. For phone or email inquiries, I add a record there myself.
2. Information captured
List what you need to decide the next step, and mark what is required. Start with name, reply email, requested service, a short description, and preferred timing. Ask only for details you actually need; passwords and payment details do not belong in an intake note.
Write something like: Name, email, service, and project description are required. Timing is optional. Missing required details mean a follow-up, not a guessed answer.
3. Repeated decisions
Write down the choices you make every time. Is this a service you offer? Is enough information present? Is it a repeat inquiry? Give each clear rule a next step, and leave judgment calls with a named person.
Write something like: If details are missing, draft a question. If the request fits our service list, mark it ready for review. If fit is unclear, ask the owner.
4. Handoff
Say where the intake record goes, who owns the next action, and what they receive. One shared list or board is enough. Include the original inquiry, a short summary, status, next action, and a review date.
Write something like: Save the inquiry and draft reply in the intake board. Assign the owner and mark it Awaiting review. The owner checks that queue each business day.
5. Human review
Choose who checks the result before anything reaches the client. Compare the summary with the original, check names and dates, and confirm service fit and availability. A draft should never promise a price, scope, or booking that nobody approved.
Write something like: The owner reviews and edits the reply before sending it, then records the next action. Quotes and bookings stay with the owner.
6. Failure cases
Plan for missing fields, duplicate inquiries, unclear requests, and a tool that stops working. Name where problems are flagged and who picks them up. Make it possible to finish by hand without sending the same reply twice.
Write something like: Mark incomplete or failed records Needs attention and notify the owner. Check for an existing inquiry before creating another. If the tool fails, use the original inquiry and update the same record manually.
Want a reusable way to capture the whole process? The workflow-mapping guide helps you turn these answers into a clear handoff.
A small-business example: a two-person web design studio
Imagine Maya runs a web design studio with one part-time assistant. New inquiries come through email and a website form. Maya keeps asking for the current website link and desired launch date because those details rarely arrive together.
Her new starting point is one intake board. The form records the client's name, email, requested service, and project description, with optional fields for their website and target date. Her assistant adds email inquiries to that same board and keeps the original message attached. Each inquiry gets a record ID so a retry can update the existing record instead of creating another.
A website redesign request with enough detail becomes Awaiting review. A request missing the project description becomes Needs information, with a draft question. Requests outside the studio's service list go to Maya for a decision. She checks the queue each business day, reviews the original message and draft, and sends the reply herself. Nobody promises a launch date until she checks capacity.
For example, a bakery asks for a redesign “before our opening” but gives no date. The draft asks for the opening date and current site link; it does not invent a deadline or offer a quote. If the form-to-board connection fails, the assistant checks the original form submissions, looks for an existing record, and adds or updates it by hand. Maya checks whether a reply was already sent before sending another.
This is a planning example, not a measured result. The first useful improvement is that Maya and her assistant can both see what happens next. They can automate a small piece once that path works by hand.