Why nearshore works, and when it doesn't
Three benefits with sources you can check, the objections answered without spin, and a list of the situations where you should not hire us.
Three reasons, with sources you can check
Capacity you can actually get
The constraint in 2026 is not budget, it is people. 86% of U.S. solar employers report difficulty filling open positions, and 47% say hiring directors and supervisors is a significant hurdle. The industry is roughly 53,000 workers short of what the 2026 installation targets require. Kurios puts a trained person in the seat in 14–21 days; the U.S. average time to fill is 36–44 days, and 40–60 for technical roles.
A cost structure that lets you add roles
A $130k base salary becomes $180k–210k in year one once you add payroll tax, benefits, 401(k), PTO and recruiting fees. The nearshore equivalent runs 40–65% below that, all-in — $35,000 to $80,000 saved per person per year. The point is not the discount: it is that the third coordinator, the second permitting engineer and the analyst you keep deferring all become affordable at once.
The same working day, not a handoff
When it is 9:00 AM in New York it is 9:00 AM in Bogotá — and 7:30 PM in India, 10:00 PM in the Philippines. That is the difference between a teammate who joins the 8:30 stand-up and answers the AHJ portal the same afternoon, and a ticket queue you read the next morning. 60% of enterprise leaders rank same-time-zone work as very important, and it is the single reason most offshore back-office experiments fail.
What one role actually costs you
Pick the role. The U.S. side is fully loaded — salary, mandatory benefits and payroll taxes, tools, management overhead, recruiting and ramp.
- Salary$54,000
- Mandatory benefits & payroll taxes$19,182
- Social Security + Medicare, FUTA/SUTA, workers' comp, health insurance, 401(k), PTO
- Tools, management & recruiting$16,818
- AI licenceYou pay it
- If they don't work outYou start over
- One monthly fee$2,800
- Mandatory benefits & payroll taxes$0
- Handled in-country. None of it lands on your payroll.
- Recruiting, training, managementIncluded
- Claude or Codex licenceIncluded
- If they don't work outFree replacement
Example figures for a Appointment Setter. The U.S. side is fully loaded — what the role actually costs your company, not the salary line. Your real numbers come out of the first call.
The reasons people don't hire us
Each one starts with the part that is actually true.
Their English will not be good enough for my customers.
Colombia scores 480 on the EF English Proficiency Index — rank 76, "moderate", just below the global average of 488.
That is the national average and it is the wrong number to hire on. It describes 50 million people, not the people who work here.
Kurios hires from the top decile: every profile carries a CEFR level (C1/C2 for anything customer-facing) and a recorded interview you watch before you commit. You are not trusting a country statistic, you are listening to the person.
If phone clarity is the real worry, run the English Voice Coach mock interview on the candidate in your own industry vocabulary before the first call.
I have been burned by offshore before.
Most of those failures were structural, not personal.
The common pattern: a 10–13 hour gap, a vendor who supplied a body instead of a role, and no training on your actual workflow. The person was set up to fail.
Kurios defines what the role owns before sourcing anyone, trains them on your CRM, your tools and your AI stack, and keeps weekly check-ins through month one. A LATAM hire on your clock is a different model from a Manila night shift, not a cheaper version of it.
If it still does not work, we replace the person at no cost. That is the part we can actually guarantee — "zero risk" is not.
I cannot supervise someone I never see.
True — which is why the role has to be measurable before it is filled.
Every deployment starts with a process consultancy that defines what the role owns, what success looks like and which numbers are reported weekly. If a role cannot be described that way, it is not ready to be filled by anyone, remote or not.
You get output you can inspect: tickets closed, permits submitted, appointments booked, RFIs cleared — in your systems, not in a vendor dashboard.
My work is too technical and too jurisdiction-specific.
Partly true. Some of it cannot be handed over.
A nearshore engineer will not stamp your plan set and will not replace your PE. What they do is prepare the package, run the AHJ portal, chase the revisions and keep the permit tracker current, so your licensed staff only reviews and signs.
AHJ knowledge is built, not bought: Kurios trains on your top jurisdictions during onboarding and maintains an internal playbook for them.
What happens to my customer data and my IP?
This is the objection that kills deals late, so handle it early.
NDA before any profile is shared, individual confidentiality agreements with every deployed person, access through your own systems with your own permissions, and no data stored on Kurios infrastructure.
You revoke access the same way you would for an employee: in your admin console, in one click.
Am I creating an employment or misclassification problem?
Not if the contracting structure is right, and you should ask to see it.
Kurios City LLC is a U.S. entity. You contract with the LLC for a service; the person is engaged in-country under local law, with payroll, taxes and benefits handled there. You are not their employer and you are not registering an entity abroad.
Ask for the contract and the in-country structure before signing. Any partner that hesitates on this question is the wrong partner.
They will leave in six months and I start over.
Attrition is real in this market. Nobody should promise it away.
What changes the odds: the person is paid a competitive local wage rather than the floor, they work on one account instead of being rotated, and they are trained into a career track rather than parked in a queue.
If someone does leave, replacement is on Kurios and the process documentation stays with you — so the next person starts from the playbook, not from zero.
Don't hire us if…
Six situations where Kurios is the wrong answer. Saying so early saves everyone a quarter.
- You need someone physically on site, on a roof or in a warehouse.
- You need a licensed PE stamp, an NABCEP certification or a U.S. electrical license.
- The role has never been documented and nobody has time to define it.
- You are shopping purely on hourly rate — there are cheaper vendors, and they will be cheaper for a reason.
- You need someone to start Monday. Real training takes 14–21 days.
- The work is under 10 hours a week; a fractional contractor fits better than a dedicated role.
Sources: U.S. Energy & Employment Report 2025 (86% hiring difficulty); IREC / pv magazine USA, April 2026 (53,000-worker gap); 2026 U.S. time-to-hire benchmarks (36–44 days); 2026 LATAM nearshore cost breakdowns (40–65% savings); 2026 U.S. SDR cost breakdown and AI engineer bases; U.S. employer burden 2026 (FICA 7.65%, FUTA/SUTA, health insurance USD 7,885 single coverage); EF English Proficiency Index 2025 (Colombia rank 76, score 480). Kurios figures are the company's own and indicative until a role is scoped.
The risks nobody puts on their website
Every nearshore vendor lists the benefits. These are the failure modes we have actually seen, because knowing them is what lets you avoid them.
Misclassification. A full-time contractor working your hours under your direction may be an employee under local law, whatever the contract says. Labour law in the region generally favours the worker, and the test is how the relationship operates in practice, not what the paperwork calls it. This is the risk U.S. companies underestimate most.
Scoping the role wrong. The most common cause of a failed placement is not the person. It is a role defined as "help with whatever comes up". A remote hire exposes an undocumented process faster than a local one, because there is no desk to lean over.
Buying on rate. Picking the cheapest option in the region usually means a weaker English level than the role needs, and you find out on the first customer call rather than in the interview.
Key-person risk. If one person builds the workflows and nobody documents them, you inherit a system nobody can maintain the day they leave.
Provider lock-in. Ask before signing whether the documentation, prompts and processes built during the engagement stay with you. If the answer is vague, the answer is no.
Where we stand on all five: employment sits with an in-country employer, so misclassification is not your exposure. We scope the role before sourcing anyone. English is tested and shown to you on video rather than claimed on a CV. And everything built during an engagement stays in your accounts.