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. Donor and household matching
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. Gift, pledge, restriction, and acknowledgment
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. Campaign and event participation
Measure elapsed work, handoffs, duplicate entry, missing context, and recovery effort. Distinguish native capability from configuration, integration, custom work, roadmap, or workaround.
4. Volunteer or program engagement
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. Consent and communication preference
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. Fundraising and finance reconciliation
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 |
|---|---|
| Fundraising owns donor workflows | must define the pass condition and approve any operating compromise |
| Program teams define service outcomes | must supply dated evidence and identify the unresolved dependency |
| Finance validates gift and grant reconciliation | must test normal work without accepting vendor coaching as product capability |
| Privacy and it review sensitive constituent data | must confirm the control, configuration, integration, and recovery owner |
| Executive leadership owns scope and adoption | 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.
Constituent and fundraising evidence a nonprofit should require
1. Donor and household matching
Import a household with two donors, a shared address, separate communication preferences, and one changed surname. Test duplicate suggestions, soft credits, relationship history, confidential attributes, salutations, and the effect of merging. Preserve the original identifiers so finance and fundraising records remain reconcilable.
2. Gift, pledge, restriction, and acknowledgment
Record a recurring pledge, partial payment, designated fund, employer match, returned payment, and corrected acknowledgment. Confirm the service keeps gift dates, posting status, restriction, recognition, tax wording, and adjustment history distinct rather than overwriting a completed record.
3. Campaign and event participation
Register a constituent for an event, connect the invitation and attendance to a campaign, then process a guest and late donation. Verify costs, source, response, consent, household credit, volunteer role, and follow-up remain explainable without creating duplicate people or disconnected spreadsheets.
4. Volunteer or program engagement
Limit a program coordinator to the participants and fields required for service delivery. Record attendance, outcome, incident, and follow-up while protecting donor wealth, health, family, or other sensitive attributes. Test reassignment and aggregate reporting without exposing individual records.
5. Consent and communication preference
Change a constituent's email preference while preserving consent source, purpose, date, and channel. Confirm suppression reaches fundraising, newsletters, events, and connected marketing tools before another send. Test deletion or restriction requests against recordkeeping duties and accepted exceptions.
6. Fundraising and finance reconciliation
Reconcile a batch containing online gifts, checks, fees, refunds, split designations, and an unmatched deposit. Compare CRM totals with the payment processor and ledger, document timing differences, and retain the person who approved the correction. Do not accept a dashboard that cannot explain the underlying entries.
Failure signals to challenge before approval
- Households, organizations, donors, volunteers, and beneficiaries are forced into one relationship model.
- Fundraising totals cannot be reconciled to deposits and restricted-fund accounting without manual rework.
- Sensitive program data becomes visible to staff who only need campaign or event access.
- A discounted nonprofit rate hides paid implementation, contact growth, email, payment, or support costs.
- Migration preserves names and gift totals but loses consent, relationships, adjustments, and historical ownership.
Measures to carry into the first renewal
- duplicate rate after household and organization matching
- time to reconcile a gift batch to deposits and ledger
- percentage of acknowledgments produced with correct treatment
- suppression propagation time across connected communication tools
- constituent records exported with complete relationships and history
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.