Sales and enquiries
Illustrative example · fictional business
What a careful snapshot looks like.
This fictional example shows how a snapshot separates what a visitor reported from what is only a hypothesis, and why the suggested next step is sometimes a simple change rather than a purchase. It is not a client result or a quote.
1. What they told us
Work stalls or gets lost between people or teams
Website enquiries arrive in a shared inbox. Whoever notices one replies, but nobody owns follow-up, so some wait days and a few are never answered. Quotes are tracked in a spreadsheet that is often out of date.
About once a day
One team
About 5 hours a week across the team
Delays, Customer impact
Email, Spreadsheets
Not written down
Office administrator, two sales staff
2. Potential friction points
Hypotheses to test, not established causes.
No owner for new enquiries
Enquiries may wait because replying is everyone's job and therefore nobody's.
Why we suggest it: You said whoever notices an enquiry replies, and some wait days.
The quote list isn't the source of truth
An out-of-date spreadsheet may mean follow-ups are missed or duplicated.
Why we suggest it: You said the spreadsheet is often out of date.
3. What would need validation
- Count last month's enquiries and how many waited more than a working day for a first reply.
- Ask the three people involved how they currently decide who replies.
- Check whether the spreadsheet or the inbox is more often correct.
4. Possible approaches
Name an owner and a reply standard
One person owns new enquiries each day, with an agreed time for the first reply and a simple handover when they are away.
One shared list of open quotes
Keep open quotes in one shared list, updated when a quote is sent and when it is won or lost.
Consider a simple CRM later
If the changes hold but volume grows, a basic CRM or an automated enquiry log may be worth scoping.
5. Recommended next step: A simple process improvement
Why this route:
- A small change to how the work is organised may be enough.
- Few people are involved, so a change is easy to agree.
- The gap looks like a process issue rather than a missing tool.
- Clear ownership, a checklist or a shared log often helps with this kind of issue.
- Writing the steps down is a low-cost first step.
The five hours a week is the visitor’s own estimate, so the snapshot repeats it as self-reported and does not turn it into a saving or a cost. If the simple changes don’t help, a short conversation about a scoped system is the next step.
6. Important limitations
A snapshot is preliminary and based only on what was reported. It is not a formal business analysis, it makes no estimate of savings, cost or timelines, and it guarantees no result.