One service first · Fictional worked example
Choose the service before choosing the follow-up process. Look at money left after direct delivery costs, team time, existing interest and capacity. Then agree which request path to examine and what should stay working. You do not have to know the best starting service before talking with us.
Choose one service before comparing the paths.
A service and a customer process are different choices. 'Exterior window cleaning' names the work the business sells. 'Website estimate request to accepted reviewer' names the part of customer follow-up we can examine.
For BusinessOS, start with one worthwhile service for one business and location. Look at what is left after the direct costs of doing the work, how much owner and team time it takes, the interest already reaching the business and capacity to deliver. Money after direct costs is not the same as full-business net profit.
A worthwhile service can still be a poor starting project if nobody can take the inquiries or the team cannot deliver more work. If the cost, demand or capacity facts are missing, record the question instead of adding an invented score.
Turn the chosen service into a small plan.
Fictional worked example: Mira and Lee at North Window Care decide to examine exterior window-cleaning inquiries. Assume they have reviewed the direct delivery costs, team time, existing requests and capacity and agreed that this service is worth a closer look. These are exercise assumptions, not measured business results.
They keep the existing website and their estimate preparation. The current problem is a request with no accepted first reviewer. The draft plan below gives that handoff a boundary. It is not a quote, a completed installation or a promise of more sales.
- Service: exterior window cleaning for the agreed business and location.
- Page: explain that service and make an estimate request clear. Choose one new hosted page or a limited existing-page improvement after checking access and practical workload.
- Existing interest: people already reaching the agreed page. Paid ads, new traffic and a full website rebuild are separate work.
- Start: an estimate request arrives. End of this review: Lee has accepted its first review and the next action is recorded.
- Customer message: confirm receipt without promising a price or an appointment.
- People: Lee checks the request; the authorized person confirms service scope, price and availability. The business makes the sale and delivers the work.
- Check-ins: choose the useful messages, timing and stop rules in writing. A reply or a request to stop needs the agreed response; the plan alone does not prove those effects work.
- Keep: the website and estimate routine that are already useful. Review only the agreed handoff before considering wider changes.
Download the blank service comparison worksheet (CSV). Use one row per candidate service. Note known costs, team time, existing customer interest and available capacity; leave unknowns visible. Keep completed notes in your own workspace.
Keep the decisions that are still open.
Mira and Lee still need to confirm who covers Lee's review when Lee is away, which service questions need the owner's judgment and what messages are appropriate. Naming a person in the draft does not show that the person accepted the work.
Write each open question beside the person who will answer it. Then use the existing notes tool below to compare the actual customer paths. The service choice gives that comparison a purpose; it does not replace the existing discussion or force a new system.
Once the path is agreed, the written package defines the page, messages, reminders and monthly care. Additional channels, complex integrations and wider projects are not automatically included. No payment, installation or client access starts just because these notes are complete.
Give each possible path a beginning and an end.
“Improve customer follow-up” can mean answering inquiries, preparing estimates, handling changed appointments or checking unfinished work. Each involves different decisions. Before choosing a project, separate the possible paths.
Write where each process starts and the specific point where this review ends. “A website estimate request arrives, then an office reviewer accepts the next action” is specific enough to examine. “Connect the whole business” leaves too many questions bundled together.
You are choosing a process to investigate, rather than deciding which customer deserves attention today. Existing promises still need their normal follow-through. Keep this comparison short: two or three genuine candidates are enough to begin a useful discussion.
Bring observations, an owner and the working parts.
For each candidate, find an example in your own records. Write what happened and what remains unclear. “The request has no accepted reviewer” describes something you can check. “We need another reminder” is a proposed solution.
The inquiry-path guide helps identify the current step, owner and next action. A single example can reveal a question worth investigating; it does not establish how often the problem occurs across the business.
Ask who understands this part of the work and can help review it. Confirm their involvement instead of assuming an available name means an available person. List the tools and routines already working well, too. A clearer handoff may need a team decision while the existing website, calendar or shared record stays in place.
Record the consequence only as far as you know it. A missed agreed update is different from an assumed lost sale.
Compare three paths in one business.
Fictional exercise: North Window Care is an invented window-cleaning business. Mira, its owner, and Lee, its office coordinator, are considering three possible starting points. The examples describe processes they could review, not three customers to rank.
On a small screen, swipe or scroll sideways to read the full table.
| Candidate path | What Mira and Lee know | Their next decision |
|---|---|---|
| Website request → accepted estimate reviewer | A request can be found, but nobody has accepted its first review. Lee agrees to examine this handoff with Mira. | Choose a bounded review. Check how the first reviewer is identified while keeping the website and estimate process intact. |
| Missed call → accepted callback task | They want clearer callbacks, but have not confirmed who manages the phone arrangement or who can cover the work. | Clarify first. Mira identifies the responsible people and checks the existing arrangement and coverage. |
| Confirmed booking → staff preparation | The example they review has the current appointment time, an accepted owner and a clear preparation task. | Keep what works. Preserve that routine and revisit if another observation reveals a gap. |
Choosing the estimate-review handoff does not mean callbacks matter less. It gives the team one question they can examine now. The missing phone and staffing facts remain visible, with Mira responsible for finding them.
Make the reason more useful than a score.
Use three plain questions: What do we know? What can we examine next? What must stay working? Compare the answers without converting them into a made-up return-on-investment score.
An expensive potential job does not automatically make its process the best starting point. Likewise, a path with fewer unknowns is not automatically the most important. Explain the choice in relation to the actual concern and the team's ability to investigate it.
In the fictional business, Mira and Lee choose to understand a specific ownership gap. They do not claim that it affects every estimate or that fixing it will increase sales. Their booking example supports keeping that reviewed routine, not declaring every booking flawless.
If all candidates depend on missing facts, choose a fact-finding step first. Leaving a path open for clarification is a useful result.
Choose a small case that can answer the question.
For the selected path, describe one review case and what you want to learn. Mira and Lee could use a fictional estimate request in a non-sending rehearsal, then ask who would accept its first review and where that acceptance would be recorded.
They can compare their answers with the current written routine. If their understanding differs, clarify the responsibility before choosing a tool change. A rehearsal should not create a real booking or contact a customer.
Agree who will run the review and when the team will discuss the finding. Then compare a better routine, software and managed help against the specific missing job. Choosing a starting path comes before choosing how to improve it.
Prepare your customer follow-up notes.
Compare two follow-up options, or add a third. Record what you would choose, clarify or keep—and why.
Use process descriptions and team roles, not customer details. These tools do not send or save entries to the website; your browser may restore them. Copy or download notes to keep them.
Open an option below. Prepare, download or print your notes with the page tools, or use the original blank follow-up selection worksheet.
Option 1
Option 2
Option 3 — optional third option
Your discussion notes
Check these notes before using them. “Not recorded” means the field is still open; an entered role does not establish that someone accepted the work.
Keep the selection and the open questions together.
Download the blank follow-up selection worksheet (CSV). Use one row per candidate process. Keep completed notes in your own workspace and reference the relevant records rather than copying private customer conversations.
Record choose, clarify or keep, followed by the reason. Name the next check and its owner. Retain dependencies and working parts so the discussion does not quietly expand into replacing everything.
This is a practical discussion aid, not a validated ranking model. Its useful result is a starting question your team understands, plus a clear account of what you are preserving and what still needs an answer.
To discuss this path with us, see what to bring to a Local Growth Call. The worksheet is optional.
Explore Choose the work. Then choose the system. for related questions and a useful starting point.