Starter vs Team vs Growth: Pick Your Tier

What each tier unlocks (platform apps)

Full limit tables live on app.salestrics.com/pricing and in Changelog #17. Tier choice should follow apps you will use in the next 90 days — not a roadmap slide from next year.

Pick Starter when…

• One or two billable GTM people proving mail on account and stage hygiene
• No customer calls in-product yet — Connect add-on is optional until you need it
• Prospecting still manual — Lead Finder is not daily workflow
• Finance apps later — Flow and Ledger add-ons require Team anyway

Starter is not a forever tier for a scaling team — it is the disciplined entry when habits matter more than app count. See Free Forever to paid before your first checkout.

Pick Team when…

• Connect is default — customer calls and calendar on the account graph
• Lead Finder is weekly+ on the Momentum line
• Support Embed or full desk on Resolve Team+
• Ledger or Flow next quarter — add-ons attach at Team tier

Team is the default standalone tier for most mid-market GTM pods once mail-on-account is proven. Pair with Lead Finder prospecting and Support Embed when those motions are live.

Pick Growth when…

• Orbit is daily — partner feed and social GTM, not an experiment
• Heavy Assistant usage — 5M tokens/person vs 2M on Team
• Record and API headroom — approaching Team caps on active book
• Standalone still beats One — run the math before flat org pricing

Growth without Orbit need is often Team plus selective add-ons. Do not buy Growth only to avoid a future upgrade conversation — step up when a cap blocks real work.

Decision matrix (quick)

Mixing tiers across teammates

Billing allows different tiers per person on the same line — but RevOps should avoid accidental sprawl:

1. Document exceptions — why one seat is Starter while peers are Team
2. Align Connect need — customer-facing roles on Team+; back-office on Starter if truly no calls
3. Review quarterly — Starter seats that need Lead Finder should move to Team
4. One comparison — mixed tiers plus add-ons may exceed One flat pricing faster than you expect

Seat map template: in-app billing RevOps playbook.

Annual billing at tier selection

Annual standalone billing pays 10 months, get 12 — two months free at any tier. Before annual commit:

• Prove tier fit on monthly for one billing cycle when possible
• Model step-up — if you are likely Starter → Team within 90 days, skip Starter annual
• Compare One annual — bundled org pricing may beat dual-line Team annual

Math guide: One vs standalone.

Worked example: five-person sales pod

At five Momentum-only seats, Team usually beats Starter once Connect is non-negotiable. One wins when Resolve seats and add-ons join the map — not at five CRM-only reps on Team.

Anti-patterns

• Growth for logo prestige — Orbit unused for 60 days → downgrade review
• Starter for entire pod — to save $10/person while paying Connect add-ons individually
• Ignore Lead Finder gates — prospecting workflow on Starter without tier upgrade plan
• Tier without line decision — pick Momentum vs Resolve first
• Skip seat map — mixed tiers without documentation → renewal surprises

90-day tier review checklist

• Connect usage — % of customer meetings in-product vs external
• Lead Finder — hits/day vs tier cap warnings
• Assistant tokens — per-person pool exhaustion (see token governance guide)
• Add-on roster — paying for Ledger/Flow on Starter seats (invalid — move to Team)
• One math — rerun bundled comparison if headcount or Resolve joined

MCP prompt (tier audit)

List teammates on Momentum or Resolve with tier, Connect usage in the last 30 days, Lead Finder activity, and any plan limit warnings. Recommend tier changes that match actual motion — not hypothetical roadmap.

Read-only; use output in quarterly RevOps review alongside Admin → Billing.

Related reading

• Compare tiers and limits
• Momentum vs Resolve — buy first
• One vs standalone math
• In-app billing RevOps
• Schedule a demo