A consultant's second brain, set up on her own machine

Emplify.World is a solo consultancy in Amsterdam with clients across several industries. We set up Claude Code on her own machine, connected 8 of her tools, wrote down her content pillars and gave her a first morning routine to build on.

Digital strategy and influence for professionals and SMBsAmsterdam, NetherlandsDWY Coaching
At a glance
Who uses it
Solo consultant, with clients across several industries
Engagement
DWY Coaching
Timeline
From April 2026
0tools connected in the first session
0content pillars written down
The starting point

Where the week went

What the work looked like before we built anything. One problem, one system to fix it.

Emplify.World, beforefrom the screen-shares and calls
everything lived inAlice's headexpertise not yet in anything repeatable
1Tools
Too many single-purpose subscriptions.
CRM, writing, research: none of them talk to each other.
2How she used AI
Claude used ad hoc.
Every session started from zero.
Worried about outages and lock-in.
3Her clients
Each client in a different industry.
Each needs its own context and research.
How we worked

Find. Fix. Automate.

Connected along the way
  • Claude Code logo
  • VS Code logo
  • Notion logo
  • Canva logo
  • Excalidraw logo
  • GitHub logo
  • Google Calendar logo
  • Gamma logo
  1. 1Find: we watched the work

    On the first calls we listed where it hurt: too many paid tools, Claude used ad hoc, and clients in different industries that each need their own context.

  2. 2Fix: we made the job simpler

    Everything lives as local files on her own machine, so an outage or a platform change does not take her work with it.

  3. 3Automate: we built what runs

    A first morning routine command, built on her own setup and tested from day one.

The system

Her second brain, day one

A second brain on her own machine: 8 tools connected, 3 content pillars, a first morning routine.

The problem

Paid tools that do not talk, and a Claude that forgot her business every session.

What we built

Claude Code on her own machine, her tools connected, her pillars written down, a first routine to run.

Before

How a piece of work started

  1. Step 1Open a new Claude chat
  2. Step 2where it hurtExplain the business again, from zero
  3. Step 3Move the result between paid tools that do not connect
After

How the system runs

Each line is a hand-off the system now does. The orange line is the result a person checks.

what comes in
Her content pillars3, written down
Her calendar and drive logo
Her calendar and driveconnected in session 1
Her Notion workspace logo
Her Notion workspacethe dashboard template
what does the work
Claude Code logo
Claude Codeon her own machine
8 connected toolsCanva, Excalidraw, GitHub, Gamma and more
what it makes
Notion dashboard logo
Notion dashboardcopied into her workspace
the result
/morning, her first routinetested as day 1 homework
who signs off
Alice runs it and checks ither files, her machine

Everything is local files she owns.

  1. 1Claude Code and VS Code installed on her own machine, with the setup command run.
  2. 28 tools connected: Canva, Excalidraw, GitHub, Google Drive, Google Calendar, Notion, Zoom and Gamma.
  3. 33 content pillars: Netherlands vs Singapore stories, insights from business reports, and thought leadership from her corporate experience.
  4. 4A Notion dashboard, copied from Sab's own template into her workspace.
  5. 5A first morning routine command, /morning, to test from day one.
What they see every day

Her second brain, day one

Emplify.World · Claude Codesession 1 · setup
Her own machine · her own files
0 of 8 tools connected
Connecting
Canva
Waiting
Excalidraw
Waiting
GitHub
Waiting
Google Drive
Waiting
Google Calendar
Waiting
Notion
Waiting
Zoom
Waiting
Gamma
Waiting
Content pillars
P1 Netherlands vs Singapore stories
P2 Insights from business reports
P3 Thought leadership from corporate experience
Notion dashboard
copied from Sab's template into her workspace
claude ·> ▍
SetupToolsPillars
What changed

Before and after

Claude used ad hoc, every session from zero.
A Claude Code workspace on her own machine, with her content pillars written down.
Paid tools that do not talk to each other.
8 of her tools connected to one place in the first session.
Worried about outages and lock-in.
Everything is local files she owns.

Run this pattern on your own data

This case is now a pattern the Unstuck MCP is trained on. Connect it to your Claude and it looks for the same signals in your own tools, picks the one worth fixing first, and builds it with you.

Pattern

Solo consultant's second brain on her own files

The consultant's context and content pillars written down as files she owns, her existing tools connected to one Claude, and a first morning routine to build on.

Connect your Unstuck MCP How the audit works
What they own now

Theirs, for good

  • Her Claude Code workspace and every file in it, on her own machine.
  • Her Notion dashboard.
  • Her content pillars and the morning routine.

The build plan continues with her context, a first end-to-end routine and testing it with real work.

Start here

Find the work that should not need you

The AI Audit Partner maps where your team's week goes and names the first three jobs worth building.

Book the audit