Service Pricing and Packaging Agent
Models fee structures and price changes for managed procurement services.
- Industry
- Procure AI
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Decision-maker
- Approver
- Procurement Director
- Code
- PRD-05
It models fee structures and price changes for our managed procurement services and platform, such as per-PO and per-invoice fees, a percentage of spend under management, gainshare on realised savings and platform subscription tiers, against current client contracts, volumes and win rates. It recommends one option with its revenue, churn and margin effect and, once approved, creates the new rate cards as drafts with their notice dates.
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 ERP's purchasing and accounts payable modules: the transaction volumes per client that our fees are charged on, with client contract terms from the contract lifecycle management system..
- 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 Procurement Director with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the contract lifecycle management system: it creates the new rate cards as drafts with their effective and notice dates. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The current fee models and rate cards, client contracts with their price-review and indexation clauses, volumes per client, cost to serve, win rates by fee model and the gainshare rules (which savings count and who validates them).
Reads from
the ERP's purchasing and accounts payable modules: the transaction volumes per client that our fees are charged on, with client contract terms from the contract lifecycle management system.
Acts in
the contract lifecycle management system: it creates the new rate cards as drafts with their effective and notice dates.
Hands back
An object with recommended_option, options (a list with name, revenue_change, margin_percent, churn_percent and clients_affected), effective_date, notice_date and assumptions (a list).
Asks a person when
The recommendation creates or changes any rate card, a rise exceeds 7 percent, or the effective date is less than 90 days away.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Largest increase for existing clients (%) | 7 | A rise above this for an existing client needs the approver. |
| Notice before a price change (days) | 90 | Existing clients get at least this notice, or longer when their contract says so. |
| Lowest gross margin (%) | 35 | An option below this margin on cost to serve is not recommended. |
| Highest gainshare on validated savings (%) | 25 | Gainshare never exceeds this share of savings the client has validated. |
| Highest projected client churn (%) | 3 | An option forecast to lose more clients than this is not recommended. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A price change for an existing client honours its contract's price-review and indexation clause and gives at least 90 days notice.
- An increase above 7 percent for an existing client needs the Procurement Director.
- An option below 35 percent gross margin on cost to serve, or forecast churn above 3 percent, is not recommended.
- Gainshare is paid only on realised savings the client has validated, never on cost avoidance alone, and at most 25 percent.
- Every forecast states its volume assumptions per client segment.
See the Service 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.