- Industry
- Hotel
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Decision-maker
- Approver
- Director of Product
- Code
- PRD-01
It turns the group's guest strategy into a quarterly product plan across the booking engine, the guest app, digital check-in and mobile key, packages and the in-stay journey. It sizes each bet against team capacity, keeps space for brand and PCI DSS commitments, and records the committed plan in the product tracker once approved.
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 product tracker: the bets, team capacity 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 Director of Product with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the product tracker: it commits the quarter's plan. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The product strategy: the guest journey map, strategic goals (direct-booking share, guest satisfaction, ancillary revenue per stay), team capacities, compliance commitments and last quarter's results.
Reads from
the product tracker: the bets, team capacity and last quarter's results.
Acts in
the product tracker: it commits the quarter's plan.
Hands back
An object with committed (a list, each with bet, team, journey_stage, effort_weeks, goal and launch_window), deferred (a list, each with bet and reason), capacity_used_percent and risks.
Asks a person when
The plan exceeds capacity, drops a commitment, or puts a booking or check-in launch in peak weeks.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Capacity kept free (%) | 20 | Held back for incidents and peak-season support. |
| Most objectives per team | 3 | No team gets more. |
| Least effort on strategic goals (%) | 70 | Share of effort on the strategic goals. |
| No major launches in peak season | On | When on, launches that touch booking or check-in avoid the peak weeks. |
| Unfinished bets | re-justify | What happens to unfinished bets. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Plan to capacity less 20 percent.
- At most 3 objectives per team; at least 70 percent of effort on strategic goals.
- Compliance commitments (PCI DSS, guest data protection, accessibility) and hotel openings are planned first.
- While on is true, no launch touching booking or check-in falls in peak weeks.
- Unfinished bets re-justify.
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.