Services
I take systems from architecture through to the pager. If a piece of this is not what you need, I will say so.
Multi-tenant SaaS platforms
One product serving many customers without their data touching.
Tenancy is an architectural decision, not a feature you add later. I build platforms where the isolation model, the migration story and the billing boundary are decided up front, so onboarding customer number two hundred costs the same as customer number two.
Typically includes
- Tenant isolation model
- Per-tenant migrations
- Role and permission design
- Subscription and billing flows
System and API integration
Connecting software that was never designed to talk to anything.
ERP systems, payment providers, carrier platforms and scanners all have opinions, and most of them are old. I write the layer in between: idempotent, retryable, and explicit about what happens when the other side is down, because the other side will be down.
Typically includes
- ERP and SAP interfaces
- Payment provider integration
- Webhook and queue design
- Failure and retry semantics
Platform engineering
Getting the thing deployed, observable and repeatable.
Software that only one person can deploy is a liability with a countdown on it. I set up Kubernetes on AWS, infrastructure defined in code, GitOps delivery and the monitoring that tells you something is wrong before a customer does.
Typically includes
- Kubernetes on AWS EKS
- Helm charts and GitOps delivery
- Infrastructure as code
- Logging, metrics and alerting
Rescue and modernisation
Taking over a system that works but nobody wants to touch.
An inherited PHP or Laravel codebase with no tests, no deployment process and one person who understands it. The first job is to make it safe to change: characterisation tests, a real pipeline, and the upgrade path staged so the business keeps running through it.
Typically includes
- Codebase and risk audit
- Framework and PHP upgrades
- Test and pipeline introduction
- Staged migration plan
How the work runs
Find the real constraint
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.
Ship in slices
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.
Stay on it in production
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.
Ways to work together
Fixed-scope project
A defined system, built and handed over running. Scoped after discovery, priced per phase.
Ongoing engineering
A recurring share of my week as the senior backend and infrastructure person on your product.
Audit or second opinion
A written review of an existing system, its risks and its upgrade path. Usually one to two weeks.
Tell me what is breaking.
Send a short description of the system and the problem. You get a technical answer, not a sales call.
Or email directly[email protected]