The product side of Bravo is largely based in the US, working closely with the client onsite. The development team has always been remote. Remote-remote, in our case, from Australia.
On paper, that distance could look inconvenient. In practice, the time difference has become one of the useful parts of how the team works. The US team spends the day with the product and the people using it. They can work through a new feature, make decisions and capture the detail while it is fresh. By the time Australia comes online, the development work is ready to move.
We use GitHub Issues and short planning documents to carry the context between the two teams. Not pages of documentation. Just enough to understand what we are building, why we are building it and the decisions that have already been made. Anything that needs a real conversation still gets one, but it's not daily standups, or hours-long backlog refinement.
Claude Code is central to our team. It works from the written plan and within the engineering rules we have already set. We review the output, test it and keep human controls around anything sensitive, particularly production data.
A recent feature, Amendment Quotes, is a good example. The original idea changed substantially during planning, before we had invested in building it. The new version went live behind a feature flag so we could test it safely in the real environment. An automated test picked up an edge case involving a declined amendment and a new one starting at the same time. We fixed it before the feature reached a user.
The product team could finish its day in the US, the development team could pick it up in Australia, and Bravo had close to continuous coverage without anyone working unreasonable hours. We expected the distance to be something we would need to manage. It has ended up giving the product a longer working day.