Product tour

One setup.
Then you stop asking.

It takes one connection — and it doesn't have to be yours. Everything after that happens without you, and without anyone else being asked.

1

Point it at the product — once

Don't have access to the code yourself? You don't need it. Send one link to whoever does; they click it, and they don't even need an account. That is the only time you have to ask anyone for anything. If you do have access, pick the project from a list instead. Either way SourcePRD can only read, private stays private, and access can be pulled at any time.

2

The whole thing is read, and written down for you

All of it is read — not a sample someone picked out. The product is split into the parts you would actually name, and each one is written up in plain language: what it is, and how a person uses it. Then every sentence is checked back against the code before it reaches you.

3

The running app is photographed

Your product is started up on our machines and photographed — the main screens, the path a customer takes through them, your own logo and marks as they appear on the page. Nothing runs on your laptop, and nothing is asked of your team. A screen that can't be reached stays blank rather than invented.

4

The story keeps up by itself

Every day the code is checked against the story. Only the capabilities whose code changed are rewritten — the rest keep their words and pictures — and each door, area and capability shows what changed and when. Nothing to approve. Your coding agents read the same story, and what changed, via MCP.

And you are told first. An email lists every change the way you would say it out loud — "partial refunds now go down to the line item" — at whatever frequency you pick: daily, weekly, monthly, or never. A quiet week sends nothing at all.

Built for the person who isn't writing the code

  • The first screen is a handful of doors — not a wall of detail
  • One click for the next layer; file names wait until you ask
  • Nothing to install, and no developer account to sign up for
  • You don't need access to the code — one link to someone who does
  • Share it by link with anyone: investors, support, a new hire
Someone mentioned “gift cards” 1 match
Cart & checkout → gift cards a door
A bit more → how people use it one layer
See the source when you want it

“I pay for this product.
Why must I ask what's in it?”

01

Every answer costs a favour

You want to know whether something shipped. That's a message, an interruption, and a wait — about your own product.

02

And you can't check the answer

“It's basically done” is something you take on faith. Nothing on your side of the table confirms or contradicts it.

03

The doc is a wish list

Written once, at the start, by someone who has since moved on. Everyone knows it's stale, so everyone ignores it.

04

You answer for it anyway

The budget, the deadline, the promise you made a customer — all yours. The visibility isn't.

Why this one can't go stale

Anything written about the product starts rotting the day someone changes it. Something read from the product can't. That's the whole idea.

The old way
  • Someone writes it down, once
  • The product moves on; the document doesn't
  • You stop trusting it, so you stop opening it
  • The real answer lives in someone else's head
With SourcePRD
  • It's read from the product, not written about it
  • It rewrites itself the day the product changes
  • Every line is checked against the code
  • The real answer lives where you can reach it

For whoever answers for the product

You approve the budget, carry the deadline and face the customer. You should be able to see the thing you're answering for.

Founders who don't code

It's your money. See what it bought — without booking time with an engineer to find out.

Paying an agency or contractors

Their status update and the product's own answer, side by side. You'll know which questions are worth asking.

Product & operations

Someone names a feature in a meeting. Search it, read it in plain words, and get back to the meeting.

Your dev team

They stop being your search engine. And their coding agents read the same story, over MCP, while they write the next change.

How MCP works →

See your product as it is now

One connection — yours, or a developer's, once — and the first story writes itself.

See your product Browse a live story ↗

14-day money-back, no questions asked.

Or ask us anything — questions, early access, feedback. We read everything.