u/AriaMoon286

so most of the sub energy lately has been about replacing Slack with Rocket Chat, Notion with Appflowy, AWS with Hetzner… which is good but the European company structure underneath is much less European than the software stack suggests.

we mostly pay our people through contractor agreements that dont quite match how the work happens day to day, and most of those contractors are sitting in european countries with rules that have tightened a lot since covid.

Saw this article today on this and the numbers are kind of brutal, Ponemon found non-compliance costs are 2.71x compliance costs, national employment law project pegs misclassification at 10-30% of employers, and the Workmotion CFO quoted in the article puts exposure at 6-figure fines to multimillion euro liabilities in some jurisdictions which is real series A money.

meanwhile the whole europe-first push gets undermined the moment your finance team realizes they have 8 long-term contractors in 4 countries with no entity setup, and one of them is sitting on slack with your company email signature looking like an employee from the outside.

doesn't matter that the contract calls them a contractor, the relationship is what gets audited, and HMRC or whichever local tax body doesnt care about your contract semantics.

Setting up entities everywhere is slow and capital-heavy, but EOR shifts you onto another companys payroll infrastructure and you get classification rigor by default which is why Deel built a big business out of it from the US side and Workmotion plays the same game from Berlin with their own local entities instead of subcontracting to partners.

P.S. either way the piece is worth a read if your team has grown faster than the legal side has caught up.

head of people at a Series B in europe, we're across 4 countries at 28 people and i'm wondering what the team i don't have yet is going to wish i'd set up now.

things that bit us in year 1 i wouldn't recreate, running contractors in every country with no classification framework, vat registration drift, signing leases before we knew where talent concentrated, treating equity rules as the same everywhere when they aren't.

what i want to know is the next layer up, what did you not see coming until country 5 or 6 that you wish you'd built in at country 2?

was it a hire, a system, a vendor relationship, a contract template, or a piece of stack you didn't think you needed yet.

less interested in generic use-an-EOR answers, more interested in the specific call you got wrong twice and corrected the second time.

second weekend in a row monday morning i'm finding out a markdown we ran in our NL store leaked into FR for like 48h before anyone caught it.

So we sold full price stuff at AW discount across 60+ orders that now need a refund or at least an apology, and the worst bit is we still don't even know how it leaked because the inventory sync between our 4 country shopify plus stores is on a 30 min delay and lies to us half the time anyway.

we're a fashion DTC (8 people), started in DE and bolted on AT/NL/FR over the last year, and the longer we run this the more it feels like the platform is fighting us.

returns come back to country A and get marked restocked even when they're sitting in a totally different warehouse, our finance lead has a vat spreadsheet she now guards like nuclear codes because last time someone edited the wrong cell we had to refile in NL, and the gmv fee changes on plus mean we're paying 4x what we paid 2 years ago for ops that are slower than when we were half the size.

i'm starting to think plus just doesn't scale past this point for our shape and we should bail before another leak nukes a weekend.

if anyone here past 8m gmv in multi country fashion is running this without it being a fire drill every other weekend, please tell me what you're doing differently.

thanks.

i can pinpoint the meeting where we lost our biggest customer, even though we didn't know it at the time.

it was a quarterly review, the CRO was friendly, and his framing was that the product wasn't moving the needle the way it had before.

We did exactly what our discovery framework said to do, so we ran a round of deep customer interviews with the power users and the executive sponsor, synthesized the recordings into a clean roadmap doc, locked the sprints, and shipped a major redesign in time for their next QBR.

the launch hit on schedule, and the demo went well, our PM was proud of the team, but the contract did not renew, which took $480K of ARR off our books in one signature.

what killed me later was going back through the data and finding that the support ticket queue from that account had been screaming about a completely different problem the entire time.

every customer call had surfaced the polished version of their workflow because that's what people answer when you ask them what they need, but the real friction was a permissioning issue in their integration that broke every time they onboarded a new manager and forced their admins into a manual repair routine that nobody on our side had ever heard of…

And it was one of the top categories in their ticket history with zero mentions in any of the calls.

we changed how the product team read signal after that, customer recordings go through BuildBetter now and the support ticket queue overlays on the same theme set, and since then we've had 3 different accounts where a top ticket cluster turned out to be a renewal-grade issue that nobody had named in their roadmap calls.

what bothers me most is the same thing that probably bothers any product lead who has been through this.

we did everything we were trained to do, even the customer was articulate, the interview transcripts were good, the synthesis was clean, and the corpus we read from was the wrong corpus.

if you run a product team in b2b SaaS, take one of your top accounts, pull the support ticket distribution from the last 6 months, and compare it to the friction your customer interviews surfaced over the same window…

Because the gap between those two will tell you whether your discovery is hearing the right room.

i've watched 4 founders get burned by the same thing recently.

they hire EU contractors thinking they're saving money and don't realize local labor courts read employment relationships off behavior, regardless of what the contract says. the misclassification bill comes due in diligence or when the contractor leaves.

one i'm advising right now is unwinding 14 of these through one of the usual EOR providers (Deel, Workmotion, Remote) and cleanup is taking months.

when our head of product did a roadmap review, only 3 of the features we'd shipped traced back to anything in the interview library, while most traced to a slack channel called #cs-rage that our CS team had been venting in for years and nobody had thought to mine.

we built what i thought was a serious customer interview program at our b2b Saas, with a proper recruitment funnel, paid incentives, a research ops lead, and an annual budget that made our CFO wince.

we were doing a steady cadence of hour-long interviews and the synthesis docs were thick and footnoted.

we put BuildBetter in front of all of it, i still don't fully understand how it ties messy slack threads to features the eng team can scope, but the proportion has flipped, roughly 70% of recently shipped features now trace back to something the system surfaced on its own.

we're still doing the interviews because the depth helps with prioritization, but they're no longer where we discover what to build, and the org-political fallout of that has been the harder thing to work through.

the budget i fought hardest for last year is now our lowest-ROI line item in product.

We're scoping Italy and France for next year, the agency came back with 4-5 months per market and that felt high.

Every vendor keynote shows brands spinning up storefronts in weeks, sometimes days for smaller market additions, even when the timezone, currency, and tax complexity is real and the localization piece is hairier than the platform work itself, which doesn't add up.

What's the gap between marketing slide and reality and where does the time go for you (platform, agency, localization, internal sign-off)?

I want to write this out because I haven't been able to say it to anyone in my life and the weight of carrying it alone is starting to do something to me.

She was my first real boss when I was 24, ran a tight operations team at a Series C company in Frankfurt, and somewhere between the third and fourth year of working under her I learned almost everything I now use to run my own company.

How to read a P&L without panicking, how to have hard conversations without making them harder, how to walk into a room of investors and not flinch.

She was the first person who told me I had it in me to start something of my own, said it casually over coffee one afternoon like she was telling me about the weather.

When I finally did start the company 3 years later she was the first person I called (for a job this time). I asked her to come on as Chief of staff and I remember she paused on the phone for a long time before saying yes, and I think now she was already seeing something I wasn't.

The first year was truly magical, we hired our first 30 people together, closed our seed round together, and built a pride culture together. she still operated like she had at her old company, calm and exacting and impossible to rattle, and I leaned on that calm in ways I didn't even fully understand at the time.

then we closed our Series A and the company started moving faster than the systems she'd built were designed for so I started noticing things I didn't want to.

Decisions sitting on her desk for a couple weeks, meetings she'd stopped preparing for the way she used to, an edge of frustration in her tone with the new hires that hadn't been there before.

none of it was a crisis on its own but the pattern was there and I kept looking past it because she was the woman who'd taught me what patterns to look for.

The conversation that broke it open was with our VP of Engineering who came to my office one afternoon and said carefully, almost apologetically that he didn't think the ops function could keep up with where the company was going and that he wasn't sure she knew how to scale herself out of where she was.

I tried everything I could think of before going to the place I knew it was going.

Restructured her responsibilities, brought in someone to take operations off her plate, offered her the COO title with a narrower scope, she saw through all of it. The Tuesday I floated the COO restructure she looked at me across the table and said quietly that I'm trying to figure out how to get rid of her without saying it… and I couldn't even pretend she was wrong.

then I made the decision on a Sunday night at my kitchen counter and didn't even tell my partner about it.

we had closed our Series A 7 months earlier and the company hadn't slowed down for a single week, we were hiring across Lisbon and Dublin, payroll had gotten complicated enough that I'd handed the international side off to workmotion to manage.

our investors were asking for forecasts I didn't have time to build, and every Friday I sat across from the woman who taught me how to do all of this knowing exactly what I was about to do.

I asked her in on a Wednesday morning, she walked in already knowing, the way she always knew everything 5 minutes before everyone else did.

I started my script and got through half of the first sentence before I just stopped and said the words.

She didn't argue, nodded slowly and said "I've been waiting for you to be ready to have this conversation for about four months" then she stood up, walked around the desk, and hugged me, which destroyed me because I had been bracing for anger and got grace instead.

The last thing she said before she left was that she was proud of me for doing it and that it took her until 38 to learn how to make a call like that (I was 31 btw). her last message in our text thread is exactly three words: you did good

I built the company she taught me to imagine and I had to ask her to leave it…