Operations

Scaling a Spanish-Speaking Remote Team in ClickUp

I run a performance-marketing agency from Dallas with three people on the team and 13 client accounts. The team is mostly Spanish-speaking — Julián in Colombia handles automations, Javier handles day-to-day ops. The clients are mostly Spanish-speaking US operators. The system is ClickUp.

Here's how it actually works.

Rule 1: Every task is in Spanish

This sounds obvious. It isn't. Most American founders who hire offshore teams write tasks in English and expect their team to "deal with it." The team will deal with it — by spending 20% of their day translating instead of executing. Multiply that across a year and you've paid for a senior hire just to fight your own language preference.

Every task in our ClickUp is in Spanish. Names, descriptions, instructions, comments. The only exception is technical specs that have to match English-language tool documentation (Meta ad API field names, GHL custom field keys).

Rule 2: Every task has 4 things or it gets rejected

The standard, written into our team rules:

Tasks missing any of these four things bounce. No exceptions. We learned this the hard way after weeks of tasks sitting in "asking for clarification" purgatory.

Rule 3: Workspace structure mirrors actual operations

We have one Workspace, one Space per business unit, one Folder per major workflow. Lists inside folders are tied to ongoing processes:

Each client is a list inside the relevant folder. Their tasks roll up to a unified "weekly priorities" view that's filtered by assignee.

Rule 4: Daily standup happens in ClickUp, not Zoom

We don't do morning standup calls. Every morning by 9am Colombia time, each team member updates 3 tasks in the "Standup Diario" list:

  1. What I shipped yesterday
  2. What I'm shipping today
  3. What's blocking me (and who can unblock it)

Async, written, searchable. I read all three in 90 seconds while I'm having coffee. No meeting required. If a blocker needs a real conversation, we Slack it or jump on a 5-minute call. Total time spent on "standup" per week: less than 30 minutes for the whole team.

Rule 5: Automated alerts catch fires before humans do

We built a Standup Alerts automation that runs every morning and pings the team in ClickUp Chat if any of these things have happened:

By the time a client emails us about a problem, we already have a fix in motion. That's the difference between a 12-month-tenure agency and a 1.8-year-tenure agency.

Rule 6: Document SOPs in Loom + ClickUp Docs, not slide decks

Every recurring process has a Loom recording (15 min max) + a ClickUp Doc with the bullet-point checklist. No 40-slide decks that nobody reads. The Loom shows the screen. The Doc gives you the steps to copy.

When we hire someone new (rare — team's been stable for 18 months) they consume all the Looms in their first week and can ship work in their second.

Rule 7: Time-tracking on, but used as data, not surveillance

We track time on every billable task. Not to police people — to know what jobs are profitable. A client that demands 6 hours of weekly account management for a $3,500 retainer is not the same client as one that needs 1 hour.

Quarterly we review the data and decide: keep, repricing, or offboard. Three clients have been moved off this way. None of them were profitable.

Rule 8: The founder is the bottleneck — and the system is designed to remove me

The whole reason this team works is that nothing routine waits on me. Sales calls? Mine. Strategic creative direction? Mine. New client onboarding? Mine for the first call, then handed off. Everything else runs without me.

Tasks that come to me get tagged requiere-chris. If that tag count grows past 8 open tasks, the team Slacks me and we re-route the bottleneck. It's a forcing function to keep me out of execution.

What this enables

The numbers:

That's the system. It's not glamorous. There's no AI agent that "manages everything for you." It's the discipline of doing 8 ordinary things every day for 18 months.

Want this operating system in your agency?

The Embedded package includes coaching on the exact operations stack I just described — workspace setup, SOP documentation, alert automation, the works.

See the Packages →
Keep Reading

More on Operations