— What I build
Systems I build and run.
Products I own and run, and platforms built for clients to run as their own. Across all of them, AI drafts, the system governs, and people make the consequential calls.
— The Wider Build
Products I run.
Local Media Desk
Revenue operating system for local media
Research, planning, proposals, compliance, pipeline and execution on one desk, including political advertising operations and events run as their own line of business. Agent-ready over MCP, with people approving what reaches a client.
Model Desk
Live operating models from the workbook you already run
Turns the operating workbook a finance team already keeps into live, interactive software, checked cell by cell against the spreadsheet's own math.
AI Readiness
Choose the AI investment worth funding
A short adaptive interview about how the operation makes money, ending in a branded read and a plan for which AI work to fund first.
Seiche
Civic intelligence for local news
Helps local publishers turn fragmented public information and reporting into a persistent, source-linked civic record, so communities can see what is changing and what happens next.
Visit Seiche ↗
Seiche name pending trademark clearance.
Discoverability OS
Search and answer-engine fixes, shipped as code
Audits a site for how search and answer engines read it, keeps the evidence behind every finding, fixes the root cause on an isolated branch and opens a reviewed pull request.
In the shop
— Agent-ready
Built for the assistant your team already uses.
Local Media Desk publishes its planning work over MCP, the open standard AI assistants use to reach tools. Sellers can work it from Claude today, with access scoped to their workspace and a person approving anything that reaches a client.
More CRMs and more assistants connect through the same contract. A customer use case sets which one comes next, and how fast.
How the desk connects →— Built for clients
Platforms clients run as their own.
Some of the work belongs to the client from the first commit. These are described by what they do; the names and links stay with the clients who run them.
Agency operating platform
The operating system for a revenue agency: account structure and health, project hubs that hold decisions, promises, meetings and documents, document search with citations, an outcome engine that estimates effort from the agency's own history, approval-gated client deliverables and a client portal that shows only released work. Agents propose the next step; a person approves it before anything is sent.
Event platforms
A conference hub for a revenue event, with attendee and sponsor portals, self-serve sponsor profiles and materials, and public sponsor pages the organizer controls. Sourced networking guides and session recaps for an industry conference. And inside Local Media Desk, events run as their own line of business, with sponsorship packages and event P&L.
Bring the operation you run today. We will work out whether the answer is one of these systems, something built on what you already have, or a tool I don’t make.
Start the conversationBuilt Revenue