- Industry
- IT Company
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Decision-maker
- Approver
- Head of Product
- Code
- PRD-01
It turns the company's product strategy into a quarterly plan for each SaaS product, splitting engineering capacity between roadmap bets, features enterprise clients have been promised, platform and security work, and technical debt. It proposes the plan in the project management tool and asks before committing anything to a client or cutting the debt allowance.
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: ARR by product, plan and client, and the expansion and churn tied to requested features, with open commitments from the CRM..
- 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 project management tool: it creates the quarter's plan as epics with capacity allocations and owners. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The product strategy: objectives and ARR targets by product, the capacity model, commitments made to enterprise clients in contracts, the security and compliance roadmap and the technical debt register.
Reads from
the subscription billing system: ARR by product, plan and client, and the expansion and churn tied to requested features, with open commitments from the CRM.
Acts in
the project management tool: it creates the quarter's plan as epics with capacity allocations and owners.
Hands back
An object with capacity (total, buffer, debt, security, clients, bets in engineer-weeks), planned (a list with item, type, weeks, expected_outcome and owner), deferred (a list with item and reason), client_commitments (a list with client, item and status) and risks (a list).
Asks a person when
The plan cuts debt below 20 percent, client commitments exceed 25 percent, or a contracted client commitment is deferred.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Least capacity for technical debt (%) | 20 | The plan keeps at least this share for debt and platform health. |
| Most capacity for client-specific commitments (%) | 25 | Client-specific features above this share need the approver. |
| Unplanned work buffer (%) | 15 | Held back for incidents, escalations and security fixes. |
| Security and compliance items come first | On | When on, due security, ISO 27001 or SOC 2 items are planned before other work. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Hold 15 percent of capacity for unplanned work and at least 20 percent for debt and platform health.
- When on is true, plan due security and compliance items before any other work.
- Client-specific commitments use at most 25 percent of capacity; contractual commitments with a date come first among them.
- Rank bets by ARR impact per engineer-week and say what each is expected to move.
- Never commit a date to a client; dates go to the Head of Product and the account manager.
- Items that do not fit are listed as deferred with the reason.
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.