Every few months someone friendly — a client, another founder — asks the same question: so when are you going to scale this thing? The implication being that a small team is a stepping stone, an awkward phase between hobby and "real company."

We used to nod along and mumble something about the right hire at the right time. We don't anymore.

Small is a design choice

LusitanIO is a small team of experienced developers because we think a lot of the work we care about is done better that way. Not all work — some problems genuinely need thirty people. But the kind of thing we take on (an AI agent that owns one workflow, a marketing site for a focused offer, an operational system for a small clinic) doesn't get better with more hands. It gets different. Usually slower, more political, more expensive.

Staying small is not a stage we're passing through. It's the shape we want the work to take.

What we gave up

There are real trade-offs. We should be honest about them:

  • We can't take everything. If you need a thirty-person delivery org and a steering committee, we're the wrong call. We say so quickly.
  • We don't scale linearly. A few projects at once is fine; twenty would be a disaster. So we plan in cohorts and book ahead.
  • Everyone is load-bearing. We document obsessively for that reason — every project ships with runbooks and a 30-day support window, so the lights stay on no matter what.

What we kept

The upside is the part we won't trade. Direct contact with the people who hire us. The ability to change the design at 11pm because someone had a better idea. No internal politics, no margin pressure to ship something we don't believe in, no calendar full of standups about standups.

Most importantly: the freedom to say no. To projects that don't fit, to features that won't help, to the constant pull toward "more." A small studio is a way of staying close to the work — and to the people we're doing it for.

If you're considering it

A few things we'd tell our past selves:

  • Charge by the project, not the hour. Hours encourage you to fill them.
  • Write down what you don't do. It's the most useful page on your site.
  • Take time between projects. The work is better when you don't sprint into the next one.

That's it. No grand thesis — just a note for the file. More writing on the way.

If this resonates and you've got a project in mind, drop us a line.