I fix production systems that move money.
For three years I have owned a Swiss money-transfer platform end to end: forty payment-partner integrations, a SQL Server database of 1,900 stored procedures, the mobile app in both stores, and the Azure bill.
If your revenue runs through a system nobody dares to touch, that is my lane. The query that got slow, the deadlocks at month-end, the partner API that fails silently at 2am, the cloud bill that quietly doubled.
Results, with receipts
The numbers I can prove.
| Metric | Before | After | Evidence |
|---|---|---|---|
| Production deadlocks | 288 / month | ≈ 4 / month | Extended Events captures; alerting still live |
| P95 response time | 1.56 s | 512 ms | 24 months of telemetry, 22.3M requests |
| Mean response time | 448 ms | 190 ms | Same telemetry, on a dashboard I built |
| Monthly Azure bill | CHF 3,335 | CHF 1,356 | Microsoft invoices, Sep 2024 vs May 2026 |
| One reporting page | 66 s | ≈ 1 s | Commit history, timed before and after |
All from one production platform. Ask me on a call and I will walk you through any of them live.
Services
What I take on.
- SQL Server performance rescue
- The slow queries, the month-end deadlocks, the page everyone avoids clicking. Fixed-price audit first, then remediation, with a measured before and after.
- Payment and correspondent integrations
- Partner APIs that move money: REST, SOAP and SFTP transports, mutual TLS, request signing, idempotency, reconciliation. I have built about forty of them.
- Legacy .NET modernization
- WebForms and .NET Framework systems kept alive and moved forward step by step. No rewrite, no big bang, no betting the business.
- Azure cost review
- Reservations, rightsizing, governance. I cut a production fintech bill by 59% without dropping a single workload, and I can show you the invoices.
- AI adoption for regulated teams
- Guardrails, governance and hands-on training in English, French or Spanish, so your developers get the speed without AI tooling ever touching customer data.
Method
How an engagement works.
Diagnosis first, at a fixed price: I audit the system, write up what I found with the evidence, and give you a plan ranked by impact. If you want the fixes done, we agree a scope and I do the work, measured against the same numbers. When I leave, you keep the dashboards, the alerts and the documentation. No lock-in by obscurity.
What I am not: an agency. There are no juniors behind me and no handoffs. I take two clients at a time, I work remote from Quito on US Eastern hours, and if your problem is outside my lane I will tell you on the first call.
Selected work
Two stories behind the table.
The deadlock line hides the better story: at the worst point the platform logged 53 deadlocks in a single day. Moving the database to Read Committed Snapshot Isolation and redesigning the worst transactions took it to about four a month, and the Extended Events capture that proved it still runs in production, paging someone whenever a new one appears.
I also wrote a money-transfer mobile app alone, React Native and strict TypeScript, 35 screens in four languages, OIDC with PKCE, biometric unlock, through a pentest remediation cycle and App Store review. It is public: App Store ↗ · Google Play ↗
About
Who is writing this.
Before software I ran restaurants in France, which turns out to be decent training for production incidents. Since 2023 I have been the engineer a Swiss fintech calls when the system that moves the money misbehaves. Associate degree in Computer Science in 2026, BSc in progress, and every claim on this page has a file behind it: telemetry exports, Microsoft invoices, Extended Events captures, commit history.
Have a system that needs fixing?
Write me two paragraphs about what hurts. I will answer honestly, including when the answer is that you do not need me.