The Remote Team
Starter Kit

A role brief is a 1-page document that tells your hiring partner — and your future VA — exactly what you need, how you work, and what success looks like. It's the single most important thing you can do before hiring remotely, and it takes about 15 minutes to complete.

Most founders skip this step or do it too vaguely. They write "Executive Assistant" and leave everything else to the recruiter to figure out. The result is a mismatch — a VA who's skilled but not the right fit for how this particular founder works, what tools they use, or what they actually need help with day to day.

Companies that submit detailed role briefs see 2.3x faster placements and 40% fewer first-placement mismatches. This template covers everything that matters: the role, hours, time zone requirements, top 5 recurring tasks, tools required, English level, reporting structure, and what success looks like at 30 and 90 days.

The first 30 days of a remote hire determine whether they become a long-term team member or a statistic. Companies that follow a structured onboarding process see 3x higher 12-month retention than those that send a welcome email and hope for the best.

This template breaks the first 30 days into four clear phases: Day 1 access and setup, a context call in the first 48 hours, shadow tasks in days 2–3, then independent ownership of recurring tasks by day 5. Weeks 2 and 3 establish the communication rhythm. Week 4 is the Day 30 review — a structured conversation, not a performance evaluation.

The Day 30 review guide included in this template is built around five specific questions that consistently surface the most important information: what's working, what's unclear, whether the original brief still reflects reality, what would make the VA's work easier, and what the goals are for the next 30 days. Most early-stage friction is a communication gap, not a performance problem — this conversation is how you find out.

Standard Operating Procedures are the single biggest factor in onboarding speed. VAs with documented SOPs are fully operational in 3–5 days. VAs without them typically take 2–3 weeks to reach the same level of autonomy — and many never fully get there because the process was never written down.

The most effective approach is to have your VA write their own SOPs as they learn each task, then review and approve them. This does two things: it catches gaps in your own process that you didn't realize existed, and it gives the VA ownership of how the work gets done. A VA who writes their own SOP is far more likely to follow it consistently than one who was handed a document on day one.

This template covers everything a good SOP needs: task name, frequency, tools, a step-by-step process, definition of done, common mistakes to avoid, and who to contact when stuck. Start with the three tasks your VA will do most in week one — don't try to document everything before they start, or you'll never finish.

One of the most common questions founders ask before their first LATAM hire is: "Will the tools work?" The short answer is yes — internet infrastructure in major LATAM cities (Bogotá, Buenos Aires, Mexico City, Lima) is reliable and fast. Fiber connectivity is standard in business districts, and all major SaaS tools work identically from LATAM as from a US office.

Every tool in this list has been validated across 500+ ThereIsTalent placements. The criteria were simple: reliable performance at variable internet speeds, minimal setup to reach full productivity, and support for both async and real-time collaboration. The list covers the four tool categories that matter most for remote teams: communication, task management, file and document management, and international payments.

If you already use tools in any of these categories, your VA can almost certainly work with what you have. This list is most useful for founders who are setting up a remote team from scratch and need a starting point.

The most common failure mode in remote team management isn't technical — it's rhythmic. Founders who have a strong first week with their new VA, then gradually let the check-ins slip, the syncs get cancelled, and the EOD updates stop. Three months later they feel disconnected from their VA and conclude the arrangement isn't working. The arrangement is fine. The rhythm broke.

This guide defines the three communication touchpoints that keep a remote VA engaged, informed and retained: a daily 5-minute async end-of-day update, a weekly 30-minute video sync, and a monthly 45–60 minute check-in that goes deeper than tasks. It also includes the EOD update template your VA will use every day — a simple three-part structure (done, blockers, plan for tomorrow) that replaces status meetings and creates a natural paper trail.

The data behind the monthly check-in is worth highlighting: LATAM VAs who had at least one career development conversation in their first 90 days had a 94% 12-month retention rate, compared to 71% for those who didn't. The monthly check-in is that conversation. It takes 45 minutes once a month.

This checklist is designed to be used three times: at Day 30, Day 60 and Day 90. It's not a performance review form — it's a conversation starter. The goal isn't to grade your VA, it's to surface small friction points before they become real problems.

Each milestone has a different focus. Day 30 is about foundations — does the VA have what they need to do the work? Day 60 is about momentum — are they proactive, or still waiting to be told what to do? Day 90 is about full integration — would you confidently introduce them as a core team member to a client or partner?

The most important insight from running hundreds of these reviews: almost every performance issue that surfaces at Day 90 had a visible signal at Day 30 or 60. The checklist is designed to catch those signals early, when they're still easy to address. A conversation about unclear expectations at Day 30 takes 15 minutes. Replacing a VA at month four takes weeks and costs thousands.