Your problem. One conversation.
Senior capacity by the day. A rescue when it's already breaking. Scaling when you've outgrown it. A cloud bill cut down to size.
Ways I solve your problem, grouped by what you need. Whether you need to build, scale, modernize, or level up your team, pick the one that matches your situation, or talk to me and we scope something custom.
Contract Engineering
On requestA senior engineer and architect on your team, by the day. Remote-first, NRW on-site when it matters. Proper B2B invoicing.
·Senior full-stack + architecture ownership
·AI-native development discipline
·Reduced rate on engagements of 3+ months
Timeline · flexible
Production Readiness
On requestYour product works and has users, but deploys are scary and nothing is tested. In 1-2 weeks I make it boring.
·Real tests against a real database
·Monitoring, backups, and a restore you have watched work
·Written handover so your team owns it
Timeline · 1–2 weeks
Scale-Up
On requestYour product works, but it buckles under load. I find where it actually breaks, database, caching, architecture, and make it handle 10 to 100x the traffic without a rewrite.
·Load profiling against realistic traffic
·Database, caching, and async fixes where they count
·A re-runnable load test and a written capacity plan
Timeline · 1–3 weeks
Legacy Modernization
On requestYour monolith earns the revenue, so you can't stop it, but every change hurts. I decompose it into maintainable services while the business keeps running.
·System archaeology + decomposition plan
·Zero-downtime migration sequencing
·Hands-on extraction, not just a slide deck
Timeline · 4–12 weeks
Cloud Repatriation
On requestMove off AWS, GCP, or Azure to infrastructure you own: a fraction of the cost, EU data sovereignty, no lock-in, with HA and backups you have actually restored from.
·Cost and dependency audit with projected savings
·Migration to owned infra with HA and real backups
·EU data residency, CI/CD, and a runbook your team owns
Timeline · 1–2 weeks
AI-Native Team Day
On requestYour team has AI licences and no shared standard. One hands-on day in your repo, and a playbook they keep.
·Agent workflows, MCP, context engineering
·Review rules that stop AI code becoming debt
·Written playbook + follow-up call
Timeline · 1 day
Second Opinion
On requestOne architecture decision, rewrite or refactor, this stack or that, analyzed in writing, with a call to argue about it.
·Written analysis of your specific decision
·Repo review, I read the actual code
·60-minute call to challenge the recommendation
Timeline · 1 week, async