What to expect in your first 90 days with a nearshore team

The pitch deck says nearshore development is “seamless.” It isn’t. It works, and it works well, but the first 90 days have a shape to them that nobody talks about on the sales call. Based on onboarding dozens of clients over the past 11 years, this is how that shape looks.

Week 1-2: The setup

This is logistics. Slack channels get created. ClickUp boards get set up. GitHub repos get shared. Zoom links get distributed. Someone figures out that your VPN blocks our IP range. Someone else realizes the staging environment credentials are in a Google Doc that nobody can find.

The boring, fiddly stuff. It matters more than people think. A bad setup week creates friction that lasts months. A good one establishes the rhythm everything else runs on.

What we do: we send a kickoff checklist before the first call. Tool access, repo access, design files, documentation, existing technical debt, known issues. The more we know before day one, the less time everyone wastes during it.

Expect this phase to take the full two weeks. Rushing it creates problems later.

Week 3-4: First sprint, first friction

The first sprint is always a little awkward. Your team has conventions that aren’t written down. Our developers follow them once they see them, but the first PR review will have comments like “we don’t do it that way” or “this file should be in a different directory.” That’s normal. It’s how the team learns each other’s standards.

This is also when communication patterns emerge. Some clients like a daily standup. Others prefer a Slack update and a weekly call. Some want detailed ticket descriptions. Others want a quick voice note. There’s no universal right answer. The goal of week 3-4 is to figure out what works for this specific team.

The friction in this phase is healthy. It means both sides are paying attention.

Month 2: Trust builds, speed increases

Somewhere in the second month, something shifts. The code reviews get faster because our developers have internalized your patterns. The Slack messages get shorter because context is shared. Someone makes a joke in the standup. That’s when you know it’s working.

This is also when the first real disagreement happens. Maybe we think a feature should be built differently than the spec says. Maybe there’s a technical debt issue we want to flag before it gets worse. How both sides handle this first disagreement sets the tone for the rest of the relationship.

Our approach: we raise it directly, explain our reasoning, and defer to you on the final call. It’s your product. But if we see a problem and don’t say anything, we’re not doing our job.

Month 3: They stop being “the nearshore team”

By month three, the distinction between “your team” and “our team” starts to blur. Our developers are in the same sprint board, the same Slack threads, the same code review cycle. Someone on your side asks a question and our developer answers it before you do. That’s the moment.

Not every engagement gets here in exactly 90 days. Complex codebases take longer. Simple ones are faster. But this is the general arc.

Common stumbles and how to avoid them

Underestimating the setup phase. Don’t try to ship code in week one. Invest in the setup and you’ll get it back in month two.

No designated point of contact. If three people on your side are giving direction to our developers, nobody knows whose feedback to prioritize. Pick one person. Even if others contribute, one person makes the call.

Expecting immediate full velocity. A new developer, whether nearshore or in-house, needs ramp-up time. Sprint one output will be lower than sprint four. Plan for it.

Skipping the first retrospective. After sprint two or three, do a retro. Not the “what went well / what didn’t” template. An honest conversation about what’s working and what’s annoying. This is where small fixes prevent big problems.

Is it worth it?

I’m biased, obviously. But the data is on our side: most of our client engagements that survive month three become multi-year relationships. The 90-day arc is real, and it’s a small investment relative to what comes after.

If you’re considering nearshore for the first time and want to understand what the first quarter looks like with a specific team, not a pitch deck, we’re happy to walk you through it.