By Caleb Barnette
A friend asked me a few weeks ago what I was actually doing with all of the Claude tools day to day. He'd heard me talk about them. He wanted the practical version. Not the demo. Not the pitch. The version you'd give somebody over coffee.
Here's the answer I gave him, expanded a little.
If you haven't kept up with the product side of all this, "Claude" is no longer one chat window. It's a small suite. Cowork is Claude with file access on your computer. Claude Design is for visual work: brand assets, mockups, wireframes. Claude Code is the developer side; it can build, edit, and run a real codebase. Each one is good at a different shape of work, and the trick to using them in a small business isn't picking the smartest one. It's matching the work to the tool.
These are the three places it's actually paid off in mine.
1. The voice guide, in Cowork
The first useful thing I did with any of this was sit down in Cowork and write a brand voice guide for Headwater. Not because anyone asked me to. Because I'd noticed that every time I asked an AI tool to draft something, it came back sounding like every other AI-drafted thing on the internet. Cheery, vague, faintly corporate, no specifics, full of words like "seamless" and "empower."
The fix is not a better prompt. The fix is the document.
The guide I wrote runs about 12 pages. It says who we are to the reader, who we are not, the words and tones we never use, the rhythm we want our sentences to land in. It lists banned words. It includes before-and-after examples. It ends with a single anchor line we measure other lines against. It took me a Saturday.
Since then, every piece of content Cowork drafts for Headwater starts by reading that guide. Email campaigns. LinkedIn drafts. Sales-page copy. The output isn't perfect, and I still edit every line. But the starting point is recognizably ours instead of recognizably nobody's. That single document has saved me hours a week.
If you only do one thing with an AI tool this year, do this. Write down how your business actually sounds when you talk to a customer. The opening line on your phone. The way you describe the work. The words you'd never use. Three pages is plenty. The tool will be better at being you than you are at remembering to tell it.
2. The brand kit, in Claude Design
Cowork is good at language. It isn't built for visual work. For that I moved to Claude Design.
What I wanted was a brand kit. Not a logo. A whole system. A primary lockup and a horizontal lockup, both on cream and on ink. A mark-alone version that would still read as Headwater when shrunk to a favicon. A small, deliberate palette. Type roles for a website, a business card, and an email signature. The kinds of "don'ts" I could point a future contractor at.
I gave Claude Design the inputs. The name. The tagline: plain talk, practical AI, Charleston WV. A short description of the voice (calm, specific, not hyped). A few references for the feel I wanted: warm, grounded, a little editorial, nothing that looked like a tech startup. Then I asked it to take a pass.
It came back with options. We iterated. What I shipped looks like this.
The core palette is four colors. A deep Charleston Ink for type and the mark. A warm Cream as the default background instead of stark white. A terracotta accent used sparingly for warmth, and a sage for calm. The supporting set adds a Paper, a Cream Alt, a Muted Ink for secondary copy, and a Line color for dividers. Eight values total. That's the whole system, and it's enough.
Typography is Inter across the board. Four roles, each with a defined weight, tracking, and line-height: a Display for hero copy, a Heading for sections, a Body for everything else, and an uppercase Eyebrow with wide tracking for small labels. One font family. Four jobs. No improvising at the design stage.
The kit also has the boring parts that matter most. Clearspace rules (a minimum safe area on every side equal to the width of the drop on the mark). A don't-do-this page: no skew, no gradients, no shadows, no use on busy color. Light and dark tile versions of the icon at 128, 64, 32, and 16 pixels. Application mockups for the business card, the email signature, and the browser tab so I know what each surface should look like before I have to make it.
What I want to flag here is the same lesson as the voice guide. The output was good because the effort was. The version I'd have gotten by typing "design a logo for a consulting firm" is a logo. The version I got by giving Design real input, a voice guide it could read, and a few clear visual references is a system I can actually run a business on.
3. The website, in Claude Design then Claude Code
The last piece, and the shortest to describe, is the site itself.
I split the work in two. Claude Design did the wireframes. Claude Code did the build.
In Design I sketched the structure of the marketing site. Home, services, about, contact. What goes above the fold on each one. Where the proof lives. Which calls to action sit where. I worked through a few passes before anything got built. Wireframing in Design is cheap, and the conversations are quick. I'd rather move a section in a mockup than in a deployed page.
Once the structure felt right, I handed the wireframes to Claude Code and asked it to build the real version. It used the brand kit colors, the Inter type roles, the lockups. I sat with it through the actual implementation, made edits, killed things that looked fine in the wireframe but didn't survive contact with real copy. By the end I had a site I'd written, designed, and built without ever opening Figma or a CSS file from scratch.
The point of splitting the work is this. Each tool is good at a different part of the job. Design is good for thinking visually before anything is real. Code is good for making things real and editing them in place. Using both, in that order, took a fraction of the time a normal small-business website project takes, and the result is actually mine.
The boring truth
Here's the version I gave my friend over coffee.
Most of what makes any of these tools useful is the work you do before and after they run. Before, it's the brand kit, the voice guide, the references, the examples, the brief. After, it's reading what came back and editing the parts that aren't right. The fast part in the middle, the part where the tool generates something, is the part everyone talks about and the part that matters least.
If you're a small-business owner thinking about where to start, start where I started. Write down how your business sounds. Get a brand system on paper before you spend a dollar on a website. Decide what the site needs to do for you before anyone builds it. Then point the right tool at each piece.
What you get back is not a suite that runs your business. It's a suite that lets one person do the work of three, in your voice, on your brand, on your schedule, so your judgment can go to the parts that actually need it.
That's the version worth your afternoon.