Scope
Define the buyer, market, currency, company shape, operating model, product version, and claims being tested.
The Field-Fit Protocol / v1.0
Our methodology separates what we observed, what a vendor told us, what public documentation states, and what users report. It also identifies the market where each claim was verified.
Six phases
A product can score well overall and still be the wrong fit for a specific operating model.
Define the buyer, market, currency, company shape, operating model, product version, and claims being tested.
Build a fresh test account using the same baseline company, permissions, services, and tax settings.
Complete the vertical scenario pack from lead intake through payment and reporting.
Trigger reschedules, weak connectivity, duplicate records, failed payments, and human handoffs.
Model the first year and steady-state cost, including seats, add-ons, fees, setup, and training.
Attach evidence types, disclose commercial relationships, name limitations, and set a re-test date.
Baseline score
Vertical guides can move up to 15 percentage points between dimensions, but every change is disclosed on-page.
Evidence labels
Completed in our test account and logged with date, version, plan, and scenario.
Vendor pricing, help center, security page, terms, status history, or product documentation.
A recurring theme across attributed user sources, clearly separated from our observation.
Useful context that cannot yet carry a score or recommendation.
Operational worksheet
The working guide converts these phases and weights into a day-by-day scenario pack, evidence record, rejection rules, and final decision.
Commercial policy
Affiliate eligibility is checked only after the editorial verdict is locked. Commercial terms may change which tracked outbound link is used; they do not change the score, winner, inclusion, or wording.