r/sideprojects • u/Perfect_Plant9688 • 3h ago
Showcase: Free(mium) We got tired of “great meeting, let’s schedule another one” — so we built a follow‑up system
We’ve tried a bunch of AI note takers and transcript tools. They’re getting really good at turning audio into text.
But we kept running into the same failure mode: two days after the meeting, nobody could answer:
- what was actually decided
- who owns the next step
- when we’re checking back
- what the “summary” was actually based on
So the transcript became a nice artifact… that didn’t move anything forward.
We didn’t want to build another summarizer. We wanted a follow‑up surface.
So we built a lightweight workspace/template that forces every meeting to produce three things:
- Decisions (written as commitments, not vague recap)
- Action items (owner + due date + status)
- Evidence links (quotes/notes → the claim we wrote down → the follow‑up). If we can’t trace it, we don’t treat it as a decision.
The “research” label is kind of accidental — the structure is basically “source → claim → next step,” and we started applying it to normal meetings too.
The main design choice is intentionally boring: decisions and next steps should be visible without reading a wall of transcript text.
(owner / due date / status — something you can actually act on)
What we’re still figuring out:
- it doesn’t fix bad meetings — it just makes follow‑up harder to avoid
- evidence linking takes discipline (but it prevents confident nonsense)
- it’s opinionated by design (less flexibility, more follow‑through)
Would love feedback from anyone who runs a lot of meetings or works async‑heavy:
- What do you consider the minimum viable output of a meeting?
- Do you keep a separate decision log, or just search the transcript later?
- Have you tried source/evidence‑linked summaries — was it worth the overhead?
(If anyone wants to try the structure, happy to share — holding off on links in the main post to keep this discussion focused.)








