Start With Requirements, Not Vendors
Document team size, process complexity, integrations, industry specifics, and AI ambitions before any vendor conversation. Without this, demos drive you. Write a one-page brief that captures: number of seats by role (sales, marketing, service, ops), the three workflows you spend the most time on today, the systems of record that must sync (ERP, billing, support, marketing), regulated data you handle (PII, PHI, PCI), and the AI use cases you can describe in a sentence. If you cannot describe the AI use case, you do not need the AI module yet.
Shortlist From Requirements
Three to five vendors maximum. For most orgs the realistic shortlist is Salesforce, HubSpot, Dynamics 365, Zoho, and Freshworks. Add ServiceNow when ITSM is in scope, and industry clouds (Veeva, nCino, Vlocity-derived) when your vertical has compliance baked into the workflow. Cut anything that requires more than one custom-built bridge to your core systems — integration debt always grows.
Comparison Framework
| Dimension | What to score | Why it matters |
|---|---|---|
| Pricing tiers | Per-seat list + add-on modules | Sticker price misleads; add-ons drive 30-50% of TCO |
| Feature depth | Out-of-box vs. configured vs. coded | Determines partner spend |
| Time to value | Weeks to first business outcome | Stakeholder patience is finite |
| Vendor lock-in | Data export, schema portability | Predicts switching cost in year 4-5 |
| Ecosystem | Marketplace size, partner count | Gaps you do not have to build |
| Migration path | From your current tools | Hidden cost line item |
| Integration footprint | Native connectors vs. iPaaS | API call volume drives surprise bills |
| Target customer size | Vendor’s center of gravity | Avoid being the smallest or largest customer |
Pilot Before Committing
Run a 30-day pilot on real data with real users on real processes. Sales-engineered demos and pilot reality often differ by a factor of two on configuration time. Pick three users who will champion the rollout and three who will resist; both groups must touch the system daily during the pilot. Measure clicks-to-complete on your top three workflows, not feature checklists.
Total Cost Modeling
Build a 3-year TCO that includes licenses, implementation partner fees (typically 1-2x year-one license), integrations, training, ongoing admin headcount, and the price increase the vendor will quote at renewal (assume 7-10% annually). Sticker price is the beginning, not the end. Salesforce and ServiceNow renewals routinely surprise buyers; HubSpot’s contact-tier ratchets surprise marketers; Zoho’s add-on sprawl surprises admins.
Choose By Profile
- Under 50 seats, sales-led: HubSpot or Pipedrive — fastest time to revenue impact.
- 50-500 seats, mixed sales/marketing/service: HubSpot, Zoho, or Dynamics 365 if Microsoft-heavy.
- 500+ seats, complex B2B or regulated: Salesforce or Dynamics 365 with industry cloud.
- IT-led service org: ServiceNow for enterprise, Freshservice or JSM for mid-market.
What to Ignore in Vendor Pitches
- “AI agents will replace your admins” — they will not in 2026; budget for the same admin headcount.
- “Native integration” — verify that means real-time bidirectional sync, not a nightly batch job dressed up.
- “Future roadmap” features you need now. Locked-in long contracts without pilots. Reference-resistant sellers. Demos that skip your real data.
Red Flags
If the vendor will not let you talk to three customers your size in your industry, walk. If the SOW will not commit to a go-live date with penalties, walk. If pricing requires a 3-year commitment to be competitive, negotiate it down to one with renewal options.
If you are under 100 seats, default to HubSpot and revisit at scale; if you are over 1,000 seats or in a regulated industry, default to Salesforce or D365 and pilot the rest only to disqualify them.
