Web applications
Dashboards, admin tools, customer portals and multi-tenant SaaS. Tested at the boundaries, and built so the next team can move fast on it.
Most of what we build is our own. We still take on a small number of outside engineering problems each year, when the problem is genuinely difficult and we are the right people for it. This page is how that works, and how to tell if yours is one of them.
We are not trying to be available for everything. The work we are best at has real stakes: money moving, sensitive records, something that has to keep running while it is being fixed.
If it is not a fit, we will say so on the first call, and happily point you to someone better.
Built in banks, exchanges, hospitals, logistics and SaaS, and most of it still running. Client names stay under NDA; we are happy to arrange a reference call.
Dashboards, admin tools, customer portals and multi-tenant SaaS. Tested at the boundaries, and built so the next team can move fast on it.
OTC desks, per-user deposit addresses, automated hot-to-cold sweeps, programmatic escrow with dispute resolution. Custody, hardened for production.
Single sign-on, role-based access and audit trails, built so legal does not lose sleep and the ops team actually uses it. Every door closed unless someone is meant to be through it.
Event-driven services, durable queues, real-time pipelines. Boring on purpose and bulletproof in practice — the kind of thing that sits there humming for years.
Infrastructure as code, observability and cost discipline. Your platform in the cloud without the surprise October bill, with runbooks written before launch.
// We work with modern, proven languages, frameworks and cloud platforms, and with AI every day. The stack is chosen after the problem is understood. It is a decision, not a menu.
Discovery to launch typically runs seven to fourteen weeks. Every phase has written acceptance criteria, and you can stop at the end of the first one with the documents in hand.
We sit with your team, audit the codebase if there is one, map the data, and write the smallest spec that will not lie to us in week six. Nothing is built before it is understood.
Schemas, failure modes and deploy topology are agreed before production code exists. AI handles scaffolds, refactors and test coverage — every pull request still walks through a senior engineer’s hands before it lands.
Staged rollouts, feature flags, dashboards lit up, on-call handed over cleanly. We do not celebrate at launch — we celebrate at week four with no incidents.
Fixed price where the scope is knowable, milestones where it is not, and a retainer only if you actually want one. The SOW always wins over anything on this page.
If you do not want to continue at the end of it — for any reason — the engagement ends and the fee is returned. You keep the documents either way.
We invoice only after you sign off in writing. If we miss the bar and cannot fix it inside the agreed cure period, the engagement closes without final payment.
Kill fees and refund terms are written into your SOW before anyone starts — never improvised after the fact. We have signed enough of them to know which ones are fair.
A paragraph is enough: what the system does, what is going wrong, and what happens if it stays that way. We reply within one business day, always from the engineer. The first call is thirty minutes and costs nothing.