How an engagement works.
The method, what you can buy, and the technical detail for whoever on your side asks.
The method
Every engagement has the same shape.
- Paid specScope, fixed price, and timeline in writing. You approve it before any build starts. The fee credits toward the build, and you keep the document either way.
- BuildWeeks, not quarters, inside your accounts: your hosting, your keys, your data. Anything that can't finish in weeks gets cut into pieces that can.
- HandoffDocumentation written for whoever inherits it. Finished means your team can run it without me.
- Ops retainer, if you want oneMonitoring, updates when vendors change things underneath you, small changes, and a one-page report each month. A build works without one.
Where most people start
AI and Automation Assessment
I inventory your systems and workflows, score three to five automation opportunities by effort and payoff, and write a one-page AI use policy. You get a roadmap that says what to do first and what to leave alone. The fee credits toward any build it recommends, and it counts as the spec, so there's no second fee.
What I build
Fixed-price builds.
- AI that knows your organizationConnectors that give Claude or ChatGPT access to your documents, your CRM, and the outside data your staff look up by hand. Each one signs in through your existing login and can read what it needs and nothing else.
- Publishing pipelinesRequest to published draft, inside the tools your staff already open every morning. A person approves the last step. Nobody has to learn a new system.
- IntegrationsTwo systems that don't talk, made to talk: CRM sync, membership data, feeds. Cleaning up the data you inherited is usually part of it, and usually the slowest part.
- Search across what you've writtenYour documents, searchable in plain English, with every answer cited to the file it came from. Scoped to your document set during the spec.
A person approves before anything goes out.
Under the hood
For the technical person who'll ask.
Python and FastAPI services, Postgres, Cloudflare Workers, WordPress and PHP, Okta single sign-on, and MCP for connecting AI assistants to your systems. Language-model calls fall back across providers, so one vendor's bad afternoon isn't your outage.
If it has an API, or even an export button, I can usually wire it in.
Agencies: I also take build work behind your team. Ask about terms.
Start here
Tell me what's eating your team's week.
Describe the workflow. I'll tell you what I think it takes, or that it isn't worth doing. If it's a fit, we talk before you pay for anything.
[email protected]