The model is the easy part. Design is what separates a Chief of Staff that saves you ten hours a week from a chatbot you stop opening after a fortnight. We call this discipline Claude Design, and it is most of the work.
Three layers of design
When we build a Chief of Staff, we are not really designing a chatbot. We are designing three things at once.
- Context design. What does Claude know about your business, your clients, your priorities, and your standing decisions before any conversation begins.
- Voice design. How does it write, edit, push back, and stay quiet so the output sounds like you on a good day.
- Ritual design. When and how do you actually meet it in your week so the system gets used, not abandoned.
Skip any one of these three and the whole thing collapses inside a month.
Context design, the part nobody else does
Most AI projects fail in this layer. A founder buys a tool, points it at a few documents, and waits for magic. The output is generic because the context is generic.
We do this differently. The first two days of a build are spent quietly mapping:
- Who your clients are and how you actually talk about them.
- What your standing decisions are, the things you no longer want to debate.
- Which numbers matter and which do not.
- What your week looks like when it is going well.
- What you will never delegate, no matter how good the model gets.
That map becomes the spine of the system. Every reply, every draft, every summary is grounded in it.
Voice design, the part everyone underestimates
Voice is not tone. Voice is the rhythm of how you make a point. It is the sentences you would never write, the phrases you reach for, the way you say no without making it weird.
We capture voice with three artefacts.
- A voice card. A short document of dos, don'ts, and signature patterns. Half a page, no more.
- Twenty real examples. Real emails, real updates, real messages, picked by you, redacted as needed.
- Three counter-examples. Things that sound like you but are not. The negative space matters.
With those three artefacts, Claude stops sounding like Claude and starts sounding like you. The first time a client replies to one of its drafts without noticing, you know the design is working.
Ritual design, the part that decides whether you keep using it
A great system that you forget to open is not a great system. So we design the moments.
- The morning triage, before you open your inbox.
- The pre-meeting brief, ten minutes before any important call.
- The end-of-day dump, five spoken minutes that close the loop.
- The Friday review, a fifteen-minute pull on what the week revealed.
Each ritual is short, named, and tied to something you already do. That is how new behaviour sticks.
What good design looks like at month three
A founder we worked with sent us a note in week eleven. I have not opened a blank email this month. That was the entire message. It is the cleanest report card we have received.
That is what the discipline produces. Not novelty, not theatre. Quieter days, cleaner work, and the slow return of attention to the things only you can do.
Why we will not skip this work
It is tempting to compress the design phase to ship faster. We do not, and we will not. The seven-day build exists precisely because we have shrunk every other part of the project. Design is the part that has to breathe.
Anyone can give you access to Claude. Very few will sit with you and design the context, the voice, and the rituals around it. That is the whole job.
The model is a commodity. The design is the work. Treat it that way and the ten hours a week show up. Skip it and they never do.