A walk through Chat, Cowork & the Q2 rollout — how we turn 80 % admin into 80 % strategy.
Today the team spends the majority of its hours on admin — sheets, reports, follow-ups, chasing transcripts. Kai's target for Q2: Claude absorbs the bulk of that work so we get back to sales and strategy.
Division leaders burn the day on spreadsheets, CRM updates, transcript wrangling, and copy-paste loops.
Claude agents handle the repetitive work. Humans stay on the decisions — and on revenue.
The familiar back-and-forth — like ChatGPT. Great for thinking out loud, drafting, Q&A.
The agent. Opens Chrome, reads Drive, drafts emails, sends Slack messages, runs scrapers.
Opens pages, fills forms, reads content, closes tabs — the way a human would.
Writes Slack messages, Gmail drafts, and replies — with your tone and the right context.
Mid-task, Claude decides which connector to call. You don't stitch the workflow.
For anything destructive — creating records, sending messages — Claude pauses and gets your nod first.
A connector is a bundle of tools — list_records, send_message, create_file. Claude picks which to call, mid-conversation, based on what you ask.
…and any other service with an MCP. Ask Marco.
Kai asked me to draft how we'd roll Claude out across the team. Here's what I gave Cowork — and what came back.
11 pages, mostly tables and bullets. Two tiny edits. On Drive before I'd made coffee.
Claude isn't one-shot. If it's mid-task and you realise something — a missing file, a wrong assumption, a better idea — just type. It hears you and adjusts.
The Fathom MCP failed mid-draft. While it was still elaborating, I just pasted the transcript into the chat. It picked it up and carried on.
Modern Claude is solid on reasoning. Where it slips is the details — a name, a date, a tiny fact. Review before anything goes to a human, a CRM, or a live channel.
The fan-pages division is hiring an editor. Kai dropped a LinkedIn post where candidates had already commented offering their work — the task was to turn those comments into a ranked shortlist. Here's what Cowork did, unaided.
"Pull the commenters on this post, find who's best for the 8 Media fan-page editor role, draft them a first message."
| # | Name | Title | Location | Comment | Priority | Status | Draft message | ||
|---|---|---|---|---|---|---|---|---|---|
| 1 | J. Martínez | /in/jm-edits | Fan-page editor | Medellín | j.m@… | "3 yrs, 2M views/mo" | High | Not sent | "Hey Juan — saw your…" |
| 2 | A. Rivera | /in/arivera | Social editor | Lima | a.r@… | "Portfolio in bio" | High | Not sent | "Hi Ana — your page…" |
| 3 | D. Okafor | /in/dok | Content creator | Lagos | — | "Dm me!" | Med | Not sent | "Hi Dami — caught your…" |
| 4 | L. Nguyen | /in/lng-social | FB page manager | Remote | l.n@… | "5M reach/mo" | High | Not sent | "Hey Linh — the reach…" |
| 5 | S. Patel | /in/spatel | Editor & designer | Bangalore | s.p@… | "Both & video" | Med | Not sent | "Hi Sana — video on…" |
"Priority" and "Draft message" were my follow-up additions mid-chat. Claude amended the sheet in place.
Friday afternoon ritual: read every message anyone has tagged me in, across DMs and channels, and build a prioritised list. Used to take 90 minutes.
Reusable as a scheduled task — see slide 15.
María asked this on the call: could Claude pull Instantly metrics on demand instead of her logging in every day? Yes — and there's one wrinkle worth knowing.
Claude can't see workspace names on its own. Teach it the mapping once — say "remember this" — and it sticks across every future chat.
Each connector exposes a set of actions Claude can call — list_bases, send_message, create_file. Claude picks the right one mid-conversation based on what you've asked.
I approve each connector once at the org level. After that, every teammate authenticates their own account — your Airtable scope never bleeds into anyone else's.
A hosted URL from the vendor. Plug in two fields, sign in, done.
Open-source connectors that need a server. Fathom is one. I host it, wire in API keys, push it out.
See a tool you use daily that's not connected? Tell me. If it has an API, I can get it into Cowork — usually within a day.
Per connector, you decide which tools Claude can call on its own, and which need your explicit OK. Set it once — the rule sticks.
Reading records, searching, listing tables. No approval needed — otherwise you'd click "yes" all day.
Creating records, editing rows, deleting tables. Claude pauses and asks before anything changes.
Canva, Figma, Gamma. Claude drives the app itself — you watch it happen and approve big steps.
Flagship reasoning. Slower, heavier. The highest quality you can ask Claude for — but you rarely need it.
Reach for it when the stakes or complexity are genuinely high — tough research, sensitive writes, gnarly edge cases.
The workhorse. Strong balance of quality and speed. Handles almost everything you'll throw at Cowork in a normal week.
Reach for it for roughly 90% of real work. It's what your chat defaults to, and that's almost always the right call.
Small and fast. Built for high-volume automation where speed beats depth — think scheduled tasks hitting thousands of rows.
Reach for it almost never. Not the right tool for the tasks you'll do by hand.
A skill is a pre-written prompt with context, triggered by /name. You do the same thing weekly? Bottle it.
Yes — these slides were generated by the /frontend-slides skill from this meeting's transcript.
Group related chats under one umbrella — a client, a campaign, an ongoing initiative. Shared memory, shared files.
Any prompt you run weekly can become a cron. "Every Monday 9am: build my task list from Slack." Runs without you.
Drive your desktop Claude from your phone. Leave Cowork running; trigger it from a couch, an Uber, anywhere.
Claude Desktop installed, connectors authenticated, Fathom recording on every call. Can ask a basic question and get an answer.
At least one real task through Claude every workday. Summarises transcripts, builds reports from Airtable, generates to-dos from meetings — without falling back to manual.
Finds new workflows. Teaches teammates. Ships their own skills. Admin time cut by 50 %+. Q2 goal: at least 3 of these on the team.
What's the first piece of your week you want Claude to take off your plate?