- Industry
- Procure AI
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Decision-maker
- Approver
- Head of Product
- Code
- PRD-01
It turns the company strategy for our procurement platform and managed services, such as raising touchless invoice rates, adding supplier risk monitoring or opening a new country for e-invoicing, into a quarterly product plan: objectives, the bets that serve them, the team each bet goes to and the key results each is measured by. It forecasts whether the plan fits each team's capacity with the buffer left free and creates the approved plan in the roadmap tool.
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 roadmap tool: the candidate bets, team capacities, client commitments and last quarter's results..
- 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 Product with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the roadmap tool: it creates the approved quarterly plan with objectives, key results and bets by team. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The company strategy and service KPIs (first-time-match rate, PO cycle time, spend under management, realised savings), team capacities, commitments made to clients in their service contracts and the country e-invoicing mandate calendar.
Reads from
the roadmap tool: the candidate bets, team capacities, client commitments and last quarter's results.
Acts in
the roadmap tool: it creates the approved quarterly plan with objectives, key results and bets by team.
Hands back
An object with quarter, objectives (a list with team, objective, key_results and bets), capacity (a list with team, available, planned and buffer_left), dropped (a list with bet and reason) and client_commitments_affected (a list).
Asks a person when
A team is planned above its capacity after the 20 percent buffer, a bet is at or above 40 engineer-weeks, less than 70 percent of effort serves a named goal, or a date promised to a client moves or drops.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Capacity kept free (%) | 20 | The share of each team's capacity left unplanned for incidents and client escalations. |
| Objectives per team | 3 | The most objectives a team carries in a quarter. |
| Key results per objective | 3 | The most key results per objective. |
| Effort that must serve a named goal (%) | 70 | At least this share of planned effort serves a strategic goal. |
| Quarters ahead to plan an e-invoicing mandate | 2 | A country e-invoicing or tax mandate is planned at least this many quarters before it takes effect. |
| Bet size that needs leadership review (engineer-weeks) | 40 | A bet this large or larger needs the approver. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Plan each team to at most its capacity less 20 percent.
- Each team carries at most 3 objectives, each with at most 3 measurable key results tied to a service KPI.
- At least 70 percent of effort serves a named strategic goal.
- A country e-invoicing or tax mandate taking effect within 2 quarters is planned before any discretionary bet, because missing it stops client invoices.
- A feature promised in a client service contract keeps its date unless the Head of Product agrees a move and the Client Engagement Lead tells the client.
- A bet at or above 40 engineer-weeks needs the Head of Product.
See the Product Planning Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.