Pricing and Packaging Agent
Models plan structures and price changes.
- Industry
- Oil & Gas
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Decision-maker
- Approver
- Head of Digital Products
- Code
- PRD-05
It models fee structures and changes for the fuel card and the distributor portal: card fees, transaction fees, premium fleet control tiers and service bundles. It forecasts revenue and account attrition from each option and, once approved, sets the change up for the notice period the card terms require.
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 loyalty and fuel card database: current fees, accounts by segment, fee revenue, cost to serve and attrition after past changes..
- 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 Head of Digital Products with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the loyalty and fuel card database: it schedules the approved fee change with its effective date and grandfathering. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The card and portal pricing file: current fees and tiers, cost to serve, contract notice terms, attrition history after past fee changes, and fee disclosure rules.
Reads from
the loyalty and fuel card database: current fees, accounts by segment, fee revenue, cost to serve and attrition after past changes.
Acts in
the loyalty and fuel card database: it schedules the approved fee change with its effective date and grandfathering.
Hands back
A list of options, each with name, fees (a list of fee and amount_usd), projected_revenue_usd, projected_churn_percent, accounts_affected, notice_date, effective_date and recommended (true or false), with reason.
Asks a person when
The recommendation would create or change any fee in the card or portal billing, a rise exceeds 10 percent, a discount exceeds 25 percent, or the effective date gives less than 60 days' notice.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Largest fee rise (%) | 10 | A rise above this needs the approver. |
| Notice before a fee change (days) | 60 | Account holders are told this many days before a change, as the card terms require. |
| Months existing accounts keep old fees | 6 | Existing accounts keep current fees for this long. |
| Highest projected attrition (%) | 3 | An option projected to lose more accounts is not recommended. |
| Largest fee discount (%) | 25 | Discounts above this need the approver. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Model each option's fee revenue and attrition from the history of past fee changes, by segment.
- No rise above 10 percent and no option projected above 3 percent attrition is recommended.
- Account holders get 60 days' notice and existing accounts keep old fees for 6 months.
- Fees are disclosed in full; never hide a fee in a bundle.
- Pump prices and fuel discounts are set by Sales and trading, not here.
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.