A five-person remote team is not a small version of a fifty-person remote team. It is a different thing with different failure modes, and most of the advice written about remote work is written for the fifty-person version by people at companies with an HR function, an IT department, and a budget for offsites.
At five people, you have none of those. What you have is one person — usually the founder — who is doing the work, managing the team, and improvising the operating system in the gaps. The result is predictable: communication happens in whatever channel someone opened first, decisions live in DMs nobody else can see, and by month nine two people are quietly duplicating each other’s work while a third has not spoken in a meeting since March.
This article covers what actually holds a small remote team together. It is not about tools, though tools appear. It is about the small number of decisions that, made explicitly, remove most of the friction — and the ones that, left implicit, generate all of it.
Write Things Down, Because Nothing Else Scales Below Ten People
The default in a small remote team is that all context lives in one person’s head. This is the thing to fix first.
In an office, context leaks. People overhear, they see the whiteboard, they catch the tone of a conversation. Remote, none of that happens. If it is not written, it does not exist for anyone who was not in the call.
The habit that fixes most of this is unglamorous: decisions get written down, in a place everyone can find, on the day they are made. Not a document management strategy. A single file, or a channel, or a page, with entries that look like:
- Date. Decision. Why. Who decided. What changes as a result.
Four lines. Two minutes. The return is that six weeks later, when someone asks why the pricing for the Austrian market is different, the answer exists and nobody has to reconstruct it from memory or, worse, re-litigate it.
What to write, and what not to.
Write: decisions, the reasoning behind them, how recurring processes work, who owns what, what “done” means for the current work.
Do not write: meeting minutes nobody reads, status that a tool already shows, elaborate process documentation for things you do twice a year. Documentation that is not read is a cost with no benefit, and small teams generate it out of guilt.
Default to public channels, not DMs.
The rule that pays back fastest in small remote teams. A question answered in a DM helps one person. The same question answered in a shared channel helps everyone who reads it and everyone who searches for it later. It also removes the founder-as-router problem, where every piece of information passes through one person because that is the only place it has ever lived.
Make it explicit: work conversations happen in the open unless there is a specific reason otherwise. Personal, sensitive, and HR matters are the reason otherwise. Almost nothing else is.
Meetings — Fewer, Shorter, and With a Written Trail
The remote meeting problem is not too many meetings. It is meetings doing the job that writing should do.
A status meeting is a document read aloud slowly to people who could have read it in ninety seconds. It exists because writing the document feels like extra work and talking feels like free work. It is not free — it costs five people thirty minutes and produces no artefact.
The meeting set that a five-person team actually needs:
- One weekly team call, 30–45 minutes. Not status. Status goes in writing beforehand. The call is for the things that need argument: decisions with tradeoffs, problems where someone is stuck, disagreements that email would drag out for a week.
- One 1:1 per person per fortnight, 30 minutes. This is the one that gets cancelled and should not be. It is the only structured place where someone tells you they are unhappy before they resign.
- Ad-hoc calls, freely, short. Two people who need fifteen minutes should have fifteen minutes. The cost of an unscheduled two-person call is low; the cost of a Slack thread that could have been a call is a day and a half.
Rules that make them work:
- An agenda or it does not happen. Three bullets in the invite is an agenda.
- Someone writes the outcome within an hour. Decisions and owners. Not a transcript.
- No meeting to inform. If the purpose is to tell people something, write it. Meetings are for things that require the other person’s response in real time.
- Async by default across time zones. If your team spans more than three or four hours, a synchronous default silently makes one person’s life worse every single day. That person eventually leaves.
Measuring Output When You Cannot See Anyone Working
The instinct to monitor is the instinct to fail.
Every founder new to remote management has the same anxiety: how do I know they are working? It produces the same bad answers — activity monitoring, screenshot software, presence indicators, an unspoken expectation of instant Slack response. All of it corrodes trust, none of it measures anything useful, and the best people leave first because they have options.
The uncomfortable thing to sit with is that the anxiety is not really about whether they are working. It is about not knowing whether the work is any good, which is a management problem that exists in offices too and is merely hidden there by the visible appearance of effort.
What to do instead: define the work well enough that its completion is observable.
- Every piece of work has a written outcome and a date. Not “improve the onboarding.” Rather: “new customers receive the three onboarding emails automatically, live by the 14th.”
- Weekly written check-in from each person. Three lines: what I finished, what I am on, what is blocking me. Takes five minutes to write, replaces a meeting, creates a record. It is the same habit that makes a weekly ops routine for a solo operator work, applied to more than one person.
- Review the output, not the hours. If the work lands, on time, at quality, the number of hours is not your business. If it does not land, the conversation is about the work — which is a conversation you can actually have, unlike “you seemed offline on Tuesday.”
The signal that something is wrong is silence, not absence. A person who is struggling remotely goes quiet. They stop asking questions, their check-ins get vaguer, they contribute less in the weekly call. That pattern shows up two to four weeks before the work visibly slips. Watching for it is the actual job.
Hours are the wrong unit anyway. For a small team doing knowledge work, the variance in useful output per hour between a good week and a bad one is enormous. Measuring the input measures the thing you do not care about with high precision and the thing you do care about not at all.
The Employment Questions to Settle Before You Hire
Remote hiring across borders is a legal question dressed as a convenience.
The appealing version: hire whoever is best, wherever they are, pay them as a contractor, invoice monthly, done. The reality is that this arrangement is often not what it says it is, and the consequences land on the employer.
The issues to resolve before, not after:
- Contractor or employee? If you direct their hours, supply their equipment, they work only for you, and they are integrated into your team, most EU jurisdictions will treat them as an employee regardless of what the contract says. Misclassification is assessed on substance. Back taxes, social contributions, and penalties follow, and they follow the company.
- Which country’s law applies? Generally the country where the person habitually works, not where your company is registered. That country’s rules on notice periods, holiday entitlement, and termination apply to your German-registered company employing someone in Portugal.
- Permanent establishment risk. An employee working from another country can, in some circumstances, create a taxable presence for your company there. This is a real question with real cost, not a theoretical one, and it is worth an hour with an accountant before it is worth a year with a lawyer.
- Social security. Within the EU, coordination rules determine which country’s system applies. It is not automatically yours. The EU’s guidance on social security coordination is the starting reference.
- Data protection. If your team handles personal data, where it is processed and accessed matters under GDPR.
The practical route for a small company: either use an employer-of-record service for people outside your home jurisdiction — it costs a few hundred euros per person per month and removes the whole category of problem — or engage genuine contractors who have other clients, control their own hours, and invoice on their own terms. What does not work is calling someone a contractor while treating them as staff, which is the arrangement most small companies drift into by default. If you are structuring an EU-adjacent base for this, our note on Serbia as an EU-adjacent base for founders covers the company-side considerations.
The Culture Part, Without the Nonsense
A small remote team does not need culture programming. It needs three things that do not happen by accident.
- Non-work contact. Not mandatory fun. Fifteen minutes at the start of the weekly call where people talk about something that is not work. It sounds trivial and it is the difference between colleagues and a group of strangers sharing a task list. People who know each other slightly will ask each other for help. People who do not, will not — and the cost of that shows up as duplicated work and unspoken blockers.
- Visible appreciation, in public. Remote work removes almost every ambient signal that your work was noticed. In an office someone says “nice one” in passing. Remote, if it is not written, it did not happen. Say it in the channel, specifically, about the actual thing.
- One real-world meeting a year, if you can afford it. Two days, in one place. It is expensive and it is the highest-return money a distributed small team spends. Everything after it is easier — the shorthand, the willingness to say “I don’t understand,” the reading of tone in text. If the budget genuinely is not there, it is not there. But price it honestly against the cost of the misunderstanding it would have prevented.
What you do not need: a values document, a culture deck, virtual happy hours, or a Slack channel for pets. At five people, culture is what the founder actually does, observed daily by four people who are very good at spotting the gap between the stated thing and the real one.
The thing nobody says about small remote teams is that they are unusually revealing. An office absorbs a lot of managerial vagueness — unclear priorities get resolved by proximity, weak definitions of done get patched by someone noticing, a founder who has not decided something can defer it in a corridor conversation. Remote, none of that padding exists. Vague priorities produce visibly wrong work. Undefined ownership produces gaps.
Which means the fixes are mostly not remote-specific at all. Write decisions down. Say what done means. Meet for arguments and write for information. Judge the output. Settle the employment question before it settles you. Do those five things and remote works fine at this size — and if you are not doing them, remote did not break your team, it just stopped hiding what was already broken.
Sources: European Commission — EU social security coordination · European Commission — Data protection