"Regional" is usually the last column in a product plan — the localisation pass, the translated strings, the currency formatter. We think it is the first column, and we have the scar tissue to explain why.
One: the payout schedule
Our first payout system ran monthly, on the first, because that is what every reference implementation does. It took a quarter to understand that a monthly cycle is a serious hardship for a creator whose costs are daily and whose other income is daily.
Weekly payouts were not a localisation feature. They changed who could afford to be a creator at all, which changed the catalogue, which changed retention. The translated version of the monthly system would have been perfectly translated and perfectly wrong.
Two: the onboarding flow
We asked for an email address first, because that is the shape of every sign-up form. Most of our creators do not lead with email; they lead with a phone number, and a meaningful fraction share a device.
Every form field is an assumption about who is on the other side of it.
Reordering two fields moved completion by more than any copy change we have ever run.
Three: the video encoder
We tuned the ladder for the connection quality we had in the office. Our median viewer is on a connection roughly a third of that, in a building with concrete walls, at seven in the evening when everyone else is also watching.
The fix was not a better encoder. It was moving the bottom rung of the ladder much lower and accepting that the floor matters more than the ceiling — which is a product decision dressed up as an infrastructure one.
What "regional first" actually means
It does not mean building a worse version for a poorer market. It means the constraints of the place are the design brief, not a filter applied afterwards. Every one of the three above was cheap to get right at the start and expensive to retrofit.
