Sample deliverable: deciding between a price increase and a cheaper tier
This is a **real, unedited output** from our consulting pipeline, produced for a prompt about a
5-person B2B SaaS at $30k MRR with 40 customers on a flat $750/month plan, asking whether to
raise prices 20% for new customers or add a cheaper tier. The question is a generic one, so
nothing here is confidential.
Two facts worth stating up front, because they are the honest version:
- **It took about six minutes** end to end (the task left `running` at 240s and finished at ~360s).
A trivial prompt finishes in about 81 seconds; a real decision question does not.
- **It cost a few cents of model tokens**, metered from the same balance you top up with.
---
1. Executive Summary
**Decision: Raise prices 20% for new customers. Do not add a cheaper tier at this time.**
- Raise the standard rate from **$750/month to $900/month for new customers**.
- Grandfather the existing 40 customers at $750/month, at least for a defined period.
- Hold off on a cheaper tier until there is clear evidence of a distinct lower-price segment with acceptable unit economics.
The company is at a scale where improving ARPU, margin, and positioning matters more than adding operational complexity or chasing lower-end volume. A 20% increase is moderate, protects the existing revenue base, and requires minimal operational change.
---
2. Current Economics
| Metric | Value |
|---|---:|
| Customers | 40 |
| Price | $750/month flat |
| MRR | $30,000 |
| ARR run rate | $360,000 |
| ARPU | $750/month |
| Team size | 5 |
The business has a single plan, one price point, and a small team. This means pricing changes should be simple and should avoid creating new support, onboarding, or packaging burdens unless the ROI is very clear.
---
3. Option Analysis
### Option A: Raise prices 20% for new customers
Proposed new price: **$900/month**
**Revenue impact:**
Each new customer adds **$150/month more** than under the current price. Existing revenue remains stable at $30k MRR.
For example, acquiring 10 new customers in a year would generate:
- Current pricing: `10 × $750 × 12 = $90,000`
- New pricing: `10 × $900 × 12 = $108,000`
- Incremental revenue: **$18,000**
The short-term revenue lift is modest because the existing base is grandfathered, but the strategic benefit is meaningful: you reset the value anchor without risking current customers.
**Key advantages:**
- Low operational complexity: only sales and marketing pricing updates.
- Low churn risk for existing customers.
- Improves unit economics and ARPU.
- Positions the product as more valuable.
- Keeps the product and packaging unchanged.
**Main concern:**
- Some new prospects may push back on the higher price if the value story is weak.
---
### Option B: Add a cheaper tier
A cheaper tier might be, for example, **$390–$450/month** with limited features or usage.
**Revenue impact depends heavily on mix.**
Suppose a cheaper tier is set at $450/month:
- If one existing $750 customer downgrades, the company loses **$300/month**.
- It takes **two new lower-tier customers just to replace the revenue** of one downgrade.
- If lower-tier customers also demand more support relative to their spend, the net margin impact may be negative.
**Key risks:**
- Existing customers may downgrade if the cheaper tier is not tightly feature-limited.
- Lower-priced customers often have higher churn and higher support burden.
- The team of 5 may not have the capacity to serve a larger, lower-revenue customer segment.
- The product may need feature gating, usage limits, new onboarding motion, and new marketing materials.
- A cheaper tier can dilute positioning and confuse the market about who the product is for.
A cheaper tier is not automatically bad. It makes sense when:
1. There is a clear product-led onboarding motion.
2. Marginal cost to serve is very low.
3. There is data showing many prospects drop off due to price.
4. The lower tier can convert into higher-tier expansions later.
In this case, with a flat $750/month plan and a 5-person team, those conditions are unlikely to be reliably in place yet.
---
4. Comparative Trade-Offs
| Dimension | Raise prices 20% for new customers | Add cheaper tier |
|---|---:|---:|
| Revenue impact | Positive per new customer; no existing-base dilution | Mixed; depends on volume vs downgrades |
| Churn risk | Low for existing customers | Higher if existing customers downgrade |
| Sales/conversion risk | May reduce win rate if value story is weak | May increase conversion but attract lower-fit customers |
| Operational complexity | Very low | High: packaging, feature gating, support, marketing |
| Fit for 5-person team | Strong | Weak to moderate |
| Strategic positioning | Premium, value-based | Broader but risks brand dilution |
| Cash flow impact | Improves unit economics | Could reduce ARPU and strain margins |
| Data required | Low | High: segmentation, cost-to-serve, upgrade path |
---
5. Recommendation and Rationale
**Recommended action: Raise the price to $900/month for new customers.**
The business is not currently suffering from an obvious lack of demand at $750/month. At 40 customers and $30k MRR, the more urgent need is to improve revenue quality and positioning, not to add a lower-priced tier that may increase customer count without improving economics.
A 20% increase is aggressive enough to improve ARPU but not so large that it should dramatically reduce conversion for a B2B product with clear ROI.
A cheaper tier should be revisited only if:
- Win/loss data shows that price is the main reason prospects decline.
- The company can serve lower-end customers profitably through automation or self-serve onboarding.
- The product can be clearly packaged into a limited tier without cannibalizing the existing plan.
For now, the simplest, lowest-risk revenue improvement is the price increase.
---
6. Three Biggest Risks
### Risk 1: New customer acquisition slows due to price sensitivity
If the product’s value is not communicated clearly, $900/month may reduce conversion rates more than expected.
**Mitigation:**
- Strengthen ROI messaging, case studies, and sales enablement.
- Offer an annual prepay option, e.g., `$9,000/year` instead of `$10,800/year`, to reduce sticker shock.
- Track conversion rate, sales cycle length, and lost-deal reasons for at least two quarters.
---
### Risk 2: Legacy price gap creates friction or perceived unfairness
Existing customers pay $750/month, while new customers pay $900/month. This can create awkward referral situations or negotiation pressure if new prospects learn about the lower legacy price.
**Mitigation:**
- Clearly define the grandfathering policy: existing customers keep $750/month for at least 12 months.
- Frame it as a loyalty protection, not a hidden discount.
- Avoid publishing the old price externally.
- Plan a later conversation to migrate existing customers to higher pricing once additional value has been delivered.
---
### Risk 3: Missing the lower-end market opportunity
A cheaper tier could theoretically expand the total addressable market. Competitors might capture price-sensitive SMB customers that the company currently turns away.
**Mitigation:**
- Monitor lost deals by company size and stated budget.
- If a meaningful percentage of lost prospects consistently cite price, run a controlled pilot with a limited-feature plan.
- Do not build the cheaper tier immediately; wait for evidence that the demand exists and can be served profitably.
---
7. Implementation Notes
1. Set an effective date for new pricing.
2. Notify existing customers that their $750/month rate is protected for a defined period.
3. Update the website, proposals, and sales scripts to reflect $900/month.
4. Add tracking for:
- New-customer conversion rate
- Sales cycle length
- Lost-deal reasons
- Existing customer churn and downgrade requests
5. Revisit pricing after two quarters.
**Final conclusion:**
Raise new-customer pricing by 20% to $900/month. Grandfather existing customers. Do not add a cheaper tier unless future data proves there is a profitable, distinct lower-end segment.