
Professional services
Multi-tenant CRM for a services group
A group of subsidiaries wanted a single CRM, but each entity needed a hard data boundary for compliance. Shared-table tenancy with a customer_id column was not going to survive an audit.
I design, build and operate production platforms for businesses that cannot afford downtime.
Four kinds of work, all of it hands-on. No account manager between you and the person writing the code.
One product serving many customers without their data touching.
Connecting software that was never designed to talk to anything.
Getting the thing deployed, observable and repeatable.
Taking over a system that works but nobody wants to touch.
Client names are under NDA, so each project is described by sector, problem and architecture.

Professional services
A group of subsidiaries wanted a single CRM, but each entity needed a hard data boundary for compliance. Shared-table tenancy with a customer_id column was not going to survive an audit.

Travel and connectivity
A paid order has to become a working eSIM, every time, across two systems that can both fail.

Retail foreign exchange
Automated margin and liquidation logic running against live price feeds.

Civic technology
A system whose entire year of traffic arrives on one fixed date.

Consumer healthcare
A consumer app that never authenticates against the clinical user table.
Most briefs describe a solution someone already chose. A short paid discovery establishes what actually limits the system: the data model, the integration, the deployment, or the org chart. Sometimes the answer is that you do not need me.
Work goes out in vertical slices that run in production, behind flags where needed. You see something real every two weeks, and the integration risk is paid down early rather than discovered in the last month.
I run what I build: deployments, monitoring, the incident at an awkward hour. When a handover makes sense, it is a documented one, not a zip file and a phone number.
A defined system, built and handed over running. Scoped after discovery, priced per phase.
A recurring share of my week as the senior backend and infrastructure person on your product.
A written review of an existing system, its risks and its upgrade path. Usually one to two weeks.
Send a short description of the system and the problem. You get a technical answer, not a sales call.
Or email directly[email protected]