Two ways in
This page works for two kinds of visitor, and the lanes stay separate on purpose.
- Hiring teams — the same work history backs full-time and contract roles in IT operations, business systems, development, and AI implementation. Start with the role-fit lane and the current resume; the experience page has the full timeline.
- Teams with a problem to solve — early products, operations, AI adoption, and tools worth building. The fastest start is a 20-minute intro call (the button above); the packages below are the usual shapes the work takes.
A good fit is usually a concrete problem: an early product that needs shape, a support process that is eating people's time, infrastructure nobody remembers how to run, or research that should become a tool people can actually use.
How I package the work
Three scoped engagements cover most of what people need. Each is fixed-fee and time-boxed, so the cost and the outcome are clear before it starts.
AI Readiness Sprint
Turn an AI idea into a plan you can actually run — or an honest "not yet."
- What you get: a map of the current workflow, where AI removes friction and where it should not, a scoped pilot with named review owners, a token-budget cost model, and a go/no-go using the Innovation or Theater framework.
- Good fit: a team that wants AI to survive contact with real work instead of dying after the demo.
- Shape: fixed-fee, priced after a 20-minute scoping call, roughly one to two weeks.
Operations & Runbook Pass
Make the systems legible so they stop depending on one person's memory.
- What you get: a documented environment, runbooks for the risky tasks, a troubleshooting and handoff reference, and plain-language reliability notes.
- Good fit: "it works, but only one person actually knows how to run it."
- Shape: fixed-fee, priced after a scoping call, scoped to the surface area.
First-Version Build
Get a real first version in front of real users.
- What you get: a working browser tool, internal app, or product slice — shipped — with the judgment calls written down so the next person can build on it.
- Good fit: an early product or internal tool that needs both shape and code.
- Shape: project-based, priced after a scoping call, scoped to the first useful outcome.
Other ways to work together
- Advisory or fractional — ongoing help on AI implementation, operations, or product direction without a full hire.
- Research into a tool — turn a decision or a recurring question into something people can use, the way the labs and tools on this site were built.
What makes a good first note
A useful first message does not need a full spec. Make these clear enough to discuss:
- The problem, the audience, and what already exists.
- What must stay private or constrained.
- Who owns the result.
- What a good first outcome looks like.
Clear constraints make better builds. Book a 20-minute intro above, or pick the lane below that fits and send a note. If you use the chat, I keep your message and reply-to so I can follow up — see the data-handling note.
The proof is already on the site
This page sits on top of working proof, not promises: browser tools you can use right now, interactive labs you can test, research behind the judgment, and ventures like AI Lunchroom. For the background that supports hiring conversations, see experience and the profile.
I keep independent work separate from employer relationships. Work featured here is personally funded and developed with my own resources or through independent collaborations, not company budgets or work-sponsored channels.