MATCH SCORE MODEL V1.5.0 · VERIFIED SEP 27, 2026

A Match Score should be reproducible, not a gut feeling.

DetailerFit separates requirement fit from evidence strength. The score is personalized to the Finder inputs and is not a universal quality rating for a software vendor.

Core rule: unknown information is not scored as failure. Weak or missing evidence pulls a criterion toward neutral instead of toward zero. Affiliate relationships and commission amounts are not scoring inputs.
On this page

1. The formula

Each applicable criterion begins with a raw score from 0 to 100 and an evidence-confidence value from 0.00 to 1.00. The raw score is then shrunk toward neutral 50 according to the strength of the evidence:

Adjusted criterion score = 50 + Confidence × (Raw score − 50)

Examples: a verified 100 with 1.00 confidence stays 100. A raw 100 supported at 0.70 confidence becomes 85. A raw 0 at 0.70 confidence becomes 15. A completely unknown criterion has confidence 0 and therefore becomes neutral 50.

The final personalized Match Score is the weighted mean of all applicable adjusted criterion scores:

Match Score = Σ(Adjusted score × Criterion weight) ÷ Σ(Criterion weights)

Evidence Confidence is reported separately as the weighted mean of the confidence values. It is not hidden inside the headline score.

2. Raw criterion scores

DetailerFit avoids free-form 83/100-style editorial scoring where possible. Workflow requirements use a conservative three-state rubric:

100Requirement clearly confirmed for the selected plan or configuration.
50Partial, neutral or not sufficiently established for a positive or negative conclusion.
0Requirement clearly does not satisfy the stated need.

Industry fit uses a separate classification rubric because it describes product focus rather than a binary feature: 100 = purpose-built detailing/appearance workflow; 75 = automotive-specialist workflow; 50 = general field-service workflow; 25 = generic horizontal business software; 0 = unrelated workflow.

3. Evidence confidence

The current model uses the following confidence multipliers:

Evidence typeConfidenceUse
Hands-on verified1.00DetailerFit directly verifies the relevant workflow.
Official help documentation0.98Current vendor help-center or support documentation.
Official pricing / product documentation0.95Current vendor pricing, plan or feature documentation.
Official demo / release material0.90Vendor demos or release notes when the workflow is shown clearly.
Vendor-confirmed0.85Direct vendor confirmation that is not yet independently reproduced.
Multiple third-party sources0.70Corroborated context, not preferred over first-party product facts.
Unknown0.00No normalized evidence strong enough to score the criterion.

The percentage is also shown with a readability band. The band is descriptive only and does not change ranking:

Evidence ConfidenceLabelInterpretation
90–100%HighMost active weighted criteria are supported by current first-party or hands-on evidence.
75–89%GoodEvidence is generally strong, with some active criteria supported less directly.
60–74%ModerateSeveral active criteria need verification before relying heavily on the Match Score.
Below 60%LimitedA material share of the active score rests on incomplete or weakly supported criteria.

These labels describe evidence coverage, not vendor quality. A high Match Score with Moderate or Limited evidence should be treated as a hypothesis to verify, not stronger proof.

4. Personalized weights

Weights come from the user's Finder inputs. They are normalized automatically, so the active weights always form one comparable score even when optional priorities are not selected.

CriterionWeight when applicableRule
Price fit30Always active.
Team / capacity fit15Always active.
Industry fit5 baseline / 25 when selectedDetailing-specific workflow increases its importance.
Device fit15Active when iPhone/iPad or Android is explicitly selected.
Customer self-booking20Active when true customer self-booking is required.
Vehicle workflow25Active when VIN / estimating / vehicle documentation is selected.
Automation / admin20Active when automated follow-up/admin is selected.
Routing / dispatch / growth20Active when the scale priority is selected.
Setup readiness15Active only when the user says guided setup/training matters.
Migration readiness20Active only when the user says existing business data must be moved.

Weights are attached to requirements, not vendors. A vendor cannot receive a different weight because it has an affiliate program or a higher payout.

5. Hard constraints

Some inputs are requirements rather than preferences. The current Finder applies these gates before ranking:

  • Budget: if at least one eligible configuration has a verified monthly cost within the stated budget, over-budget and price-unverified configurations are removed before Match Score ranking.
  • Required customer self-booking: a product is not presented as a verified match when native customer-facing self-booking is either unverified or not available on the selected configuration.
  • Plan capacity: the Finder chooses the first plan configuration that can be supported by the current team-size/job-volume rules. Where the official documentation conflicts, the configuration is marked for verification instead of guessed.

6. Price fit

Known configurations at or below the stated monthly budget receive a raw Price Fit of 100. If no in-budget configuration exists and an over-budget option remains in the pool, Price Fit declines continuously using:

Raw Price Fit = 100 × (Budget ÷ Monthly cost)², capped between 0 and 100.

An exact price that is not verified receives neutral raw 50 with low confidence rather than a guessed dollar amount.

7. Setup readiness

Setup Readiness is only added when the user explicitly says a guided setup matters. It does not use subjective claims such as “easy to use” or a vendor's marketing estimate of how many minutes setup takes.

Instead, it is a composite of three observable support dimensions. Each subcriterion is evidence-weighted with the same shrink-to-neutral formula before the composite is calculated:

Setup subcriterionShare of Setup ReadinessWhat counts
Documented setup path40%A current step-by-step account setup, onboarding or go-live path.
Training / onboarding35%Structured tutorials, certification, workflow training, demos or onboarding material.
Human setup help25%A documented setup call, onboarding specialist, partner-assisted setup or paid setup service.

This means a vendor is not rewarded because DetailerFit “feels” it is simple. The model rewards verifiable setup infrastructure when that infrastructure matters to the user.

8. Migration readiness

Migration Readiness is only added when the user says they are moving existing business data. The model separates the data types and migration mechanics so a vendor is not given a full migration score merely because it can import a contact CSV.

Migration subcriterionShare of Migration ReadinessWhat counts
Customers / contacts25%Documented bulk import of customer/contact records.
Services / price book20%Documented import of services, materials, products or price-book data.
Work / history20%Documented import of jobs, quotes, estimates, invoices or comparable historical work records.
Field mapping15%Ability to map or validate source columns rather than requiring a guessed conversion.
Assisted migration20%Documented vendor/partner help for moving data.

Unsupported or unverified migration dimensions remain neutral instead of being silently counted as zero. Plan-limited assistance is also treated at the selected-plan level where the evidence allows it.

9. Unknowns, conflicts and missing evidence

“Not found” and “does not exist” are different claims. The model therefore does not assign zero merely because DetailerFit has not verified a feature. Unknown criteria use raw 50 and confidence 0 unless stronger evidence supports a different state. When official pages conflict, the model uses the conservative plan interpretation and lowers certainty or asks the reader to verify.

10. Setup & migration evidence reviewed

The v1.5.0 setup/migration normalization was checked against current first-party documentation on September 27, 2026. These are source families, not endorsements:

11. Capability evidence refresh

Model v1.2.0 rechecked several previously neutral workflow criteria against current first-party product and help documentation. A neutral 50 was upgraded only where the requested capability is now explicitly documented; missing evidence remains neutral.

VendorCriterion updatedFirst-party evidence
ServiceM8Automation; Routing / dispatch / growthPricing comparison confirms automated reminders/follow-ups and Dispatch Map; Auto Routing documents route optimisation.
JobberRouting / dispatch / growthRoute Optimization documents automatic route ordering, map views and Connect/Grow/Plus availability.
UrableRouting / dispatch / growth; Vehicle workflowUrable product page documents route optimisation and personnel assignment; Pricing documents VIN barcode scanning, a two-way Carfax link and vehicle data/image storage.
StrataNew normalized vendorPricing confirms standard plan rules, booking, automation, iPhone/Android apps and CSV migration; Client & Vehicle CRM confirms vehicle records and history. Route optimization and VIN scanning remain unverified and therefore neutral.
DetailPilotNew normalized vendorPricing confirms Starter/Growth/Pro/Business plan rules and team gating; product documentation confirms detailing-only workflow, booking, crew tools and mobile-web support. migration guidance confirms customer CSV import. Route optimization, VIN scanning and broad historical-data migration remain unverified and therefore neutral.
Housecall ProAutomation / adminPricing and Customer Management document automated reminders and follow-ups on the entry plan path.

This refresh changes evidence-backed fit only. It does not introduce affiliate status, payout, popularity, review sentiment or editorial preference into the formula.

12. Current scope and limitations

Model v1.5.0 scores the requirements currently collected by the Software Finder across eight vendors in the normalized ranking set. Strata and DetailPilot joined the normalized set only after first-party plan, booking, automation, device and migration rules were documented well enough to reproduce their scores. DetailPilot’s free Starter plan is treated as $0 monthly software cost while its published 1% payment fee is disclosed separately rather than hidden inside a guessed monthly amount. The current public pricing page does not publish a monthly booking/job cap for Starter, so the Finder does not invent one; this should be rechecked if DetailPilot republishes a volume limit. Setup and migration are now included only when the user activates those needs.

The model intentionally does not score claimed setup time, UI aesthetics, generic review sentiment or undocumented migration capabilities. A documented import path can still have real-world edge cases, and a successful migration may depend on the quality and structure of the source data.

The Match Score should therefore be read as: “How well does this currently verified plan fit the requirements I entered?” It should not be read as “Which software company is objectively best?”

13. Commercial independence

The scoring implementation contains no commission amount, EPC, payout, affiliate-status bonus or revenue weight. Affiliate relationships can change the destination URL or disclosure text, but they do not change raw criterion scores, confidence multipliers, user weights, plan gates or the ranking formula.