A collective, not an agency.

Most of us spent years inside the other kind of company — the kind that runs in a line. Someone sells the project, someone else scopes it, an engineer inherits a spec they didn’t write, a designer is handed it to decorate at the end, a marketer gets something finished and is told to move it. What we remember is how much intent leaked out at every seam. By the time a thing shipped, you often couldn’t say why half of it was the way it was.

code9 started as a quiet reaction to that. No office, no middle layer. We’re spread across Berlin, Dubai, Kuwait and Calicut, each of us deep in one thing — engineering, design, growth, the commercial side — and the same small group stays with a piece of work from the first line of code to the market it’s meant to win.

Someone is always accountable for a project. But the lead moves — whoever’s sharpest for the problem in front of us picks it up.

That’s less tidy than an org chart, and we’ve come to trust it more than one. A gnarly build decision falls to whoever has to live with it. A brand question goes to the person whose craft it genuinely is. Nobody performs expertise they don’t have, because someone here actually has it. The person steering can change by the afternoon; who’s answerable for the whole never does.

What it costs us

It doesn’t scale the way a headcount chart does, and we’ve stopped pretending we want it to. A collective this flat only works while everyone can still see everyone else’s work — so we keep the active list short and take on less than we’re asked to. Most weeks that feels like a limitation. On the good ones it feels like the entire point.