← caelith labs

artefact · 02 · 03

operations sprint — handover runbook.

Anonymized template · v0.1 · 8 sections

SAMPLE This is the runbook shape every Operations Sprint engagement ships with — anonymized for review. Real engagement runbooks include named systems, named team members, and engagement-specific workflows. The structure below is the actual handover artefact.

§ 1system map

What we built. Three connected layers:

who owns what

SystemPrimary ownerAdmin backup
Attio workspace<ops lead><partner>
Calendly account<ops lead email>
Notion workspaceexisting — 3 new DBs added<partner>
Vendor accountssee § 6 (credentials)

§ 2daily · weekly · monthly procedures

daily (5 min)

weekly (30 min, Friday)

monthly (1 hour, first Monday)

§ 3common tasks — step-by-step

add a new pipeline stage in Attio

  1. Open Attio workspace · sidebar → "Records" → select the relevant object (Opportunities, Companies, etc.)
  2. Click the kanban icon (top-right of the record view)
  3. Click "+" at the end of the stage row · name the stage
  4. Set the stage's probability field (used for forecast roll-up in the Notion dashboard)
  5. If the stage triggers automation (notification, task creation): see § 3.4 "sync Attio → Notion"

onboard a new team member to the CRM

  1. Attio: Settings → Members → Invite · set role (Admin / Member / Viewer)
  2. Calendly: Account → Teams → Invite · assign to the right routing pool
  3. Notion: ensure they have access to the project hub workspace
  4. 1Password vault: share the <firm name> Ops vault with their account
  5. Walk them through this runbook (15 min)

set up Calendly routing for a new service line

  1. Create a new Calendly event type · name it after the service line
  2. Set the routing form: which partner gets which inbound (by industry / size / urgency)
  3. Connect to Attio: Calendly → Integrations → Attio · map fields (name, email, company → Attio Contact)
  4. Test: book yourself a test slot · verify the contact lands in Attio with correct pipeline assignment

sync Attio → Notion (manual)

  1. Open Attio · Opportunities view · filter "stage = Won this week"
  2. Export selected → CSV
  3. Notion · "Engagements" database · import CSV · map columns
  4. Update the Notion dashboard with the weekly close count

Automation path (if n8n is in scope): the Attio webhook fires on stage change; n8n picks it up and writes to Notion via the API. Manual sync above is the fallback.

migrate inbound from email-only to Calendly-form

  1. Add a Calendly link to the firm's website "Get in touch" section
  2. Configure email auto-reply for contact@<firm> to gently suggest the Calendly link for booking
  3. Run for 30 days; review uptake rate; adjust messaging if uptake <40%

§ 4troubleshooting — top 5 known issues

Issue 01

"Attio webhook to Notion isn't firing."

Diagnosis: Check Attio webhook log (Settings → Integrations → Webhooks → History). If green, check n8n run history. If yellow/red, check the Notion API integration token hasn't expired.

Recovery: Re-trigger via the manual sync (§ 3.4). Rotate the Notion token if needed (§ 6).

Issue 02

"Duplicate contacts after Pipedrive migration."

Diagnosis: Attio's import dedupes on email; duplicates usually mean the source had multiple email fields per contact.

Recovery: Attio · Contacts view · sort by email · merge duplicates (Attio has a built-in merge tool). Document the merge in the change log (§ 8).

Issue 03

"Calendly form routing to the wrong partner."

Diagnosis: Routing form logic has hit an edge case (likely a multi-criteria rule with overlap).

Recovery: Calendly · Routing → audit the rule order. Calendly evaluates top-down; reorder so most-specific rules fire first.

Issue 04

"Notion dashboard not refreshing weekly numbers."

Diagnosis: Either the sync didn't run (see Issue 01) or the dashboard formula has stale relations.

Recovery: Open the Notion dashboard · refresh the database queries (right-click → refresh). If still stale, rebuild the relation (15 min).

Issue 05

"User says they can't see their contacts in Attio after onboarding."

Diagnosis: Either Attio role permissions or a view-level filter is hiding records from them.

Recovery: Settings → Members → check their role · then on the relevant view check the filter pane for "Only show records assigned to me" toggles.

escalation path

What brokeCall firstCall second
Vendor account / billingVendor support
Workflow logic seamJulian — caelith labsVendor if needed
"We need a new service line"Julian — caelith labs
Pipeline-wide failureJulian + vendor support in parallel

§ 5maintenance schedule

CadenceTaskOwner
DailyToday's-tasks reviewOps lead
Weekly · FriPipeline reviewPartner + ops lead
Monthly · 1st MonData hygiene + backup verifyOps lead
QuarterlyArchitecture reviewPartner
QuarterlyVendor cost reviewPartner
YearlyDPA + sub-processor renewal checkPartner

§ 6credentials + access

where credentials live

1Password vault <firm name> Ops, shared with the partner + ops lead. Set up during engagement week 3.

rotation policy

CredentialRotate everyTrigger
Attio API key180 daysOn team-member exit
Calendly OAuth token365 daysOn team-member exit
Notion integration token365 days
n8n credentials (if in scope)180 daysOn team-member exit

sub-processors — your data routes through

DPAs on file with each. Renewals tracked in <your compliance calendar>.

§ 730-day open line

Caelith Labs is available for follow-up questions for 30 days post-handover, free of charge.

After 30 days, optional retainer available (€1,500–€2,500 / month, billed quarterly). Discussed at handover, never required.

§ 8change log

DateChangeAuthor
W3 Day 4Initial handoverJulian Laycock

Append new entries on top. Every change to the system should land in this table — keeps the runbook trustworthy.