Skip to content
Team Nexa
All posts

Success storyIllustrative

How a 150-person vertical SaaS company decided on a price increase with evidence, not gut feel

The board wanted a price increase. Sales feared churn. The Revenue and Finance agents modelled the change segment by segment, and the leadership team chose a staged rollout it could stand behind.

2 min read

  • Revenue
  • Finance
  • Strategy

Illustrative story: a composite scenario built on sample data to show how the agents work. It is not a customer testimonial.

The challenge

List prices hadn't changed in three years, while costs had. The board suggested a 15% increase across the board. The CRO worried about losing small customers, the CFO pointed at margin, and both sides had a few anecdotes. Nobody had looked at what customers actually paid after discounts, or how each segment had reacted to price changes in the past.

What they set up

  • The Revenue agent read the CRM and billing read-only, rebuilt the effective price each customer paid after every discount, and added renewal and churn history by segment.
  • It brought in product usage, so the price each segment paid could be set against how much of the product it actually used.
  • The Finance agent modelled three options against the plan: a flat increase for everyone, a staged increase, and a staged increase with small customers' prices held for a year.
  • The Strategy agent wrote the decision memo, with each option's assumptions and its expected range for revenue and churn on one page.

What changed

recurring revenue from the increase in its first two quarters
+6%recurring revenue from the increase in its first two quarters
small customers kept their price before any change
12 monthssmall customers kept their price before any change
logo churn, inside the range the memo predicted
+0.4 ptslogo churn, inside the range the memo predicted

The leadership team chose the staged option. Larger accounts moved at renewal, with notice and a conversation with their account manager, and small customers kept their price for a year. Sales went into renewals with the numbers in hand rather than hoping for the best. The agents didn't set the price. They made sure the people who did could see what each choice would cost.

What's next

The Revenue agent now tracks renewals and downgrades by segment against the memo's assumptions, so the team will know before the year is out whether small customers are ready for the next step.

Keep reading

All posts
  • Use case

    From brief to action: how the agents handle follow-through

    A good brief tells you what changed. Then someone still has to send the email, update the plan and chase the owner. Here is how the agents take that part off your plate, with your approval at every step.

    • Strategy
    • Finance
    • Revenue
    • Operations

    2 min read

  • Use case

    Linking the product roadmap to revenue and cost

    Roadmap reviews talk about features. Board meetings talk about revenue. The Product & Tech agent connects the two, so you can see what each big bet is worth and what it costs.

    • Product & Tech
    • Revenue
    • Finance

    2 min read