A $4.8M DTC brand lost $53,800 on a single launch. Here are the 5 failures that caused it, the sunk cost mistake that made it worse, and the process changes that fixed everything.
A $4.8M DTC brand planned their first major product expansion. Four new SKUs. $85,000 in inventory. A November 1 launch timed for peak season. Projected revenue: $180,000.
The actual result: $147,800 in total costs, $94,000 in revenue, and a net loss of $53,800. Plus brand damage from a 22% return rate that took a year to repair.
Every failure was visible before it became expensive. None of it was acted on.
This is that story, told in full. The plan that looked solid on paper, the phase-by-phase unraveling, the sunk cost decision that turned a manageable problem into a $53,800 loss, and the five process changes that made them one of the most disciplined launchers in their category one year later.
What Is a Product Launch Process Failure?
A product launch process failure is a breakdown in the systems and decision points that govern how a new product moves from concept to market. It is distinct from a product failure, where the product itself is flawed or unwanted. In a process failure, the product may be good but the organizational infrastructure around the launch, the timelines, the decision authority, the cross-functional alignment, and the criteria for stopping, fails to protect the brand from preventable problems.
The case study in this post is a process failure. The products were not bad. The process that brought them to market was.
The Plan
The brand had grown steadily to $4.8M in annual revenue on three core SKUs. The decision to expand with four new products was strategically sound. The market opportunity was real. The supplier relationships were in place.
The plan: a 12-week timeline from final sample approval to November 1 launch, 12,000 units across four SKUs at an average cost of $7.08 per unit, $85,000 total inventory commitment. Revenue projection based on existing customer base engagement rates and seasonal demand: $180,000 in the first 90 days.
On paper, the plan was reasonable. In execution, it fell apart in phases.
The Timeline: Phase by Phase
Weeks 1 to 4: The Optimism Phase
No formal kill-gates. No documented pass criteria. Samples were reviewed quickly by one person, approved on gut feel, and the team moved to production.
The sample approval speed felt like efficiency. It was not. It was the absence of process being mistaken for speed. Two of the four SKUs had quality issues that a structured three-round sampling process would have surfaced and resolved before production began. They were not surfaced. They were not resolved.
Production started on time. The timeline looked intact. The team felt good.
Weeks 5 to 8: The Reality Phase
Production delays began in week 5. The supplier, operating near capacity during peak season, could not hold the committed lead time. A PERT timeline built around three scenarios would have flagged this as a likely outcome. The launch timeline had been built on the optimistic scenario only.
By week 7 it was clear the inventory would not arrive by November 1 without intervention. The team authorized expedited air freight. Cost: $18,000.
The timeline was preserved. The budget was not.
Weeks 9 to 12: The Disaster Phase
Inventory arrived. Quality inspection revealed a 14% defect rate across two of the four SKUs. The specific issues: the same fit-and-finish problems that had been present in the samples and glossed over at approval. Production had not fixed what sampling had not caught.
The team had three options. Delay the launch, rework the defective units, or launch knowing the defect rate.
They launched.
The reason: $85,000 in inventory was already paid for. Marketing had been running pre-launch content for three weeks. Influencer relationships had been activated. A delay felt like admitting failure on a project the whole organization had committed to.
The sunk cost of what had already been spent drove a decision that cost more than the sunk cost itself.
Weeks 13 to 20: The Aftermath
The 14% defect rate in the warehouse became a 22% return rate from customers. Defective units reached buyers. Negative reviews followed. An emergency markdown campaign was required to move remaining inventory.
Customer service volume for the launch products ran at three times the normal rate for six weeks. Two influencer partnerships had to be renegotiated after product quality complaints surfaced publicly.
The November 1 launch date had been hit. Everything else had not.
The Complete Financial Picture
| Category | Planned | Actual |
|---|---|---|
| Inventory cost | $85,000 | $85,000 |
| Expedited freight | $0 | $18,000 |
| Defect rework and disposal | $0 | $11,200 |
| Returns processing | $2,500 | $14,800 |
| Emergency markdowns | $0 | $9,400 |
| Customer service overrun | $0 | $7,200 |
| Influencer renegotiation costs | $0 | $2,200 |
| Total cost | $87,500 | $147,800 |
| Revenue | $180,000 | $94,000 |
| Net result | +$92,500 | -$53,800 |
The difference between the plan and the outcome was $146,300. Not because the market did not want the products. Because the process that brought them to market failed at every stage where it could have intervened.
The 5 Failures, Named Exactly
Failure 1: No Kill-Gates
There was no formal decision point at any stage of this launch where the team evaluated whether to proceed, pivot, or stop. Samples were reviewed informally. Production was started without a documented sign-off. The quality inspection results in week 10 were shared internally but triggered no formal decision process.
Kill-gates exist precisely for the moment in week 10 when 14% of inventory is defective and there is $85,000 already spent. They give the team a framework for making that decision based on criteria established before the sunk cost existed. Without them, the sunk cost wins.
Failure 2: Optimistic Timeline
The 12-week timeline was built on a single scenario: everything goes right. No PERT analysis. No buffer for production delays during peak supplier season. No contingency for the expedited freight that was actually required.
A PERT timeline for this launch, run before production began, would have produced an expected timeline of approximately 16 to 17 weeks and a pessimistic timeline of 20 weeks. A November 1 launch would have required starting the process in late June rather than early August. That was achievable. It was never planned for.
Failure 3: MOQ Not Negotiated
The team committed to standard MOQs across all four SKUs. Total inventory: 12,000 units at $85,000.
Had they negotiated 40 to 50% of standard MOQ on the first order, accepting a 15 to 20% per-unit premium, total cash at risk would have been approximately $35,000 to $40,000. The quality issues discovered at Week 10 would have been a $35,000 problem, not an $85,000 one. The sunk cost pressure driving the launch decision would have been roughly half what it was.
Smaller first orders do not prevent quality problems. They reduce the financial pressure that causes teams to launch despite them.
Failure 4: Marketing and Supply Chain Disconnect
Marketing had been running pre-launch content and activating influencer relationships from week 6 onward, based on the original timeline. Supply Chain knew by week 7 that the timeline was at risk. That information did not reach Marketing’s planning calendar.
By week 10, when the quality issue was confirmed, Marketing had external commitments that could not be easily reversed. The organizational cost of delaying had become significantly higher than it would have been if Supply Chain had communicated the timeline risk three weeks earlier.
Marketing and Supply Chain were not working from the same information. They never were.
Failure 5: Launching Despite Known Problems
This is the failure that multiplied all the others.
The team knew the defect rate before the launch decision. They had the data. They made the choice.
The calculation they made, implicitly, was: we have spent $85,000 and cannot recover it by stopping, so we launch and hope for the best. The calculation they should have made: delaying to rework or replace the defective units would have cost approximately $20,000 and three to four weeks. Launching cost $53,800 and a year of brand repair.
The sunk cost of $85,000 already spent cannot be recovered regardless of the decision. It is gone either way. The only question is what the next decision costs. Evaluated correctly, the delay was the obvious choice. Evaluated through the lens of sunk cost, it felt impossible.
This is why walk-away criteria need to be established before the sunk cost exists.
The Sunk Cost Decision, Quantified
| Decision at Week 10 | Cost |
|---|---|
| Delay launch: rework defective units, push timeline 3 to 4 weeks | Approximately $20,000 |
| Launch with 14% defect rate | $62,800 in additional costs plus $86,000 in lost revenue versus plan |
The delay was the correct financial decision by a significant margin. It was not made because the team was evaluating the future cost of each option. They were evaluating the past cost of what had already been spent.
Sunk cost bias does not feel like bias in the moment. It feels like responsibility.
The Process Changes That Fixed Everything
One year after the disaster, this brand runs the most disciplined launch process of any brand in their category. Here is what changed.
Formal kill-gates at four stages. Concept, sample, pre-production, and final. Each gate requires a proceed, pivot, or stop decision documented in writing with sign-offs from Supply Chain, Marketing, and Finance. Finance signs off at pre-production because that is when the inventory buy is authorized. A gate cannot be bypassed without a written exception approved by the founder.
PERT timelines on every launch. Three scenarios built before any external commitment is made. Marketing receives the pessimistic date. Operations targets the realistic date. No external announcement is made until Supply Chain has confirmed the pessimistic date is achievable.
MOQ negotiation as standard practice. First orders are negotiated to 40 to 50% of supplier standard MOQ with an explicit per-unit premium. The additional unit cost is budgeted as a launch line item. The reduction in cash at risk is modeled explicitly in the launch financial case.
Joint planning sessions before production begins. Supply Chain and Marketing meet at the start of every launch to align on the PERT timeline, the external commitment schedule, and the trigger points at which Marketing will be notified of timeline changes. Information sharing is a structural requirement, not an optional courtesy.
A walk-away rule with a specific threshold. Any production run with a defect rate above 5% is an automatic delay, regardless of sunk cost. Not a discussion. Not a judgment call. An automatic delay. The threshold was set when no sunk cost existed, so it cannot be overridden by sunk cost pressure when it matters.
One Year Later
Twelve months after the launch that cost $53,800, the same brand ran four new SKU launches using the framework above.
Results: 100% on-time delivery. Average review score of 4.6 stars across new products. Return rate of 6%, down from 22%. Zero emergency markdowns. Zero expedited freight.
The disaster taught them everything. The process they built from it is worth more than the $53,800 it cost them to learn it.
Frequently Asked Questions About Launch Process Failures
What is the most common reason DTC product launches fail? Process failures rather than product failures cause most DTC launch problems. Specifically: no formal kill-gates that create a legitimate option to stop, optimistic timelines with no buffer for normal production variability, marketing and supply chain misalignment on launch dates, and sunk cost bias that drives teams to launch despite known quality problems.
What is sunk cost bias in product launches? Sunk cost bias is the tendency to continue a course of action because of resources already invested, regardless of whether continuing is the correct forward-looking decision. In product launches, it typically manifests as launching with known quality problems because inventory has already been paid for. The correct evaluation compares the future cost of each available option, not the past cost that cannot be recovered.
When should you delay a product launch? A product launch should be delayed when quality inspection results exceed a predefined defect threshold, when the production timeline cannot support the announced launch date without emergency freight costs that change the financial case, or when kill-gate criteria have not been met at any stage. Establishing these thresholds before the sunk cost exists is what makes them possible to act on.
How much does a failed product launch cost? Costs vary significantly by brand size and launch scale, but the categories are consistent: expedited freight to preserve a timeline, quality rework or disposal costs, elevated return rates from defective product reaching customers, emergency markdowns to clear slow-moving or damaged inventory, and customer service overruns. For a mid-size DTC brand, an unmanaged launch failure can easily add 50 to 100% to planned launch costs while simultaneously reducing revenue below projection.
What is a walk-away rule in product development? A walk-away rule is a predefined threshold that triggers an automatic decision without requiring a new judgment call under pressure. In product launches, a common walk-away rule is an automatic launch delay if quality inspection reveals a defect rate above a specified percentage, typically 3 to 5%. Setting this threshold before any inventory is committed means the decision is made when the answer is obvious, not when sunk cost pressure makes the obvious answer feel impossible.
How do you recover from a failed product launch? Recovery requires addressing both the financial damage and the brand damage separately. Financial recovery involves clearing defective or excess inventory through markdowns, negotiating return terms with the supplier where quality issues originated with them, and modeling the path back to margin on remaining product. Brand recovery requires direct customer communication about quality issues, a replacement or refund policy for affected customers, and a demonstrably improved product in the next production run.
The June NPD Series: What We Built
Four weeks on the most common way growing DTC brands destroy the margin they worked hard to build.
Week 1 named the five process failures that sink most launches before a single unit ships. Kill-gates, timeline buffers, contingency planning, Marketing and Supply Chain misalignment, and optimism bias. Each one preventable. Each one showing up in this case study.
Week 2 built the sampling process. Three rounds, documented criteria, defined pass thresholds, and the sign-off structure that brings Finance into the golden sample decision where they belong.
Week 3 covered the two financial levers. MOQ negotiation tactics that reduce first-order cash at risk by up to 64%. And PERT timelines that give Marketing a campaign anchor they can actually plan around.
Week 4 (this post) showed all of it in a real brand story. The plan, the unraveling, the $53,800 loss, the sunk cost decision that made it worse, and the process changes that produced 100% launch success the following year.
The through-line across all four weeks: process is cheaper than heroics. Kill-gates are cheaper than emergency freight. Honest timelines are cheaper than missed dates. Smaller first orders are cheaper than $85,000 worth of pressure to launch despite known problems.
Build the process before you need it. It is always cheaper that way.
Coming in July
You know how to manage what you make, where you make it, and how you launch it.
July we look at what happens when it goes wrong after it ships. The Returns Reality Check: building a returns process that recovers margin, retains customers, and generates the product data most brands leave on the table.
See you next week,
— Lara
The Failures in This Case Study Are More Common Than You Think
I break down the 10 biggest NPD mistakes DTC founders make (falling in love with ideas instead of data, uncontrolled sampling, committing to one supplier too early) with real examples from apparel, beauty, lifestyle, and home brands. Plus, how to calculate true margins and scale only the SKUs that actually prove themselves.
Already know your bottleneck?
Join the Supply Chain Lounge on Slack where we discuss these exact challenges every week.