.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
How to Handle SaaS Customers Who Want a 99 Plan When You Charge 299
A customer asking for a $99 plan when your company charges $299 is not merely asking for a discount. They are telling you something about their budget, their confidence in the product, their intended use, or their place in your market. Treat the request as a negotiation over price alone, and the sales team will slowly teach the market that $299 is optional.
The stakes are larger than one deal. A poorly handled concession can cut ARR, create renewal friction, confuse the product roadmap, and reward customers who negotiate hardest rather than those who fit best. A well-designed response can open a new segment without weakening the plan built for your core customer.
Monetizely's position is clear: do not sell the full $299 promise for $99. Either build a genuinely narrower $99 offer for a repeatable lower-value segment, or hold the $299 price and change the rollout, scope, or commitment terms.
A $99 request usually reveals a mismatch before it reveals a price problem
The phrase “we only have $99” covers several very different situations. A five-person startup may need only one workflow and self-serve support. A 500-person company may want enterprise controls, implementation help, and custom integrations, but hope to pay startup prices. Those are not variants of the same buyer problem.
Monetizely's 5-Step Pricing Framework puts this distinction in the proper order. First, define the business goal and the customer segments. Second, build packages that fit those segments. Third, choose the metric you charge on. Fourth, set the actual price points. Fifth, make the model work through product entitlements, billing, sales rules, and renewal processes. The sequence matters because a price cannot fix a segment definition or package design that was wrong from the start. Monetizing Agentic AI develops this same logic in greater depth.
Before responding to a buyer, the account team should diagnose what the $99 request actually means.
Exhibit 1: The same $99 request can call for four different responses
| What the customer says or does | What it may actually mean | Best commercial response |
|---|---|---|
| “We only need this for one small team.” | The customer has a narrow use case and may belong in an entry segment. | Offer a limited $99 package if that use case repeats across the market. |
| “We need the whole platform, but procurement capped the budget.” | The account wants a $299 outcome at a $99 price. | Hold the package boundary. Trade only for a measurable concession, such as annual prepayment. |
| “We are not sure adoption will stick.” | The buyer sees adoption risk, not necessarily a value gap. | Offer a phased rollout, a short paid ramp, or a smaller initial deployment. |
| “Your competitor starts at $99.” | The comparison may be between unlike offers. | Reframe around included scope, support, security, implementation, and limits. |
| “We will expand later.” | The buyer may be real, or may be using a common negotiating line. | Price the current commitment correctly and make expansion an upside, not the rationale for underpricing now. |
The table points to a simple rule: a lower number should follow a different customer need, not a louder objection.
The first question is not, “Can we afford to discount this account?” It is, “Do we want to serve this type of customer at $99?”
A company pursuing rapid market entry may decide that a $99 plan is worth offering to gain adoption among small teams. A company trying to raise average contract value, fund high-touch onboarding, or protect gross margin should not make the same choice. Both strategies can be rational. Confusion begins when a company says it wants premium customers but asks its sales team to close them with entry-level economics.
The segment test should be concrete. A viable $99 segment has a repeatable profile:
- A limited and common use case, such as one team, one workspace, or one department.
- Low need for implementation, custom work, dedicated support, or legal review.
- A clear reason to upgrade, such as more users, more workflows, higher volume, or stronger controls.
- Enough prospective accounts to justify product, billing, and support investment.
- Economics that remain sound after onboarding, support, cloud costs, and sales expense.
A single buyer does not create a segment. Twenty similar buyers who need the same constrained version of the product may.
When a seller grants a 67% discount on the same product, the buyer receives the full value while the vendor collects less revenue. The next buyer will hear about the exception. The renewal team will inherit the reference point. Product leaders will struggle to explain why a customer on a $99 contract has access to features designed to justify $299.
A real entry plan operates differently. It gives a smaller customer a complete path to a useful outcome, while withholding the depth, scale, and service level that make the $299 plan valuable.
Exhibit 2: A defensible $99 offer changes the offer, not just the invoice
| Design choice | $99 entry plan | $299 core plan | Why the distinction holds |
|---|---|---|---|
| Intended customer | One team with a standard use case | A department or company with broader needs | Buyers can recognize themselves in the offer. |
| Product scope | Core workflow, standard templates, limited automation | Advanced workflows, deeper configuration, broader collaboration | The higher tier solves more complex work. |
| Scale | One workspace, lower included volume, fewer admin controls | Multiple teams, higher limits, centralized administration | Growth creates a natural reason to upgrade. |
| Service model | Self-serve setup, documentation, community or standard support | Guided onboarding, priority support, success coverage where justified | Service effort remains aligned with revenue. |
| Commercial terms | Standard card or annual self-serve terms | Annual contract, larger commitment, procurement support | The selling motion matches the account value. |
The practical meaning is straightforward: customers should be able to succeed at $99, but they should not be able to buy a $299 operating model for $99.
Feature gates should not be arbitrary. Remove capabilities that either raise your cost to serve or solve a more valuable buyer problem. For example, a lower tier may exclude SSO, advanced permissions, sandbox environments, premium support, high-volume automation, or complex integrations. Those limits are easier to defend than a vague message that the $99 customer receives “fewer features.”
The market offers a useful lesson. Mature SaaS companies rarely maintain price gaps merely by changing a few cosmetic features. They change the customer’s operating model: scale, control, support, automation, or the breadth of work covered.
Exhibit 3: Four SaaS pricing pages show how higher tiers earn higher prices
| Vendor and displayed pricing as of September 8, 2026 | Lower-priced offer | Higher-priced offer | What changes with the higher tier |
|---|---|---|---|
| Salesforce Sales Cloud | Pro Suite: $100 per user/month, billed annually | Enterprise: $175; Unlimited: $350 per user/month, billed annually | Enterprise adds advanced pipeline management, deal insights, conversation intelligence, and Agentforce. Unlimited adds predictive AI, sales engagement, a full sandbox, and premier success support. (salesforce.com) |
| HubSpot Marketing Hub | Starter: $20 per seat/month | Professional: $890/month with three Core Seats, plus required $3,000 onboarding | The move changes the buying model from a seat-level entry plan to a broader marketing platform with a base subscription, included seats, automation, and contact-based expansion. (legal.hubspot.com) |
| Zendesk | Support Team: $19 per agent/month, paid yearly | Suite Professional: $115 per agent/month, paid yearly | The higher package adds omnichannel service, AI capabilities, skills-based routing, and more advanced reporting and workflow tools. (zendesk.com) |
| Atlassian Jira | Standard: $7.91 per user/month | Premium: $14.54 per user/month | Premium adds cross-team planning, dependency management, more automation, unlimited storage, 24/7 critical support, and a 99.9% uptime SLA. (atlassian.com) |
The pattern is consistent: higher prices attach to broader responsibility, greater scale, stronger controls, or more service, not simply to a more expensive logo on the invoice.
A $99 plan can follow that model. It should be designed for a buyer who truly needs less, not for an enterprise buyer who negotiates more aggressively.
Step three of the framework asks what the company measures and bills for. A customer’s request for $99 sometimes signals that the current meter is creating fear.
Consider a collaboration product sold at $299 per workspace per month. A prospect with one pilot team may resist because it expects only intermittent use for the first quarter. Cutting the whole plan to $99 is one response. A better response may be a smaller workspace package, a paid pilot with explicit limits, or a ramp that converts to the standard plan once a defined activation point is reached.
Three tests keep this decision disciplined:
- Value alignment: The meter should track something the customer recognizes as useful, such as active users, managed accounts, transactions, or a governed workspace.
- Risk perception: New or uncertain buyers may need a smaller initial commitment, while established customers often value a predictable bill.
- Operational fit: The company must be able to measure usage accurately, explain the invoice, and enforce the rules without manual exceptions.
A variable meter is not a discount strategy. If the current primary meter already matches customer value and is easy to understand, retain it. Build the $99 package around lower entitlement, lower scale, or a smaller commitment.
The price point comes fourth because it should be the output of earlier decisions. Many teams reverse the sequence. They begin with the buyer’s target number, then work backward to invent a rationale.
That approach produces fragile plans. A $99 tier needs a business case that goes beyond “some prospects asked for it.” The company should know who will buy it, what they will receive, what it costs to serve them, what triggers an upgrade, and how many such buyers exist.
Exhibit 4: Score whether the request supports a new $99 package or a firm no
| Evaluation question | Score 0 | Score 1 | Score 2 |
|---|---|---|---|
| Is the use case common across a recognizable group of prospects? | One-off request | Seen occasionally | Repeats across a clear segment |
| Can the customer succeed without the $299 plan’s high-cost features or service? | No | Partly | Yes |
| Does the buyer have a clear upgrade trigger? | No visible trigger | Possible future need | Defined trigger tied to growth or use |
| Can the company serve the account economically at $99? | Margin or support risk | Uncertain | Sound economics at expected use |
| Can sales qualify and route the segment consistently? | Requires case-by-case judgment | Some guidance exists | Clear eligibility rules exist |
| Total score | Commercial decision |
|---|---|
| 8-10 | Test a purpose-built $99 package with a defined segment. |
| 5-7 | Keep the $299 package, but consider a phased rollout or structured ramp. |
| 0-4 | Decline the request or disqualify the account. A lower price would mask a poor fit. |
The scoring table does not replace judgment. It prevents the sales team from treating every budget objection as proof that the market needs another tier.
Buyers usually focus on the monthly gap: $99 versus $299. Sellers should understand the gap over the life of a relationship, then connect it to the economic value of the work being improved.
For a buyer, the higher plan must clear a modest but real threshold. For the vendor, the same $7,200 difference may fund onboarding, support, product development, and the sales capacity required to serve a more demanding account.
Exhibit 5: The $200 monthly gap is $7,200 over a three-year contract life
| Measure | $99 plan | $299 plan | Difference |
|---|---|---|---|
| Monthly subscription spend | $99 | $299 | $200 |
| Subscription spend over 36 months | $3,564 | $10,764 | $7,200 |
| Monthly labor time that must be avoided to cover the gap at $75/hour | - | - | 2.7 hours |
The implication is not that every $299 plan is justified. Rather, the seller should be able to show why the fuller package saves more than roughly 2.7 hours of work per month, prevents a meaningful error, accelerates a revenue process, or enables a business capability the $99 plan cannot support.
A disciplined value conversation changes the discussion. Instead of asking, “Can we meet $99?” the seller can ask, “Which plan gives your team the lowest total cost to reach the result you need?”
A company may still choose to discount. The key is to make the exchange explicit and economically useful.
Discounts can be appropriate when the customer gives something measurable in return:
- Annual prepayment that improves cash collection and reduces billing cost.
- A multi-year commitment with a defined minimum spend.
- A smaller initial deployment that converts to the standard rate at a stated date or usage threshold.
- A strategic, leadership-approved market-entry investment with a fixed budget and a documented learning goal.
None of those is equivalent to allowing a rep to reprice the $299 plan to $99 because a deal is late in the quarter. The former choices create a commercial trade. The latter turns list price into theater.
Operational discipline matters here. Product entitlements must match the contract. Billing must recognize the correct tier and any ramp dates. Sales compensation should not reward a $99 exception as though it were a full-price $299 win. Step five exists because pricing fails when these systems tell different stories.
Monetizely's position is not that every SaaS company should avoid a $99 tier. Many should build one. The right $99 plan can widen the funnel, shorten sales cycles, and establish a clear path toward a $299 plan.
The discipline lies in refusing to confuse an entry offer with a discounted premium offer. A $99 plan must be a designed product for a defined segment, sold through a repeatable motion, with clear limits and a credible upgrade path. If those conditions do not exist, the $299 price is not the problem. The account is either asking for a smaller deployment, a different commitment structure, or a product the company should not sell at all.
What operators should do next:
Set a portfolio target for entry, core, and enterprise revenue. Decide how much ARR the company wants from each segment before the sales team begins to create exceptions.
Add a structured “price objection” field to CRM. Track whether losses stem from budget, missing capability, deployment risk, procurement timing, or a true lower-segment need.
Review $99 requests quarterly as product evidence. Look for repeated customer profiles, not individual anecdotes, and use the pattern to decide whether a new package deserves investment.
Measure entry-plan upgrades and support load separately. A $99 offer is working only if it attracts qualified customers, serves them efficiently, and creates credible expansion.
Give one executive owner authority over pricing exceptions. Sales can surface evidence and propose trades, but one accountable leader should protect the architecture across quarters.
Footnotes
- Monetizing Agentic AI: A Handbook for Transformation - https://www.amazon.com/Monetizing-Agentic-AI-Handbook-Transformation/dp/B0H7Z13VKJ/
- Salesforce, “Sales Cloud Pricing,” accessed September 8, 2026. (salesforce.com)
- HubSpot, “Product & Services Catalog,” accessed September 8, 2026. (legal.hubspot.com)
- Zendesk, “Pricing Plans,” accessed September 8, 2026. (zendesk.com)
- Atlassian, “Jira Pricing,” accessed September 8, 2026. (atlassian.com)