01
Input your current state
Pages in your content map, pages shipped last month, team size, and hours per page.
Free tool
Input your current setup and see how page velocity changes when implementation becomes an agent workflow instead of a ticket queue.
How to use
Most teams know they are slow. This calculator shows exactly how slow — and what an agent-assisted workflow could change.
01
Pages in your content map, pages shipped last month, team size, and hours per page.
02
The calculator shows your current velocity, your theoretical max, and the pages left unshipped.
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 — not just looked at once.
Current velocity: 4 pages/month
Content map backlog: 48 pages
Time to clear backlog: 12 months
With agent-assisted workflow: 16 pages/month
Time to clear backlog: 3 months
Annual difference: +144 pages shipped
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, 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.