I lead two small companies. With Claude Code I rebuilt our whole brand and the operating systems behind it. Then a team of agents that work alongside me, and the tools my clients use. Here is what that looks like — and eight things you can try this week.
This has not been delightful by any means. It has been hard, it has been wrenching. But here we are — and I, who really only know enough to be dangerous, have pulled off a wall-to-wall rebrand, rebuilt our whole company and service infrastructure, and built solutions for my clients.
I went from a small small business to a big small business — one that is punching above its weight. Claude Code is creating a whole new reality for me. Push the tools you are using to their limits. You are in charge. You have agency.
None of this needed a developer or a big team. It is the kind of work a small company can do for itself, one piece at a time.
The whole brand, rebuilt as one brand system — the company and every service under it. One palette and one voice, encoded so every new page and deck comes out on-brand without me re-deciding it each time. A small company can finally look as considered as a big one.
What it took — a written brand system Claude reads before it makes anything.
The boring, load-bearing stuff — the operating systems behind the company and each service. Processes written down once, then run the same way every time. The plumbing a two-person team usually never has time to build is the plumbing that lets a two-person team act much bigger.
What it took — turning how I work into files Claude can follow.
A small team of named agents that handle the daily work alongside me. My morning brief is ready before I am up. Romy watches relationships and tells me who has gone quiet. Rupert preps my meetings. Each one solves a problem I used to drop on a busy day — and each one has a human accountable for it, which is usually me.
What it took — one skill per problem, built and named, not a single giant bot.
Working tools and deliverables my clients use, made fast and made well. A landing page or a planning tool, built properly — the kind of thing that used to mean an agency invoice and a six-week wait. Now a small firm can hand a client something polished inside the same week.
What it took — the brand and infrastructure already in place, so building is the easy last step.
Everything the company knows, written down and reusable — books, guides, curriculum, and the process behind how things get done. I indexed everything I have ever made — campaign plans, workshops, every fundraising asset — into a digital twin of my own work. Instead of living in my head, it lives in files my agents and my teammates can both read. It compounds. Each project adds to what the next one starts from.
What it took — saving what I learn as I go, so it is there next time.
Start with the one that matches what you are working on right now. You do not need to have built anything yet. That is the point — each of these is a single ask you can make today, and the agent it points to is one you can build later if it earns its keep.
Tell Claude what you are managing — clients or members. Ask it to pull from your CRM and your messages and tell you who has gone quiet and who is overdue for a touch. Tell it which database, which channel. The more specific you are, the more useful it gets.
Tell Claude what is on your calendar and what you have open. Ask it to pull from your calendar and your messages and build you a brief — what today needs from you, what is overdue and who has it, and what could blow up if nobody catches it. Then go further and let it ask you questions about your day.
Tell Claude the person's name and ask for a summary. It pulls from your CRM and connected sources and brings you current — their status, their history with you — without you digging through four different places first.
Paste in a name and a topic and tell Claude to go find the rest. It pulls from your CRM and your transcripts, wherever it needs to go. Stop switching apps and let Claude do the gathering. Then tell it exactly how you like to prepare and ask it to follow that format every time, so it sticks.
Paste in a plan, a timeline, or an agreement. Ask Claude what is missing, what is ambiguous, and what could create a problem later. When it surfaces something useful, tell it to save the lesson — then share it with your team, because they would want to know too.
Pick anything you are trying to improve and ask Claude to prepare a context packet. It can send several agents at once — one to mine how you have done it before, one to gather best practices from the web, another to stress-test your best idea before you commit, and one more to find the numbers that tell you whether it worked. All without scheduling a meeting.
Tell Claude what you are working on this week and ask what you already have that could help. You do not need to remember everything you have built. Asking is how you find out what is in there — and what is worth building next.
A tracker, a process doc, a small tool — something a teammate can use. Tell Claude what you are missing, ask it to build the first version, and put it somewhere the team can find it. Building the first one shows you what to build next.
Thirty-three years in fundraising, now building small companies that run on AI and human judgment together. Built with help from the She Leads AI agent team.
The SLAI Effect is the weekly letter on AI for women, written plainly. Useful and short.
Yah, Let's SLAI
The whole community in one place — the women building with AI on purpose, gathered for three days.