The buyer in the first call has heard the pitch. "Not outsourcing, we're an extension of your team." They have heard it from Andela. From Toptal. From Turing. From three competitors with worse logos and the same deck.
By minute eight they're polite but skeptical. By minute twelve they're checking their phone.
We get this. We sound like the category we're trying to leave.
So let's do something different in this post: instead of telling you we're not a BPO, let me show you the four places where our operating model actually diverges, and why those divergences are what the leaders we work with care about.
1. Engineers are named. Not pooled.
A BPO sells you capacity. You buy "seats" or "agents" and the BPO rotates whoever's available against your queue. The agent who answered your ticket Tuesday may not be the one who answers Wednesday's. Their attrition is your continuity problem.
We sell you people. Specific senior engineers with names, roles, GitHub history, and a 1:1 with their manager every other week. If Diego is your backend lead, Diego is your backend lead in eighteen months. If he leaves (it happens), we know about it three months ahead and his replacement shadows him for two.
This isn't marketing. It's the line item structure on the invoice. BPOs bill capacity. We bill specific humans.
0
Shared agent pools. By design.
2. The engagement starts small and grows horizontally.
A BPO wants a 50-seat contract because that's how the unit economics work. The salesperson is pushing scale early because their commission depends on it.
We do the opposite. The first engagement we recommend is usually one senior engineer on a high-leverage problem. We want you to prove the model with the lowest-stakes possible bet. Three months in, if it works, you'll be the one asking us about role two.
The pattern we see: client starts with one engineer, reaches eight people within 12 months, twelve within 18 months. That growth is horizontal (engineering becomes CX becomes ops), not vertical inside a single function.
If we close you on a 50-seat contract on call one, neither of us trusts the integration. It's a worse business for us long-term. So we don't.
3. We handle payroll, equipment, training, retention. The whole employer stack.
This is the one most CTOs don't know to ask about until it's broken.
A "recruiting firm" places candidates and walks away. You pay the placement fee. The engineer is now your problem: your payroll, your equipment, your visa questions, your retention plan. The recruiter texts you in six months asking for the next req.
A "freelance marketplace" (Toptal, Upwork) takes a cut on every hour and doesn't employ anyone. The engineer is a contractor. They have no benefits, no retirement, no equipment provided. Their tenure depends entirely on whether your gig is the most lucrative one on offer that week.
We're neither. We're the employer of record. In Costa Rica that means:
- Local labor law compliance (CCSS, INS, aguinaldo, all of it)
- Equipment provisioning (we ship the laptop)
- Annual performance reviews with a US-style framework adapted to local context
- Local benefits + USD-denominated bonus structures
- A people manager who's seen the engineer's last three projects
You get the engineer. We get the operational complexity. The engineer gets a real career.
4. The exit is documented and humane.
BPO contracts have lock-in clauses, ramp-down penalties, and exit fees calibrated to make you stick around. Read the fine print on Andela / BairesDev / Concentrix and you'll find them.
Ours don't. The contract is monthly. If the engagement isn't working in month two, you can wind down in month three. We help you transition the work, including, if relevant, helping the engineer find their next role inside our portfolio.
The reason this works is the same reason we don't push 50-seat deals: if the easiest path out is short, you have to be honest about the work all the way through. That keeps both sides accountable. It's also why our average engagement length is 18+ months, not because we trapped anyone, but because the model holds up.
Why this category fight matters
Because the buyer's mental model decides the outcome of the engagement before week one.
If a CTO hires us as a BPO, they treat the engineers as fungible capacity. They don't onboard them into Slack. They don't put them on the on-call rotation. They don't invite them to roadmap planning. And then six months in they wonder why "the offshore team" isn't owning anything.
If a CTO hires us as an extension of their team, they treat the engineers like new hires. They put them through onboarding. They give them roadmap input. They run them on the same review process as the in-house team. And then six months in they tell us "I forget which of these people are SMASH and which are us."
Same engineers. Same model. Two different outcomes, entirely determined by which category the buyer mentally filed us under on day one.
So we'd rather lose the deal than win it under the wrong frame.
If "extension of your team" sounds like the right frame for what you're building, let's talk or book a 30-minute call. If it doesn't, we're probably not the right partner, and there's no shame in saying so.