PRD FROM YOUR VOICE

Talk through an app idea. Get a product brief.

TalkGraph turns an app idea you talk through into a product requirements document (PRD). Say what the problem is, who it's for and what it must do; the map sorts it into decisions, ideas, questions and risks; then the Product brief agent writes a PRD from your map, with must-have and nice-to-have features kept apart and anything you didn't settle marked as a gap.

By Klevis Kokoshi, Founder of TalkGraph · Updated

1 · YOU TALK IT THROUGH, THEN OPEN AGENTS
Shift swaps for the café2 speakers · 9 cards
Café shift swaps
QUESTIONRota spreadsheet integrationWhether the app should integrate with or replace the rota spreadsheet managers use is still unknown.Tom
ACTIONAsk other branchesMaya will ask the other two branches how they handle swaps before deciding whether to integrate with or replace the rota spreadsheet.Maya
Current swap problems
FACTWhatsApp swap chaosEveryone currently swaps café shifts in the WhatsApp group, and it is chaotic.Maya
FACTUncovered shifts last monthThree shifts went uncovered last month, and each time the manager found out only when nobody turned up.Tom
Approval workflow
DECISIONManager-approved swap flowThe manager approves a claimed shift before it is final, and both people are notified when it is approved.Maya
DECISIONPhone-first web appThe first version must work on a phone and can be a web app without an app store.Maya
Eligibility and incentives
IDEAStation-trained visibilityOnly show a shift to colleagues trained for that station, since not everyone can run the coffee machine during a Saturday rush.Tom
QUESTIONTraining records locationMaya asks where trained staff are recorded, since she does not think this is written down anywhere.Maya
IDEALast-minute cover bonusTom suggested a small bonus for last-minute shift cover; Maya is not sure about it, so it is parked for now.Tom
2 · THE AGENT WRITES IT FROM YOUR MAP
Product brief (PRD)
From the map "Shift swaps for the café" · 20 nodes · saved with the map

Example: written by this agent from the sample map above. The conversation is fictional, made for this page.

Problem

Everyone currently swaps café shifts in the WhatsApp group, and it is chaotic. Last month, three shifts went uncovered, and each time the manager found out only when nobody turned up. Managers need to approve a claimed shift before it is final, so the process is more reliable than WhatsApp.

Who it's for

  • Café staff and colleagues who need to post or claim shifts.
  • Managers who approve claimed shifts.

Goals

  • Make shift swaps less chaotic than the current WhatsApp process.
  • Ensure a claimed shift is not final until the manager approves it.
  • Notify both people when a swap is approved.
  • To decidehow will you know it works?

Features

  • MUSTLet someone post a shift they cannot work.
  • MUSTLet a colleague claim a posted shift.
  • MUSTRequire manager approval before a claimed shift is final.
  • MUSTNotify both people when the swap is approved.
  • MUSTWork on a phone as a phone-friendly web app, without an app store for the first version.
  • NICEShow a shift only to colleagues trained for the relevant station.
  • NICEOffer a small bonus for covering a shift at the last minute. This idea is parked for now.

User flows

Post and claim a shift

  1. A staff member posts a shift they cannot work.
  2. A colleague claims the shift.
  3. The claim goes to the manager for approval.

Approve a swap

  1. The manager reviews the claimed shift.
  2. The manager approves the claim.
  3. The swap becomes final, and both people are notified.

Out of scope

  • A last-minute cover bonus is deferred for now.
  • An app-store version is out of scope for the first version.
  • To decidewhat is not in the first version?

Open questions

  • Should the web app integrate with the rota spreadsheet managers use, or replace it?
  • Where are station-training records kept? Maya does not think this is written down anywhere.
  • Should station-trained visibility be included if training records are not currently recorded?
  • Maya will ask the other two branches how they handle swaps before the decision about integrating with or replacing the rota spreadsheet.

What's in the brief

Gaps instead of guesses

The agent writes only from your map and your words. It doesn't invent features, users, platforms, numbers or deadlines; where the brief needs something you didn't say, it marks it in amber as 'To decide', such as 'To decide: who can sign in?'. Talk it through again, or answer the gaps on the map, and run it again.

From brief to build

The brief costs 20 nodes and is saved with the map. Copy it, download it as Markdown or as a PDF in this design, and hand it to a developer or paste it into an AI coding tool.

Questions people ask

What is a PRD?

A product requirements document: the brief a team builds from. It says what problem the product solves, for whom, what it must do, what is out of scope and what's still undecided.

Can AI write a PRD from a conversation?

Yes. TalkGraph maps the conversation as you talk, and the Product brief agent writes the PRD from that map. It uses only what was said and marks the rest as gaps.

How much does it cost?

A product brief costs 20 nodes. The free plan gives 250 nodes a month with no card, so you can run it on the free plan.

Can I use it with an AI coding tool?

Yes. Copy the brief or download it as Markdown and give it to the tool as the spec. Fill the gaps first: they are exactly the questions a builder would ask.

Does it use my earlier conversations?

No. It writes from the map you run it on and that map's transcript. To bring earlier thinking in, talk it through again on this map; Prep me is the agent that pulls in earlier conversations from your Brain.

Related

Say it out loud. Map it now.

Write a brief free

These optional services load only after you accept. Closing the banner leaves them off. You can change your choice at any time using “Review privacy choices” on our Privacy Policy page.

Read the Privacy Policy