01
Input your current state
Pages in your content map, pages shipped last month, team size, and hours per page.
Free tool
Enter your backlog, last month's shipped pages, team size, and review time. Compare the current ticket queue with an agent-assisted workflow using editable assumptions.
How to use
Most teams know the content map is backed up. This calculator shows the backlog, the current pace, the assumed agent-assisted pace, and the review-time assumptions behind the estimate.
01
Pages in your content map, pages shipped last month, team size, and hours per page.
02
The calculator shows current velocity, estimated agent-assisted velocity, backlog clear time, and annual page difference.
03
See how agent-assisted generation changes the numbers — without claiming guaranteed results.
Example output
The output is designed to be pasted into a doc, a slide, or a team chat with the assumptions visible, not hidden behind a speed claim.
Current velocity: 4 pages/month
Content map backlog: 48 pages
Time to clear backlog: 12 months
Estimated agent-assisted capacity: 64 pages/month
Time to clear backlog: 1 month
Annual capacity difference: +720 pages
Assumptions: review time drops from 4h to 1h per page
agent handles metadata, schema, and discovery Related tools
Ship faster
Install Pagewell and give your agent the context to generate routes, run QA, and update discovery files as normal repo work.
bunx skills add ReScienceLab/pagewell --skill pagewell Then ask: Use Pagewell to generate the next 5 pages from our content map.
FAQ
Pages in your content map, pages shipped last month, team size, and average hours per page from brief to merge.
No. The calculator uses adjustable assumptions. Your actual velocity depends on review thoroughness, agent quality, repo complexity, and how well your PAGEWELL.md and DESIGN.md are maintained.
No. All calculations run in your browser. No data leaves your device.
Yes. Click copy to get a formatted report you can paste into docs, slides, or team chats.