A deal pipeline across two markets
Property acquisition and disposition for HW Legacy Group across the UK and the US, where the same pipeline has to behave differently depending on which side of the Atlantic the asset sits.
Client: HW Legacy Group.
A deal pipeline looks generic until it crosses a border. Then the stages stop matching: what a UK acquisition calls an offer, a US one calls something else and times differently, and the compliance obligations attached to each stage are not the same obligations.
The wrong fix is two applications. The other wrong fix is one application with a country flag and a forest of conditionals inside every screen. What works is one pipeline whose stages are configuration rather than code, so a market is a set of stage definitions and rules rather than a branch in a function.
This is the same instinct as the content engine and the brand configuration: put the thing that varies in data, keep the thing that does not in code, and you can add the next market without reopening the machine.