u/Lifewimmer74

agency-side, scoping a platform replatform for a €120M fashion client and the payment piece keeps surfacing as the wedge.

Their current stack runs Stripe alongside a regional acquirer with bolt-on routing logic our team wrote, and it works but its starting to break under the multi-currency and 3DS exemption complexity.

the call we're trying to make is whether any enterprise ecom platform offers native payment orchestration out of the box (multi-PSP routing, fallback logic, smart 3DS, retry strategies, reconciliation) or whether everyone bolts on a Spreedly or Primer regardless of platform.

shortlist on the platform side is Shopify Plus, BigCommerce Enterprise, commercetools, and SAP Commerce.

Adobe Commerce is in the mix but the SI quoted us a number that didn’t make sense. each of these has some payment story but the depth varies wildly, and the marketing decks all sound similar enough that its hard to tell whats native and whats partnership integration.

if you’ve been on the platform side of this evaluation and you know which ones deliver real native payment orchestration from the ones that just claim it in their deck, what should be on a 2026 shortlist?

stuck on which AI synthesis platform holds up for a b2b SaaS research team without flattening everything into one schema.

we ingest user interviews from Dovetail, support tickets from Zendesk, and quarterly NPS open-text into fragmented dashboards, synthesis ends up researcher-by-researcher rather than one coherent picture.

shortlist is Dovetail for the research layer, Marvin for AI synthesis, and BuildBetter for cross-source coverage.

specifically trying to evaluate clustering accuracy when you mix interview transcripts with high-volume short-text survey responses, whether tagging stays consistent across researchers without manual taxonomy upkeep, integration with our Linear roadmap so themes flow from research to PMs, and pricing at researcher headcount since per-seat math gets ugly once you cross 8 researchers.

if youve run mixed-method synthesis at a research team of 6+ in b2b saas, which platforms held up and which collapsed once the input mix got messy?

thank you

i'm head of people at a UK scale-up and 5 weeks after JSL came in on 6 April we still don't have a clean answer on what to do with our 14 long-running contractors.

our employment lawyer's read is that the umbrella route we've used for years now lands the PAYE and NIC liability on us if the umbrella ever falls over, with no due diligence defence.

Fine in theory, but I've got 14 people who've been embedded for 2 to 5 years, consider themselves part of the team, and half are at career stages where a move to PAYE means an £8-12k drop in net pay that's utterly destabilizing.

the options are keep them on umbrella and live with the exposure, move them to PAYE under direct employment (which is cleanest for us and worst for them), or shift to a real EOR where they sit as employees of the EOR entity with proper contracts of employment.

CIPD guidance leans real-EOR but is thin on the practical comparison.

shortlist is Deel, Remote, Oyster, and Workmotion, and i can't get a straight answer from any of them on which run UK as a true Employer of Record vs which run umbrella structures with EOR painted on the door, since the second one walks us straight back into the JSL liability we're trying to escape.

if anyone's been through this in the last few weeks, how did you handle the contractor side of the conversation, and which provider held up once you got past the sales pitch?

we're a mid-market fashion business in europe and last summer we replatformed off a monolith that had been holding us back for years.

I still believe we picked the right platform but the replatform itself almost ended the company anyway, and the gap between those two facts is what a few folks talk about properly.

the headline number was a 14% revenue drop in the first quarter post-launch, some of that was the SEO transition and the price-feed mapping issues that come with every replatform, but the bulk of the damage was a slower kind that doesn't show up in any vendor's case study.

our merchandising team had been hand-tuning the product detail template for years and rebuilding every one of those tweaks took us most of the spring.

Our integrator was greener on multi-country VAT than they showed in the demo, and we burned hundreds of internal QA hours catching their corrections, our customer data migration ran clean, which sounded great until we realized the new recommendation engine was scoring against a different signal set than the old one, and personalization quality dropped silently for weeks before our merchandiser caught it in the cohort retention numbers.

we'd already committed to SCAYLE by the time these problems surfaced, and looking back i still think the platform pick was right because the migration disasters i'm describing were the same kind of disasters my friends running Magento and Salesforce migrations were dealing with this year.

but right call or not, the replatform cost us €2.4M more than the original budget and an extra credit line in q4 we couldn't foresee whatsoever.

what nags me most is the same thing that probably bothers any operator who has been through this. we did the platform comparison properly, even the integrator vetting was thorough, the data migration plan was clean, the SEO redirects were mapped, and what almost ended us was the line item got the least conversation at the kickoff and the most calendar time in execution.

if you're in the middle of a replatform evaluation right now, ignore the platform comparisons for a week and ask your finance team to model the budget for the non-platform line items…

Because that's the conversation that should be hardest, and the budget conversation gets compressed into a single afternoon.

we have a contractor in Italy who's been with us going on 20 months (full-time hours, our equipment, our process, basically an employee in everything but the contract) and the misclassification noise is getting harder to ignore especially after the French judgment earlier this year and the Italian guidance on heteroorganized contractors.

been quietly looking at flipping them to an EOR setup before something breaks, weighing Workmotion (covers Italy directly which matters for the redundancy clause) and a couple of others.

at what stage did you pull the trigger? audit signal or preemptive?

saw a demo last week that i still cant decide if i should believe.

our PM fed maybe 3 months of customer call recordings and support tickets into some AI tool she's evaluating, and it spit out what she called a PRD for our most-requested feature.

it had a problem statement with real customer quotes pulled directly from the calls, user stories with acceptance criteria, links back to the source conversations so we could verify where each requirement came from, and some kind of severity ranking across accounts.

the requirements weren't hallucinated, the quotes were real, and the acceptance criteria were at least in the right ballpark.

it looked better than half the PRDs we get written by humans on a tight deadline.

but i've been burned by enough demos that look amazing in a meeting and fall apart the moment you try to build from them.

my question for the engineering managers here is whether anyone has shipped features from one of these. like, your team takes the AI-generated spec, builds the thing, it works in prod, you didnt have to rewrite the whole document first….

does that happen, or does the PM still rewrite 80% of it and the AI bit is essentially a fancy transcript summary?

not anti-AI by any means, copilot is part of my daily flow, but there's a real gap between AI helping me autocomplete code and AI replacing the human judgment that turns messy qualitative customer signal into requirements an engineering team can build from.

pretty much as the title says, we're around 800 customer call transcripts in one notion db and search has just stopped being usable, taking 2-3 mins per query and missing half the references it should hit.

eventually the whole thing started crawling, and the tagged setup we have (fathom into zapier into notion, linked to a tickets db) just stopped scaling past a certain volume, to where nobody trusts what they pull up anymore.

where do most people hit the wall (page count, db size, tagging falling apart, something else), and did you stay in notion past that point or move it elsewhere?