A studio, not an agency.
Zeraio is two people. One software engineer, one business analyst and manager. We started in 2026 to build the software our clients can't buy off the shelf. We don't subcontract.
Zeraio started in 2026 with two people, one room, and a long list of bad spreadsheets we wanted to retire.
We met working at a freight company. One of us was writing scripts to glue a dispatch tool to an accounting tool to a customer portal. The other was running the ops team that suffered through it. We realised the gap, that small and medium businesses run on patchwork because the alternative is a six-figure enterprise contract, was a thing we could fill.
So we started Zeraio. Two people on purpose. We will hire when the work demands it, not before. Every project gets both founders at the table, from kickoff to ship.
The name comes from zero. A clean canvas, a blank slate. We meet you with no opinion about your stack, your team, or your industry, and we leave with software that fits exactly.
Six principles we actually use.
Not a wall poster. These are the things we will push back on you about during a project.
Ship every Friday
Staging gets deployed every Friday by 5pm, every week, from week one. If we cannot ship something, we tell you Monday.
One team, one room
No project manager between you and the people doing the work. You talk to the engineer and the lead, directly.
Boring beats clever
We pick Postgres over the new graph database. We pick server-rendered HTML over a single-page app, when we can.
Show, don't tell
No fifty-slide decks. We build clickable prototypes by week three, and you test them with your actual team.
Own your code
You own everything we build, on day one. Code, infra, docs, design files. We don't lock you in.
Calm to operate
We design the boring parts. The error states, the empty states, the migration scripts, with the same care as the dashboard.
Two people. For now.
Both founders work on every project. We will grow the team when the work demands it, with seniors only.
Writes the production code. Picks the stack. Owns delivery from spec to ship.
Sits with your team to write the spec. Owns scope, schedule, and the boring parts that make a project ship.