For product managers
Your team of engineers, working around the clock on your specs.
Write the roadmap the way you already do. ampm turns each spec into acceptance criteria, plans it, builds it, tests it and opens a reviewed pull request — feature by feature, in the order you set. Attach screenshots, chat with a task, and stop waiting for next sprint to find room.
A kanban board with four lanes — Ideating, Planning, Building and Shipping — carrying tasks from a fresh idea through to a pull request waiting for review.
Roadmap to release
Write the roadmap. ampm dispatches it, feature by feature.
Ideas wait on the Roadmap until you start them. Then each one is refined into acceptance criteria you approve, queued behind whatever it depends on, planned, built, tested and reviewed — and lands as a pull request that says exactly which criteria it meets.
You own the what and the order. The how is the team's job, and you can read every decision it made.
- Roadmap
- Refiningyour call
- Next
- Planning
- Implementing
- Testing
- Reviewing code
- Mergingyour call
Have a poke around
A roadmap that grooms itself
Invented data, real mechanics. Grooming proposes closing a duplicate request, raising what customers keep asking for and linking what depends on what — each change waits for your yes, right on the Roadmap.
Raise “Share a note with a public link” to P1?
Three customers asked for it this week, and it unblocks the team plan.
Close “work offline??” as a duplicate of “Offline mode for notes”?
Same idea, filed four months apart. The older one has the better description and 6 votes.
Dependencies
A web of dependencies? Fire and forget.
Write specs in the order you think of them. ampm orders the work by what builds on what, and each feature starts the moment the one it needs merges or deploys — no meeting to re-sequence the sprint.
Have a poke around
Your roadmap, in flight
Invented data, real mechanics. Hand the team a spec and watch it split into three tasks that wait on each other — or merge a pull request and watch the feature queued behind it start.
Scroll a little further to load the demo
Engineer from anywhere
Approve between meetings
Your day is meetings. The calls that are yours — a plan, a merge, a question about scope — fit between them, and the roadmap keeps shipping in dependency order while you're in the next one.
From a beach chair
Scroll a little further to load the demo
Signals from the outside world
Tickets and reviews become prioritized tasks
Intake processes group what customers ask for across support and app reviews, and suggest tasks with the evidence attached. You decide what goes to the team.
Processes
- Keep bugs and feature requests
- →Group by product area
- →Suggest tasks
- Drop reviews with no detail
- →Group by theme
- →Suggest tasks
Suggested tasks
Suggestions arrive once signals come in.
Sent tasks land here.
Made for specs
Talk to it like you talk to your team
Screenshots and mockups
Attach images to tasks and questions. For new screens, agents mock up the design for your approval before anyone builds it.
Chat with a task
Ask a task what it's doing, why it chose that approach, or to change course — in plain language, mid-flight.
Acceptance criteria you sign off
Every feature starts with criteria you approve, and every pull request says how it meets them.
Order that respects dependencies
Features that depend on each other are sequenced automatically, so nothing is built on a foundation that isn't there yet.
Questions
Do I need to read the code?
No. Every feature starts with acceptance criteria you approve, and every pull request says how it meets them. Engineers can still review the code if your team wants to.
Can I attach screenshots and mockups?
Yes. Attach images to tasks and questions, and new screens are mocked up for your approval before they're built.
Which coding agents does ampm work with?
Claude Code and Codex. ampm runs them on the subscription you already pay for — no API keys and no second bill for tokens — and when one account hits its usage limit, work moves to a backup account without losing anything.
Does ampm merge code on its own?
Nothing merges unless you want it to. Plans, questions and merges wait in your inbox with the plan, diff, pull request and full transcript attached, and you decide which decisions to keep and which to hand off.
Where does the code run, and is my repo safe?
Every task runs in an isolated sandbox on its own worktree, on workers you choose — your laptop, a server you own, or a cloud machine — and can only push to a branch. The output is always a pull request into your repo.
How is this different from chatting with a coding agent?
A chat forgets everything when you close the tab and needs you watching it. ampm keeps every task in a database with its plan and history, runs a real process — plan, implement, test, review, merge — and only asks you when a decision is actually yours.
Can one workspace cover several repos?
Yes. Add the repos agents should change, and add more as read-only context — a design system, an API they call, product docs — so their work matches what's around it. One change can span several repos as one piece of work.
How do I get access?
Join the wait list with Google or GitHub. We're letting people in a few at a time, in the order they joined, and we'll email you when it's your turn.
Early access
Put your roadmap to work
We're letting people in a few at a time. Join the wait list with Google or GitHub and we'll email you when it's your turn. Run it on our cloud or on infrastructure you control — your repos, your subscriptions, workers on machines you choose.