Sample Business Process Review · fictional service company
What the $950 review actually delivers.
This is a finished-example brief, not a testimonial or client result. Every name, event, and measurement below is fictional; the structure follows Meridian's current review method.
Problem under review
Prospects receive estimates, then go cold because follow-up has no visible owner.
Scope: four recent estimates from first contact to last action—not a full CRM, sales, or implementation audit.
Evidence compared
Case A: Estimate sent; no owner or next action for four days.
Case B: Two employees each assumed the other would follow up.
Case C: A personal inbox hid the follow-up from the team.
Case D: The customer booked only after calling again.
Observed pattern
Initial responses were timely. The breakdown came after the estimate, when ownership, deadlines, and outcomes were split across inboxes, spreadsheets, and memory.
Price, timing, and fit may also affect sales; this evidence does not prove follow-up caused every loss.
Likely cause
Every active estimate needs one visible owner, next action, due time, and close reason. That operating rule is missing.
Confidence: medium-high for the workflow gap—not for revenue impact.
Recommended first repair
Use one shared view with five fields: owner, next action, due time, last contact, and outcome. Review overdue items daily.
Automation may flag reminders. Messages, pricing, discounts, and close decisions remain human-approved.
Thirty-day measure
Baseline: three of four estimates lacked a visible next action by the next business day.
Measure: assignment speed, visible next steps, overdue follow-ups, and recorded close reasons. Compare the same definitions before and after; do not promise sales growth.
Decision and next steps
Implement internally, request a Focused Repair quote, or stop. The $950 review ends with this brief, its limitations, and a 45-minute walkthrough.
Configuration, integrations, automation, training, and monitoring require separate scope and approval.
Proof boundary
This fictional sample shows the deliverable's structure and restraint. It does not represent a real customer, testimonial, or promised outcome.
Sample format · August 24, 2026