I'm Bo Hodnett, in Lubbock. I set up Claude inside small offices out here: connected to the email, files, and QuickBooks you already run, configured so client data stays where it belongs, and taught to your people until they use it without thinking about it. You don't buy new software and you don't learn a system. I do the wiring and the teaching.
Small professional offices in Lubbock and West Texas, five to thirty people, living in email. The work below is the kind of drafting a well-set-up Claude starts for you, in your own voice, from your own files.
Engagement letters, first-drafted from last year's letter and this year's fee schedule. Monthly report narratives written straight out of QuickBooks.
Matter summaries ready before the client calls, and first-draft letters that start from the file instead of a blank page.
Renewal reminders and policy summaries drafted ahead of the date, so renewals stop sneaking past anyone's inbox.
Owner statements narrated 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.
If you need one, I also build the simple website and set up the Google listing that go with a small office, so people can find you and see you're real.
An office manager at a CPA firm typed the note on the left between phone calls. The letter on the right came back. Both are real in shape and length; the names are changed.
Typed into Claude between phone calls.
Robert,
Attached is our engagement letter for the 2026 tax year. The scope is the same as last year, preparation of your federal and state returns, and we've folded in the payroll questions you raised this fall so they're covered under the same agreement.
Our fee this year is $2,400, up from $2,150. Most of that difference is the added payroll work, and I'd rather name it plainly than have it surprise you on an invoice.
To keep your returns on schedule, we'd need your documents by March 1.
Thank you for a twelfth year with us, and give our best to the family.
Denise
Drafted in the firm's own wording, pulled from last year's letter and this year's fee schedule. Denise read it, changed one phrase, and sent it.
You don't manage a project and nobody on your staff studies a manual. 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 runs. I find the three biggest time sinks and name them back to you. Diagnosis, not a pitch.
Claude set up for the owner and key staff, wired to the tools you already use: inboxes, document folders, QuickBooks, calendar. Nothing connected that we didn't agree on.
Aimed at the time sinks we named. Client emails drafted in your voice from bullet points, morning inbox summaries, first-draft proposals or engagement letters, report narratives straight out of QuickBooks.
Every connector switched on deliberately, and a one-page plain-English data map of what it can see, what it never can, and where your data goes. The whole thing is laid out in the next section.
One recorded session plus a one-page cheat sheet per workflow. The recording is there when someone new starts.
Email me anything for a month. If something breaks or drifts, I fix it. No ticket queue.
Scope, 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 this as a one-page map in plain English, filled in for their office, before anything is connected. It's the first thing I show and the reason offices hire me. Here is what it covers.
What your staff type, and whatever it pulls from connected accounts, goes to Anthropic, the company that makes Claude, encrypted in transit and at rest, to write the response. On the business plan your office runs on, your data is not used to train their models by default. I verify that setting on your own account and hand you the screenshot. It stays that way unless someone with owner access changes it, and the owner is you, not me.
You type your own credentials, always. The connected list is written down together and it doesn't grow without you.
I'm Bo, and I'm an accountant by trade. My day job is in grants and finance, so I spend it reading budgets, ledgers, and P&Ls. That's the reason I started Mainspring instead of some general tech shop: when I sit down with a CPA firm or a bookkeeper or an insurance office, we already speak the same language. I read a P&L the way you do, and I know what a clean set of books is worth.
The other half of me runs a serious homelab at home: my own servers, my own network, all of it built privacy-first. So the data question on this page isn't a marketing line for me. I run the infrastructure myself. When I tell you I'll show you exactly where your data goes and exactly what it never touches, I mean that literally, because it's the same care I take with my own.
And I'm right here in Lubbock, working with offices around West Texas, with my real name on the work. This isn't an anonymous agency on a coast that you email into a void. It's a person you can call. That's the whole idea.
All six deliverables above. Half up front, half at handoff. No hourly meter and no surprise line items. For reference, a readiness assessment alone commonly runs $2,000 in this space before any work starts; this price covers the whole setup on purpose, because I'm building the local track record.
I keep everything running. When a tool changes and something breaks, you call me, not a help line. I answer your questions, vet any new tool before it touches your data, and once a quarter I look for the next thing worth building. Cancel any month; everything already built keeps working and stays yours.
If the first workflow I build doesn't save you time in the first month, I'll rebuild it or refund the retainer. You keep whatever's already working. I'd rather fix it than keep money for something that isn't earning its place.
An honest note on proof: I'm finishing the first documented setup right now with a real office here in town. When it wraps, the written account goes here, with numbers and the owner's permission. Until then, you can ask me for the writeup and I'll send it when it's done.
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 to book, no form, no follow-up sequence. You watch it and decide.
Or just write it down for later: [email protected]