How much do you save on annual billing?

Two months free — you pay for 10 months of service and receive 12. Exact invoice amounts depend on tier, seats, and add-ons at commit time.

Should new customers start on annual?

Usually no — prove tier, line (Momentum vs Resolve), and add-ons on monthly for at least one billing cycle when possible. Annualize after a 90-day review passes this checklist.

Does annual billing lock add-ons?

You can still change seats and add-ons in Admin → Billing — but annual commit makes wrong add-on stacks expensive to unwind psychologically. Map seats before annual.

What about FREE180 or promotions?

Promotional credits and trials have their own terms — run this checklist after promotion pricing normalizes to standard tiers so math reflects steady state.

← Back to Salestrics Today

August 20, 2026 4 min read Salestrics Team

Annual Billing: When to Commit (2026 Checklist)

Annual billing on Salestrics is straightforward: pay 10 months, get 12 on standalone tiers and Salestrics One. The discount is real — roughly two months free. The mistake is timing: mid-market teams annualize before tier fit, add-on roster, or One vs standalone math is proven, then spend Q1 arguing about upgrades that should have been monthly pilots. This 2026 checklist is the commit gate RevOps runs with finance before anyone clicks annual in Admin → Billing.

What annual billing includes

Standalone Momentum or Resolve — Starter, Team, Growth per-seat annual
Salestrics One — Team, Growth, Scale flat org annual
Add-ons — Flow, Ledger, Insight SQL, Connect (Starter) annualize with seats
Not a separate SKU — same products; billing cadence changes in Admin → Billing

Pricing tables: app.salestrics.com/pricing and Changelog #17.

Pre-commit checklist (all must pass)

Line decision documented — Momentum vs Resolve buy order
Tier fit proven 60+ days — Starter vs Team vs Growth review passed
Seat map signed — who holds which line, tier, add-ons — billing RevOps playbook
Add-on roster justified — Flow, Ledger, Insight SQL owners named
One math rerun — One vs standalone at current headcount
Upgrade path known — if Starter → Team likely in 90 days, skip Starter annual
Finance sign-off — PO, card owner, and renewal reminder owner assigned

When to wait (stay monthly)

Situation	Why wait
First 60 days on paid tier	Tier and add-ons still moving
Pending Resolve or second line	Dual-line math changes One breakeven
Headcount hiring spike	May cross One teammate cap
Migration in progress	Seat count unstable until cutover done
FREE180 or promo active	Annual math should use standard pricing

Monthly is not failure — it is the pilot cadence. Upgrade playbook: Free Forever to paid.

Annual savings example

Five people on Momentum Team ($39/person/mo):

Cadence	Calculation	Annual cost
Monthly × 12	$195 × 12	$2,340
Annual (10 months)	$195 × 10	$1,950
Savings	2 months free	$390

One Team ($499/mo): annual pays $499 × 10 = $4,990 vs $5,988 monthly — save $998/year when standalone stack would exceed $499/mo anyway.

Commit order (recommended)

Prove monthly one cycle on chosen tier
Freeze seat map for 30 days — no experimental add-ons
Run One comparison — if One wins, annualize One not dual stacks
Annualize core seats — CRM/desk lines first
Annualize add-ons only on seats with 60-day usage proof
Calendar renewal review — 60 days before annual renews, rerun checklist

RevOps renewal calendar

T−60 days — rerun One vs standalone and tier review
T−30 days — seat map audit; remove unused add-ons
T−14 days — finance confirms PO or card for renewal
T−7 days — document any headcount change affecting One cap
Day 0 — renewal processes; file seat map PDF in finance folder

Token and Assistant review: AI token pools governance.

Anti-patterns

Annual on Free Forever upgrade day — tier unproven
Annual Growth for Orbit only — partner motion not live yet
Ignore One cap — 16th hire on One Team without Growth plan
Finance-only decision — no RevOps seat map
Skip mid-year review — annual is not set-and-forget

Document template (one page)

Before annual commit, RevOps publishes:

Headcount — by line, tier, add-on
Monthly run rate — current month invoice screenshot
Annual run rate — 10-month total
One alternative — one-line breakeven note
Upgrade triggers — what would force tier or One change mid-year
Owners — billing admin, finance approver, renewal reminder

MCP prompt (billing snapshot)

Summarize current plan lines, tiers, add-ons, and teammate count. Compare monthly run rate to One Team and One Growth flat pricing — read only, for annual commit memo.

Mid-year change discipline

Annual billing does not freeze your business — headcount, motion, and apps still change. What changes is how carefully you manage mid-year adjustments:

Seat adds — prorate new teammates onto annual cadence in Admin → Billing; document why
Tier step-ups — Starter → Team mid-year is common; avoid downgrades that fight annual psychology
Add-on trials — run Flow or Ledger monthly on one seat before annualizing org-wide
One migration — moving standalone → One mid-year needs full seat map reset; schedule quiet week
Offboarding — remove seats same day; annual does not refund unused months automatically

Seat timing guide: land and expand seat timing.

Finance + RevOps handoff

Owner	Before annual	After annual
RevOps	Seat map, tier proof, One math	Quarterly seat audit
Finance	PO, card, 10-for-12 invoice approval	Renewal calendar T−60
IT / security	SSO need on One Growth	Access review at renewal
Leadership	Sign-off on headcount cap vs One tier	Mid-year hiring vs cap check

Billing operations detail: in-app billing RevOps playbook.

Scenario: dual-line team crossing One breakeven

A twelve-person team runs six Momentum Team and six Resolve Team seats with Ledger on two finance seats:

Line item	Monthly
Momentum Team × 6	$234
Resolve Team × 6	$234
Ledger × 2	$70
Total	$538

Standalone already exceeds One Team at $499/mo — annualizing standalone leaves money on the table versus One annual at $4,990 (10 months). Run this comparison before any dual-line annual commit.