PM on Rails
Join waitlist

For PMs and development agencies

No more writing requirements after the meeting.

Drop in the meeting notes and AI drafts the requirement cards, user stories and acceptance scenarios in plain language. The only job left for you is deciding what is still undecided.

Join the waitlistTalk to us about rollout

Free to start. One set of meeting notes is enough.

A 30-second look at which parts of a PM's week get lighter. Everything shown is the real product. No audio.
(01)

The problem

Does this happen after your meetings?

The questions only come to you afterwards

You notice what you forgot to ask once the meeting is over, and chase it on Slack.

Answers from Slack never make it into the requirements

Things that were decided scroll away, and the mismatch shows up during development.

Every spec change means hunting for affected tasks

How far the change reaches is decided from memory, every time.

(02)

How it works

Leave everything but the decisions to AI.

Asking, organizing, following up. AI takes over the work that used to fill a PM's time, and only the decisions stay with you.

  1. 01
    PM on Rails AI review. Gaps, ambiguities and contradictions in stories and scenarios listed in one place. The questions you did not think of in the meeting appear here.

    Find what is still undecided

    AI reviews the stories and scenarios and lists contradictions, gaps and open points. Questions for the customer can be sent to Slack as they are.

    You: Send the questions

    About open questions
  2. 02
    PM on Rails feedback. Input from the field listed with proposed spec changes you can approve, adjust or reject. AI does the thinking, the PM decides.

    Every pending decision comes with a proposal

    Answers and feedback come back as proposed changes to the spec. You pick approve, adjust or reject.

    You: Approve or adjust

    About feedback
  3. 03
    PM on Rails board. Tasks from to-do to done, linked to pull requests. Where work has stalled is visible without collecting daily reports.

    Progress updates itself from pull requests

    Tasks are linked to pull requests and complete when they merge. You see where work has stalled without collecting status reports.

    You: Just look

    About progress tracking
(03)

The loop

From request to passing test, the same loop every time.

You are involved in the two highlighted steps. AI and the tool handle the rest.

  1. 01RequestNotes and asks
  2. 02ScenarioAcceptance criteria
  3. 03BuildClaude Code / Codex
  4. 04TestCI results recorded
  5. 05FeedbackQuestions and decisions
Where you are involved
Where AI and the tool take over
(04)

From early users

What surprised the people who tried it.

Things I used to leave entirely to the engineers, I can now do myself.
A client-side PM on an outsourced project
Scenarios are written in plain language, so I can hand them straight to the customer to check.
A PM at a development agency

Summarized from interviews with early users.

Takes over the PM's workload

Anyone can be the hero PM.

Your first project is free. Drop in one set of meeting notes and watch the requirement cards appear.

Join the waitlistTalk to us about rollout

Pages for other roles

For clients & in-house teamsFor anyone who delegates development but refuses to fly blind or hand over a black box.For engineersFor anyone who has Claude Code or Codex writing code every day.For solo buildersFor anyone who can build with Claude Code but has no structure for running the project.