Self-built product
Workbench
A complete Claude Code setup around a revenue assistant for a subscription business, answered through a custom MCP server.
A complete product I designed, built and tested myself. Client work is in Case studies.

Claude Code needs a setup, not just a prompt
Without project rules, access to the business’s data and checks that run every time, Claude Code is unreliable from one task to the next. Workbench shows what a proper setup looks like.
A revenue assistant answered through its own MCP server
Workbench is a revenue assistant for a subscription business, answered through a custom MCP server with four tools: headline KPIs, a revenue bridge that always adds up, customer search, and a churn-risk list with reasons.
Rules, skills, subagents and hooks around it
Around the server sit a CLAUDE.md with rules and a definition of done, skills such as adding a metric with its test, reviewer and test-writer subagents, and hooks that run the tests after every edit, block changes to protected files and send Claude back to fix failing tests. Every file explains why it exists, and a step-by-step guide goes from installing Claude Code to the first MCP tool call.
Tech stack
- Node.js
- MCP
- Claude Code
Screens from Workbench

How the pieces fit, one change from start to finish.

Calling the MCP server’s tools directly.
Want something like this for your business?
Tell me what you need it to do. I’ll reply within 24 hours on weekdays with questions or a suggested first step.
Start with the $150 scoping session, credited toward the build.