Record the current failure, affected population, baseline, target, measurement source, accountable owner, adoption threshold, and decision date. Product preference and feature volume are not substitutes for an observable result.
Six scenarios to run with every finalist
1. Lead capture and duplicate handling
Prepare realistic source data, name the actor and owner, include a failure or exception, and set a measurable completion threshold. Preserve the output and every manual correction.
2. Territory and ownership changes
Use the proposed permission role and actual integration boundary. Ask an ordinary user to complete the work, then repeat it after a changed owner or invalid input.
3. Opportunity qualification and stage evidence
Measure elapsed work, handoffs, duplicate entry, missing context, and recovery effort. Distinguish native capability from configuration, integration, custom work, roadmap, or workaround.
4. Forecast override and inspection
Inspect audit history, notifications, approvals, reports, and exports. A successful screen demonstration is insufficient if the team cannot operate or evidence the result later.
5. Quote or order handoff
Stress the expected volume and an adverse case. Record the plan or add-on required, the accountable administrator, and the consequence if the scenario fails in production.
6. Activity, file, and relationship export
Export the finished record with relationships, attachments, history, permissions, and identifiers. Estimate the work required to reconcile it and move to another service.
Give vendors the same script, roles, data, integrations, constraints, and time. Reviewers should score independently before discussion and cite a retained artifact. Mandatory legal, privacy, security, data, and critical-workflow gates are pass or fail; they cannot disappear inside an average score.
Stakeholder decision table
| Accountable stakeholder | Decision and evidence required |
|---|---|
| Sales leadership owns outcome and forecast rules | must define the pass condition and approve any operating compromise |
| Revenue operations owns process and data design | must supply dated evidence and identify the unresolved dependency |
| Frontline representatives validate usability | must test normal work without accepting vendor coaching as product capability |
| It and security validate identity and integrations | must confirm the control, configuration, integration, and recovery owner |
| Finance and procurement normalize total cost and terms | must reconcile the quote, complete cost, term, renewal, reduction, and exit exposure |
Record dissent and conditions instead of forcing false consensus. The final approver should know which claims were observed, which were documented, which remain assumptions, and who accepts any residual exposure.
Normalize the complete cost
Model the billable user or usage population at launch, year one, and renewal. Add edition, minimum quantity, guests or collaborators, consumption, AI, storage, integrations, support, services, migration, data preparation, internal administration, training, parallel operation, tax, renewal uplift, and exit. Keep vendor charges and internal labor separate. Compare a likely case with a stress case that assumes slower adoption, more billable volume, a premium control, and delayed implementation.
Retain the public price page, dated quote, assumptions, calculation, and contract position. Reconcile plan names, currency, term, discounts, add-ons, allowances, overages, implementation scope, service levels, start date, and renewal protection. An unknown cost should be a range with an owner and due date—not zero.
Implementation and first 90 days
Require owners for design, identity, permissions, data preparation, migration, validation, integrations, testing, training, support transition, acceptance, and decommissioning. Define launch gates and rollback authority. During the first billing cycle, reconcile provisioned access to the invoice. At 30, 60, and 90 days, review adoption by required workflow, unresolved incidents, administrator effort, outcome measures, and any tool that was supposed to be retired.
Renewal and exit
Record term, auto-renewal, notice deadline and delivery method, quantity reduction, uplift, price protection, true-up, suspension, service levels, support, export, transition help, post-termination access, deletion, and retained copies. Test a representative export before signature and again early enough before renewal to switch. A renewal decision should be retain, resize, renegotiate, replace, or cancel, supported by usage, outcome, risk, invoice, support, and portability evidence.
Run the same test and retain the decision
Use the demo scorecard for observed workflows and the pricing worksheet for a three-year commercial model.
Sales workflow evidence that separates CRM finalists
1. Lead capture and duplicate handling
Submit the same prospect through a web form, event import, and manual entry. Verify matching rules, consent source, campaign attribution, territory, owner notification, and the review queue for uncertain duplicates. Measure correction time and confirm that merging records does not discard activity or permission history.
2. Territory and ownership changes
Move an account with open opportunities between representatives, teams, and regions. Inspect inherited activities, forecasts, tasks, shared access, restricted fields, automation, and manager visibility. Test a temporary coverage assignment and a departing seller so ownership continuity is proven beyond the happy path.
3. Opportunity qualification and stage evidence
Create a multi-product opportunity with missing information, a competitor, a stalled next step, and an approval exception. Require the system to distinguish required evidence from optional notes, prevent unsupported stage movement, and show managers why the deal changed without reading every activity.
4. Forecast override and inspection
Build a forecast from representative pipeline data, then let a manager override one judgment. Confirm the original value, reason, actor, timestamp, roll-up effect, currency, period, and later correction remain visible. Compare the executive total with the underlying opportunities and document any offline spreadsheet dependency.
5. Quote or order handoff
Pass an approved opportunity to finance, contracting, provisioning, or an order system. Introduce a changed quantity and expired discount. Verify approval routing, product and price integrity, duplicate prevention, failed integration recovery, customer communication, and reconciliation back to the revenue record.
6. Activity, file, and relationship export
Export accounts, contacts, opportunities, products, activities, emails, attachments, owners, custom fields, stage history, and identifiers for a representative segment. Check relationships and timestamps after extraction. Price any API, service, storage, or manual reconstruction required to leave.
Failure signals to challenge before approval
- Representatives keep decisive notes in private documents because the CRM adds too much work.
- Pipeline stages carry different meanings across teams, making the forecast look precise but incomparable.
- Premium controls are discovered only after the preferred edition and budget have been announced.
- Implementation customizes the old process instead of removing unnecessary steps and duplicate data.
- Renewal quantity follows provisioned seats even when required workflows show a smaller active population.
Measures to carry into the first renewal
- time from qualified inquiry to accountable owner
- percentage of opportunities with current next-step evidence
- forecast error explained by stage, segment, and owner
- seller time spent on duplicate entry and correction
- complete export rate for the representative record sample
Assign one named owner and evidence source to each measure. Record the baseline before configuration, review it during the first 90 days, and preserve the result beside invoice and support evidence. If a measure cannot influence retain, resize, renegotiate, replace, or cancel, it is not yet a useful renewal control.