folo for consultants
Last updated: July 2026
Use cases › Consultants
As an independent consultant you are the delivery and the back office. The calendar is back-to-back client calls, each under its own NDA, and the value of a call starts leaking the moment it ends: the decision nobody wrote down, the scope change nobody logged, the follow-up you meant to send before the next call swallowed the afternoon. This page is about using on-device notes so the record of every engagement stays yours — private, billable, and off anyone else’s server.
The call ends and the unpaid work begins
The meeting is the easy part. Then comes the write-up: reconstruct the decisions, pull out who owns which action item, draft the follow-up email, update the status doc for the retainer. Consultants routinely lose 30–40% of their non-billable hours to this, and a two-hour discovery session can generate 45–90 minutes of documentation while you scramble to get it down before the memory fades.
folo writes that structured summary the moment the call ends — decisions, next steps and a clean list of action items — using a Sales/Customer or General template. Apple Intelligence, Ollama and Local MLX process it on your Mac when selected globally. Otherwise, folo sends transcript text directly to Anthropic using the stored API key, or the locally installed Claude CLI sends it to Anthropic using its separate CLI authentication. You review and send instead of reconstructing from a legal pad, and the record is the same for every client whether the call ran long or you were three engagements deep by lunch.
Every client sits under a different NDA
A solo consultant’s meeting archive is unusually sensitive: competing clients, confidential strategy, numbers under NDA — all yours to keep separate. A cloud notetaker collapses that separation. It uploads every client’s call into one vendor account, governed by a terms-of-service document you can’t negotiate, and increasingly enriched with names and titles pulled from the invite until the archive is a map of your whole book of business.
folo is on-device by default: recording and speaker recognition happen on your Mac, and local transcription and summary backends are available. Backend choices apply globally in Settings. ElevenLabs receives meeting audio only when selected for transcription. For summaries, folo sends transcript text directly to Anthropic using the stored API key, or the locally installed Claude CLI sends it to Anthropic using its separate CLI authentication. Configured webhooks send selected meeting metadata — local numeric ID, suite UUID when available, title, start/end/duration, language, attendees, status and assignment engagement ID — to user-added HTTPS endpoints, not audio, transcripts or summaries. Keeping transcripts off other people’s servers goes deeper on why that distinction matters.
Who committed to what — and when
Scope creep is where consulting money quietly disappears. A client drops an out-of-scope request into a call, everyone nods, and it never gets logged because “we can’t bill it anyway.” Months later there’s no evidence for a change order or a renewal conversation — just a vague memory against the client’s vaguer one.
A verbatim, timestamped transcript with who-said-what is the paper trail that fixes this. folo’s on-device speaker recognition separates each voice in the room, and Speaker Memory lets you name a client stakeholder’s voice once so folo recognizes that same person across every future meeting in the engagement. When you need to show exactly what was agreed and by whom, it’s already written down — locally, and searchable.
From the call to the invoice
Consultants leak an estimated 15–25% of billable hours simply because the time never got recorded, and reconstructing a week of calls from memory is where more of it vanishes. folo closes that gap: one toggle hands every finished meeting to Døgn, the companion time tracker, so the call you just had becomes tracked, billable time without retyping a thing — and that tracked time flows on to a tjent invoice. It reads your macOS calendar locally through EventKit to label meetings, so there are no calendar accounts connected to a cloud. The conversation, the billable minutes and the line item on the invoice are one continuous chain instead of three separate acts of admin.
Where folo fits — and where it doesn’t
folo is Mac-only, single-user, and it needs to be running on your machine during the call. If you need a recording made while you’re away from your desk, or a shared workspace a whole client team can open, a cloud recorder is the honest better fit — folo vs Otter.ai and folo vs Fathom lay out where those win. But if you’re at your Mac anyway, you can keep meeting content local by selecting local transcription and summary backends and leaving external webhooks unconfigured. None of this removes the duty to tell clients you’re recording; consent comes first.
Questions, answered
Can I keep each client’s meetings confidential and separate?
Yes. folo records and recognizes speakers on your Mac, and local transcription and summary backends are available. Backend selection is global in Settings; optional cloud backends and configured webhooks are the disclosed egress paths.
Does folo help me actually bill for meeting time?
One toggle hands every finished meeting to Døgn, the companion time tracker, so the call becomes tracked, billable time without retyping — and that flows on to a tjent invoice. It reads your macOS calendar locally to label meetings, with no calendar account connected.
Will it capture what a client committed to?
folo produces a verbatim, timestamped transcript with who-said-what plus a summary of decisions and action items from the globally selected backend — the paper trail you need for a change order or renewal. It’s documentation, not legal advice, but it’s far better than reconstructing a call from memory.
Do I still need consent to record a client call?
Yes. Selecting a local transcription backend keeps meeting audio away from a transcription provider; globally selected ElevenLabs uploads the audio. Either way, you must disclose the recording — required outright in all-party-consent states and generally under GDPR. Announce it and note it in the invite. This is not legal advice.