← Back to Salestrics Today

In-App Billing for RevOps: Seats and Add-Ons

RevOps used to reconcile CRM seats in a spreadsheet while finance waited on a support ticket to add Ledger. In-app checkout in Admin → Billing — shipped in Changelog #17 — puts plans, seats, and add-ons where operators already work. The hard part is not clicking upgrade; it is maintaining a seat map that matches how your team sells, supports, and uses finance apps. This 2026 playbook is for mid-market RevOps owners: document who needs which line, when add-ons beat bundled One, and how plan limits stay honest after checkout.

What changed with in-app billing

  • Checkout in workspace — plans, seats, add-ons without leaving Admin
  • Path-aware UI — Momentum, Resolve, and One tabs reflect your packaging choice
  • Limits match purchase — enforced caps align with what you bought
  • Pricing page parity — same tables at app.salestrics.com/pricing

RevOps wins when billing state is visible to the people who assign seats — not buried in a PDF invoice.

The seat map (living document)

Maintain one table — updated when someone joins, changes role, or leaves:

PersonPrimary motionLine(s)TierAdd-onsMailbox
AEPipelineMomentumTeamConnect incl.Yes
CSMSupportResolveTeamYes
FounderBothMomentum + ResolveTeam bothLedgerYes
FinanceLedgerMomentum or OneTeam+Ledger, Insight SQLOptional

Agents and finance both read this map — it explains usage at renewal. Pair with finance permissions for Ledger writes.

Checkout order (standalone path)

  1. Pick line — Momentum, Resolve, or both (see buy-first guide)
  2. Pick tier — Starter / Team / Growth per seat map row
  3. Add seats — billable people only, not every login
  4. Add-ons — Ledger, Flow, Insight SQL, Auto as needed; avoid duplicate Insight + Insight SQL
  5. Compare One — before annual commit, run bundled math
  6. Annual vs monthly — annual pays 10 months, get 12

Add-on discipline

Add-onAssign whenSkip when
ConnectCustomer calls on graphIncluded on Team+ already
LedgerInvoices tied to oppsFinance still in separate ERP only
FlowApprovals on quotes/discountsFounder approves in Slack
Insight SQLRevOps owns SQL reportsBasic dashboards enough
AutoNurture at scaleMail-on-account not proven

On Salestrics One, bundled apps remove checkout scavenger hunts — revisit standalone add-ons at renewal if you migrated to One.

Monthly RevOps billing ritual (30 minutes)

  1. Admin → Billing — confirm plan matches seat map
  2. New hires / role changes — update lines and add-ons same week
  3. Limit warnings — records, mailboxes, Lead Finder — upgrade or archive
  4. Offboarding — revoke seats and keys same day
  5. One comparison — if dual lines + add-ons grew, rerun One math

Upgrade reviews (quarterly)

Before QBR, answer:

  • Teammate cap — approaching One tier boundary?
  • Dual motion — still Momentum-only but Resolve volume grew?
  • AI pools — heavy Assistant users may need tier or token packs (see pricing page)
  • Support Embed — requires Resolve Team+ or One; not on Momentum-only

Upgrade playbook for free workspaces: Free Forever to paid.

Finance + sales alignment

Billing changes should not surprise pipeline owners:

  • Seat adds — RevOps notifies managers before checkout
  • Ledger seats — finance owns invoice send policy on account mail
  • Trial windows — 30-day trial on paid paths; document end date in seat map
  • Legacy plans — grandfathered names in billing; new signups use Momentum / Resolve / One

Anti-patterns

  • Resolve seat for every employee — only customer-facing roles need full desk
  • Duplicate Insight purchases — Insight SQL includes dashboards
  • Personal card checkout — use org billing owner in Admin
  • Ignore limit banners — archive stale data before forced upgrade fire drill
  • Seat map in Notion only — stale map → wrong renewal quote

MCP prompt (billing hygiene)

Summarize teammates with Momentum vs Resolve seats, add-ons enabled, and mailboxes active. Flag anyone with a seat but no mail activity in 30 days or add-ons they do not use.

Read-first; use output in monthly ritual — not as automatic seat removal without manager review.

Legacy vs new packaging (renewals)

Existing workspaces may still show legacy plan names (Intro, Startup, Launch, Runway, Scale) in billing — those maps are grandfathered. New signups and public pricing use Momentum, Resolve, and One. RevOps on legacy plans should still maintain a seat map; at renewal, compare grandfathered terms to current paths before auto-extending.

  • Document legacy entitlements — which apps and caps differ from today's tables
  • Model migration — standalone vs One at next renewal, not only month-over-month
  • Communicate to managers — seat adds on legacy plans may not match new tier names

Worked example: dual-line Team stack

Eight people — five AEs on Momentum Team, three CS on Resolve Team, Ledger for two finance users:

Line itemCalculationMonthly
Momentum Team × 5$39 × 5$195
Resolve Team × 3$39 × 3$117
Ledger add-on × 2$35 × 2$70
Total standalone$382
One Team (≤15 teammates, bundled)Flat$499

At eight teammates with only Ledger as add-on, standalone wins on math — but adding Flow, Insight SQL, or Auto seats narrows the gap quickly. Run the table every quarter; do not assume last quarter's answer still holds after headcount changes.

Related reading