You run a small agency. The shape of the problem is always the same: a new client lands, you write the brief, you brief the team, you review the work, you write the deck, you walk the client through it, you write the recap, you scope the next phase. Most of that work is yours specifically, not because you don't trust your team but because the client signed because of you. Hiring another senior is expensive and slow, and the new person still won't have the context that lives in your head and your old project folders. The honest version of "scaling without hiring" isn't magic. It's taking the work that already lives in your past projects — briefs, decks, recaps, retainers, scopes — and re-using it more efficiently than humans can. That's what AI notes are good at when they're set up right. If you're [a fractional executive juggling multiple engagements](/guides/founders-ceos/fractional-executives-multiple-engagements/) instead of an agency, the underlying shape is similar — a vault per client, an agent that reads across. ## The bottleneck is recall, not effort When agency owners say they're at capacity, they usually mean something specific. It's not that the next client would double the hours. It's that the next client would double the *thinking* — and your thinking is the one resource you can't multiply. A new positioning brief doesn't take three days because typing is slow. It takes three days because you have to remember what worked for the last three clients in that vertical, dig through old Drive folders, find the deck, find the email where the client asked the awkward question, find the rewrite that landed. By the time you've reassembled the context, you're tired, and the actual writing happens at half-energy. Capy is built for this exact recall problem. Your past briefs, decks, and recaps live in your vault as plain markdown notes. When you start a new project, you point Capy at the relevant ones and ask it to draft from there. The agent reads your actual past work and pulls forward the patterns that worked, not a generic agency-template version. ## A working setup for an agency vault The shape of vault that scales for agency owners isn't complicated. Most owners we've talked to converge on something like this: - One top-level page per active client, with sub-pages for brief, scope, weekly recaps, and the deck-in-progress - One archive page per closed engagement, kept around forever for reference - A cross-cutting "playbook" page per service line — positioning, brand, paid acquisition, whatever you sell — that links to your three or four best examples - An inline database for the new-business pipeline so prospect notes live in the same vault as everything else Unlimited page nesting handles the hierarchy without you having to pick a depth in advance. You can let some clients balloon into ten sub-pages and keep others as a single page, and Capy reads across all of it. ## Drafting briefs from your actual past briefs The single highest-leverage workflow is brief drafting. New client signs, you've got a kickoff in three days, and you need a positioning brief on the page before that meeting. Drop the new client's discovery-call notes onto a fresh page. Tell Capy: read my last four briefs in this vertical, identify the structure they share, draft a v1 brief for this new client using that structure, pull the audience definition tone from the one that the client praised most. You get back a draft that looks like *your* briefs, not a templated one. You spend the saved time on the parts that genuinely are new — the specifics of this client's market, the bits where your gut is doing real work. The same pattern works for scope-of-work documents, statement-of-work updates, and renewal pitches. The agent isn't inventing structure; it's lifting your structure forward. ## Turning client calls into recaps without losing the call itself Client recaps are a tax on senior time. The call is an hour, the recap is another hour, and you've already mentally moved on to the next account. Record the call inside Capy. The recording lands on the page with speaker diarization, so the transcript reads as "Speaker 1: …" rather than a wall of unattributed text. Ask the agent to draft a recap with three sections — what was decided, what's still open, what we owe the client by Friday. The first version is rarely perfect, but it's close enough that editing takes a fraction of the time of writing from scratch. The recap goes in the client's page next to the actual transcript, so when somebody on your team asks "wait, did the client say X or did we?" you can answer it from the source. If the client raised a budget concern that needs internal follow-up, ask the agent to add it as a row in your account-issues database on the same page. The database lives inline via the `:::database:::` directive, so you don't have to switch tabs to a separate tracker. ## PDFs the client sends, finally readable Clients send PDFs. Brand guidelines, RFPs, prior agency decks, audit reports. Most of the time those PDFs sit in your inbox until you need them, and then you're skimming sixty pages at midnight. Drop the PDF on a Capy page. It auto-converts to markdown via docstrange, which means the agent can actually read it instead of treating it as an opaque blob. Ask the agent to summarize the brand guidelines in plain English, or to pull the three RFP requirements that are likely to be load-bearing for your response. You're not summarizing for fun — you're summarizing so the next time you draft something for that client, the agent has the brand context loaded in the same vault. The PDF→markdown conversion is also why "chat with PDFs" works as more than a parlor trick. The agent isn't running OCR on every query; it's reading text it already has, fast. ## Codifying the parts of you that get repeated Every agency owner has a handful of opinions they re-explain a hundred times a year. Why we don't take the cheap-paid-acquisition gigs. How we price retainers. What good looks like in the first deck. These opinions are the actual product, and they get burned every time you re-explain them in a new pitch. Write them down once as playbook pages — short, opinionated, in your voice. Then when you draft a new pitch and tell the agent to "use the pricing rationale from my retainer-pricing playbook," it cites your own rules instead of guessing. This is the agent-acts-on-your-docs pattern at work — the same idea behind [Claude Code for documents](/blog/claude-code-for-documents/) but for agency operating material. The playbook also doubles as onboarding material for the next contractor or freelancer you bring in. They read your six playbook pages and they have a tighter sense of how you think than a week of shadowing would give them. This is the real shape of "scale without hiring." You're not pretending one person can do four people's work. You're moving the slow part — context loading, pattern matching, draft assembly — to an agent that does it in plain English while you keep the parts a human has to do. ## What this doesn't fix Worth being clear: AI notes don't make your team unnecessary, and they don't make a five-person agency act like a fifty-person one. The work that requires presence — the awkward call where the client is unhappy, the creative call where everyone's riffing in real time, the negotiation — is still human work. Capy makes the documents around that work less expensive, which gives you more energy for the calls themselves. It's also worth noting Capy is single-user by design. One person, one vault. If your goal is a team workspace where five account directors share one notes app with permissioned access, this isn't that product. The shape that scales for the agency owner specifically is a personal vault that holds your institutional memory and lets you draft fast from it. ## Try it on this week's brief If you want to feel whether this changes anything, the cheapest test is to take whichever brief or deck you owe a client this week and run it through Capy with three or four of your best past examples loaded. The first draft will be rough; the second draft, after you tell the agent which patterns you want kept and which dropped, is usually the surprise. That's the moment most agency owners realize they were doing more re-assembly than original thinking, and the re-assembly is what's eating the week. The same instinct shows up in our writeup of [how account managers keep client context from slipping](/guides/sales-accounts/account-managers-ai-notes-client-context/) — different role, same compounding pattern. [Try Docapybara free](/accounts/signup/). Drop in your last four client recaps and ask the agent to draft this Friday's recap from them.