Independent product & systems practice
You already know how the business should work.
I build the system that makes it work that way.
Customer-facing websites, internal tools, integrations and automation for owner-led companies — designed around the real operation instead of forced into somebody else's template.
01
Customer-facing systems
02
Internal operations
03
Integrations
04
Data and automation
The problem
Most small businesses do not have a software problem. They have five tools that each know part of the truth.
The booking system knows the calendar. The processor knows the money. A spreadsheet knows the packages. Nothing knows all of it, so the owner becomes the integration layer — reconciling by hand, holding the state in their head, and staying the bottleneck the business cannot grow past.
Off-the-shelf platforms answer this by asking you to run the business their way. That works right up until the part of your operation that actually makes you money is the part that does not fit the template.
I build the missing layer instead — the one shaped like your business.
Capabilities
What I actually build
Four areas, usually in combination. Most engagements start in one and grow into the next once the first is carrying real weight.
- 01Customer-facing systemsThe public surface of the business: a site that earns trust, explains the offer in plain terms, and moves the right person to the right next step without a sales call in between.
- 02Internal operationsThe daily work pulled out of tabs, spreadsheets and memory, and into one place shaped around what the owner needs to see and do — not around a vendor's menu.
- 03IntegrationsGetting the tools already carrying the business to talk to each other, so a number entered once stops being re-entered in three more places.
- 04Data and automationReliable collection, review and automation for the work that is expensive precisely because it repeats — with the source of truth kept explicit and uncertainty shown rather than guessed away.
Selected work
Systems that are running
A few builds that show the range — from a full operating system for an indoor golf business to a deliberately minimal local sales site.
CC Golf Lab
2026Full operating system for an indoor golf business
Booking, memberships, consent, expenses and revenue reconciliation pulled into one owner-facing system instead of five disconnected tools.
Read the buildJust Edging
2026Right-sized local sales system
Real project photography, local search structure and a text-first quote path — where the correct answer was a simpler system, and it deliberately stayed that way.
Read the buildUrbyn + LenderGraph
2025 — 2026Source-backed data products
Fragmented public records and lender material turned into searchable products with traceable sources, review queues and honest publication boundaries.
Read the buildNeurobase
2025 — 2026Privacy-first memory infrastructure for coding agents
A local-first memory layer that lets AI coding agents carry context across sessions, with consent, provenance and deletion designed in from the start.
Read the build
How I work
Three commitments
- 01
Sit with the actual operation
Before anything gets built I want to see how the work really moves — including the spreadsheet nobody mentions and the step that only happens because one person remembers to do it.
- 02
Build the smallest system that holds
The goal is the least software that solves the problem completely. Every feature that is not needed is one more thing to maintain, explain and eventually replace.
- 03
Hand it over so it stays yours
You get the code, the accounts and a system you can operate without me. I would rather be called back for the next thing than be a dependency on this one.
Next step
Tell me where the business is losing time.
No pitch deck and no discovery-call funnel. Describe the bottleneck and I will tell you plainly whether it is worth building something for, and roughly what that would take.