Pricing Enterprise Deals When the User Count Is Unknown

Pricing Unknown User Count: The Pilot-Based Approach

Most enterprise buyers ask "what's the price?" before they know how many users they need. If you quote a number without definition, you lose leverage and invite scope creep. Per Bessemer's State of the Cloud 2026 (bvp.com/atlas/state-of-the-cloud-2026), the median public cloud company sees 110-120% net dollar retention precisely because they price the *land* small and let *expansion* drive ACV - the top quartile clears 130%. Your job is to engineer that same motion deal-by-deal. The pilot pricing model below is how you do it without a CFO's quarterly approval cycle.

THE PRICING TRAP: You: "It's $10K/month for up to 25 users" Buyer: "We might need 50 users, but we don't know yet" Now you're in a conversation about $20K/month before they've even used it - and any concession you make now is anchored against a fictional 50-seat baseline. Worse, your champion will use *your* 50-seat anchor in their internal pitch, then come back saying "exec said only 30 - can you hold the 50-seat price?" You just bought yourself a 40% discount you didn't agree to.

THE FIX: Tiered Pilot Pricing (3 stages)

Tier 1: Pilot (90 days, capped scope)

• User count: 3-5 core users (typically 1 manager + 2-3 reps + 1 ops/admin)
• Price: $3,000/month flat (roughly 30-40% of full-scale unit economics)
• Terms: Month-to-month, no auto-renew, defined success criteria in writing
• Telemetry stack you must have on Day 1: WAU, MAU, feature-event funnel, ROI dashboard, and a per-user activation checklist. If you can't measure adoption, you can't enforce the tier.
• Why 90 days: Per Gartner's B2B Buyer Sentiment research (gartner.com/en/sales/research), enterprise buyers need ~60-75 days of usage before they'll commit to a steady-state seat count. 30 days isn't enough; 180 days lets them coast on pilot pricing forever.
• Activation gate (week 2): every pilot user must complete the activation checklist by day 14. Users who don't activate get yanked from the pilot and replaced - you do not want a 5-user pilot where 2 users never logged in showing up in your day-60 telemetry.
• Kickoff artifact: Mutual Pilot Plan (MPP) signed at day 0. One page, names the exec sponsor, 3 success metrics with thresholds, and the day-60/day-90 dates. No MPP, no pilot.

Tier 2: Expansion Commitment (Day 60 decision point)

• Buyer commits to user count based on adoption telemetry from days 1-60
• Pricing snaps to a published tier table at 80-85% of list (volume-earned, not negotiated)
• Example: "If WAU/MAU is 80%+ and you expand to 15 users, price is $6K/month"
• Key: They commit at day 60, not day 1 - by then they have data, not guesses
• Decision artifact: a one-page Expansion Memo signed by the exec sponsor that states (a) seat count, (b) start date, (c) tier price, (d) which adoption metric was met. No memo = no expansion price.
• Telemetry transparency: share the WAU/MAU dashboard with the buyer weekly. Surprises at day 60 are a sign you didn't manage the pilot - they're also the #1 reason expansion deals slip a quarter.
• Forecast posture: the deal does NOT enter Commit until the Expansion Memo is countersigned. AEs who push pilot deals to Commit at day 1 are the same AEs whose Q4 forecasts blow up.

Tier 3: Negotiated Price (only for non-standard terms)

• Volume discount: 15+ users = 10% off list, 25+ = 15% off
• Term discount: 12-month = 5% off, 24-month = 10% off (stack with volume up to a 20% cap)
• Support tier: Standard included; premium = +15% of ACV add-on, never bundled "free"
• Payment terms: Net-30 default. Net-60 costs 1.5%. Net-90 costs 3%. Never give Net-90 free - it's working capital you're loaning unsecured.
• MFN (Most-Favored-Nation) clauses: decline by default. If forced, scope MFN to "same SKU, same tier, same term, same region" - never raw price.
• Auto-renew + cap: 12-month auto-renew with a 7% cap on price escalation. No cap = procurement will spike year 2 negotiations.

PUBLISHED PRICING TEMPLATE (for a ~$50-80K ACV enterprise motion):

HOW TO PRESENT IT (verbatim script, refined):

> "Here's how we typically structure this when seat count is still TBD: 90-day pilot with your core 5 users at $3K/month, month-to-month. At day 60, if adoption is at or above 80% weekly active and you've validated ROI, you commit to a seat tier from this published table. You're not paying for users you don't have, and we're not pricing on guesses. Either of us can walk at day 90 if it's not working. Want me to send the published tier sheet so you can socialize it with procurement before we paper anything?"

The last sentence is the close - it gets the tier sheet into the procurement workflow on *your* terms before they draft an RFP.

Objection-handler one-liners (memorize these):

• "Why $3K?" -> "It's our standard pilot price for 3-5 users. It's the lowest we publish."
• "Why not free?" -> "Free pilots produce free results. Paid pilots produce committed buyers."
• "Can we get a discount on the pilot?" -> "Pilot pricing is already a discount. Expansion pricing is where you earn structural savings."
• "What's the all-in price for 25 users?" -> "Tier 4 list is $14K/month, ramps to $11.9K with volume - but I'd rather you commit to that tier with day-60 data than guess today."
• "We need a single number for the budget request." -> "Use $63K Year-1 (the 5-then-15 ramp). That's the conservative budget number. If adoption beats 80%, the next tier is $102K - good problem to have."

EXPANSION TRIGGER (the contract clauses that do the work):

4.3 Expansion Commitment. On or before Day 60 of the Pilot Term, Customer shall elect a User Tier from Schedule A, conditioned on: (a) WAU/MAU ratio >= 80% measured by Provider telemetry (b) Written executive sponsor approval of ROI (c) A committed seat count (no "TBD" or "up to" language) Failure to elect by Day 60 terminates the Pilot at Day 90 with no auto-renewal and no expansion pricing carryover. Provider retains no obligation to honor pilot pricing in any future engagement.

4.4 Telemetry Audit Right. Customer waives objection to Provider's adoption telemetry methodology, provided Provider shares WAU/MAU dashboards weekly during the Pilot Term. Disputed metrics must be raised within 5 business days of weekly report or are deemed accepted.

4.5 Renewal Cap & Co-Term. Annual price escalation capped at 7% on seat-tier list. Multi-product co-termination requires 90-day notice; mid-term seat reductions accrue at the next-lower tier price for the remainder of the term, no refund for current period.

4.6 No Side Letters. Any pricing concession, discount, payment-term modification, or expansion-pricing carryover not appearing in this Order Form or a fully countersigned Amendment is void. Email, Slack, and verbal commitments do not bind Provider.

The "deemed accepted" language in 4.4 is what kills day-58 disputes about whether adoption actually hit 80%. The 7% cap in 4.5 is the year-2 negotiation killer; without it, your CSM is re-selling the contract every renewal. Clause 4.6 is the AE-discipline clause - it stops your own team from giving away pricing in Slack DMs.

Bear Case: Where This Breaks (read this before you ship it)

Adversarial pushback you must rehearse:

1. "Procurement won't sign a tier table - they need a fixed price." Real. Mid-market and PE-backed buyers often have procurement gates that disallow indexed/escalator pricing. Counter: offer a fixed annual contract at the 15-user tier with a true-up clause (overage @ list, underage non-refundable). You've now anchored at 15 users instead of "TBD." If they insist on a fixed price below the 15-user tier, that itself is data: they don't actually need the tool.

1. "They'll pilot, gather feedback, and rebuild internally." This is the real risk for tools with thin moats. Mitigation: pilot scope must include data residency, integrations they'd have to rebuild (Salesforce, HubSpot, Slack, SSO), and a usage threshold below which the pilot auto-extends (so they can't extract value cheaply and exit). Build in a "data export at termination" clause that requires 30-day notice and an export fee equal to one month of expansion pricing - this prices in the rebuild risk.

1. "Day 60 is too aggressive - they need a quarter." Sometimes true for regulated buyers (healthcare, finance). Acceptable variant: 90/180 instead of 60/90, but pilot price escalates 25% at day 90 to discourage stalling. Per Pavilion's 2026 Compensation & Benchmark Report (joinpavilion.com/compensation-report), enterprise sales cycles in the >$100K ACV band have stretched to a median of 96 days in 2026 - plan for that, but don't subsidize it.

1. "You'll lose deals to vendors who quote a flat $X." Yes - and those are the deals you want to lose. A flat quote for an unknown user count is a margin-erosion event waiting to happen. Bridge Group's 2026 SDR Report (bridgegroupinc.com/blog/sales-development-report) shows that vendors who flat-quote into ambiguous accounts post 18-22% lower gross margin on those logos in year 2.

1. "What if pilot adoption is 70%, not 80%?" Don't move the goalpost. Either extend pilot at 1.25x pilot price for 30 days OR exit. Lowering the bar trains buyers to under-deliver on every future commitment. Track which CSMs/AEs request goalpost moves - it's a leading indicator of churn risk on those accounts.

1. "Champion left mid-pilot - now what?" Pause the day-60 clock with a written amendment, but only for 30 days. If the new exec sponsor isn't onboarded and signing telemetry reviews within 30 days, terminate. Do not let "champion churn" become an indefinite extension lever.

1. "They want a parallel pilot with two competitors at the same price." Charge for it. Bake-offs are 2x the work for 1x the deal probability. If they insist on a parallel pilot, the pilot fee doubles to $6K/month and is non-refundable. If they balk, they weren't serious about you anyway.

1. "Mid-pilot, they want to add 3 more users 'just to test.'" Allow it once, free. After that, $500/user/month overage. Track this in the deal CRM - "expansion creep during pilot" is a positive signal at day 60.

1. "Buyer wants to start the clock when 'production data' is loaded, not at signing." No. The pilot clock starts at signing or at provisioning, whichever is earlier. "Production data readiness" is a buyer-side problem; if you let it gate your clock, expect a 6-month free trial. Offer a 14-day implementation grace period if needed - that's it.

1. "They want their MSA, not yours." Acceptable IF the MSA permits Schedule A tier pricing, telemetry collection, deemed-accepted dispute windows, and 7% renewal cap. If their MSA strikes those, walk back to your paper or restructure as a click-through to the pilot only.

1. "Two BUs, same legal entity, want separate pilots at the pilot price." No. One legal entity = one pilot. Second BU pays the second-tier price ($5.2K-$8.5K/mo depending on seat count). Otherwise enterprise buyers will fragment by department and run 4 concurrent pilots at $3K each = your enterprise discount, paid by you, given for free.

Field-Tested Edge Cases (production-grade only)

• Government / education buyers: the day-60 commit clause must be reframed as a "best-efforts election" because GovCloud/EDU procurement timelines run 90-120 days minimum. Use a 90/120/150 cadence and surcharge the pilot 15% to compensate.
• PE-backed buyers in transition: if the buyer is mid-acquisition, pause the clock with a 30-day written extension - but require change-of-control language giving you the right to renegotiate the tier table if ownership changes during the term.
• Reseller / channel deals: reseller margin (typically 15-20%) is paid out of the *list* price, not the *ramp* price. Make this explicit in the partner addendum or you'll find your channel lieutenant has been re-selling the ramp price net of margin.
• Multi-currency: publish tier table in USD only. FX exposure is the buyer's problem unless they want to pay a 5% FX-stability premium for a EUR/GBP/INR quote locked for 12 months.
• Compliance-heavy verticals (HIPAA, FedRAMP, SOC2): the pilot price assumes baseline compliance. Custom DPAs, BAAs, or data-residency requirements that exceed standard add 15-25% to the pilot price - never absorb compliance work for free during a $3K/month pilot.

DISCOUNTING RULES (avoid these):

• Don't discount on the pilot - $3K is already a deal
• Don't lock in a deep "if they expand later" discount (you lose all leverage)
• Don't do "blended" pricing ("let's say 15 users average, $9K/month") - they'll stuff in 25 and claim "we thought 15 was average"
• Don't discount because "we don't know user count yet" - that's their problem, not yours
• Don't let a single AE approve >10% off - route to deal desk
• Don't grant MFN clauses without scoping language (see Tier 3)
• Don't let pilots run >120 days - the day-90 termination clause exists for a reason
• Don't accept "pending board approval" as a reason to extend the pilot price - that's a not-yet-qualified deal

WHAT TO DISCOUNT ON (legitimate value exchanges):

• Term length (12+ months = 5-10% off; 24+ months = 10-15%)
• Verified adoption (90%+ WAU earns the next tier discount automatically)
• Multi-product attach (2+ SKUs = 5-10% package discount)
• Reference rights / case study cooperation (3-5% for written + named exec)
• Logo rights for marketing (2-3%)
• Co-marketing webinar or conference appearance (2-5%, one-time)
• Beta participation on new SKUs (2-4%, in exchange for product feedback rights)
• Prepay annual at signing (3-5%, in exchange for working-capital benefit)

EXPANSION MATH (concrete worked example):

• Pilot: 5 users x $3K/mo x 3 months = $9K
• Expansion: 15 users x $6K/mo x 9 months = $54K
• Year 1 ACV: $63K
• Counterfactual flat 15-user contract upfront w/ 15% discount = $61.2K
• Net: you captured ~$1.8K more AND the buyer feels they earned the deal - psychological ownership drives renewal
• Year 2 NDR (if adoption holds): typical expansion to 20-user tier = $102K = 162% logo growth
• 3-year cumulative: $63K + $102K + $130K (25-tier) = $295K LTV vs $61.2K x 3 flat = $183.6K. You leave +$111K LTV on the table by flat-quoting upfront.

Quick-reference deal-desk approval matrix:

Related Pulse RevOps playbooks

• /knowledge/q237 - Handling buyers who demand a 6-month free pilot
• /knowledge/q283 - Pricing deals with hidden multi-year volume commitments
• /knowledge/q288 - Positioning concessions as scope-creep trades vs. discounts
• /knowledge/q594 - Deal-desk approval authority to prevent pricing hero-culture
• /knowledge/q595 - Discount governance vs. discount controls
• /knowledge/q256 - Pricing localization across regions (FX, taxes, parity)
• /knowledge/q1731 - Outreach platform buy-vs-build decision
• /knowledge/q1598 - Compute pricing comparison: Snowflake / BigQuery / Redshift
• /knowledge/q1161 - Per-event pricing and add-ons for service-tier deals

TAGS: enterprise-pricing, user-count, pilot-pricing, tiered-deals, pricing-strategy

Related on PULSE

• [How do you restrict field-level CRM visibility without breaking integration user permissions?](/knowledge/q9859)
• [How do you restrict field-level CRM visibility without breaking integration user permissions?](/knowledge/q9844)
• [Should Datadog kill its Real User Monitoring module?](/knowledge/q1695)
• [What is the right framework for AE discount autonomy: should it scale by tenure, deal size, quota attainment, or manager override count?](/knowledge/q9516)
• [What's the realistic break-even cup count per day for a 1200-square-foot coffee shop, and how long does it take to reach it?](/knowledge/q1131)
• [How do you know when to refresh or replace an escape room theme — by month count, repeat-customer ratio, or review trend?](/knowledge/q1139)

Sources

• Gartner — pricing models and metrics for enterprise software licensing
• Forrester Research — enterprise deal structuring and value-based pricing frameworks
• SaaS Metrics (e.g., OpenView, SaaStr) — guidance on per-user versus usage-based pricing
• Harvard Business Review — strategic pricing principles for B2B and enterprise sales
• Pragmatic Institute — product pricing and packaging best practices for tech companies
• U.S. Small Business Administration (SBA) — general pricing strategies for business-to-business contracts

FAQ

What if the prospect refuses to do a pilot? If they won't commit to a 5-user, 90-day pilot, they're not ready for a real enterprise deal. Without pilot data, you have no WAU/MAU metrics to gate expansion. Politely walk away or offer a shorter 30-day proof of concept at the same $3K/month—but never quote a full price against an unknown count.

How do I handle a prospect who demands a per-user price upfront? Don't give a flat per-user number—anchor on the pilot. Explain that pricing depends on actual usage patterns, which the pilot will reveal. You can share a general range (e.g., "$X–$Y per user per month at 80–85% of list after tier commitment"), but never lock in a price before you see data.

What happens if the pilot shows low engagement (WAU/MAU below 80%)? At day 60, if WAU/MAU is below 80%, don't gate expansion to a full tier table. Extend the pilot for another 30–60 days, or offer a smaller per-user rate tied to actual usage. No commit means the pilot ends at day 90 with no carryover—no discounts for uncertainty.

Can I offer a discount if they commit to a longer term? Yes—discount only on term length (e.g., annual vs. monthly), adoption volume, multi-product bundles, and reference willingness. Never discount because the user count is unknown. A 2–3 year term might earn 10–15% off list, but only after the pilot confirms engagement.

What if the user count is huge (e.g., 10,000+)? Still start with the same 5-user, $3K/month pilot. The tier table will scale based on actual usage data from the pilot. For very large prospects, you might offer a volume tier at 80–85% of list after day 60, but never quote a massive number upfront—anchor small, gate on data.

How do I explain this approach to a skeptical procurement team? Frame it as risk mitigation: "We're pricing the land small to prove value before scaling. The pilot gives you a low-cost test, and expansion pricing is based on your real usage—not a guess. No hidden fees, no lock-in until we both see the data." Procurement typically respects data-driven pricing over flat guesses.