u/Castieell99

Ma belle-mère a 62 ans, elle vit à Wazemmes depuis 40 ans, et son médecin lui a mis de la vitamine D en ampoules il y a je sais pas combien de temps. Jamais mesuré avant, jamais mesuré depuis.

En en parlant à table dimanche on s'est rendu compte qu'on est 5 autour de la table à en prendre l'hiver, et zéro à avoir déjà vu un chiffre. On prend tous quelque chose sur la base de « on est dans le Nord, c'est logique ».

Ce qui est peut-être vrai. À notre latitude entre octobre et mars la peau produit quasiment rien. Sauf que ça dit pas si la dose que chacun prend est la bonne, et on prend pas tous la même.

Ma belle-mère est sur des ampoules Uvedose tous les 3 mois, mon beau-frère sur des gouttes tous les jours, et moi sur un truc que j'ai acheté en parapharmacie sans réfléchir.

Last year we had a roughly 45-minute window where the storefront started returning errors on add-to-cart, spent the rest of the BF midnight opening watching monitoring dashboards, and this year I want to fix the architecture.

Warming CDN caches in the week before BF means category pages and PLPs serve from edge on day one and stop hammering the origin, and adding read replicas with catalog queries routed through them separates the read load from the order-insert write load…

That's where SAP Commerce stacks tend to collapse under peak, with catalog reads and order writes competing for the same connection pool until the writes start losing.

Where I'm unsure is the third-party script situation, since we have around a dozen external JS tags firing on every page (analytics, consent, heatmapping, chat widget) and the conventional wisdom is to defer or remove them during peak windows.

But the business side wants the session recording data from BF specifically, so I'd be curious if anyone has won that negotiation with stakeholders.

The real question underneath all of this is whether BF prep on a monolithic stack is mostly window dressing at this scale, given we're spending weeks on infrastructure config to compensate for what is fundamentally a serialized architecture.

And a few teams in my circle have started landing on the same conclusion, with one that moved off SAP Commerce this year ending up on SCAYLE (came out of About You's retail stack, so the BF performance claim has operational history behind it) and another that went headless storefront on top of their existing OMS and said that alone changed the BF calculus more than any infra tweak had.

So what's worked for you all at this sort of volume?

We went through a full platform migration last year, and the total came in around 60% above the original business case, where almost none of the overrun came from the line items the vendor quoted.

The ERP integration was the biggest one, specifically the bidirectional sync for order management and inventory, which took double the estimated time because what the vendor called a pre-built connector was a starting point that still needed significant custom work on our side.

Data migration looked manageable until we got into the schema, but the real work was the schema mapping, not the data transfer itself, and that pulled in our internal dev team for longer than planned.

We're on SCAYLE now, and the 4-month integration runway we'd scoped became closer to 7, most of it going into the integration work and QA coverage.

The redirect management and structured data handling during the switchover also ran long, particularly in the weeks after go-live where search visibility was inconsistent in ways the implementation partner hadn't flagged.

Mostly writing this out because the honest breakdown didn't exist when we were building the business case, so what surprised your budget the most when you went through this?

We have 3 fashion brands on Adobe Commerce and the last year of signals from Adobe has been hard to read, with pricing moving upmarket and every renewal conversation tilting toward the full Experience Cloud stack over just the commerce piece on its own.

Not looking to replatform unless the trajectory is clear, but the contract cycle is close enough that waiting feels like a decision by default, and I'd rather understand what's happening before defaulting into another term.

For multi-brand retailers in Europe, is Adobe Commerce still worth betting on, or is the direction obvious enough that teams in this range are already moving?

Because the 2 paths that keep popping up in this sub are going composable with something like commercetools or SCAYLE, or staying and building a tighter Adobe Experience Cloud stack, and I'm not sure I'm even framing the choice right.

We're in the middle of building a business case for moving off a legacy monolith and every conversation we've had runs straight to licensing and implementation without touching the stuff that blows the budget once you're in the weeds.

ERP integration is the main one, particularly the bidirectional sync for order management and inventory where estimates have ranged from 6 weeks to 6 months depending on who you talk to, and every platform we're looking at (commercetools, SAP Commerce Cloud, SCAYLE, Spryker) has given us figures in wildly different ranges where the delta seems to come from how much of that integration layer is already built and how much is custom scope.

Data migration is a separate headache because our catalog is 4 years of accumulated schema decisions that don't map cleanly to anything off the shelf, and the QA coverage budget for a parallel-run period is listed as "TBD" in every proposal we get back.

That's about where our visibility runs out, so what hit your budget that wasn't in the original scope?

Spent the weekend trying to pull renewal date, health, and recent customer feedback into one view per account, and wanted to see how others had structured this.

Organizing the transcripts and tickets was most of the lift, so once that was done, ran everything through buildbetter for the per-account summaries and sentiment, then into a Notion board sorted by account, and even considered going fully custom with GPT, but the transcript pipeline wasn't worth maintaining.

Still not sure the GPT approach would've been worse, so what are you all using here, especially for voice of customer and usage data?

We're 8 hires in through an EOR across the UK and a couple of EU markets, and the per-head cost has started to feel off relative to what I was quoted when we signed because the number now has line items I wasn't expecting and no explanation of what they're for.

A friend of mine mentioned Workmotion as being transparent on how they structure fees, because they'd run into the same billing ambiguity with their previous provider and said the management fee is flat with nothing layered on top, so I've been wondering whether this is a billing-style problem that varies by provider or whether we're just getting a bad deal.

We're at the stage where EOR cost is a real budget line, so I'd rather understand what I'm comparing before committing to another year on the same contract.

So, what are you all paying per UK head and does the number still match what you were originally quoted?

We're 2 CSMs managing around 90 accounts and starting to question whether ChurnZero is still worth it.

ChurnZero runs our email plays and health scores fine, but the price went up again this cycle and we're barely touching most of what's in it.

What it never covered is the why, so we started running customer calls through BuildBetter, and it pulls the actual quotes when an account starts complaining about onboarding or a missing integration, which is the part I was doing manually.

Thinking of pairing that with a lighter CRM instead of renewing, so tested vitally which seemed decent, and custify which felt very mid-market.

If you've made a similar switch, what did you end up with?

We're 5 hires in through an EOR across Germany and the Netherlands, and what we're paying per hire is at the point where the question of setting up a direct entity in at least one of those markets has come up internally.

But I have no idea whether that crossover happens somewhere between 5 and 15 hires or depends entirely on the country.

Part of what makes it hard to compare is that we're not clear on what we're paying as EOR management fee versus what's employer contribution markup, and with our current provider those line items aren't clearly separated, so comparing against the cost of running direct payroll in Germany is basically guessing.

A founder I know had been on Deel before switching and mentioned Workmotion as having a cleaner cost breakdown, which is what made me wonder if the problem is the provider or just EOR pricing generally.

So, what's the cheapest EOR you've found for Europe-first hiring, and at what team size did EOR stop making sense for you?

The term “product intelligence” is vendor marketing, but the pain behind it is real for us since we're 8 PMs with feedback scattered across call recordings, support tickets, Slack threads, G2 reviews, and every sprint planning session turned into an argument about what customers wanted because there was no clean read across all of it.

Tried Productboard first since it's what most people we knew were running and the roadmap layer is solid, but it's built for structured input so it doesn't do much with transcripts or anything unstructured.

And Amplitude is a different job entirely since it's behavioral analytics rather than qualitative synthesis.

A few weeks into BuildBetter now, what got it adopted is that it starts from the call recordings, so it generates a doc per theme with the quotes behind it, and the PMs started pulling it into sprint review.

We're still in pilot, so if you've run this eval already, what's working for your team?

Killing our ZoomInfo renewal when it comes up in a couple of months, because the cost is impossible to justify for what we get, and the mobile match rate on tech titles is embarrassing.

Been doing a parallel test with Apollo as the base layer and FullEnrich on top for the numbers Apollo whiffs on, and the mobile coverage on engineering titles between 300 and 5000 headcount jumped noticeably, while the bill comes in nowhere near what ZI was charging us for the same volume.

Still testing deliverability on the emails, so i can't call that part yet.

What I'm still unsure about is whether Apollo + a waterfall provider covers enough of the account intelligence ZI was giving us (funding signals plus tech stack changes), or if I need to layer something like Crustdata or Ocean io on top for that.

So what's your setup, and how are you handling the account-level intelligence gap?

My boss slacked me a screenshot this afternoon with just a question mark under it, and I knew right away exactly what I'd done.

For context, I use one of those AI notetakers that sit in on your calls and email out a summary the moment you hang up, and a while back I turned on a setting to have it send that summary automatically to everyone on the invite, then forgot the setting even existed like an idiot.

So this morning we get on a call with a client who's been, to put it kindly, high-maintenance.

In the couple of minutes before they joined, my 2 coworkers and I were venting the way you do when you think it's just you…

One of us saying the account was going to churn anyway and another saying we'd padded the timeline because this client never approves anything on the first try, then they joined and we were perfectly pleasant to their face, had a totally normal call, and all hung up thinking everything was fine.

And the notetaker did what it was built to do, it recorded the whole call including those couple of minutes before the client joined, then turned the lot into a summary and emailed it to everyone on the invite, the client included.

I didn't find out until my boss's question mark landed, by which point the client had already replied to all of us asking, word for word, what "padded the timeline" was supposed to mean, with the whole BuildBetter summary quoted right there underneath.

My whole afternoon's gone to damage-control calls, the account's now 2 levels above me, and I've switched off every automation I own since, even a few that never did anything wrong, because I don't trust myself with a checkbox anymore.

The tool did nothing wrong, it did exactly what I set it up to do, and I'm the genius who armed it a year ago and walked away.

TL;DR: left auto-send on for my AI meeting notes, forgot about it, and it emailed a difficult client the 2 minutes of us trashing them right before they joined the call.

Fellas I've hit a wall and I'm thinking of giving up. not on the channel, but on filming myself every single day. that's the part that's burning me out slowly. I can write, I can generate great ideas, I just cannot keep setting up and recording five times a week. every time I try to post consistently it's the filming that makes me quit.

Been looking for a way around it and nothing feels clean. faceless voiceover and stock footage works but feels soulless and I'm still editing every clip anyway. the avatar route (heygen, synthesia, argil…) this turns your scripts into video with your own face so you skip filming, but people can tell it's an avatar if they look close, so I don't know if I'd run a whole channel on it.

Honestly the thing that got me is filming was never even the real problem. it's the 30 minutes of editing and captions after every video. the tools that just spit out a raw clip don't fix that, they fix the easy half.

So before I throw in the towel - how are you posting daily? filming and grinding the edit? faceless? avatar? and is the AI stuff worth it?

These days i keep most of my work thinking in Claude.
Mainly strategy docs, 1-on-1 prep, the occasional career vent, and a couple of weeks ago out of curiosity i exported 6 months of threads plus my meeting notes and clustered the whole pile to see what i spend my thinking on, expecting the categories to line up with the projects i'm working on.
Instead, the cleanest cluster that came back wasn't a topic at all, it was a habit, specifically the set of things i say i'm going to do in a meeting to sound aligned and then never do.
And there were something like a dozen of them across 6 months, the same 3 or 4 commitments rephrased and re-promised over and over, "i'll get you a doc on that," "let me own the follow-up", "i'll take that offline"…
None of which i actually did, and seeing them stacked in one place was worse than any performance review i've sat through.
For the mechanics, I ran it through BuildBetter, which is meant for clustering customer and call transcripts but works fine on any pile of text you hand it.
And the thing that stuck with me is that Claude was already the honest dataset the same way it is for a lot of people here, because it's the one place i write what i'm thinking and not performing it for a room.
So the promises i plan around in Claude are the real ones and the promises i make in meetings are the performance, and the gap between those two lists is basically the entire problem.
Anyway i haven't fully worked out what to do with it beyond the obvious of shutting up in meetings unless i mean it, but it's changed how i use Claude.
Less as the place i draft the aligned-sounding version of myself and more as the place i check whether i'd stand behind a thing before i say it out loud.
So anyone else clustered their own threads and found the pattern said more about you than about your work?

We're a UK company with contractors in Portugal, Poland, and Spain, and we're partway through moving most of them onto proper employment contracts.
It came down to a couple things really, an audit flagged us on misclassification risk while the contractors themselves had started asking for benefits and more stability. once we got into it the whole thing was messier than expected, and there's one piece i still want to sanity-check with people who've done this.
Every country draws the contractor/employee line differently, and almost all of them are stricter than the US, so misclassification is an easy trap to fall into.
For starters, Portugal has a subordination test that treats you as an employee past a certain threshold no matter what the contract says, Poland's social security body has been chasing IT contractors specifically, and Spain is about as harsh as it gets on false self-employment right now.
The exposure only grows the longer someone's been on a contract.
Sorting the mechanics took longer than deciding to do it, since you can't just reclassify someone on paper, so for each person we closed the contract cleanly, settled anything owed on IP or work in progress, then put a real employment offer in front of them.
We had no entities in any of the 3 countries obviously, so we ran the new contracts through an EOR instead.
We spread them across a couple of the bigger providers at first (Workmotion and Deel) i won't say which for which, then consolidated onto one, and the timing mattered a lot more than which provider we used, getting the switch right so we didn't reset their seniority for benefits.
A couple of things caught us off guard that our own prep had missed, the big one being retroactive benefits, since some countries make you backfill pension and benefit contributions once someone converts.
Portugal does exactly that on social security, so we negotiated a one-off settlement per person to close the gap and budgeted for it upfront.
The other was legal continuity, because if the termination and rehire aren't structured right the person can later claim they were an employee the whole time, which drags the liability backwards.
Our lawyer handled the wording, and having the EOR act as legal employer from day one of the new contract kept a clean line between the old setup and the new one.
Cheers if you read this far, and tell me how did you handle the retro-benefits settlements, per person or one policy across the board?

We're finalizing the employment contract for our first Porto-based hire (senior product designer) and the annual leave clause has become a back-and-forth with our EOR.
The initial draft they sent had 22 days annual leave, which matches the código do trabalho minimum for Portuguese employees. Our account manager at Workmotion said this is the standard for any full-time employee under portuguese law, whether onboarded directly or through an EOR.
That's what i expected, but our head of people flagged the follow-up question, which is whether the 22 days can be reduced to 20 for the first year of employment (the primeiro ano reduction some portuguese contracts include) or whether that's a myth that gets applied in bad-faith contracts.
The offer letter we already sent quoted 25 days annual leave to be competitive with our London team's 25-day standard, and the EOR is now asking whether we want the 3 extra days as contractual (permanent) or discretionary (year-by-year).
the read i got from both the EOR conversations and our portuguese lawyer is that the 22-day minimum is non-negotiable and the +3 days above the minimum are pretty common for tech roles.
our lawyer also flagged that structuring the extra days as contractual is the safer play because retracting them mid-contract triggers reduced-benefit challenges under portuguese labour law.
so if it were you, would you structure the extra 3 days above the 22-day floor as contractual or discretionary?

Our CSMs hear the same objections and questions over and over across accounts, but almost none of that signal makes it to the marketing team for positioning or campaign updates. It lives in slack messages, hallway conversations, and an Airtable someone on CS built last spring.
We're weighing two paths, either committing to a tool like BuildBetter, Vitally or Enterpret to cluster the CS conversations into themes we can pull messaging angles from, or accepting we need one person on the marketing side hand-tagging highlights in Notion or coda.
The tool options all promise auto-tagging, but i'm skeptical because our conversations mostly live on zoom and slack, and none of these tools plug in cleanly there. the hand-tagging option is the most boring but probably the most reliable path for our next positioning refresh.
so how are other B2B marketing teams pulling this off?