Home › Roles

Roles we build

Ranked by where transformation happens first. Every role has a page with what it owns, the stack we train on, the cost vs. a U.S. hire and the profiles available now.

Every role we build, by family

Sales & Support
Solar & Energy Operations
AI & Digital Transformation

How to pick the right first role

Most teams choose wrong on the first hire, and the wrong choice is almost always the most visible pain rather than the most expensive one. The question worth asking is not "where does it hurt" but "which hours are my most expensive people spending on work that does not need them". That is usually not sales. In a growing installer it is coordination: job files, permit packages, supplier follow-up, scheduling. In a developer it is document control. In an industrial team it is data reconciliation.

A practical test: for one week, have your two most senior people log what they actually did in thirty-minute blocks. The role you need will be obvious by Thursday, and it will usually not be the one you were about to post.

The three families, and what they are for

Sales and revenue roles exist to stop leakage at the top of the funnel — leads that go cold, quotes that never get a second call. They pay back fastest and they are the easiest to measure, which is why teams start there. They are also the easiest to get wrong, because a sales hire on a broken process produces more activity and no more revenue.

Solar and project roles handle the execution paperwork: design and permitting, procurement, project coordination, back-office administration. These are the roles that raise throughput without raising headcount on the roof. The payback is slower to see and larger once it lands, because they remove a ceiling rather than adding a channel.

AI and data roles are for teams that have already fixed the first two layers. Automating a process you have not documented produces an automated mess. If your workflows still live in people's heads, hire the operations role first and the automation role second — in that order, six months apart.

What every role includes

Recruiting and vetting with a recorded interview you watch before choosing. Verified English level, tested rather than self-reported. Training on your stack before day one, not on your team's time. In-country employment, payroll, benefits and compliance carried by Kurios. Ongoing management and weekly check-ins through the first month. Free replacement if the person is wrong for the role, with the documentation and playbooks staying in your account so the next person does not start from zero.

What none of them include

Field work. Anything requiring a professional licence or a stamp. Anything requiring physical presence at a site or an inspection. These roles are office roles executed on your time zone, and any vendor blurring that line is describing a compliance problem you will inherit.

Before you pick a role

Three questions decide more than the job title does. Whether the work needs a person at all — we walk through that on automate it or hire for it. Whether you are buying capacity or an outcome, which is the difference between staff augmentation and outsourcing. And who legally employs the person, covered on how an employer of record works.

If the gap is on the revenue side rather than in operations, the two roles that come up most are a sales development rep in Latin America and someone to own revenue operations and the CRM. If it is the AI backlog, that is a nearshore AI automation team.

SEO · página actual
URLhttps://kurios.city/industries/ai-operations
Title
Nearshore teams for AI Operations | Kurios City (47 car.)
Meta
Industrial, energy and SaaS teams putting AI into the operation. Trained on your tools, on U.S. hours, live in about 21 days, free replacement. (143)
H1
Nearshore teams for AI Operations companies
KeywordAI operations team for industrial companies
Schema
Service + BreadcrumbList
Canonical
✓ self · lang=en · in sitemap