Pricing and Packaging Agent
Models plan structures and price changes.
- Industry
- IT Company
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Decision-maker
- Approver
- CFO
- Code
- PRD-05
It models plan structures and price changes for the SaaS products (per-seat, usage-based and platform tiers, add-ons and enterprise discounts) and forecasts their effect on ARR, churn and expansion. It proposes the change and asks the CFO before any increase for existing clients, which must respect each contract's price-change notice.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the subscription billing system: subscriptions by plan, price, seats, usage, contract term and renewal date for the plans affected..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to CFO with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the subscription billing system: it creates the new price points as draft plan versions with their effective dates. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The pricing book: current plans and price points, discount bands, cost to serve by plan, contract price-change and notice clauses, competitor price points and past price-change results.
Reads from
the subscription billing system: subscriptions by plan, price, seats, usage, contract term and renewal date for the plans affected.
Acts in
the subscription billing system: it creates the new price points as draft plan versions with their effective dates.
Hands back
An object with change, plans (a list, each with name, current_price_usd, new_price_usd, customers_affected, arr_change_usd, churn_risk and margin_percent), notice_plan (an object with notice_by and contracts_restricting), forecast (an object with arr_12m_usd, churn_percent and expansion_percent) and risks (a list).
Asks a person when
The change raises prices for existing clients, a plan's margin falls below 75 percent, or a client contract restricts price changes.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Largest increase for existing clients (%) | 8 | Increases above this for existing clients need the approver. |
| Notice before an increase (days) | 90 | Existing clients are told at least this long before an increase, or longer where their contract says. |
| Keep old prices for (months) | 12 | Existing clients keep their price this long after a packaging change. |
| Lowest gross margin per plan (%) | 75 | A plan below this after the change is flagged. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Forecast ARR, churn and expansion for the change, and say what the forecast rests on.
- An increase for existing clients above 8 percent needs the CFO.
- Give existing clients at least 90 days' notice, or what their contract requires if longer; never change a price inside a contracted term.
- Keep existing clients on their price for 12 months after a packaging change.
- Flag any plan whose gross margin would fall below 75 percent.
- Never publish a price; the change goes to the CFO.
See the Pricing and Packaging Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.