Shelf
Catalog Meeting-to-Memo Newsletter
See how it works · Meeting-to-Memo

How Meeting-to-Memo works

Your expertise, faster.

Here's the full flow, end to end. A realistic sprint-planning meeting goes in. A memo, action items, decisions, risks, a stakeholder email, and a Slack post come out.

The actual tool runs locally and works exactly the way you'll see below. This page is the preview.

Step 01

The tool opens with empty form sections

Double-click Meeting-to-Memo.html from your downloads. It opens in any browser. No install, no account, no API key.

file:///Meeting-to-Memo.html
Shelf HQ v2.2

Paste your meeting transcript

Any format works: Otter, Fireflies, Granola, Zoom, voice-to-text.

Paste transcript here...

Tell me about the meeting

Optional. Type, audience, anything that affects tone.

Optional context...

What do you need?

Three core outputs are checked by default. Add what fits.

Memo
Concise paste-ready summary
Action items
Owner, task, due date table
Decisions plus open questions
What was decided. What's still TBD.
Risks raised
Concerns surfaced and mitigations discussed
Stakeholder follow-up email
For the VP who wasn't there
Slack post
Recap for the team channel
Pastes a ready-to-go prompt for ChatGPT, Claude, or Gemini.
Step 02

Paste the meeting transcript

Drop the raw transcript in. Speaker names, timestamps, side-threads. Leave it messy. The tool handles it.

Paste your meeting transcript

Any format works: Otter, Fireflies, Granola, Zoom, voice-to-text.

[14:03] Sarah: ...so we're pushing checkout to sprint 12. Marcus, does that work?
[14:03] Marcus: If we move payments to 13, yeah. But that bumps everything after.
[14:04] Sarah: OK. Marcus takes payments in 13, Priya does checkout mocks by Friday.
[14:04] Tom: Will there be a flag for beta users? I promised three by the 15th.
[14:05] Priya: I can add a toggle to the mocks.
[14:08] Sarah: Dave, when you're back from PTO Monday, can you take over the auth migration?
[14:09] Dave: Yeah. I'll review what's been done and pick it up Monday morning.
[14:14] Tom: One concern. If checkout slips to 13, does that affect the holiday push?
[14:15] Sarah: Q4 launch still hits the same deadline. We're parallelizing, not delaying.
... 18 more minutes of discussion, decisions, and side-threads ...
Step 03

Add a bit of context. Pick what you need back.

A short context note sharpens tone. Then check the outputs that fit this meeting. The three core outputs come pre-checked. Add stakeholder email, Slack post, and risks for this one since it's a sprint shift the VP needs to know about.

Tell me about the meeting

Optional. Type, audience, anything that affects tone.

Engineering sprint planning. 30 min. Team of 5. We're 6 weeks from Q4 launch and shifted two work items between sprints today. The VP wasn't in the room and needs the recap.

What do you need?

Three core outputs are checked by default. Add what fits.

Memo
Concise paste-ready summary
Action items
Owner, task, due date table
Decisions plus open questions
What was decided. What's still TBD.
Risks raised
Concerns surfaced and mitigations discussed
Stakeholder follow-up email
For the VP who wasn't there
Slack post
Recap for the team channel
Step 04

Click Build. The full prompt assembles.

One click. The tool stitches your transcript, your context, and the output rules into one paste-ready prompt. Copy with one button. Open ChatGPT, Claude, or Gemini directly with the next.

Your prompt is ready

You are processing a meeting transcript and producing structured follow-through outputs. CONTEXT FROM THE BUYER: Engineering sprint planning. 30 min. Team of 5. We're 6 weeks from Q4 launch and shifted two work items between sprints today. The VP wasn't in the room and needs the recap. TRANSCRIPT: [14:03] Sarah: ...so we're pushing checkout to sprint 12. Marcus, does that work? [14:03] Marcus: If we move payments to 13, yeah... [full transcript embedded here] OUTPUT EVERY SECTION BELOW, CLEARLY DELIMITED: ===== MEMO ===== [concise paste-ready summary, 150-300 words] ===== ACTION ITEMS ===== [owner, task, due date table] ===== DECISIONS PLUS OPEN QUESTIONS ===== [what was decided. what's still TBD.] ===== RISKS RAISED ===== [concerns surfaced with mitigations discussed] ===== STAKEHOLDER FOLLOW-UP EMAIL ===== [email to the VP who wasn't there] ===== SLACK POST ===== [team-channel recap, scannable] ===== OUTPUT RULES (STRICT) ===== - No preamble before the first output - No clarifying questions - No meta-commentary or step-by-step explanation - No disclaimers - Produce all selected sections in one response, clearly delimited - Do not skip a section even if information is sparse
Step 05

Paste into your AI. Every piece comes back, ready to use.

Open a fresh chat in ChatGPT, Claude, or Gemini. Paste. Hit send. Every piece you checked comes back in one response, each clearly labeled, ready to copy where it's going.

Claude Fresh chat. Response received.
===== MEMO =====
Sprint 12 checkout pushed to sprint 13 to avoid a payments-refactor conflict. Priya delivers checkout mocks with a beta-user flag toggle by Friday. Three beta customers are promised access by the 15th. Dave picks up the auth migration Monday on PTO return. Q4 holiday launch deadline unchanged; tracks parallelized.
===== ACTION ITEMS =====
MarcusPayments refactorSprint 13
PriyaCheckout mocks plus beta flagFriday
TomConfirm beta customer listMon 9am
DaveAuth migration (review and pickup)Mon 9am
TomValidate Q4 holiday-push timingWed
===== DECISIONS PLUS OPEN QUESTIONS =====
Decisions made
  • Checkout pushed from sprint 12 to 13
  • Payments refactor moved to sprint 13
  • Beta-user flag toggle added to checkout mocks
  • Dave owns auth migration starting Monday
Open questions
  • Will sprint 13 still hit Q4 holiday-launch dependencies?
  • Does the beta flag need analytics tagging?
===== RISKS RAISED =====
  1. Holiday-push exposure. Checkout slipping into sprint 13 puts Q4 launch on the same critical path as the payments refactor. Mitigation discussed: parallelizing tracks, not delaying.
  2. Beta customer commitment. Three customers promised by the 15th. The flag toggle has to ship Friday with the mocks to allow integration testing.
===== STAKEHOLDER FOLLOW-UP EMAIL =====
Subject: Sprint 12 update, checkout moved to 13

Hi [VP],

Quick recap from today's sprint planning. We moved the checkout launch from sprint 12 to 13 to avoid a regression risk with the payments refactor landing in the same window.

Priya delivers checkout mocks with a beta-user flag by Friday. Three beta customers are promised access by the 15th, so the flag has to ship on time. Dave picks up the auth migration Monday from PTO.

Q4 holiday launch hits the same deadline. We're parallelizing, not delaying.

Let me know if you have questions.
===== SLACK POST =====
:rocket: Sprint planning recap

Big shifts:
• Checkout to sprint 13 (was 12)
• Payments refactor to sprint 13 (was 12)
• Auth migration to @dave on Monday

Owners:
• @marcus, payments refactor (S13)
• @priya, checkout mocks plus beta flag (Fri)
• @tom, confirm beta list (Mon)

Q4 holiday launch deadline unchanged. We're parallelizing.

That's the whole flow.

From a 30-minute meeting transcript to six paste-ready follow-through pieces in under two minutes of your time.

The 15% that matters (verifying who said what, fixing names, confirming action items with attendees) is yours.

$10
Buy Meeting-to-Memo Back to product page
One-time. Lifetime updates. 7-day refund if the product doesn't work as described.
Powered by Gumroad
Walkthrough captured on v2.2.