At around fifty headcount, the same three people keep showing up.
A controller running close, AP, AR, and audit prep alone. A head of people spending afternoons scheduling interviews instead of running a hiring plan. A general counsel redlining standard vendor MSAs because there is nobody else to hand them to.
Engineering got the headcount. The functions that keep the company running did not.
The nearshore industry has spent a decade solving exactly one side of that imbalance. Search "nearshore engineering team" and you will find more firms than you can shortlist. Search for an embedded staff accountant who runs your close cycle in your time zone, or a recruiter who lives inside your ATS, and the category goes quiet. Almost nobody has built a real practice around it.
We did. This post is about why the gap exists and what a nearshore business support team looks like when someone builds one properly.
“Everyone sells nearshore engineers. Nobody staffs the functions that keep the company running.
”
The wall at fifty headcount
Engineering headcount grows with the roadmap because leadership watches the roadmap. Back-office headcount grows by exception: someone escalates, twice, and the req still loses to the next engineer. So the pattern repeats in company after company:
- The controller is doing four jobs (close, AP, AR, audit prep), and each one gets a fraction of the attention it needs.
- The head of people is a team of one with three open reqs, so the strategic work (comp bands, a real hiring plan, onboarding that doesn't leak people) never starts.
- The GC keeps the work that needs a GC and also the work that doesn't, because first-pass contract review has to happen somewhere.
None of it registers as a crisis. It registers as slow closes, slipped offers, a contract queue nobody can see the bottom of. The company doesn't feel broken. It feels heavy.
Why nobody talks about it
Engineering is where the nearshore category started, where the demand was loudest, and where every firm's marketing went. Nobody built a category around the back office.
So when a COO goes looking for an embedded staff accountant, the options are a placement firm that collects a fee and walks away, a virtual assistant marketplace, or a back-office outsourcing vendor with a shared queue. Three models, and none of them puts a specific senior person inside your team, in your tools, on your cadence.
That absence is the gap. Not a talent gap. A model gap.
What a nearshore business support team actually is
The same operating model we run for embedded engineering, applied to the functions that hold a company together.
Concretely: your staff accountant logs into your QuickBooks or NetSuite the same morning as your US controller, runs the same close cycle, and reports through the same dashboards. Your HR coordinator lives inside the ATS and Workday alongside your head of people. Your paralegal sits in the matter-management tool and on the legal team's Slack.
The roles cover the whole back office: bookkeepers, staff accountants, FP&A analysts, AP/AR specialists, and controllers on the finance side. HR generalists, HR coordinators, and recruiters on the people side. Paralegals for legal. Ops coordinators, project managers, and data analysts for everything in between.
The structure is what makes it work:
- Full-time, one client. Your embedded specialist works for you and only you. Nobody rotates off your account to run another company's books.
- Managed by you, employed by us. Your controller manages the work, same as an internal hire. We employ each person directly in Costa Rica or Colombia and carry payroll, benefits, tax withholding, and labor compliance. You sign one services agreement and pay one monthly invoice per role.
- Priced like a hire, not a transaction. Per role, per month, the way you would budget internal headcount. Not per ticket, not per interaction.
- Your tools, not ours. QuickBooks, Xero, NetSuite, Sage, Workday, BambooHR, Greenhouse, Lever. Whatever your functions already run on. We don't bring a parallel stack.
What it is not
Two disclaimers, because the words matter here.
It is not a virtual assistant. A VA handles task-level work, part-time, as a generalist. An embedded staff accountant at SMASH is a CPA-track professional with five to ten years of experience, working your close full-time for years. Different talent, different model, different outcomes.
It is not back-office outsourcing. Outsourcing means handing a workflow to a shared vendor pool, billed per interaction, with people you never meet running your books or your HR queue. What we build is the inverse: a named person, embedded in your team, accountable to your manager. Not outsourcing. An extension of your team. The phrase was written for engineering. It applies to a finance pod without a single edit.
Why Costa Rica and Colombia
Business support roles at SMASH are staffed from Costa Rica and Colombia, specifically.
Costa Rica sits on Central Standard Time year-round. Colombia sits on Eastern Standard Time year-round. Your close calendar, your interview loops, and your contract queue run inside the US business day, with no overnight gap where the work goes to wait.
English fluency is the standard for every person we place, written as well as spoken. Financial commentary, HR documentation, and contract redlines read like they came from the desk next to yours, because operationally, they did.
How the engagement usually starts
Almost nobody calls us about business support first. Most clients meet SMASH through engineering or CX, prove the model with one or two roles, then look at the org chart again. Twelve months later the embedded team includes a staff accountant in QuickBooks next to the US controller, a recruiter inside the ATS, a paralegal supporting the GC.
One real version of that arc: a US services company started with a single embedded bookkeeper supporting an overworked controller. Three years later, the finance pod was five people, including FP&A and AP/AR, ran every monthly close, and carried the controller through two acquisitions.
1 → 5
One bookkeeper to a five-person finance pod in three years
That growth path says something about the gap itself. Nobody budgets for a "nearshore back office team." They budget for engineers, feel the relief, and then notice the controller is still underwater. Business support is how the partnership grows, because it is where the unstaffed work was hiding all along.
Where to start
Not with ten roles. With the one person carrying the most jobs.
If that's your controller, start with a staff accountant or an AP/AR specialist. If it's your head of people, start with an HR coordinator or a recruiter. If it's your GC, start with a paralegal. One embedded hire, in your tools, on your cadence, and let the results make the case for role two.
The full role list, tooling detail, and FAQ live on the business support page. If you'd rather talk it through, book a 30-minute call: we'll sketch the team we would build for you, which role to start with, and what each role costs per month. If embedded isn't the right answer for your back office, we'll say that too.