Know what your team can deliver, and when.
One workspace for the roadmap, the team's real capacity and the story behind every date. See over-commitment the moment it happens, not at the next steering meeting.
- Roadmap timeline
- Capacity month by month
- Every date change recorded
- Available
- 29.4 d
- Planned
- 36.4 d
- Search relevance
- 20.0 d
- Checkout redesign
- 16.4 d
The whole idea, in 36 seconds
A roadmap, the month it breaks, the trade-off that fixes it, and the hand-over to development.
Three questions every roadmap review asks
Roadmaps break where capacity is a guess
Capacity lives in a spreadsheet
Headcount, holidays, vacations, maintenance and BAU sit in a workbook only one person understands, and it is out of date the day after it is built.
Commitments exceed what the team has
Initiatives are added one at a time and each looks reasonable. Nobody sees that December is already full until December arrives.
Dates move and nobody remembers why
The roadmap shows the current date, not the three it replaced. The reasons stay in someone's inbox.
From team setup to a plan that holds
- 1
Describe the team
Add the people, their time off, the holidays and the share reserved for maintenance and BAU. Capacity is worked out for every month.
- 2
Plan the initiatives
Give each initiative a priority, an owner, dates and an estimate. It appears on the timeline and counts against its team.
- 3
See what fits
Months that are over capacity turn red, with the initiatives responsible one click away. Move a date and the reason is kept.
Capacity you can explain line by line
Available capacity starts from working days and subtracts holidays, absences, maintenance and BAU. Every number on the roadmap opens into the lines that produced it.
- Part-time people and mid-month joiners counted correctly
- Holidays and vacations never double-counted
- Maintenance and BAU reserved as a share of each month
The story behind every delivery date
Changing a date, a status, a priority or a team writes a history entry with the old value, the new value, who did it and why. Entries cannot be edited or deleted.
- Old and new value side by side
- Optional reason on every change
- One activity feed for the whole workspace
Decisions kept next to the work
Meeting notes and links to documents live on the initiative they belong to, so the context is there when the date is questioned six months later.
- Notes with author and time
- Links checked before they are saved
- Searchable list of every initiative
Built to be trusted with the plan
The application runs on your own server and database. Security controls are part of the foundation, not an afterthought.
Access checked on the server
Every request is checked against workspace membership and role before any data is read.
Protected sign-in
Passwords are stored as salted scrypt hashes; sessions live in cookies scripts cannot read.
History that cannot be rewritten
Change events are append-only, enforced by the database as well as the application.
Validated input
Strict schemas on every endpoint, and links limited to http and https.