Follow the sun describes work moving between teams in different time zones so that it carries on while any one team sleeps. The name suggests something more elegant than it usually is. In practice it means one team finishes, writes down where things stand, and another team picks it up.
The gap between the promise and the reality is entirely down to that handover. Companies that get this right treat the written handover as the deliverable. Companies that get it wrong assume the model works by geography alone, and then discover their two teams have spent three months quietly redoing each other’s work.
The arithmetic, with real hours
Jakarta runs on UTC+7 and Indonesia does not observe daylight saving. The United States does, which means the gap shifts by an hour twice a year.
A conventional Jakarta workday of 9am to 6pm lands on 10pm to 7am US Eastern and 7pm to 4am US Pacific. The consequence is the whole reason the model works here: a standard Jakarta workday finishes between 6am and 7am US Eastern.
Work handed over at 6pm in New York gets a full nine hour day in Jakarta and is finished before anyone in America opens a laptop. Nobody worked unsocial hours. Their team simply came in.
If you also want some live overlap, a modest shift buys it without pushing anyone onto nights:
Jakarta 12:00 to 21:00 is 1am to 10am Eastern, giving one hour of live overlap with the US morning
Jakarta 13:00 to 22:00 is 2am to 11am Eastern, giving two hours
Jakarta 06:00 to 15:00 is 4pm to 1am Pacific, giving West Coast teams two hours at the end of their day
Put a US Eastern team on 9am to 6pm together with a Jakarta team on 12:00 to 21:00 and you get contiguous coverage from 1am to 6pm Eastern, seventeen hours, with a shared handover hour from 9am to 10am. The uncovered window is 6pm to 1am Eastern, which for most businesses is the cheapest window to leave open.
Be honest about the limits
With both sides on conventional hours there is no live overlap with the continental United States at all. None. A Jakarta 9 to 6 and a New York 9 to 6 do not touch.
This matters because the alternative that competes for the same budget, a nearshore team in Latin America, does overlap a US day directly. If what you need is constant synchronous availability, someone who can join any meeting at any time, nearshore is the better answer and it is worth saying so plainly.
What nearshore cannot do is cover your overnight without night shifts, or reach Asian business hours at all. The decision is really about whether you need live hours or covered hours.
What the model is good at
Support queues. First response time is the metric most support organisations are graded on, and for a single time zone team it is structurally capped. A ticket raised at 11pm sits until morning. With overnight coverage it gets worked in the hour. This is the clearest case and usually the first one companies move.
QA and release cycles. Your engineers push at 6pm. Overnight the Jakarta team runs regression, triages the bug queue and works through code review. At 9am it is done. You get two passes over the work per calendar day instead of one, which compounds across a quarter in a way that is hard to appreciate until you have had it.
Operations processing. Reconciliation, order processing, exception queues and reporting are asynchronous by nature. Yesterday’s transactions are closed before you open the books. There is almost no downside here; the work simply happens earlier.
Monitoring and alert response. Somebody awake, on a normal shift, beats paging an engineer at 3am. It is better for response times and considerably better for the engineer.
What it is bad at
Anything genuinely collaborative in real time. Design sessions, live pair programming, whiteboarding a new architecture. You can schedule these into an overlap window, but if your working culture depends on ad hoc synchronous conversation, an eleven hour gap will grind on you.
Work that needs a decision from someone in another time zone. If the Jakarta team hits an ambiguity at 2pm their time and cannot proceed without an answer, that is 3am in New York and the work stalls for six hours. Good handover discipline anticipates this by flagging likely decision points before the previous team logs off. Bad handover discipline discovers it every day.
Poorly specified work. Ambiguity that a colleague at the next desk would resolve in twenty seconds becomes a lost day. Follow the sun rewards teams that write things down and punishes teams that do not.
Making the handover work
The practices that separate the two outcomes, from what we see across client teams:
Write the handover as a note, not a status field. What was done, what was learned, what is blocked and what decision is needed. Two minutes of writing saves hours of guessing.
Flag decisions before you log off, not when you hit them. If there is any chance the other team will need an answer, leave the answer in advance or leave the alternatives.
Keep one shared source of truth for state. If the ticket, the board and the Slack thread disagree, the handover fails regardless of what anyone wrote.
Use the overlap window for questions rather than status updates. If you have an hour of live time, spending it reading out what is already written is a waste.
Rotate who writes the handover. It stops the practice from decaying into a formality performed by whoever cares least.
Who is actually covering your overnight
Coverage only pays off if the person covering it can resolve things. An overnight shift staffed by someone trained to a script clears the easy tickets and escalates the rest into your morning, which leaves you roughly where you started.
So the hiring bar matters more here than almost anywhere. A conventional seat based operation staffs for cost per seat and trains to a script. We recruit the way a corporate employer does. The professionals we place hold degrees from Indonesia's top universities. Under the QS World University Rankings 2026 that means institutions like Universitas Indonesia at 189 globally, Universitas Gadjah Mada at 224 and Institut Teknologi Bandung at 255, with 26 Indonesian universities ranked overall. They average six years of professional experience, most of it inside multinationals and global agencies, and they range from individual contributors through team leads to managers.
That is the difference between an overnight pass that genuinely moves work forward and one that just sorts your queue. It is also why we can staff the overnight with people who make judgment calls rather than waiting eight hours for yours.
Why we do not use night shifts
We are asked about this regularly, so it is worth explaining the reasoning rather than just declining.
Getting a full US business day of live overlap would require Jakarta staff working 20:00 to 05:00 or 22:00 to 07:00. That is achievable and other providers offer it. We do not, for one reason: night rotas are where offshore teams churn.
Retention is the entire economic case for an offshore team. A support engineer at eighteen months resolves tickets several times faster than one at three months. An engineer who has been in your codebase two years is worth several who arrived last quarter. Every departure resets that, and night shift attrition guarantees departures.
Twelve-month retention across MixWork placements runs above 90%, and protecting it is worth more to our clients than the two extra hours of overlap a night rota would buy. We would rather build the coverage out of ordinary working hours and put the effort into handover discipline instead.
What it costs
MixWork places permanent full time employees on compliant Indonesian contracts, from USD 249 per employee per month for employment, payroll, HR and Total Care 360, with recruitment from 10% of first year salary charged on success. Salary is separate and depends on the role.
Where to start
Pick the function where the overnight gap costs you most. For most companies that is the support queue, because the cost is visible in first response time and customers feel it directly. Prove the handover discipline there, then extend it.
It is also a different arrangement from a contractor, freelancer or virtual assistant. Those give you someone splitting attention across several clients, with no continuity when they move on. Ours are permanent employees dedicated to your business, which is what produces twelve-month retention above 90%.
Worth a benchmark, because "attrition" on its own is just a word. The US Bureau of Labor Statistics recorded voluntary quits across professional and business services averaging 2.3% a month through 2025, which annualises to roughly 28% (JOLTS Table 22, accessed 16 August 2026). Retention above 90% over twelve months is under 10%. The gap between those two numbers is what a night rota puts at risk.
