Skip to main content

Operations

We document your business while you run it.

Most small companies run on the founder's memory. That's a single point of failure. We turn meetings into records, records into process, process into something your team can actually follow.

Otter · Team Meeting · Nov 20
REC 00:52
R
Rok00:12

When a new provider signs up, first we verify their business number.

L
Lara00:18

And that goes through the KVK check?

R
Rok00:21

Yes — KVK check. If it fails, we email them for manual docs.

R
Rok00:29

Then we create the Stripe account — that takes about ten minutes.

L
Lara00:36

What about insurance?

R
Rok00:38

Insurance check happens after. We call them to confirm coverage.

R
Rok00:47

Finally we publish them on the marketplace.

docs.google.com/d/sop-onboarding
SOP — Onboarding
RL
Normal textBIUClaude drafting

Provider Onboarding — SOP

What this feels like

  • If my assistant quits, this company breaks.
  • I explain the same thing every week.
  • Meetings happen, nothing gets done.
  • I have no idea what my team is doing today.
  • Onboarding a new person takes three months.

How it works

MeetingRecorded on FathomTranscriptSpeaker-labelledClaudeReads, structures, draftsSOPEdited + publishedyour company’s memory

What we solve

Specific problems. Specific approaches.

Problem

Knowledge lives in your head.

Approach

Claude listens to your meetings and turns them into SOPs. You review. They become your company's memory.

Problem

Action items get lost in calls.

Approach

Every call produces a list. Items are assigned, land in Linear or ClickUp, and get tracked to done.

Problem

Friday reporting takes hours.

Approach

Claude reads tasks, CRM, calls. Writes the weekly ops report. You read, nod, forward.

Problem

Onboarding is chaos.

Approach

Claude builds role-specific onboarding docs from your existing meeting recordings and docs.

Problem

Slack is where decisions die.

Approach

Claude scans channels daily, surfaces what needs a decision, drafts the reply for you to approve.

Problem

You're the bottleneck for every decision.

Approach

We build a decision framework with you — Claude pre-filters what actually needs you, routes the rest.

What's included

Scope of work.

Meeting-to-record pipeline

Every call recorded, transcribed, summarised. Action items extracted and assigned. Decisions logged.

SOP library

A living set of process docs, generated from what actually happens, not what should happen.

Weekly ops report

One page every Friday. What moved, what didn't, where you're blocked.

Onboarding kits

Role-specific docs, videos, checklists — produced once, used forever.

What it looks like

A typical timeline.

Week 1

We sit in on your meetings, read your docs, see how your team actually works.

Weeks 2–4

First SOPs drafted, action-item pipeline running, weekly report format agreed.

Month 2

The SOP library covers your top ten processes. Reporting is boringly reliable.

Month 3 onward

Ops run without you looking. New hires onboard themselves from the docs.

Want us to run this for you?

Thirty minutes, no slides. We'll tell you honestly whether this is the right first thing to fix.