Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Product Roadmap Tool
- Access
- Document storage
- Finance
A delivery lead starts with a project, its organization, owner, budget and dates. Project managers divide the work into work packages, set estimates and assign tasks.
Projects in one list
Reviewer decides whether the delivery subject is Approved, Rejected or Returned.
Every feature works on the same records. Pick one to see the screen your team works in.
Set ownership, budget and delivery dates for each engagement.
Projects
| Project code | Project name | Status | End date | Budget | |
|---|---|---|---|---|---|
| PRJ-2026-014 | Customer portal launch | Planned | 30 Oct | 470 | |
| PRJ-2026-019 | Service scheduling refresh | Active | 24 Oct | 760 | |
| PRJ-2026-023 | Partner onboarding rollout | At risk | 17 Oct | 610 | |
| PRJ-2026-028 | Mobile field reporting | Completed | 20 Oct | 870 | |
| PRJ-2026-031 | Billing workflow modernization | Planned | 16 Oct | 890 |
Group project work with owners, dates and estimated hours.
Tasks
| Task key | Title | Work package | Assignee | Priority | Due date | |
|---|---|---|---|---|---|---|
| TASK-241 | Map account roles to permissions | Portal account setup | Nadia Rahman | Low | 11 Oct | |
| TASK-242 | Review appointment conflict rules | Access role migration | Mei Chen | Medium | 02 Nov | |
| TASK-243 | Build partner invite email | Invoice approval routing | Lucas Bennett | High | 28 Oct | |
| TASK-244 | Test offline report sync | Offline report capture | Hugo Fischer | Critical | 29 Oct | |
| TASK-245 | Approve invoice exception copy | Portal account setup | Lucas Bennett | Low | 26 Oct |
Assign delivery work and follow its status, dates and hours.
Approval conditions
| Entry number | Team member | Project | Work date | Hours | Status | |
|---|---|---|---|---|---|---|
| TE-47284 | Anika Shah | Account access redesign | 15 Oct | 7 | Submitted | |
| TE-52193 | Hugo Fischer | Support knowledge migration | 28 Oct | 13 | Submitted | |
| TE-54554 | Hugo Fischer | Mobile field reporting | 16 Oct | 6 | Submitted | |
| TE-63162 | Lucas Bennett | Partner onboarding rollout | 28 Oct | 5 | Submitted | |
| TE-60879 | Mei Chen | Service scheduling refresh | 11 Oct | 6 | Submitted |
Track the dated checkpoints a project needs to meet.
Approval conditions
| Milestone name | Project | Due date | Owner | Status | |
|---|---|---|---|---|---|
| Pilot scope approved | Service scheduling refresh | 03 Nov | Mei Chen | Pending | |
| Design signoff | Billing workflow modernization | 17 Oct | Lucas Bennett | Pending | |
| Integration test complete | Service scheduling refresh | 11 Oct | Samira Diallo | Pending | |
| Partner preview opens | Support knowledge migration | 26 Oct | Lucas Bennett | Pending | |
| Training materials ready | Account access redesign | 22 Oct | Yuki Tanaka | Pending |
Triage raised issues and track project exposure with named owners.
Release milestones
| Milestone name | Project | Due date | Owner | Status | |
|---|---|---|---|---|---|
| Pilot scope approved | Operations analytics launch | 23 Oct | Rafael Costa | Missed | |
| Design signoff | Billing workflow modernization | 25 Oct | Yuki Tanaka | Missed | |
| Integration test complete | Account access redesign | 20 Oct | Anika Shah | Missed | |
| Partner preview opens | Billing workflow modernization | 31 Oct | Rafael Costa | Missed | |
| Training materials ready | Service scheduling refresh | 23 Oct | Owen Castillo | Missed |
Submit project hours and compare assignments with weekly capacity.
Time entries
| Entry number | Work date | Project | Task | Hours | Status | |
|---|---|---|---|---|---|---|
| TE-91815 | 28 Oct | Mobile field reporting | Migrate service articles | 2 | Draft | |
| TE-58247 | 15 Oct | Service scheduling refresh | Approve invoice exception copy | 16 | Submitted | |
| TE-85569 | 17 Oct | Operations analytics launch | Audit access role assignments | 11 | Approved | |
| TE-95397 | 19 Oct | Mobile field reporting | Audit access role assignments | 7 | Draft | |
| TE-12802 | 28 Oct | Account access redesign | Validate daily operations totals | 12 | Submitted |
Keep delivery decisions, attachments and operation results traceable.
Review decisions
| Decision number | Subject type | Subject reference | Decision | Decided at | Reviewer | |
|---|---|---|---|---|---|---|
| RD-11415 | Project | Customer portal launch | Approved | 11 Oct | Samira Diallo | |
| RD-47196 | Work Package | Scheduling API integration | Returned | 19 Oct | Rafael Costa | |
| RD-21167 | Task | Partner invite flow | Approved | 27 Oct | Hugo Fischer | |
| RD-27246 | Milestone | Mobile field reporting | Returned | 02 Nov | Lucas Bennett | |
| RD-36661 | Deliverable | Invoice approval routing | Approved | 26 Oct | Talia Brooks |
Plan and deliver project work ships ready to use. One step needs a named approval before the work moves on: Review delivery (Reviewer).
Name the owner, organization, budget and dates.
Group project scope and estimate the work.
Give each piece of work an assignee and due date.
Follow task status and dated checkpoints.
Record the reviewer's decision on the subject.
Check the tasks and packages before completion.
Open any project to see its issues, the roles that work on it, its process stages and its approvals on one page.
Project name, Owner, End date and Progress percent.
Each line is linked to this project.
Admin, Delivery Lead and Project Manager, each with their own permissions.
Plan work packages and Assign tasks, with the role that acts.
Review delivery, with who decides.
Customer portal launch · Active
| Issue key | Title | Project |
|---|---|---|
| ISSUE-118 | Invite link expires too early | Customer portal launch |
| ISSUE-119 | Schedule changes fail to sync | Account access redesign |
| ISSUE-120 | Mobile report omits photos | Partner onboarding rollout |
Signed in as Reviewer
| Decision | Approver | |
|---|---|---|
| Review deliveryRecord the reviewer's decision on the subject. | Reviewer | |
| Approve review decisions | Reviewer |
Everyone opens Product Roadmap Tool to the work that is theirs. Pick a role to see what it starts with.
Maintains access, organizations and the delivery setup.
Owns the project portfolio and records delivery decisions.
This is the first screen this role sees.
Release milestones · Delivery Lead
| Milestone name | Project | Due date | Owner | Status | |
|---|---|---|---|---|---|
| Pilot scope approved | Service scheduling refresh | 03 Nov | Mei Chen | Pending | |
| Design signoff | Billing workflow modernization | 17 Oct | Lucas Bennett | Pending | |
| Integration test complete | Service scheduling refresh | 11 Oct | Samira Diallo | Pending | |
| Partner preview opens | Support knowledge migration | 26 Oct | Lucas Bennett | Pending | |
| Training materials ready | Account access redesign | 22 Oct | Yuki Tanaka | Pending |
Plans project work and follows assignments, dates and exceptions.
This is the first screen this role sees.
Time entries · Project Manager
| Entry number | Team member | Project | Work date | Hours | Status | |
|---|---|---|---|---|---|---|
| TE-47284 | Anika Shah | Account access redesign | 15 Oct | 7 | Submitted | |
| TE-52193 | Hugo Fischer | Support knowledge migration | 28 Oct | 13 | Submitted | |
| TE-54554 | Hugo Fischer | Mobile field reporting | 16 Oct | 6 | Submitted | |
| TE-63162 | Lucas Bennett | Partner onboarding rollout | 28 Oct | 5 | Submitted | |
| TE-60879 | Mei Chen | Service scheduling refresh | 11 Oct | 6 | Submitted |
Updates assigned work and submits time for review.
This is the first screen this role sees.
Work packages · Team Member
Triages issues and verifies fixes against project work.
This is the first screen this role sees.
Issues · QA Engineer
Records decisions on delivery subjects and checks supporting evidence.
This is the first screen this role sees.
Time entries · Reviewer
| Entry number | Team member | Project | Work date | Hours | Status | |
|---|---|---|---|---|---|---|
| TE-47284 | Anika Shah | Account access redesign | 15 Oct | 7 | Submitted | |
| TE-52193 | Hugo Fischer | Support knowledge migration | 28 Oct | 13 | Submitted | |
| TE-54554 | Hugo Fischer | Mobile field reporting | 16 Oct | 6 | Submitted | |
| TE-63162 | Lucas Bennett | Partner onboarding rollout | 28 Oct | 5 | Submitted | |
| TE-60879 | Mei Chen | Service scheduling refresh | 11 Oct | 6 | Submitted |
Answer delivery, exposure and workload questions from project records.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Planned | 32 | ||
| Active | 12 | 38% | |
| On hold | 3 | 25% | |
| At risk | 1 | 33% |
Sample counts per stage
Which owned projects are Active or at risk and when do they end?
Where do package task actual hours exceed task estimates within a project?
Which project tasks remain Backlog, in progress, in review or Blocked?
Which pending milestones have the earliest due dates?
Which projects have open or triaged Critical and High issues?
Which open risks have High probability or impact and who owns mitigation?
What hours are awaiting approval for each project and team member?
How do assigned estimate hours compare with weekly capacity for each active team member?
Which delivery subjects have Approved, Rejected or Returned decisions?
See how Product Roadmap Tool fits your kind of team.
Each stage of plan and deliver project work names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Help your team inspect delivery records and prepare routine updates.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 13 tablesStart with one team and one process, then add the rest once the basics are running.
Enter the organizations and active team members who will own the first project.
Add its owner, budget and dates, then create packages, tasks and milestones.
Raise an issue with severity, add a risk with mitigation, and follow a blocked task and missed checkpoint.
Submit a valid time entry, inspect the decision and receipt, and have a Reviewer decide on a delivery subject.
Agree the meeting cadence and who updates each status, date and estimate.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Product Roadmap Tool for your business. Begin with one project, its owner, work packages, tasks and next milestone.
Connect it to an organization, name an owner and enter the budget and dates. Group the work in packages, then assign tasks.
Yes. Task Board by Status shows Backlog, in progress, in review, Blocked and Done tasks. Tasks In Flight focuses on work under way or in review.
Create a milestone with a project, owner and due date. Mark it Met or Missed after the outcome is known.
Give an Open issue severity. Issue Triage moves a valid issue to Triaged and writes an operation receipt. The failed attempt is recorded if severity is missing or the issue is no longer Open.
Record probability, impact, mitigation and owner on the project risk. Review Open and Monitoring risks before the next checkpoint.
A team member submits a time entry with positive hours. Time Entry Approval checks the entry, records a decision and receipt, and approves a valid submission.
The Reviewer records the subject reference, decision, date and notes on the review decision. Attachments can identify a related delivery record.
Start from the project status and dates, then inspect the task, milestone, issue, risk and hour records behind them.
Start free, then use Proto to change fields, steps and approvals before your team goes live.