Selected work.
Systems, teams, and the trade-offs each one cost. Some clients are named. Some are current, so they are not.
Rebuilding a remittance platform, then getting it licensed
Idempotency keys and saga orchestration across mobile money and bank rails, then ISO 27001 and a central bank licence led from inside the engineering team.
What changes between eight engineers and thirty
What stopped working past a single team, what had to be written down, and how quality holds when I cannot review everything.
Estimating engineering work you then have to deliver
Work breakdown to per-role hours, requirement compliance matrices, and banded thresholds that stop a bid and re-estimate instead of silently overrunning.
Making a versioned datastore queryable without losing its history
An append-only analytical replica that keeps every version of a record intact on a backend with no cheap UPDATE, from backfill to live replication.
Making three custody providers interchangeable behind one wallet interface
Three MPC custody models with different trust boundaries and key ceremonies, abstracted so product code never learns which one is underneath.
Onboarding and identity for a regulated crypto platform
A single-use invitation token lifecycle specified as a state machine, an auth gateway with OIDC/PKCE, and KYC verification across core services.
A promotion framework for a consultancy that does not fit product-company ladders
Five levels, forking into IC and management tracks at L4, adapted from consulting firm models for an engagement-based services context.
Automating end-of-day reconciliation
Financial errors down over 75% after end-of-day reconciliation stopped being a job someone did by hand.
Reporting to a foreign regulator out of a core banking system
FATCA returns assembled out of the bank's core banking system for the US IRS, plus a utility payments integration that lifted collections over 10%.