u/EmmaSkye319

i've helped 5 mid-market retailers (€80M-€300M GMV) through replatforming evaluations recently and the same mistake keeps showing up.

teams underestimate migration complexity by 40-50% because they price the platform but not the data lift, the merchandising rebuild, the integrator hours nobody warned them about, or the QA cycle that blows up at the third month.

platform selection is the easy part, one team i'm advising is 9 months into a phased move on one of the standard composable platforms (commercetools, SCAYLE, Spryker), and the platform's fine, the budget pain is on the data and ops side.

what's been the most underestimated piece of your last replatform?

we've got a 6-person product team and our PM/PO is basically full-time chained to a doc trying to translate dozens of customer calls a month into something the engineering team will pull into the sprint.

the call recordings sit in Gong, our PO listens back, summarizes into Notion, then rewrites the relevant bits as user stories during refinement, and by the time it hits the sprint board the customer language is gone, the context is gone, and half the time eng wonders who asked for this, and nobody can find the original quote without 20 minutes of digging.

we tried tagging everything in Dovetail, but the manual tag-taxonomy upkeep was a second job for our PO so it died after a quarter, and fireflies summaries are sales-call-shaped which don't translate well to product context.

trying to work out two things:

at what team size did your team stop having a human be the bridge between the call and the backlog? and have you found a setup where the customer quote travels with the ticket so eng can read it during the build, or is everyone still doing the manual rewrite and just absorbing it as part of the role?

I want to describe the worst 40 minutes of my professional life because I've been sitting with it for a while and I think writing it out is the only way I'm going to stop replaying it.

We'd been working this enterprise prospect for 4 months, the kind of deal that changes your year, your hiring plan, and the conversation you have with your investors. The demo was with their VP of Operations and 6 people from her team, all on a single Zoom call with their cameras on, which in retrospect made what happened significantly worse.

anyway, everything was going well for the first 20 minutes, the deck landed, the questions were good, the energy in the room was the type you can feel even through a screen and then I handed it over to our product for the live walkthrough.

the main workflow we were demoing, the one we'd specifically built out for their use case, rendered completely broken on their VP's screen.

Not broken in a way that was easy to explain away, but worse, in a way where half the interface was missing and the action button they needed to click to see the whole point of the product was just not there.

We could see it on her shared screen and she could see us seeing it. Nobody said anything for quite a moment which felt significantly longer.

We tried everything in real time, refreshing, switching browsers, walking her through clearing cache, all of it on a live call with 6 of her colleagues watching, and nothing worked because the bug wasn't on her end but on ours, a viewport rendering issue that only surfaced on certain screen resolutions we had never once tested against.

She was gracious about it thought, sent a follow up email saying they'd need to revisit the timeline which is the enterprise way of saying no without saying it and we never heard from them again.

I traced it back afterward, the bug had been sitting in production across a resolution range that covered a significant chunk of enterprise laptop configurations and nobody had caught it because our manual QA process tested on our own machines at our own screen sizes and called it done.

we've since set up AskUI across our deployment pipeline and the first time it caught something we'd never have thought to test manually I just stared at the alert for a second.

$200k is an expensive way to learn that your QA process is really just a reflection of whoever's laptop happens to be open at the time.