Service · Workspace Setup
you@your-business:~$ claude_

Your business,
running on Claude Code.

You're already paying for Claude. A chat window is maybe ten percent of it. I build the other ninety: a workspace that knows your business, runs your recurring work, and compounds every week. Then I hand you the keys.

A chat window forgets. Your business can't.

Every conversation with a chatbot starts from zero. You re-explain your business, re-paste the same three documents, re-describe your standards. And the draft still sounds like a press release from a company you've never met.

The difference between chatting with AI and running on it isn't a better prompt. It's structure: files that hold what Claude needs to know, skills that encode how you work, memory that persists between sessions. That structure is what I build.

What a Tuesday looks like, after setup

The folders are just the mechanism. What you're buying is clarity: one place where your business thinks straight.

Draft this month's invoices.

It pulls your rates, your clients, your template. You review for two minutes instead of assembling for an hour.

Write the follow-up email for yesterday's workshop, in my voice.

It reads your files, not the internet's average. The draft sounds like you on a good day.

What did we decide about fall pricing?

The workspace remembers. You don't have to.

tree your-business/
your-business/
├── CLAUDE.md how your business works, loaded every session
├── skills/
│ ├── invoicing/ a recurring process, encoded once
│ ├── onboarding/ your checklist, made executable
│ └── content/ your voice, never generic AI text
├── memory/ decisions and facts that persist
└── projects/ one folder per client, product, or launch

The mechanism underneath

Clarity needs structure. This is the folder that makes that Tuesday possible. It lives on your machine, under your control:

Not a template. Every folder is built around work you already do. In the discovery call, we pick the workflows that hurt most.

How it works

01

Discovery call

Free, 30 minutes. We map your workflows and I tell you honestly whether this is worth your money. If it isn't, we stop here.

02

Setup sprint

About two weeks, part-time, without disrupting your operations. I build in passes and check in as pieces land.

03

Handover

A working session where you run the workspace yourself. You leave with the keys, not a dependency.

Pricing

I take two setups per month, alongside running my own business on the same system. Published prices. No call required to find out.

Start here

Working Sessions

$125 USD / hour
book by email, 2-hour blocks preferred
  • One-on-one, on your machine: we build your workspace together
  • You drive, I navigate, and you keep everything we build
  • No commitment: book one hour and see if it's useful

After a setup, ongoing help is simply more sessions. No retainer required.

Go deeper

Audit + Roadmap

$2,500 USD
1–2 weeks
  • A working audit of how your business actually runs
  • The 2–3 automation opportunities worth building, prioritized
  • A written roadmap you can execute with me or without me

Credited in full against the Business OS Setup if you upgrade within 60 days.

The flagship

Business OS Setup

$6,500 USD
~30 days, part-time
  • Everything in Audit + Roadmap
  • Workspace architecture: CLAUDE.md, memory conventions, permissions
  • Three to five custom skills built on your real recurring work
  • Connections to your tools: documents, spreadsheets, email, your website
  • Hands-on handover session: you drive, I navigate
  • Thirty days of async questions after handover
Also included with your setup:
  • The Owner's Manual: a short video mini-course on running and extending your workspace
  • The Ask-for-Anything Cheatsheet: one page of prompts for the twenty most common business asks
  • Starter skill kit: proven skills you adapt to your business in minutes

» Founding rate: first three OS setups at $5,000, in exchange for a written case study.

The OS Setup is a fixed price with a 30-day delivery target. The efficiency risk is mine, not yours.

The workspace, the skills, the files: yours, on your machine. No lock-in, no dependency on me.

If the discovery call shows Claude can't materially help your business, I'll say so and we stop. Free.

I run my own business this way.

The content pipeline, publishing, research, and operations behind this site run on the exact structure described above. The first draft of this very page was built by an agent in my pipeline: it picked the task off a queue, wrote the code, opened the pull request, and shipped while I was busy elsewhere. That's not a pitch I read somewhere. It's my Tuesday.

Questions you should ask

Do I need to be technical?

No. If you can find a file you saved last week, you're qualified. The setup makes the technical parts invisible, and the handover session exists so you never wonder what to click.

Will my content sound like AI?

The rule the workspace is built on: AI-assisted, never AI-generated. Claude drafts in your voice from your files. You decide what ships, and nothing goes out that you didn't shape.

What about my data?

Everything lives on your machine, under your Claude account. I work in your workspace during the sprint and keep no access after handover.

What does it cost to run afterward?

Your existing Claude subscription. No servers, no per-seat software, no ongoing fees to me unless you want the Care Plan.

Can't I just do this myself?

Honestly? Yes. The documentation is public, and if you have the hours, I'd cheer you on. What you're buying is the trial and error I already paid for, compressed into two weeks, plus someone who's seen where these systems break.

What if my business is unusual?

Good. Templates are the enemy here. The discovery call exists precisely to find out what your version of this looks like. If Claude genuinely can't help your business, I'll say so on that call.

Start with the discovery call

Leave your email and I'll reply within a day to set it up. Free, thirty minutes, no deck, no funnel. Just straight answers about whether this is worth it for you.

Prefer email? me@simonparis.ca