Career Stories

Three Continents, Four Offices, One Lesson

· Felix Lenhard

When the 360 Innovation Lab expanded to Warsaw — where we built a 120-developer code lab — I learned a lesson that reshaped how I think about business. The lesson was simple but expensive to learn: trust and contracts work differently depending on where you are.

I had spent years building my career by then. I had built frameworks, run strategy sessions, advised companies across industries. I thought I understood how business worked. What I actually understood was how business worked in Austria. The distance between those two things was about to become the most expensive education of my career.

360 Innovation Lab started in Graz. It expanded to Warsaw, then San Francisco, then back into the DACH region with a broader mandate. Four offices across three continents over several years. Each market taught me something specific. But the core lesson was always the same: in some cultures, you sign a contract and then begin to trust. In others, you trust first, and the contract is a formality.

Graz: Where Structure Is the Default

Graz is a city that runs on precision. The trams arrive on time. The Steuerberater expects your documents on the fifteenth. When you schedule a meeting for ten o’clock, people arrive at nine fifty-five. This is not a stereotype. It is the operating system of Styrian business culture, and when you have grown up inside it, you assume the rest of the world runs on the same clock.

360 Innovation Lab was born in this environment. Our processes reflected it: detailed project scopes, clear deliverables, milestone-based billing, meticulous documentation. Everything a consulting firm should have. We were good at what we did. Our clients in the Graz startup ecosystem trusted us because we delivered exactly what we promised, on time, within scope.

The problem was not the system. The system worked beautifully — in Austria. The problem was that I confused the local operating system with a universal truth. I assumed that if our structured approach worked in Graz, it would work anywhere. Structure, after all, is structure. Contracts are contracts. Deliverables are deliverables.

I was wrong in ways that cost real money and real relationships.

The Austrian approach gave us a foundation, though, and I do not want to dismiss it. The discipline of clear scoping, the habit of documenting everything, the expectation of punctuality and precision — these became our backbone. But a backbone is not a personality. And when you walk into a new market, personality matters more than process.

Warsaw: Where Trust Precedes Paper

Poland was our first expansion. The logic was sound: lower operational costs, a growing tech talent pool, EU membership for seamless operations, geographic proximity to Austria. On paper, it was a perfect strategic move. I wrote about the mechanics of exporting from Austria — the structural advantages are real. But what no spreadsheet captures is the cultural distance between how two EU countries actually do business.

Our first six months in Warsaw were a masterclass in misapplied assumptions. We showed up with contracts. Detailed ones. Multi-page agreements specifying every deliverable, every timeline, every contingency. Our Polish partners read them, nodded politely, and then proceeded to build the relationship as if the contract did not exist.

I was frustrated. We had agreed on terms. We had signatures. Why was everything still being negotiated informally over dinners and coffees?

Because in Polish business culture — particularly in the tech sector we were operating in — the contract is a backstop, not a blueprint. The real agreement lives in the relationship. You build rapport first. You share meals. You learn about someone’s family, their ambitions, their frustrations. Then, once trust is established, business flows naturally. The contract sits in a drawer and hopefully never needs to be referenced.

I learned this slowly and expensively. Our first two Polish hires quit within four months because we managed them like Austrian employees: clear KPIs, structured feedback cycles, formal performance reviews. They felt micromanaged. What they wanted was to be trusted with a problem and given space to solve it.

The third hire stayed. She stayed because by then I had started having lunch with the team instead of eating at my desk. She stayed because I stopped leading every meeting with an agenda and started leading with a question: what do you need from me this week? She stayed because I finally understood that in Warsaw, the relationship is not a means to productivity. The relationship is the productivity.

Within a year, our Warsaw office was outperforming Graz on several metrics. Not because the talent was better. Because the management approach matched the culture.

San Francisco: Where Speed Eats Everything

If Warsaw taught me that relationships precede contracts, San Francisco taught me that speed precedes everything.

I arrived in the Bay Area with what I thought was a fast-moving European consultancy. We shipped projects in weeks, not months. We prided ourselves on velocity. And then I sat in my first meeting with a San Francisco startup founder who told me, without irony, that a two-week turnaround was “way too slow.”

The clock runs differently in Silicon Valley. It is not that people are smarter or work harder. It is that the culture has internalized a specific belief: speed of iteration is the primary competitive advantage. A mediocre product shipped today beats a perfect product shipped next quarter. This is not just a slogan on the wall. It is how decisions are made, how resources are allocated, how people are evaluated.

Our Austrian instinct for precision collided with this at every turn. We wanted to scope properly. They wanted to start building. We wanted to define success criteria. They wanted to see a prototype. We wanted a signed agreement. They wanted a handshake and a Slack channel.

The adjustment was brutal. I had to learn to operate at a level of ambiguity that made my Austrian brain physically uncomfortable. Contracts were one page. Scopes were verbal. Pivots happened mid-project without formal change orders. I remember calling my co-founder in Graz after one particularly chaotic week and saying, “I think they’re all insane.” He laughed and said, “Or maybe they just know something we don’t.”

They did know something. They knew that in a market moving as fast as the Bay Area tech ecosystem, the cost of being slow exceeds the cost of being wrong. You can fix wrong. You cannot fix late. This was a genuine insight, not just cultural preference. And it forced me to separate the parts of our process that were genuinely valuable — quality control, clear communication, accountability — from the parts that were just Austrian habit dressed up as best practice.

What I brought back from San Francisco was a framework for deciding what to subtract. Not everything needed to be fast. But the things that could be fast should be fast. The two-week scoping process that added marginal value? Gone. The three-round approval cycle for minor deliverables? Gone. The hundred-page strategy document that nobody read past page twelve? Replaced with a one-page brief and a working session.

The Lesson That Kept Repeating

Here is what nobody tells you about international expansion. The hard part is not logistics. It is not legal structures, tax implications, or time zones. Those are solvable problems with known solutions. The hard part is recognizing that your way of doing business is not the way of doing business. It is a way. One of many. Shaped by the culture you grew up in, the market you learned in, the norms you absorbed without noticing.

In Graz, the relationship follows the contract. In Warsaw, the contract follows the relationship. In San Francisco, both follow the prototype.

Each of these approaches works. None of them is objectively superior. The mistake — and I made it repeatedly — is assuming that your local approach is the rational approach and everything else is a deviation from the norm.

When I worked with the 40+ startups at Startup Burgenland, I saw this pattern play out in miniature. Founders who adapted their sales approach to each customer’s culture closed deals. Founders who had one pitch, one contract template, and one follow-up sequence regardless of who they were talking to struggled. The product was the same. The adaptation was in the relationship layer.

This is not about being a chameleon. It is not about abandoning your values or your standards every time you cross a border. The quality expectations we built in Graz — the discipline that later produced a near-zero return rate at Vulpine Creations — those traveled with us everywhere. Quality is not cultural. But the way you build trust, the way you communicate expectations, the way you earn the right to do business with someone — that is cultural. And if you ignore it, no amount of quality will save you.

What Magic Taught Me About Reading Rooms

There is a parallel between international business and what I learned from magic performance. In magic, you learn very quickly that the same effect plays differently depending on the room. A close-up card routine that devastates a table of four will die in front of a crowd of two hundred. The material is identical. The context has changed. And the performer who refuses to adapt to the context — who insists on doing the same set regardless of the audience — is the performer who fails.

Business is the same. The “material” — your product, your service, your expertise — might be excellent. But if you present it the same way in every market, you are ignoring the room. You are performing for the audience you wish you had instead of the audience sitting in front of you.

In Warsaw, I learned to read the room by slowing down. In San Francisco, I learned to read it by speeding up. In both cases, the skill was the same: paying attention to what the people across the table actually needed, not what I assumed they needed based on where I came from.

The founders I work with now sometimes ask me whether they should expand internationally. My answer is always the same. Yes — but not because of market size or cost optimization or strategic positioning. Those matter, but they are not the real reason. The real reason is that operating in a different culture forces you to examine every assumption you have about how business works. It strips away the habits you mistook for principles. And what you are left with, once the cultural defaults are removed, is the actual core of what makes your business work.

That core, in my experience, always comes down to the same thing. Relationships. Not contracts, not processes, not frameworks. Relationships. Built differently in every market, but the foundation of everything everywhere.

Five Things I Would Tell Myself Before That First Flight to Warsaw

1. Your process is a product of your culture, not a product of logic. The things you do “because that is how business is done” are actually “how business is done here.” Question every default before exporting it.

2. Hire for cultural fluency, not just technical skill. Our best hires in every market were people who understood the local business culture intuitively. They saved us from mistakes that no amount of research could have prevented.

3. Relationships are not a soft skill. They are the skill. Every market we entered, the breakthrough came when we stopped trying to close deals and started trying to build genuine connections. The deals followed. They always followed.

4. Subtract your assumptions before you add new markets. Before expanding, audit what you believe about how business works. Write it down. Then test each belief against the new market. Most of them will not survive contact with reality. That is the point.

5. The lesson is always the same. Three continents, four offices, hundreds of clients. And the lesson that kept repeating, in every language, in every timezone, in every conference room and bar and late-night phone call: trust first. Everything else is paperwork.

international lessons

You might also like

career stories

Why I Wrote 6 Books (The Real Reason)

The real reason behind writing six books wasn't productivity. It was a strategic decision about leverage and legacy.

career stories

From Engineer to Entrepreneur: The Mindset Shift That Took Years

The transition from engineering thinking to entrepreneurial thinking took a decade. Here's what actually had to change.

career stories

What RHI Magnesita Taught Me About Enterprise Innovation

Working with a multinational industrial company showed me what enterprise innovation really requires — and it's not what you think.

career stories

The Pitch That Got Laughed Out of the Room

And why I'm glad it did. Some rejections are redirections.

Stay in the Loop

One Insight Per Week.

What I'm building, what's working, what's not — and frameworks you can use on Monday.