Field notes

A translated website tells a buyer you can afford a translator. It doesn’t tell them you understand their market. Those are different things, and buyers can tell the difference within a few seconds.

The signals they read are mostly not linguistic. Which customers you name. Whether the pricing is in their currency and their model. Whether the case study is from a company they’ve heard of. Whether the compliance page mentions the regulation they’re worried about. Whether the demo is booked through a tool they use and run by someone who knows what a Tuesday looks like in their industry.

A useful test: show your localized site to a buyer in the target market and ask them where the company is based. If they can tell, the localization isn’t finished. The goal isn’t to hide where you’re from. It’s to make it irrelevant to the decision.

The practical order of work is the reverse of what most companies do: fix the proof and the offer first, adapt the product and the funnel second, and translate last, when there’s something worth translating.

Three things, usually in this order.

First, that Europe is one market. It isn’t. A go-to-market that works in the UK will need real changes for Germany and more for France, and not just in language. Buying committees are structured differently, procurement expectations differ, and the proof that reassures one buyer is invisible to another. Pick a country. Win it. Then use it to open the next one.

Second, how slow trust is to build and how long it lasts once built. European buyers are cautious with new vendors, especially foreign ones, and especially in categories where switching is painful. The first sales cycle will be longer than you’re used to. The customer, once won, tends to stay longer too. Plan the cash and the patience for the first, and the retention motion for the second.

Third, that speed of product iteration is enough. It’s a real advantage. It doesn’t substitute for references, local support hours, data residency answers and a contract a European legal team will sign. Those are table stakes, and they’re usually missing from the first pitch.

An office is a conclusion, not a hypothesis. Before signing a lease, you want to know whether the buyers you think exist actually exist, whether they’ll talk to you, and whether they’ll pay. All three can be tested in weeks from where you are now.

Start with twenty conversations. Not surveys: real calls with people who match the profile you’d sell to. Ask about the problem, the current solution, the budget, and who would need to agree. You’ll learn more from these than from any report.

Then run a small outbound test. A defined segment, a localized message, a modest volume, a fixed period. What you’re measuring is whether anyone replies, and what they say when they do. Reply rates and objections are a market talking to you.

If those two produce signal, run a pilot with two or three of the interested accounts, with someone local representing you. Now you know what an office would actually be for, and you can hire into that rather than hoping to discover it after the fact.

Usually not, and the reason is simpler than it sounds. A sales team needs something to sell in a way that works. Before regional fit, you don’t know what that is yet: the segment, the message, the price and the proof are all still moving. Hiring salespeople into that is expensive learning.

What you want in the early phase is a small, flexible team whose job is partly to sell and mostly to learn. Fractional representation, an outbound engine you can retune weekly, and a founder or senior person from home who takes the important calls. The goal is to find the repeatable motion.

Once you have it, hire. You’ll write a better job description, you’ll onboard faster, and the first hires will inherit pipeline instead of building it from zero. The order matters more than the speed.