JOURNAL

What Claude actually does inside a 12-person SaaS team.

It removes the work your team shouldn't have been doing in the first place.

Claude does not replace your team. It removes the work your team should not have been doing in the first place.

That is the line I use in audits, and it is the only one a 12-person SaaS team needs to understand before they decide whether Brinvik is worth talking to.

The audit moment

Walk into a 12-person SaaS company on a Tuesday and watch the week:

The two salespeople spend 6 hours each on CRM hygiene. Updating stages. Logging activities. Writing the same handoff note for the third time this month.

The customer success lead spends 4 hours pulling reports. The same reports. From the same places. Every week.

The two founders spend a combined 5 hours writing the same three onboarding emails to new customers. Every email is technically personalized. Every email is functionally identical.

Engineering does not show up in this list because engineering is doing the work nobody else can do. The work that makes the product the product. That is the work you want preserved.

The other 27 hours are repetitive knowledge work. They are not the product. They are not the moat. They are the friction the company tolerates because nobody has shown them the alternative.

The wedge

Claude is best at repeated knowledge work that has clear inputs and clear quality bars. The five tasks that come up in every audit:

1. Lead qualification. Inbound form, enrichment data, prior touches. The team writes a draft qualification in 30 seconds based on the same five criteria they have been using for a year. Claude can write that draft in two seconds and route it to a human for the final yes or no.
2. Meeting prep. A 30-minute prospect call needs a 15-minute prep brief. The brief lives in HubSpot, your notes, LinkedIn, and the prospect's pricing page. Claude gathers, summarizes, and surfaces three good questions before the call. The salesperson reads it walking to the kitchen for coffee.
3. Post-call summaries. Recording in. Transcript out. Action items, follow-up email draft, CRM update, ready in 90 seconds. The salesperson reviews, sends, and moves on.
4. Documentation drafts. A new feature ships. The release note, the help-center article, and the in-app tooltip can all start from the same Claude draft. The product writer becomes an editor instead of a generator.
5. Internal Q&A. "What is our refund policy for annual contracts canceled in month 11?" The answer lives in three documents your team has not opened in six months. Claude has read them. Claude knows.

Five tasks. Roughly 18 hours per week recovered, in a typical 12-person team.

What Claude does not do well

The honest list:

• Novel creative work that requires taste rather than competence.
• Judgment calls that depend on relationship context the team does not write down.
• Decisions where the right answer needs human accountability.
• Anything where being wrong silently is worse than being slow.

If your team's Tuesday is mostly judgment calls and novel creative work, Claude is not your wedge. If your team's Tuesday is mostly the five tasks above, you are leaving 18 hours per week on the floor.

A specific deployment

A 14-person sales-led SaaS in the Nordics, four months into a Brinvik retainer:

I deployed three Claude projects. The first runs against HubSpot — qualification, meeting prep, post-call summaries. The second runs against Notion — documentation drafts and internal Q&A. The third runs in Slack — answering "where is X" and "what is the latest version of Y" without anyone needing to ping the founder.

The integration list is short. HubSpot read and write. Notion read. Slack bot. Calendly read for prep timing. Five integrations total. Every integration uses an existing API. Every integration was wired in days, not weeks.

Time recovered, by the team's own measure: between 14 and 19 hours per week. The variance is honest. Some weeks the team uses more of the system. Some weeks the team is in client meetings and the system runs unattended.

I do not claim a precise number. The team feels the difference. That is the metric that matters.

The handoff

At the end of the engagement, the team operates the system. Documentation lives in their Notion. Admin access is on their Anthropic account, their HubSpot account, their Slack workspace. The Brinvik retainer is optional, not required.

A retainer makes sense if the team wants continuous tuning. New projects. New integrations. Performance review on the existing deployments. Some teams take it. Some teams do not. Both are fine.

What I never do is build a system the client cannot run without me. The whole point is that the team gets stronger, not more dependent.

Closing

If your team has 5 hours a week or more of repeated knowledge work with clear inputs and clear quality bars, Claude probably handles it. Audit your week. Be honest about what is judgment and what is friction. Decide.

Most teams will find the friction is bigger than they thought. A few will find it smaller. Either answer is useful. Neither answer requires a six-month engagement to discover.

The audit is one week, fixed price, walk away with a documented plan whether you proceed or not. That is on purpose. The cheapest way to find out whether Claude earns its place inside your team is to look.

Written by Kim Olsen, principal of Brinvik. Get new essays by email.