Why I built Briefi — five workspaces, one chair

I work across five workspaces. A consultancy, a SaaS I'm building, a marketing arm I'm a director of, and a couple more besides — between my own ventures and the work I do for the businesses I help run, the calendar lands somewhere between sixty and eighty external calls a month. Most weeks I'm in seven meetings a day across three workspaces.

Nine months ago, on a Friday afternoon, I counted the follow-up emails I owed. Forty-two. Some were ten days old. The pattern was always the same: walk in half-prepped because the brief was 'later', take notes that didn't survive the day, and try to write the recap on a Sunday night when I should have been off. The post-meeting tax was eating the meetings.

What nothing in the category did

The honest version of why I built Briefi: nothing in the category had the shape of my actual day. Otter solves transcription, which I don't need — I take my own notes. Gong solves sales-team analytics, which I'm not. Granola is closer in vibe but assumes one workspace and one notebook. Nothing did the loop end-to-end across multiple workspaces, and nothing pushed outcomes into the right CRM per workspace.

The other gap was post-meeting work. Even the best meeting AI stopped at the transcript. None of them wrote the follow-up in my voice, marked the deal stage in the right CRM, scheduled the next call, and surfaced what I should have done that I hadn't. The work between meetings is most of the work.

The loop, end to end

So I built the loop. Prepare reads my calendar, picks the right discovery guide for the industry, and drafts a brief that names the three smart questions and the red flags. During gives me a focused notepad with one-tap chips for Decision / Action / Pain — and a discovery-guide drawer I can walk live without breaking eye contact. Follow-up writes the email in my voice the moment I leave the room, then pushes the deal, contact and notes into the right CRM. Salesforce, HubSpot, GoHighLevel, Monday, Pipedrive, Zoho — ten in total, picked per workspace.

The shape that mattered most was the one most existing tools assumed away: that I'm in different workspaces during the day. Same hour, different context. The meeting AI either lives inside one workspace forever, or it dumps everything into one big bucket and you sort it later. Neither works for someone juggling four or five.

Why workspaces, not accounts

The multi-tenant model exists because I literally needed it. One Briefi login, multiple workspaces, segregated data per workspace, one Command bar across the lot. Logging in and out of separate accounts isn't a workflow — it's an interruption every twenty minutes for the rest of your career.

A workspace doesn't have to be a separate registered business. It might be a brand inside one company, a consulting client, a personal project, a board role. The criterion is simpler: if the meetings, contacts, and pipeline genuinely shouldn't mix with everything else, it gets its own workspace.

Mundane in the best way

I dogfooded for nine months before letting anyone else in. Started with two workspaces, scaled to five. The MCP server exists because I wanted my Claude Desktop to read my own meetings without copy-pasting briefs into the chat. Native scheduling exists because Calendly couldn't route invites to the right Google account per workspace.

The thing that's worked for me, and the reason I'm finally shipping it: the loop is mundane in the best way. I never log out of a workspace. I never lose context. The follow-up email is in my drafts before the next meeting starts. The CRM is clean by Friday. The week ends.

Who this is for

Briefi is for people who run too many meetings — solo founders, sales-led small teams, directors juggling multiple ventures, consultants juggling client work, chiefs of staff sitting in everyone else's calendar. If you've ever ended a Friday with twenty follow-ups owed and no system for closing them, this is the tool I wish I'd had four years ago.

Run the full loop on a few meetings each month, free. Founder pricing locked forever for the first wave. I'm building this for myself, and I want the people who join early to feel that.

If you want the long version of the multi-workspace architecture decision, that's in multi-workspace is not multi-tenancy. The founder-pricing reasoning is in founder pricing — locked forever. And the product page walks through the whole loop in screenshots.