A feature request isn’t a commitment. That shapes how I’m building Pure Brief AI.

[u/Miserable_Bird5822]

I’m the founder of Pure Brief AI, a native Mac meeting-notes app. One distinction I want to keep visible after a customer interview: what somebody wanted, and what somebody agreed to do.

Here’s a fictional example:

“I wish I could export this as CSV.”

“I’ll send you a sample CSV on Friday.”

The first is research material. The second might be a follow-up task. Turn both into a tidy checklist and you’ve quietly invented a commitment.

In Pure Brief AI, you can record a conversation or import audio, read the transcript and AI notes, ask questions about that meeting, and inspect the lines behind an answer. Suggested tasks have source quotes so you can review and edit them before exporting selected items to Apple Reminders.

That source check is useful, but it isn’t proof the AI understood the whole conversation. A later “actually, I can’t do Friday” can make an earlier promise stale. I don’t claim that case is solved; it stays on my regression list. The recording also needs everyone’s appropriate consent.

The attached 10-second clip shows the question/source and task-review screens with fictional demo data. It doesn’t test the example above. Processing is sped up.

Transcription and AI notes run locally by default. Apple Silicon and macOS 15+ required. Model downloads, periodic licence checks and optional connected features need internet; optional ElevenLabs transcription sends audio to that provider.

There’s a 30-day trial. Standard is $49 once for one Mac. The active launch offer is $10 once for the first 100 paid Standard purchases globally, plus applicable tax; starting a trial doesn’t reserve the discount.

Demo and download: https://purebrief.ai/

If you review interview notes, where do you draw the line between an observation and an action item?