For most of software’s history, “enterprise-grade” and “one person” were mutually exclusive. Multi-tenancy, audit logs, encrypted backups, billing, compliance — that was a roadmap for a team of fifteen and a year of runway. So solo developers built toys, and enterprises bought bloat.
That trade-off is dead. I ship software alone that a mid-sized team used to ship, and I don’t cut the corners that matter. Not because I work harder — because I work with a system. This is that system.
1. If you can’t measure how you ship, you’re not engineering — you’re gambling
The first thing I built for my own company wasn’t a feature. It was a scoreboard.
I measure my delivery with the four DORA keys — deployment frequency, lead time for changes, change-failure rate, and time to restore — and I publish them live, in public, on my own site. Not because a customer asked. Because a solo builder’s greatest enemy isn’t a competitor; it’s the slow, invisible rot of a codebase that gets harder to change until one day you can’t ship at all.
DORA is the early-warning system. When lead time creeps up, something in my process is decaying and I fix it now, while it’s cheap. When change-failure rate spikes, I’m going too fast for my safety nets and I add one. As a team of one, I don’t have a QA department to catch me — so the metrics are the department. Publishing them keeps me honest: it’s very hard to fool yourself about your engineering effectiveness when the numbers are on a URL anyone can open.
2. Enterprise-ready is a posture, not a phase
The most expensive mistake in solo software is “we’ll add security and multi-tenancy later.” Later is a rewrite. Later is the moment your first real customer walks because you can’t isolate their data.
So I start there. When I build a product like Desk & Park — workplace and parking booking for hybrid offices — the first commit already assumes:
- Multi-tenant with hard data isolation. Every customer is a separate tenant, and one company’s numbers can never leak into another’s.
- Role-based access, 2FA, a full audit log, and nightly encrypted backups with reversible restore — from the beginning, not as a “security sprint” bolted on before a big deal.
- Self-serve and self-hosted. A free tier so a small team can start in minutes, and an enterprise deployment they can run in their own infrastructure. Same core, no forked “enterprise edition.”
This sounds like more work up front. It’s actually less. Retrofitting isolation into a single-tenant app is agony; designing for it from line one is a decision, not a project. Enterprise-readiness isn’t a feature you add — it’s a shape you keep.
3. Ship business value, not features
A feature list is what you build. Business value is why anyone pays. As a solo founder, I can’t afford to confuse the two, so every capability has to earn its place by answering: what does this unlock for the customer’s business?
Desk & Park doesn’t sell “desk booking.” It sells utilization you can actually plan around — reclaiming the space no-shows waste, showing cost-per-seat, turning a half-empty office into a lease decision backed by data. The floor map is a feature. “Right-size your real estate without guessing” is the value.
The pricing follows the same logic: a genuinely free plan to remove every reason not to start, transparent tiers that scale with the team, and a custom enterprise path for the ones who outgrow them. Adoption first, revenue as trust compounds. You enable the customer’s potential, and your business becomes a share of the value you created — not a toll you extract.
4. Build for the planet, and prove it
Sustainability in software is usually a slogan on an “About” page. I think it should be a feature with a number next to it.
Desk & Park ships Eco-Sync: occupancy-reactive HVAC. Zones nobody booked don’t get heated or cooled, and the board report shows the kWh saved and the CO₂ avoided — a line item, not a vibe. Because the platform already knows who’s in the building and where, saving energy isn’t a separate green initiative; it falls out of the data the product already has.
That’s the pattern I look for: sustainability that’s structural, not performative. Lean infrastructure that idles cheaply instead of burning idle cycles. Software that helps a company use less of the physical world — fewer square metres heated, fewer floors lit, fewer cars circling for parking. If a product can make its customer measurably greener as a side effect of doing its actual job, that’s real. Everything else is marketing.
5. Agile is a rhythm, not a ceremony
I don’t run stand-ups with myself. But I am relentlessly agile in the only sense that matters: small batches, fast feedback, and the willingness to change direction on evidence.
Solo agile means shipping the smallest thing a real user can react to, then letting reality — and the DORA numbers — decide what’s next. No quarter-long roadmaps defended out of pride. No big-bang releases hiding a hundred untested changes. The discipline a team gets from process, I get from constraints: if I can’t hold it in my head, it’s too big, so I make it smaller. Small changes are safe changes, and safe changes are fast changes. That’s the whole loop.
6. The bar doesn’t move because the team is small
Here’s the part people get wrong about the one-person company: they assume it means lowering standards. It’s the opposite. With no one to blame and no one to hide behind, craft is survival.
Clean, DRY, professional-grade code isn’t vanity when you’re solo — it’s how you’ll still understand your own system in six months. Every abstraction I don’t duplicate is a bug I’ll never have to fix twice. Every shared component driven by one source of truth is a place where the marketing page can’t drift from what the product actually does. Quality is velocity when you’re the only one maintaining it.
What makes this possible now — genuinely, not aspirationally — is AI leverage. Modern AI agents let one disciplined engineer operate at the scope of a team without dropping the standard, because the standard is enforced by taste and tests, not headcount. It’s why I also build private, on-premise AI tooling: the same leverage that lets me ship enterprise software solo should belong to my customers too, on their own hardware, with their own data staying home.
The synthesis
None of these five ideas works alone. DORA without business focus is measuring the wrong thing precisely. Enterprise-readiness without craft is a fortress built on sand. Sustainability without real numbers is a sticker. Agile without discipline is just chaos with a nicer name.
Together, they’re a coherent way to build: measure what you ship, build for real businesses, respect the planet, move in small honest steps, and never lower the bar. A team of one, delivering high-class applications that stand next to anything a big shop makes — sometimes better, because there’s no one in the room defending the thing that stopped making sense.
The future of software isn’t only bigger teams. It’s smaller ones that refuse to act small.
#DORA #Enterprise #GreenSoftware #OneManShow #CleanCode #AI