Skip to content

Building a remote-first team that ships weekly

Alex Reece · 1 min read · March 24, 2026

Building a remote-first team that ships weekly

NeuralPress is fully remote across twelve countries. Here’s what we’ve learned about shipping weekly without burning out.

Async writing first

Every decision lands in writing. Every project starts with a doc. Synchronous meetings are the exception, not the default. The cost is more time spent writing; the win is everyone in every timezone has the context.

Office hours, not meetings

Each leader holds 90 minutes of office hours per week. Open Zoom, drop in if you want. Most weeks the room is empty. Some weeks it’s full. Either is fine.

We replaced the weekly all-hands with a Friday written update. It takes an hour to write, fifteen minutes to read, and reaches everyone — including the people on PTO and the new hire who joins next month.

Defaults beat policy

We don’t have a remote-work policy. We have defaults. Default to async. Default to writing. Default to “this can wait until tomorrow.” Policies feel like rules; defaults feel like culture.

FILED UNDER Culture
SHARE
Alex Reece
WRITTEN BY

Alex Reece

NeuralPress · Culture

/ JOIN THE CONVERSATION

Leave a comment.

Add your thoughts

Your email won't be published. Required fields are marked with an asterisk.