Editorial note. Edition prices are from salesforce.com/sales/pricing as of September 2026. The renewal uplift is the widely reported default in Salesforce order forms (7%, negotiable to 3–5% or flat) rather than a published list term. Salesforce is not affiliated with Sonic AI. Edition names were restructured this year; the billing shape has been the same for two decades.
Salesforce is the contract every enterprise SaaS order form descends from. Per user, per month, by edition; billed annually, in advance; users added mid-term at the contracted rate, prorated to the end of the term; no reductions until renewal; and a price escalator built into the renewal. If your company sells annual seat contracts to enterprises — and especially if your renewals carry an uplift — this is your reference bill, and the uplift is the part most billing systems cannot express.
What Salesforce charges
| Edition | Per user / month | Billing |
|---|---|---|
| Starter Suite | $25 | Annual |
| Pro Suite | $100 | Annual |
| Core | $195 | Annual |
| Advanced | $395 | Annual |
| Max | $550 | Annual; includes the Agentforce AI suite and a Flex Credit allotment |
Contract mechanics, as they appear in a typical order form:
- The full year of seats is invoiced up front at term start.
- Users added mid-term are charged at the same per-user rate, prorated from the add date to the end of the term (co-termed).
- Seat count cannot be reduced until the renewal date.
- Renewal carries a price uplift — commonly 7% a year by default, negotiated down to a cap or held flat in larger deals — and the renewal quantity defaults to the current seat count.
The model underneath
- Seat-based linear, annual basis, in advance for the whole term.
- Proration policy: added seats only — adds are prorated to term end and co-termed; removals are ignored until renewal.
- Multi-year phases with a price change — the renewal is not a new contract, it is the next phase of the same schedule at
rate × 1.07. - Editions are simply different catalog rates; an edition upgrade mid-term is a phase change at a higher rate, prorated.
The uplift is what makes this a schedule rather than a subscription. Year 2 at $107 and year 3 at $114.49 are known at signature. A billing system that stores "$100 per user" as a single number has to be edited by hand every anniversary, and the person who does it is the one who forgets the customer whose cap was 5%.
What the term looks like
A Pro Suite customer, 40 users, annual term Sept 1 2026 – Aug 31 2027, 7% uplift; 5 users added Feb 1 2027:
| Invoice | Line | Qty | Rate | Amount |
|---|---|---|---|---|
| Sept 1 2026 | Pro Suite — Sept 2026 – Aug 2027 (in advance) | 40 | $100 × 12 | $48,000.00 |
| Feb 1 2027 | Pro Suite — added users, Feb 1 – Aug 31 2027 (co-termed) | 5 | $100 × 7 | $3,500.00 |
| Sept 1 2027 | Pro Suite — Sept 2027 – Aug 2028, year 2 at +7% | 45 | $107 × 12 | $57,780.00 |
The renewal invoice picks up the 45-user count and the escalated rate without anyone re-keying either. The Feb add walks calendar months (seven of them) of a monthly-basis rate, which is why it is a round $3,500 and not $100 × 5 × 212/365.
Where annual seat contracts go wrong
- The uplift lives in someone's head. If the escalator is not on the schedule, renewals are re-quoted from memory and the cap a customer negotiated gets missed.
- Co-terming. A mid-term add must end on the term end date, not run twelve months from its own start — or the renewal has two seat cohorts on different dates.
- No reductions until renewal. The billing system must not credit a removed seat mid-term when the contract says it cannot be removed; that is a proration-policy setting, not a manual override.
- Revenue over the term, cash up front. $48,000 is billed on day one and recognised at $4,000 a month. The journal has to carry the deferred balance and release it — and the Feb add starts its own release schedule.
- Edition upgrades. Pro → Core mid-term is a phase change at a new rate, prorated, on the same schedule, not a second subscription.
Billing this shape on Sonic AI
A Salesforce-style order form is one billing schedule on Sonic with a seat-based linear list price on an annual in-advance basis and proration policy added seats only. Mid-term adds are seat events prorated by calendar units to term end. The renewal is the next schedule phase, created from the contract's renewal clause with its stated price change, so the year-2 rate and the roster at renewal are on the schedule from the day the PDF is ingested. Revenue is recognised straight-line over each phase, with the waterfall showing the deferred balance releasing month by month.
See contracts, subscription billing, and revenue recognition.
If you sell annual seat contracts
- Is the renewal uplift on the schedule, per customer, with its cap?
- Are mid-term adds co-termed and prorated by calendar month?
- Is "no reductions until renewal" a policy setting rather than a manual rule?
- Does the deferred revenue release per phase, including the mid-term add's own schedule?
Bring a multi-year order form to a demo — we will schedule the term, the co-termed adds and the uplift from the PDF.
Similar pricing models
Annual per-user editions with co-termed adds and a renewal escalator are the enterprise standard: Workday, ServiceNow, SAP SuccessFactors, Zendesk Enterprise and Microsoft 365 enterprise agreements all bill this way, most with a published or negotiated uplift. Monthly with proration in both directions is Slack; per-user with tiered rates is Jira; the order form with usage bands and onboarding on top is HubSpot.
Related terms: renewal clause, schedule phase, seat-based billing, deferred revenue.