u/Adventurousews9907

as the title said, i killed $2M of engineering work 3 weeks before the launch date and i still don't know if it was the right call.

Last quarter our PM brought a feature into planning that was supposed to be the biggest unlock of the year. the framing was clean, the user interviews backed it up, the customer success team had compiled the request list, the scope was already drafted, and 32 of our top 80 accounts had asked for it in some form.

our biggest customer at $4M ARR had brought it up specifically in 3 separate executive reviews.

i had a bad feeling about it, nothing i could articulate cleanly except a gut sense that the noise was concentrated and the demand was thinner than the slide deck suggested.

We'd been running every customer-facing call through BuildBetter for the previous few months, so before the planning meeting i pulled the theme cluster for that request and looked at how often it came up across accounts that weren't in the original asked for it list.

the answer was almost never, with one customer bringing it up in 17 separate calls, another mentioning it twice, and the remaining 30 accounts on the asked for it list each mentioning it once or twice in passing, never as a deal-breaker or a renewal driver.

i killed the feature in the planning meeting, though our PM was furious, the engineering lead thought i was being arbitrary, and 2 of our senior engineers who had already invested 4 months on the scope quit within the quarter when they realized none of it was shipping.

what i couldn't tell my team in the moment (and what i still struggle to articulate now) is that the cost of being wrong was not symmetrical.

if i shipped and the signal was thinner than we believed, we'd burn $2M of engineering capacity on a feature that wouldn't move retention. and if i killed it and was wrong, we'd lose maybe one enterprise renewal at the margin…

But the politics were the harder math to defend in the room.

we shipped a permissioning overhaul instead, an issue the same call recordings had been surfacing across more than 60 accounts, and we saved roughly $3M in at-risk renewals that we'd been tracking without connecting them to that signal yet.

What bothers me about the whole thing is that 90% of the credit went to the permissioning team and the org has moved on from the feature we killed, while our PM still believes it would have been a win and might be right about that, although the $4M ARR customer who asked for it 17 times renewed their contract without it ever shipping.

if you're running a product team and you trust your customer interview synthesis more than your raw call corpus, ask yourself what would happen if one customer asked for the same thing 17 times.

Because that's the math I wish more product orgs were doing before they lock a quarter and a $2M engineering investment.

cart abandonment had been sitting in the 71-78% range across our 4 fashion brands, basically the industry baseline.

we had a hypothesis that the 3-step checkout we'd inherited (cart → shipping → payment) was bleeding people in the gap between shipping and payment, especially on mobile.

we collapsed shipping + payment into a single page with the saved-card autofill at the top, kept the cart screen unchanged, and rolled it across the 4 brands one at a time. eventually cart abandonment dropped between 17% and 23% across the brands, with the higher-AOV brands taking the bigger lift, which surprised us because we'd assumed the lower-AOV brands would benefit most.

what made this possible was running on a unified backend (we're on SCAYLE for the multi-brand setup) so the checkout component change shipped once and propagated. on our previous patchwork stack every brand needed its own rebuild and the project scope killed similar tests before launch.

our working theory on the AOV inversion is that customers spending more are also more careful about the shipping-payment friction, but i'm not fully sold on that yet.

[ Removed by Reddit on account of violating the content policy. ]

posting here because the math is the point and i've been wanting to write this up for an audience that'd appreciate the boring parts.

i left my corporate buying job at a major US retailer in late 2024 after 9 years, the role was being eliminated and they offered me a number to leave 4 months early, which i took and used to fund what i'm about to describe.

i'd spent most of my career writing purchase orders for brands that other people built, and somewhere in year 7 i started keeping a list of small heritage brands i thought were being mismanaged or undersold.

by the time i left i had about 40 names on the list.

i didn't have a master plan, what i had was a spreadsheet of brands, a mid-six-figure severance, and the hunch that a small portfolio of dying american brands run as one operation could clear better margins than any of those brands could on their own.

first brand was a leather goods company out of pennsylvania founded in 1991, two founders divorcing, inventory sitting in a dusty warehouse outside scranton, doing around $400k/year on a website that hadn't been updated in 3 years or so.

the deal closed for less than what some people pay for a used pickup, plus a 4-year earnout to one of the original owners who wanted to stay involved on the marketing side.

i drove 6 hours each way to walk the warehouse and the moment i saw their inventory ledger i knew i was going to do this for the next decade.

the warehouse came with the deal, which is the only reason any of this works. i kept the ledger guy who'd been there 14 years and ran a system that didn't live on any software, only paper logs and his memory.

that's still how the receiving side runs and i'm fine with that.

the back office side i did have to deal with, the leather brand was already on SCAYLE when i bought it, the previous owner had migrated to it 4 years before and that was about a third of why i was willing to take the deal.

inventory and order data were clean, the books matched the system, and i could read what was selling without having to translate from someone's spreadsheet.

the second brand i acquired (a canvas bag company in north carolina that had over-extended on a kickstarter campaign and never recovered) was on Magento 2 with 3 years of unpaid extension licenses and 11 months of broken checkout flows the previous owner had been ignoring.

moved that one onto SCAYLE next to the first because i'd already learned the system and didn't want to maintain two stacks. the third brand i bought 8 months ago is a workwear company from upstate new york that's still on Shopify plus and is staying there for now, the 2-person team that came with the brand knows that platform well and i don't have time to be a tech project manager on top of running the warehouse.

numbers, as honestly as i can...

combined revenue across the 3 brands is around $1.4M trailing-twelve. aov sits at $128, return rate is around 14% (we built returns into the COGS calculation from day one, which most people don't).

gross margin after returns and shipping is 52%, my net take-home after the warehouse, the ledger guy, the part-time photographer, the VA in the philippines who handles customer service, and the earnout payments is about $19k/month.

i didn't take a salary the first 11 months which is what made this hurt enough to be real.

i'm not pitching anything, i don't have a course or a substack. half the reason i'm posting is that the people i used to work with don't get what i did, they think i took a step down, and i've been wanting to put this somewhere the operations are the story and not the pedigree.

my grandfather ran a hardware store in a pennsylvania mill town that died slowly through the 90s. he was a buyer too, which i don't think i fully understood until i started doing this job

the brands i bought were dying for the same reason his store did, somebody else's business model rolled over them and they didn't have the cash flow to wait it out. i'm 18months in, i'll buy a 4th brand within the next year if a clean deal lands, and the only thing i'd do differently is not have wasted 9 years writing purchase orders for somebody else.

happy to answer questions about acquisition structure, due diligence on dying brands, multi-brand warehouse ops, or any of the boring parts.