For builders leveling up for the AI era
Level up your building skills for the AI world.
ampm runs a workflow adapted from the best Silicon Valley tech companies — refine, plan, build, test, review — and explains every decision along the way. You don't just get an app. You learn why it's built the way it is, from agents that recommend an answer and show their reasoning.
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.
The workflow
The way the best teams build, running on your projects
The best engineering orgs don't just start typing. They agree on the problem, plan the change, build it, test it, and review it before it ships. That discipline usually takes years inside one of those companies to absorb — distilled here from fifteen of them, and codified into machinery.
ampm runs that workflow on every task you file, and stops at each decision that's yours with a recommendation and the reasoning behind it. Answer enough of them and you start making the call before you read the recommendation.
- Refiningyour call
- Planningyour call
- Implementing
- Testing
- Reviewing code
- Mergingyour call
Learn by deciding
Every decision comes with a recommendation and a reason.
When there's a real choice — Postgres or SQLite, a library or hand-rolled, now or later — the planner stops and asks. It tells you what it would pick, what the trade-off is, and what experienced teams usually do.
You make the call, and the reasoning stays in the plan, so the next time you see the same choice you'll recognize it.
- questionplan · diff · transcript
Postgres or SQLite for workouts? (Recommended: Postgres)
- planplan · diff · transcript
Sign in with Google: approve the plan, with the reason for each choice?
- mergeplan · diff · transcript
Workout history page: merge after review?
Have a poke around
Make an architecture call with a coach beside you
Invented data, real mechanics. Open the decision in the inbox, read the recommendation and the trade-off, and choose. Then watch the plan pick up your answer.
Scroll a little further to load the demo
The board
Every piece of work, at the exact stage it's in. Positions aren't decoration — a card's column IS its state.
The inbox
One queue of everything blocked on you, each ask carrying the plan, the diff and the transcript behind it.
Activity
Who's working right now, on what, and what each run cost — live, with every finished run still on the record.
Have a poke around
Ask why, then decide
Not sure about a plan? Ask ampm to walk you through it — why a library, why sessions in the database — and what it would do. Then approve it right from the chat.
Scroll a little further to load the demo
Engineer from anywhere
Ask why from anywhere
Every decision comes with its reasoning, and that reasoning fits on a phone. Ask ampm what a choice means, get a recommendation, and make the call wherever you're learning.
From a beach chair
Scroll a little further to load the demo
What you pick up
Habits that make software hold up
Architecture, explained
Every plan says why — why this database, why a library, why this shape — so the reasoning becomes yours, not just the code.
Code review on every change
A reviewer reads every change against your repo's rules and pushes back, the way a senior engineer would on a good team.
Tests from day one
The first thing set up is a safety net: tests, lint and CI, so every later change is checked before you see it.
See it before it's built
For screens, agents mock up the design first, so you agree on what you're building before anyone writes code.
Questions
Do I need to be an experienced engineer?
No. Every plan explains its choices, and every decision comes with a recommendation and its trade-offs, so you learn the reasoning as you build.
What workflow does ampm follow?
Refine, plan, implement, test, review and merge — the discipline top engineering orgs use, adapted from fifteen years inside them.
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
Start building like the best teams do
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.