When a scale-up is asked to do more with the same, the first ideas are usually the hardest ones: freeze hiring, cut a team, restructure. Often there is a quieter option. Do not change the team you have. Change where the next seat goes.
The next opening is the decision
Every scale-up opens seats all the time:
- a backlog nobody reaches
- a specialist the team needs but cannot justify at local rates
- a replacement for someone who moved on
Each opening is a small decision about cost structure. Most companies make it by default: post locally, as always.
The alternative is to ask one question every time a seat opens: does this role need to be here?
Which seats travel well
Execution roles with clear output and good briefs:
| Role | Mid level, per month, all-inclusive |
|---|---|
| QA engineer | $2,200 to $3,200 |
| DevOps engineer | $2,800 to $4,200 |
| Data analyst | $2,200 to $3,200 |
| Customer support rep | $1,500 to $2,200 |
| Content writer | $1,500 to $2,200 |
Which seats stay
- leadership
- enterprise and in-person sales
- roles your customers expect in their language
- anything that needs someone in the room
The answer is role by role, never all or nothing.
Why capacity holds
The worry with any change like this is that output drops. It holds when three things are true:
- The person is dedicated to you. They work for one company, not split across clients.
- They work from a real office. A premium co-working office with IT support, not a spare room.
- Someone runs the employment. Payroll, compliance, equipment, reviews and exits are handled, so your managers manage work, not HR in another country.
A satellite office is built around those three. Each seat sits in the same office, employed by us, on one invoice.
Start with one seat
You do not need a plan for twenty people. Pick the next opening that fits, and place it in your satellite office.
- Grow when it works.
- Scale down with 30 days notice if it does not.
- Your team gets one seat bigger, and your overhead does not.
See the scale-up view on /scaleups, the scenarios on /use-cases, or talk to us.