A completed implementation and a business outcome answer different questions. A launched CRM workflow is an output; shorter response time is an observed operational result; additional revenue is a business outcome that needs a stronger measurement path.
The decision sequence
Begin with a real buyer or team task and keep the relevant source record. The worksheet below is meant to expose a decision that someone can check, rather than replace specialist review or claim a Megvi client result.
| Decision point | What to check |
|---|---|
| Name the level | Label each proposed claim as activity, output, operational outcome or business outcome. |
| Match evidence | Use project logs for outputs, time-stamped process data for operational outcomes and reconciled business records for commercial outcomes. |
| Check the comparison | State baseline, observation window, population and other changes before describing improvement. |
| Use careful wording | Say “implemented” for verified delivery. Say “associated with” for observed changes when causation is uncertain. |
Worked example
Illustrative CRM project: the team connects a web form and creates a lead queue on 1 June. That proves an output. A later sample shows median first response fell from 18 to 6 hours, but staffing also increased. The report can describe the observed change and confounder; it cannot attribute every hour saved to the CRM.
What could change the decision
A client approving a project does not verify a revenue claim. Business outcomes need their own source, period and definition.
Review before using it
For every numeric line, write the numerator, denominator, dates, data owner and alternative explanation. Remove numbers that cannot be reproduced.
Next useful step
To preserve the chronology behind an output claim, use How to Document What Changed During a Client Project. For help with a live implementation, see Megvi’s integrated digital growth services. Bring the current page, workflow or evidence record and the decision you need to make.