A remote practice or small business is held together by context — the things you and your few collaborators know about each client, each project, each decision — much more than by meetings. The trouble is that the context is everywhere. Slack DMs, Google Docs, scattered email threads, your own head. When you're remote, the absence of a hallway conversation means there's no informal layer to backstop the formal record. The formal record has to actually carry the weight.
A notes app with an integrated agent is a calmer way to carry it. Not a project-management tool, not a wiki, not a CRM — a vault of plain markdown that the agent can read across, holding the connective tissue of the practice. The same shape underwrites how agency owners take on more work without hiring and how fractional executives manage multiple engagements — different containers, same problem of distributed context.
A vault that mirrors how the practice actually moves
The shape that holds up across practice size is roughly: one top-level page per client or project, with sub-pages for the brief, the running notes, the decisions log, the meeting recaps, and any reference documents. A second top-level page for the practice itself — pricing, positioning, processes, the running ops log. A third for the personal layer — your own goals, energy, weekly review.
Capy supports unlimited page nesting, so larger practices can fan out by service line, geography, or client tier without you having to commit to a depth in advance. The whole vault is plain markdown. That matters because when you sit down on Monday morning and ask "what's open across all my clients," the agent reads across every page in one query and writes a status summary. You don't need to remember where you wrote things down.
Async updates that carry the weight
A remote practice can't lean on stand-ups. The substitute is async updates that are short, structured, and actually written. Most practices try this for a month and then drift back to "let's just hop on a quick call," which is the death spiral.
The fix is to make the cost of writing an update closer to zero. A working flow: at the end of the day or week, ask the agent to read the day's notes — the meeting recaps you dropped in, the decisions you logged, the followups you closed — and draft a one-paragraph update in your voice. You edit. You ship.
The draft is usually 70% of the way there because the agent has read your actual notes, not generated from generic web data. The remaining edit is the judgment call about emphasis and tone, which is the part that's actually yours. The update lands in your collaborator's inbox and the meeting you would have called doesn't need to happen. (The drafting-from-vault pattern is the same one underwriting investor-relations and board updates — different audience, same speed-up.)
Client context that survives the gap between calls
The hardest part of running a remote client engagement is the gap between calls. You meet with the client every other week. In the gap, you're working on three other clients, and by the time the next call rolls around, you can't quite remember whether the thing the client mentioned last time was a casual aside or a real commitment.
A working setup: each client page has a "running thread" sub-page where you drop a one-line entry after every interaction. Email exchange, slack message, call recap, even a half-formed thought you had in the shower about their account. Two minutes per entry, max. Over a quarter, the running thread becomes the primary-source archive of the relationship.
Before the next call, ask the agent to read the running thread, the most recent meeting recap, and any open followups, and draft a one-page brief: what's open, what they last raised, what you committed to, and what you should ask about. You walk into the call having actually remembered the relationship. (The same client-context habit is the spine of how account managers keep client context from slipping.)
Recordings with speaker labels for the calls you do have
Most calls don't need to be recorded. The ones that do are the kickoff, the quarterly review, the hard conversation about pricing or scope. Those are the calls where a transcript would help and where you don't want to be the one taking notes during the conversation.
Record the call in Capy. The transcript comes back with speaker diarization — labels like "Speaker 1: …" so you can tell who said what, not just a wall of text. Park the recording on the client's page. Ask the agent to draft a recap with three sections: what we agreed, what's still open, what we agreed to revisit and when. Pull a list of followups with owners.
The transcript matters less for the call itself and more for the next time. Two months later, when the client says "we agreed in the kickoff to handle X this way," you can search the vault and find the moment in the transcript where it was said, with the speaker labeled.
A decisions log the agent helps you keep, with PDFs alongside
Decisions in a remote practice get made in writing — over Slack, over email, in the agent itself — and then quietly forgotten. The reason you set the price at $X. The reason you offered a discount to client A but not client B. The reason you onboarded vendor X over vendor Y. Six months later, the rationale is gone and you're either making the same decision again from scratch or, worse, making a different decision because you forgot the original rationale.
The fix is mechanical. Have an inline database called "practice decisions" inside your top-level practice page, with rows for date, decision, rationale, area affected, and what triggered it. The database lives directly in the page via the :::database::: directive — you don't switch tabs.
After meaningful working sessions or client calls, ask the agent to read the recap and propose decision entries with rationales. You confirm or edit. The cost of keeping the log gets close to zero, which is the only way it actually gets kept.
The same page accumulates the PDFs your practice generates — signed contracts, vendor invoices, regulatory letters, partner MSAs. Drop them in; they auto-convert to markdown via docstrange so the agent can read them as searchable text the same as any other note. When the question comes up about a clause in a thirty-page MSA, you ask the agent and get the relevant section back with the rationale entry that lives next to it. The same workflow underwrites our writeup of contract negotiation with AI notes — different surface, same mechanic.
The weekly review the practice runs on
Most remote practitioners try to keep a weekly review and most quietly drop it after a month. The reason is the cost of looking back — gathering the inputs, remembering what you committed to, comparing it against what actually happened. With the working record in plain markdown, the review becomes a single prompt.
A working flow: every Friday, ask the agent to read the week's client running threads, the followups closed and slipped, the decisions logged, and the calls recorded, and draft a one-page review with four sections: what shipped, what slipped, what you learned, what's open for next week. You edit. The review takes twenty minutes instead of an hour, and it actually gets done. (The weekly-review-from-vault habit is the same one underwriting annual planning and goal setting at a longer horizon.)
What this isn't
Capy isn't a multi-user team workspace. It doesn't have role-based access, shared workspaces, or admin permissions. The shape that works for a remote practice is one operator with their own vault, sending async updates and structured outputs to collaborators through whatever channel makes sense. If your practice has grown into a team of five who all need to edit the same artifacts with permissions, that isn't this product today.
It's also cloud-hosted on Linode. Your vault sits on our servers. For most solo or duo remote practices, the cloud-vault shape with one integrated agent is a strict upgrade over the current reality of Drive folders plus Slack plus a notebook. Pricing tiers are on the pricing page.
A small first test
Take the client you've been running the longest. Drop the last two meeting recaps, the most recent contract, and any open followups into a Capy page. Ask the agent to draft a one-page brief for the next call. If the brief surfaces something you'd otherwise have walked into the call having forgotten, that's the agent doing the connective work that running a remote practice requires.
Try Docapybara free. Load one client's last month and see what the next call feels like.