Roadmap review prep
Maya Okafor, head of product at Northwind, asked what on the mobile roadmap was running late. Memtro listed the bars by end date with percent done and lane, and the comments on the one furthest behind.
What is on our roadmap, and which launch tasks are blocked?
ProductPlan shows you your roadmaps and their bars with lane, legend, dates, progress and tags, and a bar's comments. It reads ideas, opportunities, objectives with key results, launches with their tasks. When asked and granted, it can create, edit or delete a bar and add a milestone. It can also create or edit ideas, opportunities and objectives, add or update key results, create a launch and update a launch task. ProductPlan can tell Memtro as it happens when a roadmap bar is created, updated or deleted, and a job can start on it. Those events are added in ProductPlan.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right ProductPlan tool, reads what it needs, and answers with the source cited.
These tools change something in ProductPlan. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in ProductPlan, choosing the same kinds; the tab shows ProductPlan's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. ProductPlan sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce ProductPlan is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which bars on the mobile roadmap end this month?
Which opportunities are still in discovery?
How are the key results on our retention objective tracking?
Which launch tasks are blocked?
What ideas have come from customers recently?
Maya Okafor, head of product at Northwind, asked what on the mobile roadmap was running late. Memtro listed the bars by end date with percent done and lane, and the comments on the one furthest behind.
When a roadmap bar was updated in ProductPlan, a job started for Priya Sharma, product director at Acme Ltd. It read the bar in full, with its new dates and comments, and summarised the change for her.
The teams that lean on ProductPlan most, a question each of them asks, and what they connect beside it.
A record in ProductPlan is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In ProductPlan open Integrations, then Custom integration, and generate the 64-character key. It is shown once and acts as your user.
In Memtro open Connections → ProductPlan and paste the API token.
Writing to a roadmap needs edit access to it, and an administrator grants the actions by name. Events are turned on from the connection's Events tab, and the address is then added in ProductPlan's webhook settings.
Ask: which bars on the mobile roadmap end this month?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The ProductPlan tools are the same everywhere.
Only when you ask, and only what it has been granted: create a roadmap bar; edit, move, park or unpark a bar; delete a bar; add a milestone to a roadmap; create an idea; edit or archive an idea; create an opportunity; edit, re-status or archive an opportunity; create an objective; edit or archive an objective; delete an objective; add a key result to an objective; update a key result's values; create a launch; update a launch task's status, owner or due date. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed ProductPlan records into memory as entities.
API token. In ProductPlan open Integrations, then Custom integration, and generate the 64-character key. It is shown once and acts as your user.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in ProductPlan, choosing the same kinds; the tab shows ProductPlan's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time