Tool selection, explainedHow we vet tools

Curated AI Stack · Independent consultants productizing delivery across 3–10 retainer clients

Consultant SOPs & Delivery Stack (2026)

Consultants sell repeatability but deliver from memory — that caps revenue. This stack documents what you already do: Scribe captures clicks, Notion stores SOPs, Loom covers exceptions, Make nudges clients when they stall. Skip enterprise CLM until 10+ concurrent engagements. Budget: $0–35/month — Scribe free/pro, Notion Plus, Loom free, Make Core if automating nudges.

Verified March 2026Data as of October 2026

Stack Operator Reliability Score

Composite from core tools only — supplementary picks do not dilute the score. Your stack fails on the weakest glue, not the average.

Stack score = 0.60 × mean(core tool scores) + 0.40 × min(core tool score). Supplementary tools are listed but do not dilute the composite — your stack fails on the weakest core glue.

ORS 70.3/100

Usable — watch pricing & rate limits

  • ScribeHow69.1/100
  • Notion AI68.9/100
  • Loom AI75.9/100

Weakest core: Notion AI at 68.9/100 — pulls the stack composite down via the 40% min term. Full ORS methodology

Core Tools

Set these up first. Each one lists who it suits and who should skip it.

Core #1 · Free

ScribeHow

AI Productivity & Automation

Auto-SOP the third time you do the same client setup — not the first.

ORS 69.1/100

Best For

Onboarding VA or associate without live training call
Handoff checklist clients can follow without you on Zoom
Internal “how we export the report” that stops Slack repeats

Core #2 · $1-50

Notion AI

Writing & Productivity

SOP library + client workspace — one portal page per engagement.

ORS 68.9/100

Best For

Link Scribe guides under client-specific “How we work” header
AI summary of weekly status into client-visible section
Revision log when scope creeps — timestamped notes

Core #3 · Free

Loom AI

Video & Audio Content

Human context when SOP is not enough — 2-minute “why this step matters” clips.

ORS 75.9/100

Best For

Exception handling when client data is messy
Quarterly review walkthrough async
Sales-to-delivery handoff video for your future self

Supplementary Tools

Add these only after the core tools have been running for a few weeks and are earning their cost.

Supplementary #1 · Free

Make (Integromat)

Automation

Notion “Waiting on client” → day 3 reminder email draft — you approve send.

ORS 72.9/100

Best For

Reducing ghosting on asset uploads
Internal Slack when client portal stale 5 days

Supplementary #2 · $1-50

Claude AI

AI Assistant

Turn Scribe steps + Loom transcript into client-facing checklist prose.

ORS 75.3/100

Best For

Polishing SOP tone for non-technical clients
Weekly report draft from bullet notes

30-Day Implementation Plan

  1. Week 1 — Name repeatable work

    1. List 3 tasks you did 3+ times last quarter. Pick one to document this month.
    2. Notion client template: goals, assets, SOP links, status — duplicate per client.
    3. Perform task manually once while noting every click — no Scribe yet.
  2. Week 2 — Scribe + Loom

    1. Scribe the task on fourth run. Edit steps for clarity — AI draft is not final.
    2. Loom 2-min overview linked at top of Scribe. Send to one friendly client for feedback.
    3. Fix confusing step. Version date in Notion — clients trust timestamps.
  3. Week 3 — Client portal habit

    1. Every client gets Notion link in welcome email — no exceptions.
    2. Make reminder only if 2+ clients missed same upload step.
    3. Claude: weekly bullets → client email draft. You personalize first line.
  4. Week 4 — Productize or pause

    1. If SOP saved 2+ hours this month, Scribe paid tier justified.
    2. If clients ignore portal, fix comms before adding tools.
    3. Pair with /stack/ai-powered-client-onboarding for intake layer.

Operator Prompts

Paste into Claude, ChatGPT, or your tool's AI assistant — tuned for this stack's core tools, not generic "help me automate" requests.

  • ScribeHow setup prompt

    ScribeHow

    Role: implementation coach for Independent consultants productizing delivery across 3–10 retainer clients.
    Tool: ScribeHow (Free).
    Job in this stack: Auto-SOP the third time you do the same client setup — not the first.
    Task: Produce a numbered day-one checklist (max 8 steps) with time boxes. Include one "stop if stuck" fallback.
    Constraints: no feature tours; one workflow only. Best for: Onboarding VA or associate without live training call.
    Avoid: Documenting a process you ran once — do it twice manually first.
  • Notion AI setup prompt

    Notion AI

    Role: implementation coach for Independent consultants productizing delivery across 3–10 retainer clients.
    Tool: Notion AI ($1-50).
    Job in this stack: SOP library + client workspace — one portal page per engagement.
    Task: Produce a numbered day-one checklist (max 8 steps) with time boxes. Include one "stop if stuck" fallback.
    Constraints: no feature tours; one workflow only. Best for: Link Scribe guides under client-specific “How we work” header.
    Avoid: Legal contract storage without counsel review workflow.
  • Loom AI setup prompt

    Loom AI

    Role: implementation coach for Independent consultants productizing delivery across 3–10 retainer clients.
    Tool: Loom AI (Free).
    Job in this stack: Human context when SOP is not enough — 2-minute “why this step matters” clips.
    Task: Produce a numbered day-one checklist (max 8 steps) with time boxes. Include one "stop if stuck" fallback.
    Constraints: no feature tours; one workflow only. Best for: Exception handling when client data is messy.
    Avoid: Replacing written SOPs — Loom supplements Scribe, not vice versa.

Rollout Templates

Copy into Notion, Google Docs, or your CRM — SOPs and handoff copy aligned with the 30-day plan above.

  • Stack rollout SOP (copy into Notion)

    # Consultant SOPs & Delivery Stack (2026) — operator SOP
    
    Persona: Independent consultants productizing delivery across 3–10 retainer clients
    
    ## Week 1 gates
    - [ ] List 3 tasks you did 3+ times last quarter. Pick one to document this month.
    - [ ] Notion client template: goals, assets, SOP links, status — duplicate per client.
    - [ ] Perform task manually once while noting every click — no Scribe yet.
    
    ## Core tools (pay first)
    - ScribeHow: Auto-SOP the third time you do the same client setup — not the first.
    - Notion AI: SOP library + client workspace — one portal page per engagement.
    - Loom AI: Human context when SOP is not enough — 2-minute “why this step matters” clips.
    
    ## Week 3 automation checkpoint
    - [ ] Every client gets Notion link in welcome email — no exceptions.
    - [ ] Make reminder only if 2+ clients missed same upload step.
    - [ ] Claude: weekly bullets → client email draft. You personalize first line.
    
    ## Definition of done
    - One workflow live for 7 days with measured time saved
    - Supplementary tools not added until core ROI logged
  • Client / stakeholder handoff email

    Subject: Your Consultant SOPs & Delivery Stack — week-one plan
    
    Hi {{name}},
    
    Here is what happens in the first 7 days:
    1. List 3 tasks you did 3+ times last quarter. Pick one to document this month.
    2. Notion client template: goals, assets, SOP links, status — duplicate per client.
    3. Perform task manually once while noting every click — no Scribe yet.
    
    Reply with your primary workflow constraint (time, budget, or skill) and I will adjust the sequence.
    
    — {{your_name}}
  • Weekly stack QA log

    | Week | Tool | Time saved (min) | Keep / cut / swap | Notes |
    |------|------|------------------|-------------------|-------|
    | 1 | | | | |
    | 2 | | | | |
    | 3 | | | | |
    | 4 | | | | |

How we curated this stack

This stack pairs 3 core and 2 supplementary tools around one weekly workflow. Tools in curated stacks are evidence-checked on a weekly schedule: pricing is read from the vendor page and compared with the catalog band, public user reports from the last 90 days are collected with sources, and a person reviews the result before it is published. The check date and sources sit under each tool above; job-in-stack copy is editorial, not a hands-on test claim.

Sources consulted

useToolCraft tool vetting methodology
useToolCraft (accessed 2026-10-05)
Related stacks

Adjacent stacks operators often run alongside this one — same budget band or persona, different primary workflow.

Tools in this stack

Each profile includes pricing reality, failure points, and a 30-day rollout — read before you subscribe.

Related guides

Playbooks and workflow hubs that pair with this stack — same operator, earlier decision points.

Want a version matched to your own task?

This page is one worked example. Describe your task, budget and experience level in the free finder and get core and optional picks for the work you actually do each week.

Get a shortlist for my task