Spend half the time on follow-ups.
Never let one slip.
ConductFlow finds commitments in your calls, emails, slack, drafts the next step, and tracks the administrative work.
google sign-in · name and email only · mac app is apple silicon, unsigned
You Yeah, that's fine. I'll get Mia's revised practice set over to you by Friday.
Parent Perfect. She'll be pleased.
Hi, sharing Mia's revised practice set, as promised.
From conversation to follow-through.
Extract the commitment
Find the promise in the transcript.
You I'll get Mia's revised practice set over to you by Friday.
Review the follow-up
Approve the words before they leave drafts.
Do the follow-up
Keep the final send in your hands.
Every commitment gets a path to done.
ConductFlow keeps the original words, the owner, the deadline, and the follow-up connected from the moment the promise is made.
Call / transcript
Bring the conversation in.
Commitment extracted
Keep the original words.
Owner + due date
Make the next step clear.
Follow-up drafted
Start from the evidence.
User approval
You decide what goes out.
Completion tracked
See whether it got done.
Six things it cannot do, whatever anyone sets
These are refused by the code that runs before any action, not by a preference somebody could change on a bad afternoon. There is no switch in settings for them, and no support ticket that makes an exception.
Send an email to anyone
refused in codeNot to your client, and not even with your approval. The Gmail module has two calls in it and neither one sends. A test reads that file and fails the build if the word turns up there at all. What approving does is write the follow-up into your own Gmail drafts, where it waits until you open Gmail and send it yourself.
- Change what was agreedchange_scope
- Change a pricechange_pricing
- Sign anythingsign_contract
- Take a paymenttake_payment
- Delete a recorddelete_record
Everything above that floor is yours to set: what the assistant may do on its own, and what it has to ask you about first. Each change writes a new version instead of overwriting the last one, so what it was allowed to do on the day it did something stays answerable.
Capture a call without opening a tab
A menu-bar app for Mac. Copy the notes from a call, press ⌘⇧I, and the commitments land in your queue as proposals. It reads your clipboard when you ask it to, and nothing else. Nothing sends — you still approve every draft here.
This build is not notarised by Apple, so the first launch needs a right-click → Open instead of a double-click. It runs on Apple Silicon only. Create a token under Settings → Desktop app once you have signed in.
What you would find out in week two
Nothing of ours joins your call. There is no bot in the meeting and no recording. You bring the transcript afterwards, or just the notes you typed while you talked.
An overdue promise shows up on your board the next time you open it. Nobody gets emailed about it, and that includes you.
Extraction is a language model reading a transcript, and it misreads things. That is why every promise arrives with the sentence it came from, and why one whose words cannot be found in your transcript is marked low confidence instead of passed off as certain. You are checking evidence, not trusting a summary.
The operations view stays quiet until there are about twenty commitments in it. Before that there is not enough there to say anything honest about your lead times.
Try it on the call you had yesterday.
Paste the notes in and read what comes back. If none of it is worth approving, you have lost about four minutes and nothing has left the building.
Start with one call