Small on purpose

Most software shops grow by adding layers. A salesperson to win the work, an account manager to hold the relationship, a project manager to shuttle messages, and, somewhere at the bottom of the stack, the people who actually write the code, who you never meet.

Every layer is a translation, and every translation loses something. By the time your problem reaches the person solving it, it's been through three retellings. By the time their solution reaches you, three more.

We build Qelo the other way round. The person who sits down to understand the job that's costing you hours is the same person who builds the thing that fixes it, and the same person who answers when you call six months later because something changed.

That keeps us small, and we'd rather be small and close to the work than large and abstracted from it. It means we take on less, because we'd rather do a handful of jobs properly than a hundred at arm's length, and it means we say no when a job isn't a fit, because we're the ones who'd have to live with saying yes.

If that sounds like the way you'd want your own work done, start a conversation. You'll be talking to the person who does it.