Tier 1 · 1-on-1 · From $1,500 · 1 day
One full day, 1-on-1, where we build your permanent Claude Code setup. Three to five MCP servers, three to five custom skills, hooks, slash commands, and a playbook document. Plus a 30-day tune-up session.
The Problem
You have opened Claude Code a few times. Maybe you have written a short CLAUDE.md. You know the docs mention MCP servers, skills, subagents, hooks, slash commands, but you have not had the afternoon to sit down and figure out which ones matter for you.
And every week you see someone online showing a setup that turns a two-hour task into a two-minute command, and you think "I should be doing that."
One day with us and you are that person.
The Day
Workflow audit (morning, 45 min)
We start by mapping your recurring work. What tasks you do every day, every week, every month. What data lives where. What tools you already use. This is where we identify the five or six highest-leverage skills to build.
MCP servers connected (morning, 90 min)
Three to five MCP servers, picked from what matters to you: Gmail, Google Calendar, Drive, Notion, Linear, GitHub, Slack, Figma, Canva, your CRM, or a custom one for your internal APIs. Tested and wired up.
CLAUDE.md and settings.json tuned (before lunch, 60 min)
Project-level and user-level instructions. Permission allowlists so you stop approving the same commands. Hooks for auto-format, notifications, and pre-commit checks. The scaffolding that makes everything else work.
Custom skills built live (afternoon, 2.5 hours)
Three to five skills, each targeting one of your recurring tasks. A weekly report. A code review. A draft email for a common client message. A research workflow. We write them, test them, tune them, and show you how to modify them later.
Subagents and slash commands (late afternoon, 60 min)
For workflows where one agent is not enough. Specialist subagents for things like research, review, or planning. Slash commands so you stop typing the same prompts.
Personal playbook written (end of day, 30 min)
A one-document reference covering your setup: what is installed, what each skill does, how to invoke them, and how to add new ones. This is the thing you re-read in three months when you want to extend it.
30-day tune-up (one month later, 60 min)
After a month of real use, we come back together. What is working. What you stopped using. What new tasks you want to turn into skills. We tune the setup based on evidence, not guesses.
Who Books This
Founders who live in their tools. Solo consultants who bill by the hour. Independent operators running a business of one. Senior engineers who want their Claude Code setup to match how they actually think.
If you are brand new to Claude Code, start with the Starter. If you want a team setup, look at the Team Rollout. The Power User Day is for the person who plans to use Claude Code every day for the next year.
Most clients tell us the day pays for itself in the first three weeks. The skills we build keep paying every week after.
What You Actually Get
Every skill we build targets a task you actually do. Not a generic example. If your weekly report involves three data sources and two templates, that is what the skill handles.
We run each skill three or four times during the session. You see where it breaks, how we fix it, and what the edge cases look like. You leave confident it will not fall apart Monday morning.
The final document is written so that in six months, when you want to add a new skill, you can do it yourself. That is the whole point. We set you up so you do not need us again.
I had Claude Code installed for four months and used it maybe twice a week. After one day with Leigh I have five skills I run every day, MCP servers connected to my whole stack, and a setup I actually understand. The day paid for itself in the first fortnight.
Independent Consultant, Professional Services
The fastest way to go from Claude Code curious to Claude Code fluent.