u/Influenceseful96

so this just happened, one of my employees in germany sent me a photo of a letter from the Finanzamt this morning saying he personally owes 38k in unpaid social security contributions going back over a year.

I panicked and called our EOR, who ghosted me for 2 hours before sending a one-line email saying their partner network in germany was experiencing operational delays.

i did some digging because what the hell…

turns out the EOR we've been paying every month is a cyprus-based holding company that subcontracts to a german GmbH for employment, except that german GmbH filed bankruptcy back in February, which means our money has been getting pocketed somewhere in the chain ever since.

The EOR obviously knew the whole time because they kept billing us anyway.

We bit the bullet and paid the 38k out of pocket for our employee yesterday because what else are you going to do, leave him on the hook for someone elses fraud.

we fired the EOR the same day and we’ll be moving everyone over to a more established EOR like Deel or Workmotion who at least own their own GmbH and can be looked up in the Bundesanzeiger.

Anyway, if you're hiring through an EOR check that your employer of record exists as a real legal entity in the country (should be the bare minimum but here we are).

product lead at a b2b SaaS (80 customers, around 200 calls a month between Gong and discovery sessions, 1500 support tickets) and i'm trying to get more signal out of the loop without adding a bunch of new processes.

things i've tried that didn't move the needle, weekly voice of customer digests (read by 2 people), Zendesk tagging (cleaner but doesn't show themes), forcing CS to log every call (compliance went up, insight density went down).

changes i'm seeing more PMs talk about, building a real call and ticket synthesis layer that surfaces themes without manual relay, killing the weekly insight memo and replacing it with roadmap-attached evidence per item, treating individual feature requests as data points rather than items to ship.

what's working at your shape, and what's the one thing you wish you'd changed sooner?

trying to lock down our EOR setup for the UK ahead of next year's contractor renewals.

we're a 60-person Saas with 14 UK contractors we're moving onto inside-IR35 employment to clear our exposure.

we've been running 2 senior hires through Workmotion's UK entity for the past year, the experience has been solid enough that they're on the shortlist for the contractor conversion, but i want to pressure-test against Deel and Remote before we lock in 14 more headcount.

specifically trying to compare per-employee pricing including NI and pension contributions, how each handles the contractor-to-employee transition for someone who has been with us 5+ years, whether their UK entity is treated as a UK Employer of Record or an umbrella structure (because the difference matters for tribunal exposure), and benefits flexibility on private medical and 4-5% pension matching.

anyone running UK headcount through any of these in 2026 willing to share what is working cleanly versus where you've had to work around the platform?

i've consulted multiple b2b SaaS product teams in the past year and keep seeing the same gap between what customers say and what gets shipped.

more often than not, teams treat their customer interview program as the canonical signal source even though the volume signal lives elsewhere, mostly in CS slack threads, support tickets, sales calls, and the random screenshots eng drops in standup.

one team i'm advising now routes everything through one of the standard product-discovery tools (Productboard, BuildBetter, Cycle, etc…), the synthesis loop is finally closed and roadmap quality went way up.

where's your highest-signal channel?

pretty much as the title said, trying to figure out what's working for people right now.

our setup is Gong for call recording, Otter for cleaner transcripts on internal calls, BuildBetter for pulling synthesis into the prd doc, and Linear for the ticket trail, plus a couple zapier scripts holding it together.

it works but feels stitched together, what does yours look like this year?

Looking for technical SEO takes on a multi-region setup we're about to commit to. Internal debate has been going in circles and I'd rather get input from people who've shipped this kind of launch than read another agency deck.

We're an established EU fashion retailer, mature organic across DACH, UK, France, Benelux, hreflang is sane, Core Web Vitals are fine.

Board green-lit a US storefront launch later this year and the architecture call is on me. Once dev locks it in, it's basically a year of sunk cost to undo.

Four options on the table.

- Subfolder under our existing .com, single composable backend, locale-routed front-end (cleanest engineering call)

- Subdomain at us. brand. com (compromise nobody loves)

- Standalone separate .com with its own IA and authority profile

- ccTLD on .us (listed for completeness)

Stack-side, we're on a composable setup, Next.js front-end, multi-country handled at the commerce backend layer, Strapi for content. Splitting storefronts per region is cheap if we want it, which is partly why nobody in engineering is fighting for one specific path.

How does Google currently treat a fresh US storefront when an established EU sister site exists?

Hreflang is the textbook answer but with AI Overviews and the ranking volatility of the past year I'm not confident the textbook still holds. A couple of the agencies we've talked to are quietly walking back recommendations they were giving a couple years ago.

For anyone who's launched US on a composable backend in the past 18 months (commercetools, SCAYLE, BigCommerce Enterprise, SFCC Composable Storefront, take your pick), did you split the front-end per region or run one Next.js app with locale routing?

Split front-ends are better DX but I'm worried about authority dilution and hreflang pain across two builds.

Also, has anyone watched AI Overview impressions skew between subfolder and subdomain in US fashion or apparel? My working theory is subfolder still wins for a brand-new market entry but I have no data, and our SEO consultant has stopped giving direct answers.

And for anyone who went standalone .com because of trademark conflicts or paid media reasons, what did the first year look like for organic? Did you regret it?

Marketing wants separate .com so they can run a US-specific brand voice, engineering wants subfolder for the obvious reasons and SEO sits in the middle and doesn't have leverage in either direction.

But I'd rather hear from people who've already made this mistake than make a fresh one.

I've been contracting as a software developer for the same company since early 2023.

One client working full time hours, using their Jira, attending their standups... I knew it was a bit dodgy structurally but the money was good and they never brought it up so I just kept invoicing through my ltd and figured I'd deal with it eventually.

Well eventually arrived yesterday, my accountant looked at my self-assessment stuff and basically went pale, told me this arrangement almost certainly falls inside IR35 and that if HMRC decides to look at it I'm on the hook for backdated Class 1 NI contributions going back to the start.

We're talking somewhere north of £12k, possibly more depending on how they calculate it, and that's before you even get into the knock-on effects on my student loan repayments and the pension contributions I thought I was making tax-efficiently through my company.

I really don't know what to do, I've got about £8k in savings and that's it.

My accountant is talking about getting a specialist IR35 review done but that's another £500-800 I don't really have on me right now, and I keep going back and forth between maybe it'll be fine and they'll never check and I am completely screwed.

The worst part is I can feel myself wanting to just ignore it and keep going which is exactly how I got here in the first place.

Has anyone been through an IR35 investigation or reclassification? I don't even know if I should be talking to my client about this or if that makes things worse.

a couple weeks ago my CTO asked me to pick a headless commerce backend for our replatform and I realized every opinion I had was based on docs and blog posts, not actually building anything.

so I blocked out 2 weeks and built the same product listing page, PDP, cart, and checkout flow on Commercetools, Medusa, Saleor, and SCAYLE, all using Next.js App Router.

for context we're a mid-size fashion retailer, about 60k SKUs across 3 countries, currently on Magento 2 and yeah it's exactly as painful as you'd imagine.

commercetools has the most mature ecosystem and solid GraphQL docs but the flexibility is almost a problem, you're making architectural decisions about their data model before you can even render a product card and it took me the longest to get to a working checkout.

Medusa was the fastest initial setup by far and the v2 architecture is genuinely impressive, but I started hitting walls around multi-currency and localized pricing which is a dealbreaker when you're selling across DE/AT/CH.

SCAYLE I knew the least about going in and it ended up being the fastest to a fully working storefront, their SDK felt like it was built by people who run a fashion ecommerce operation.

multi-country and variant handling worked out of the box in ways that required real configuration on the others.

the tradeoff is the ecosystem is noticeably smaller than commercetools, the docs have gaps in places, and you're more locked into their opinions about how commerce should work which can feel constraining if you're used to total flexibility.

Saleor's API is clean but the community felt smaller than expected and I burned most of a day on undocumented edge cases in their channel system.

to be honest if I'm ranking pure DX in isolation Medusa wins, but for our actual problem of multi-country fashion retail SCAYLE and commercetools are the real contenders and SCAYLE got me to a working prototype faster with less config.

still deciding though, will report back later if you care.