Most software companies are organized around growth. Stable is organized around finishing things. We pick problems that are real, scope them honestly, and ship them on a calendar a human can read.
The companies we work with are the ones that make the country run: customs brokers, freight forwarders, equipment dealers, regional banks, manufacturers. They have systems older than their newest hires and stories about the consultant who promised a rewrite in 2017.
Those stories are why we're careful. A migration that breaks billing for an afternoon is not a war story. It is a fireable offense at the customer's company. We design every engagement so that nobody has to call their boss on a Saturday.
What that looks like in practice is unfashionable. We staff small senior teams. We refuse fixed-price contracts longer than twelve weeks. We keep the old system running until the new one has earned its keep. We write down what we don't know.
It also means we say no. We say no to greenfield rebuilds that should be incremental. We say no to retainers that don't have a deliverable. We say no to “AI strategy” that isn't tied to a workflow with a name.
We are not against ambition. We just think the most ambitious thing you can do with someone else's company is leave it more functional than you found it, and then leave.
Every engagement is different, but the floor underneath them isn't. These have held for seven years, twelve verticals, and one minor fire.
The person typing into your codebase has been doing this for a decade. There is no offshore team behind the curtain, no junior pool you didn't agree to, no staff augmentation in trench coats. The proposal lists the people. The people are the people who show up.
We work in twelve-week slices with a fixed scope, a fixed fee, and a real deliverable at the end. After each slice you can renew, redirect, or part ways with everything in your possession. Our incentives stay aligned because the off-ramp is always one quarter away.
We almost never turn the old system off. We run new alongside old, ramp traffic in controlled steps, and keep a one-button rollback for as long as your team wants it. Big-bang cutovers are a category we don't sell. The boring switch is the safe switch.
Thirty-four operators, engineers, and designers. Most of them have built the kind of system you're reading this page from.
Spent eleven years rebuilding billing systems at a payments company most people have never heard of. Owns the migration playbook.
Customs broker's son. Built three trade-compliance systems before deciding the fourth one should exist as a company.
Came from a sixteen-year tour at a regional bank's core platform team. Has opinions about COBOL that she will share if asked.
Designs the dense interior screens nobody photographs for a portfolio. Previously at a logistics platform you've shipped through.
Distributed systems by training, integrations by trade. Holds the record for fastest ACE certification in the studio.
Started in scientific computing, ended in supply chain. Will explain why the two are more similar than they should be.
The person who reads the contract before you do. Twelve years running PMO at a customs broker, escaped intact.
Made the spreadsheet you use into the application you use. Likes typography, dislikes pie charts, tolerates Figma.
The honest version, including the parts where we got it wrong.
We are not remote-first or office-first. We are this team, in these rooms, on the days it matters.
The books we keep on the shelf, and the things we'd argue about over the kettle.
We hire slowly because we keep people for a long time. If you're reading this far, you already understand the studio.