How many meetings does a remote project need?

One a week is enough in most cases, thirty minutes, to decide. Progress is read in the deliveries and the written reports, not in meetings.

Which tools do you need?

Few: a code repository, a shared priority list, a messaging tool, a mockup tool such as Figma and video calls. The tool matters less than the rule: information only exists if it is written in the right place.

How do you approve work without being in the same room?

On a preview address, with your real content, from your phone and your computer. Feedback is recorded directly on the priority list.

GuidesRemote work

Running a remote digital project: the asynchronous method

By the Banzai Labs teamUpdated on November 11, 20262 min read

Why distance is not the problem

Projects that fail remotely fail for the same reasons as the others: fuzzy scope, spoken decisions, late approval. Distance only makes them visible sooner. A team that works well remotely simply works well.

Write decisions down

The basic rule: what is not written is not decided.

Every meeting ends with a five-line report: decisions, owners, dates.
Requests go through the priority list, not private messages.
Questions come with their context, so they can be answered without a call.

A good asynchronous message contains the question, what has already been looked at, the options and the one recommended. The answer is often a single word.

Deliver every week

The client does not judge a project on reports. They judge it on what they can open.

1A permanent preview addressUpdated at every delivery.
2A short noteWhat is new, what to test, what is waiting for a decision.
3A two-minute videoWhen a journey deserves to be shown.

It is the same principle as in our guide How to scope a digital project: visible deliveries, no staged demo.

Organising time zones

Situation	Organisation
Less than 3 hours apart	Almost shared days, nothing to adapt
3 to 7 hours apart	A fixed shared slot every day for decisions
More than 7 hours apart	A written handover at the end of the day, a weekly call

The gap has a benefit: a request sent in the evening can be delivered by the time you wake up. It requires complete requests, because a follow-up question costs a day.

Acceptance testing at a distance

The client tests on their own devices, not on a shared screen.
Each piece of feedback is one line: where, what was expected, what happens, a screenshot.
Feedback is sorted together once a week: fix now, later, or not at all.

Access and security

Remotely, access is handled cleanly from the start:

accounts (domain, hosting, stores, measurement) are created in the client’s name;
each team member has named, revocable access;
secrets never travel by chat;
the code lives in a repository the client owns.

What to keep live

Not everything goes through writing. We keep a call for the scoping workshop, for disagreements, and for moments when something is wrong. The rest moves better without interrupting anyone.

For the agency model that goes with this method, see the nomad agency.

Frequently asked questions

How many meetings does a remote project need?: One a week is enough in most cases, thirty minutes, to decide. Progress is read in the deliveries and the written reports, not in meetings.
Which tools do you need?: Few: a code repository, a shared priority list, a messaging tool, a mockup tool such as Figma and video calls. The tool matters less than the rule: information only exists if it is written in the right place.
How do you approve work without being in the same room?: On a preview address, with your real content, from your phone and your computer. Feedback is recorded directly on the priority list.