Comes in from

KakaoTalk chats — PC · Android · iPhone · Mac
Zoom · Teams · Google Meet — transcripts · meeting audio
CLOVA Note · recording apps
Call transcripts
In-person meeting recordings
Audio files

Goes out to

Your client — a sign-off link, no sign-up
Claude Code · Codex — read-only
Extra-work quote
Change agreement
Acceptance record
Excel · table copy

Each name is a trademark of its company. PLARO is not affiliated with them.

Why it matters

Requirements don’t change in the document. They change in conversation.

After kickoff, changes scatter across chats, calls and meetings. The document stays at v1, and your developers — and their AI — keep building v1. When it comes down to “but we said that,” there is nothing on record.

1 → 60: Disputes over extra work in Korean public-sector software sent to mediation — 1 in 2014, 60 in 2025, and 59 in the first half of 2026 alone · Jodal Economy (Korean)
₩17 million: A Korean court dismissed a claim for extra-work payment because no record showed the agreement · Seoul Central District Court 2023Gadan5186183

① Import conversations

Bring it in from wherever the conversation happened

Upload a Zoom or Teams transcript, a KakaoTalk chat export, a CLOVA Note file or a call transcript — or paste the text. PLARO tells from the content where the file came from. You can also record the meeting in PLARO: in person on your phone, or online in Chrome with the meeting’s own audio.

Files: txt · docx · pdf · vtt · srt · csv · zip · hwp · xlsx — up to 20 MB
Paste: Up to 40,000 characters · audio files up to 500 MB
Transcripts: Speakers and times read from Zoom and Teams files

① Drop a Zoom transcript — one line says what it is → [Compare]

What changed, what’s missing, what’s open — with who said it and when

PLARO compares the conversation with your current requirements line by line and sorts what it finds into three kinds. Each card carries the original line it rests on, with who said it and when. A finding that quotes words not in the original is dropped before it is saved.

Time taken: 27–35 s — a two-week chat sample, timed 4 times
AI findings: A draft — a person picks what goes in
Recordings: Jump to that moment in the original audio

② When the comparison ends: result chips → the evidence line up close — who said it and when

Only what you pick becomes the new version

Choose Apply, Edit and apply, or Ignore on each card, then press [Create v2]. The previous version stays as it was, and the change log keeps what changed and why, line by line.

Numbers: R-n stays the same across versions
Change log: Before · after · reason · evidence (quote) · who · when
Export: Copy the table · Excel · [Copy this meeting's changes]

③ Apply · Edit and apply · Ignore → [Create v2] → changed and new lines → change log

Your client confirms only what changed — no sign-up

Your client opens the email link — or a link you sent in a chat — and sees only the lines that changed in this version. [I confirm] or [Something needs to change]. Who confirmed what, and when, is kept as a record that can’t be edited later.

Client sign-up: None — a copied link asks for an email code once
Record fingerprint: Each answer’s SHA-256 fingerprint is chained to the one before
Limits: A confirmation record, not an e-signature

④ Email → link → [I confirm] → “Client confirmed” on the PM’s screen

More on client sign-off and documents →

⑤ Developer AI

Confirmed changes go straight to your developer’s AI

Connect the project to the Claude Code or Codex your developer uses. When they talk to it, it first sees “since the last notice — 1 new version · 3 requirement changes · 1 open question” and plans the work in that repository to match. PLARO only gives read access, and never sends meeting transcripts, amounts or client contacts.

Connect: Two lines for the Claude Code plugin · one for Codex
Developers: No sign-up — they sign in with a mailed code
What the PM sees: “Sam — received up to v2”

⑤ Change notice “v1 → v2” → the change-planning command → PLARO shows “received up to v2”

What changed, in writing

Add the extra days and amount to each applied change and it becomes an extra-work quote. When your client confirms it through the link you get a change agreement, and when they confirm the acceptance results at delivery, an acceptance record. People write the amounts — the AI never fills them in.

These are records of agreement. They don’t replace an e-signature or a contract.

Can you trust it with your work?

What the AI does — and doesn’t — stated up front

Storage: Requirements and meeting transcripts are stored encrypted
AI training: Not used for training — by PLARO, or by the AI and transcription providers it uses (OpenAI API · Anthropic API · AssemblyAI with model improvement turned off)
Where the AI stops: Findings without evidence are dropped · amounts are never filled in · a person decides what goes in
Our own test: 4 fictional meetings · 31 answers fixed in advance · 3 runs — 98.8% found (lowest meeting 86%) · 0 wrong findings · slowest comparison 47 s
Deletion: Projects 30 days after they go to the trash · right away when you close your account
Service countries: Korea · United States · Canada · Australia · New Zealand · Singapore

Our test uses meetings and answers we wrote ourselves, so real meetings may differ.

Pricing

Start free, move up when you need to

Sign up without a card. The free limits refill every month.

Pricing details →

No card to sign up · tax included · cancel any time (keeps the paid period)

Questions

The usual hesitations, answered first

Do meetings have to happen in PLARO?: No. Wherever you meet, add the transcript or the recording. Recording in PLARO just saves you that step.
How do chats get in?: Upload the file the chat app exports. A KakaoTalk “Export chat” file goes in as it is — from PC, Android, iPhone (zip) or Mac (csv). Zoom and Teams transcripts (.vtt) work the same way.
What if the AI gets it wrong?: What it finds is a draft. On each card you see the original words and choose Apply, Edit and apply, or Ignore. Only what you choose goes into the new version.
Does my client need an account?: No. They open the email link. A link you send in a chat asks for an email code once.
What does the developer’s AI receive?: Only the confirmed requirements, what changed, open questions and unmet acceptance criteria. Meeting and chat transcripts, amounts and client contacts never go. It is read-only.
Is our conversation used to train AI?: No. Neither PLARO nor the AI and transcription providers it uses — we only use them on terms that rule out training.
Can I use it on my own?: Yes. It is built for one PM to sign up and use end to end. For a team, there is the Business plan.

Guides to requirements and meeting changes

PLARO compares client project requirements with meeting content, helps managers keep reviewed changes in new document versions, and records client confirmation.

Getting started

Requirements document example and reusable template

Use an online store redesign sample to separate requirements, acceptance criteria and open questions, and keep document versions.

Review meeting changes and request client confirmation

Compare a meeting excerpt with requirements v1, review the proposed change, then create v2 and request client confirmation.

Importing conversations

How to bring chats and meeting transcripts into PLARO

Where to export KakaoTalk chats (PC · Mac · iPhone · Galaxy), Zoom, Teams and Google Meet transcripts, CLOVA Note files and iPhone call recordings — and how they go into PLARO.

Developer AI

Connecting your developer’s Claude Code or Codex to the requirements

How a developer’s email lets their AI read the confirmed requirements and what changed — what goes and what doesn’t, connecting and signing in for each tool, and managing connections.

From your next meeting on, PLARO finds what changed

Sign up and try it right away with the sample project “Online store redesign”.

Start free

Requirements changed in conversation,built exactly as agreed