CrewViper

BUYER WORKSHEET

Score the work. Not the sales pitch.

A long feature list cannot tell you whether tomorrow’s crew will arrive at the right address. Compare each platform using the same jobs, roles and evidence.

Agree on the weights before the demo

The worksheet below totals 100 points. Adjust weights for your business before evaluating vendors, then keep them fixed across candidates. A solo operator and a multi-crew office may reasonably value dispatch and permissions differently.

Suggested evaluation weights: 100 points total
WorkflowWeightEvidence to request
Customer records and import15Map a sample customer, multiple properties and a duplicate; inspect the resulting records.
Quotes and scope changes15Create a line-item quote, revise it and show what the customer and office see.
Scheduling and dispatch20Assign and reschedule a job; verify crew visibility and conflict handling.
Crew usability and permissions15Complete a job from a phone with the crew role, not the owner account.
Invoices and payment records10Check totals, partial payments and outstanding balances; distinguish manual records from a live payment integration.
Data control and recovery10Show export options, access controls and evidence of the recovery process.
Ongoing cost and support10Document seats, usage charges, required add-ons, setup effort and support escalation.
Connected automation5Demonstrate a controlled integration test, including failure and retry behavior.

Use a repeatable 0–5 scale

0: tested and cannot complete the required workflow. 1: major workaround. 2: partial completion with substantial manual work. 3: completes the agreed baseline. 4: completes it cleanly with a useful operational advantage. 5: meets the baseline and your pre-agreed stretch criteria with supporting evidence.

For each row, calculate weighted points = weight × score ÷ 5. A dispatch score of 4 at weight 20 contributes 16 points. Sum the rows for a maximum of 100 only when every row is tested.

Mark untested rows NT, not zero and not five. Report evidence coverage separately: tested weights ÷ 100. If tested weights total 70 and earned points total 48, report “48 points earned; 70% coverage; 30 points untested.” Do not present that partial result as a final vendor ranking.

Keep an evidence ledger alongside the score

Copy these columns into your evaluation sheet
ColumnWhat belongs here
RequirementA specific outcome, such as a crew member seeing a rescheduled job.
Candidate / datePlatform, evaluated plan and the date of the test.
Test / roleThe exact action and permission level used.
Result / scoreObserved outcome, 0–5 or NT, and weighted points.
EvidenceA safe screenshot, test notes or an authorized recording without customer information.
Dependency / ownerAny integration, paid add-on, configuration work or follow-up required.

Some failures override the total

A high weighted score should not excuse a critical gap. Decide your hard gates before reviewing candidates: appropriate tenant and role access, reliable next-day scheduling, accessible data exports, recoverability, and a viable total operating cost. Mark a failed gate separately and do not launch until it is resolved.

Claims about a roadmap are not evidence of current availability. An attractive demo does not prove persistence, message delivery, a production restore or a successful charge. A manual workaround can still be acceptable, but record its owner and recurring effort.

Put CrewViper through the same test

Use the public app demo for fictional workflows, then the pilot scorecard for a structured review. Production accounts remain invite-only; live integrations and recovery checks need separate authorized testing.

For a Jobber comparison, use the same sample records and evaluate the actual plan you would buy rather than assuming all features are included. The Jobber alternative guide frames the workflow comparison. The migration acceptance checklist covers the changeover after you choose.

The goal is a defensible decision, not to make one vendor win. Keep the scores, evidence and unresolved questions together so the owner and crew lead can reach the same conclusion.

Test the workflow before moving the business.

CrewViper is in private pilot. The public demo uses fictional data and resets on reload. It is not an importer, a backup test, or proof that a production integration is connected. Do not upload real customer data to the demo.

Switching guide · Compare with Jobber · Pilot scorecard