I set up Claude inside small professional offices: connected to the email, files, and QuickBooks you already run, configured so client data stays where it belongs, and taught to your staff until they use it without thinking about it. Two weeks, fully remote, one flat price.
Small professional offices in Lubbock and West Texas, five to thirty people, living in email. The work below is the kind of drafting and follow-up a well-set-up Claude starts for you, in your voice, from your own files.
First-drafted from last year's letter and this year's fee schedule. Plus monthly report narratives written straight from QuickBooks.
A matter file summarized before the client calls, and first-draft letters that start from the file instead of a blank page.
Renewal letters and policy summaries drafted ahead of the date, so renewals stop sneaking past anyone's inbox.
Owner statement narratives and lease summaries written up the same day, not the weekend after the month closes.
Different kind of office? If it runs on email, calendars, and documents, the same setup applies. Write me what eats your week.
The offer is called the AI Back Office Setup. You don't learn a new tool and you don't manage a project. I do the work; your people get shown how to use what's built.
Thirty to forty-five minutes on a screen share, watching how your office actually works. I find the three biggest time sinks and name them back to you. Diagnosis first.
Week oneA workspace for the owner and key staff, connected to what you already run: Outlook or Gmail, OneDrive or Drive, QuickBooks, your calendar. HubSpot, Canva, or Docusign if you use them.
Your toolsBuilt against your named time sinks, not a template. Client emails drafted in your voice from bullet points, morning inbox triage, meeting notes turned into action items, first-draft engagement letters or proposals, report narratives from QuickBooks, client file summaries. We pick the three that hurt most.
The workEvery connector switched on deliberately, and a one-page plain-English map of what Claude can see, what it never can, and where your data goes. You keep the page. The whole thing is laid out in the next section.
The differentiatorOne recorded training session, plus a one-page cheat sheet for every workflow. Nobody studies a manual. They follow the sheet, and the recording is there when someone new starts.
HandoffEmail me anything for a month after handoff. If something breaks or drifts, I fix it. No ticket queue, no support portal.
AfterScope, in writing: configuration and workflow building inside your existing tools. Custom code, new integrations, or new infrastructure always get a separate written quote first. That boundary is how the price stays flat.
Every client gets a one-page data map, filled in for their office, before anything is connected. It's the first thing I show and the reason offices hire me. This is what it covers.
One page on purpose. If any line on it is unclear, that's my failure, not yours.
When your staff use Claude, the conversation and whatever it pulls from connected accounts goes to Anthropic, the company that makes it, encrypted in transit and at rest, to generate the response.
On the business plan your office runs, your data is not used to train AI models by default. I verify that setting on your account and hand you the screenshot. It stays that way unless someone with owner access changes it, and the owner is you, not me.
A person checks numbers before they go out. The AI drafts; a human verifies figures against the source. It's printed on every cheat sheet I leave behind, because a confident wrong number is the real risk with these tools.
New tool, new conversation. Nothing gets connected without a five-minute check against this same map. On retainer, that check is my job.
Custom code, integrations beyond your existing tools, or new infrastructure: separate written quote, always before work starts.
This space is held for the first documented setup at a West Texas office. When it wraps, the real record gets published here with the owner's permission:
A short recorded walkthrough of a completed setup will sit here: the workflows running on real (permissioned) files, start to finish.
Email me what kind of office you run and the one task that eats the most hours in your week. I'll send back a short recording of what the setup looks like on a stack like yours. No call, no form, no follow-up sequence.