How I work
The method, the packages, and what's under the hood.
The home page is the short version. This is the detail: how I shape engagements, what you can buy, and the technical specifics for whoever on your side asks.
The method
The method matters more than the technology.
I shape every engagement the same way, so you know what you're buying and when it ends.
- A paid spec before any buildScope, price, and timeline written down and agreed before code starts. You own the document either way; if you take it somewhere else, it still works.
- Fixed priceQuoted after the spec, not adjusted after the fact. The number you agree to is the number you pay.
- One named deliverableA specific thing that either exists at the end or doesn't.
- A hard end dateWeeks, not quarters. Projects that can't finish in weeks, I cut into pieces that can.
- Your accounts, not mineYour hosting, your API keys, your repository, your data. I work inside them and hand back the keys when it's done.
- Everything is handed overDocumentation written for the person who inherits it, plus your accounts and your keys. Finished means your team can run it without me.
Packages
Fixed price, named deliverable, hard end date.
A paid spec gates every build, so nobody is guessing at scope when work starts, and the spec fee credits toward the build. The price comes back fixed, in writing, before you commit to anything.
Most people start here
AI and Automation Assessment
Your systems and workflows inventoried, three to five automation opportunities scored by effort and payoff, a one-page AI governance policy, and a roadmap that says what to do first and what to leave alone. The fee credits toward any build it recommends, and it satisfies the spec requirement, so there's no second spec fee.
Content and Publishing Pipeline
Request to published draft, wired into the tools your staff already open every morning, with human approval built into the last step rather than bolted on. Nobody has to learn a new system.
Data and API Integration
Two systems that don't talk, made to talk. CRM sync, membership data migration, feed automation. Expect cleanup of the data you inherited to be part of it, and the part that takes longest.
Document Search with Citations
Your own documents, searchable in plain English, with every answer cited back to the file it came from. Scoped to the shape of your document set during the spec.
Paid Spec gates every build
Scope, fixed price, and timeline in writing before work starts, with the fee credited to the build. Whatever you decide about the build, you end up with a document you own.
Ops Retainer optional, per system
Monitoring, model and API updates as vendors change them underneath you, small changes, and a one-page report each month. A build works without one. What you're buying is not having to track vendor changes yourself.
Under the hood
For the technical person who'll ask.
Python and FastAPI services · Postgres · Cloudflare Workers, D1, KV · WordPress and PHP · Okta SSO · MCP for tool integration · multi-provider language-model orchestration with fallback, 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.
Working together
- Typically able to start within two weeks.
- One call before you pay for anything.
Tell me what's costing you the most time.
Describe the workflow, and I'll tell you what I think it takes, or that it isn't worth doing. If it looks like a fit, we'll get on a call before you pay for anything.