Rent the Runway Case Study

Introduction – Rent the Runway Case Study

The case tracks Rent the Runway’s early venture journey (set in 2009, USA) as the founders (the two Jennifers) move from idea to product–market fit. The focus is on the micro‑steps of hypothesis testing, building MVPs, capturing data, and iterating – how an entrepreneur actually turns assumptions into validated learning.

Problem & Solution

Problem (demand side)

• Young women (18–35) face social pressure to wear a new outfit to every event and avoid repeating clothes on social media.
• Designer clothing is aspirational but unaffordable; buying multiple outfits for different occasions is not feasible.

Solution
Create a rental platform for designer clothes. Instead of buying, customers can rent high‑end apparel for events.

Designer side (secondary)
Designers currently target only older, high‑purchasing‑power customers. Renting could be a new customer‑acquisition channel without diluting the brand.

Leap‑of‑Faith Assumptions

The idea rests on several untested assumptions – both on demand and supply.

Exam tip: In a lean‑startup context, these are called leap‑of‑faith assumptions – the ones that must be true for the business model to work. The venture’s first task is to test these, not to build a full product.

Lean Canvas – First Iteration (White‑Label Solution)

The founders initially proposed a white‑label solution: build and run a rental infrastructure for designers, on the designers’ own websites. The customer was the designer (the paying entity); the end‑user was the fashion‑conscious woman.

The core assumption to validate first: designers want to expand into rental.

Testing the Hypothesis – Build‑Measure‑Learn Loop

• Build: The pitch itself was the MVP – no code, no product.
• Measure: Conducted interviews with designers (e.g., Diane von Furstenberg). Response was lukewarm; designers were not keen.
• Learn: Designers worried rental would cannibalise full‑price sales. The original white‑label hypothesis failed.

Pivot to Platform Model

The founders executed a pivot – a fundamental change in the business model. The new approach:

• Rent the Runway buys designer clothes directly from designers.
• They hold inventory and rent it out to end consumers via their own platform.

The Lean Canvas changed: the customer segment became young women (paying renters), and the solution shifted from white‑label to a direct‑to‑consumer rental marketplace.

Key takeaways

• The problem is social pressure + high cost of designer clothes for women 18–35.
• Early assumptions must be identified and tested – not just on the demand side, but also on the supply side.
• The first hypothesis (“designers want a white‑label rental service”) was tested via interviews (MVP = pitch) and failed.
• Failure led to a pivot – from serving designers as customers to building a direct rental platform for consumers.
• Every pivot is a learning opportunity; no market research can substitute for real customer feedback.

Testing the Hypothesis for Rent the Runway — Part B

After the initial pivot, the co‑founders returned to designers to re‑validate the core assumption: will designers supply dresses for rental? Designers remained hesitant but became willing if the rental service targeted younger demographics (20s), a segment they did not already serve, thereby minimising cannibalisation. This partial validation reshaped the Lean Canvas further and sharpened the early‑adopter focus.

Revised Lean Canvas After Designer Feedback

• Customer segment: Fashion‑conscious women (unchanged), but early‑adopter segment narrowed to fashion‑conscious women in their 20s.
• Solution: Designer clothes available for rental on Rent the Runway’s own website, delivered on time.
• High‑level concept: “Netflix for fashion.”
• Key unresolved assumptions: Will women actually rent? Will they pay? Will they return dresses in good condition? Will they rent without trying on (as in online rental)?

Three Successive Market Trials (MVPs)

Each successive MVP moved closer to the eventual online model (catalog → computer screen) while requiring zero technology investment. This allowed the team to test the riskiest assumptions — problem‑solution fit — before building any infrastructure.

How the Lean Canvas Evolved

1. Designer buy‑in was secured by promising access to a younger, new customer base.
2. Customer segment was refined to early adopters (20‑something women).
3. All three trials confirmed demand, rental behaviour, and return reliability.
4. At the end, the Lean Canvas showed a validated set of assumptions, ready for the next stage (building the website).

Exam tip: Rent the Runway is a classic Lean Startup example. The key lesson is to validate the riskiest assumption first — here, “will women rent?” — using the simplest possible MVP (a rack of dresses). The pivot from “rent through designers” to “own website + target younger women” was driven by designer feedback.

Key takeaways

• Designer willingness was conditional: only if rental did not cannibalise their core older‑demographic sales.
• Early adopters were fashion‑conscious women in their 20s.
• Three MVP stages (Harvard → Yale → catalog) progressively increased fidelity to the online model.
• Each trial tested demand, pricing, return behaviour, and willingness to rent without trial.
• Problem‑solution fit was achieved before any technology investment; the MVP was never the final product.

Lean Validation and Learning from Beta Test

After building a website, Rent the Runway (RTR) did not launch fully. Instead, they ran a beta test with 5,000 customers — a functioning but not fully robust product. This was a second level of validation after the mail-order test.

What the beta revealed

• Customers had many questions about size, fit, and style.
• They needed support from stylists to guide their rental journey.

RTR responded by adding styling advice as part of the solution, iterating the Lean Canvas in real time.

Evolution of the Value Proposition

The value proposition evolved naturally through customer feedback. Over time, RTR also built strong relationships with designers — a small, interconnected community critical to the business. This eventually became an unfair advantage / moat, but did not exist at the start.

---

Strengths

• Iterative process — multiple MVPs with real-world testing.
• Customer feedback loop — kept customers in the loop at every turn.
• Systematic, cheap validation — they tested assumptions inexpensively before scaling.

Weaknesses

Exam tip: RTR was lucky to have no close competitor at launch. With competition, poor tech or inventory would have driven customers away. This illustrates the importance of operational excellence even for high-demand startups.

---

Product-Market Fit Assessment

Product-market fit requires both demonstrated demand and profit potential.

Demand Indicators

Worked Example: Computing Unique Renters and Conversion Rate

Let $R$ = number of unique renters.
Given:

• 12.5% of renters are repeat renters, each averaging 2.5 rentals.
• 87.5% rent only once.
• Total orders = 2,000.

$$0.875R + 0.125 \times 2.5R = 2000$$ $$0.875R + 0.3125R = 1.1875R = 2000 \implies R = 1684$$

Conversion rate from registration to renting:
Registration started at 0, ended at 150,000 → approximate average registered users = 75,000.

$$\text{Conversion rate} = \frac{1684}{75,000} \approx 2.3\%$$

This rate is considered good for e-commerce (typical range). Combined with repeat usage and emotional response, demand is robust.

Profit Potential: The Dress Turn Problem

RTR buys dresses at 40–50% of retail (assume 45%).
They rent at 10–15% of retail per rental (assume 12.5%).

If shipping one dress per rental:

$$3–4 \text{ rentals} \ (3 \times 12.5\% = 37.5\%, 4 \times 12.5\% = 50\%) \ \text{breaks even on cost.}$$

But RTR ships two sizes per rental to ensure fit, doubling the cost.
Therefore, each dress must be rented 7–8 times to be profitable (dress turn).

Risks to Achieving 7–8 Turns

• Returns in poor condition → repair time, unusable inventory.
• Dry-cleaning turnaround slows reuse.
• Fashion cycles – a dress may go out of style.
• Seasonality – initial high demand (Nov–Dec) may not persist.

Early data (2,000 orders from ~800 dresses in 2–3 months) implies ~2.5 turns so far – promising but not conclusive.

Exam tip: The dress-turn calculation is a classic example of unit economics. Always ask: how many times must a rented asset be used to cover its acquisition cost? Include any multiplicative factors (like shipping two sizes).

---

Next Steps: Operations vs. Expansion

RTR faces a classic startup dilemma: improve operations (tech, inventory) or expand into new markets (demand is knocking).

Arguments

Given the lack of competition, RTR could pursue both – operational improvements and expansion.

Expansion Options

Expansion into older demographics is operationally simpler (same backend, same processes) but requires new acquisition channels and inventory selection. New product categories are tempting but add significant complexity across inventory, logistics, and styling.

---

What Actually Happened

• RTR raised capital sooner than expected.
• Grew rapidly: 1 million members, 25,000 dresses, 140+ designer partnerships within a few years.
• Went public around the time COVID hit → severe downturn.
• Currently rebuilding.

Exam tip: This case shows how a startup can validate systematically (cheap MVPs) and then scale. But even with strong product-market fit, external shocks (COVID) can devastate a business – and operational weaknesses (tech) can become fatal if competition appears.

Key takeaways

• Beta testing with 5,000 customers revealed need for styling advice → iteration on Lean Canvas.
• Value proposition evolved from “convenient designer clothes” to “making women feel beautiful and confident.”
• Tech and inventory were weak spots; lack of competition masked these.
• Product-market fit requires both demand (conversion ~2.3%, repeat usage) and profit potential (dress turn 7–8 times).
• Expansion decisions must weigh operational complexity vs. market opportunity.
• RTR’s growth was rapid, but COVID and IPO timing created major challenges.

Wrap-up: Lean Method Reflection

The two case studies — Meesho and Rent the Runway — were deliberately paired to show how the Lean Method works in practice. Together they demonstrate how every tool from earlier modules fits together into a single, repeatable process.

The core journey: from assumption to evidence

Every venture starts with an idea that is entirely assumptions. The entrepreneur’s job is to turn those assumptions into evidence — also called validated learning — through a fast, flexible, cheap cycle.

Double loop: each failure to validate leads to a pivot or refinement, not a large sunk cost.

Tools revisited

All four tools are applied iteratively, with minimal investment at each step.

Why this matters: navigating uncertainty

The Lean Method is not about getting it right the first time — it is about navigating uncertainty without betting the entire company on untested beliefs. By making small, cheap moves, the entrepreneur avoids the trap of building something nobody wants.

Exam tip: The key phrase that summarizes the Lean Method is “moving from assumption to evidence.” Any exam question about its purpose should lead with that idea. Also remember: it is fast, flexible, and cheap — the textbook three adjectives.

Key takeaways

• The Lean Method transforms assumptions into evidence through iterative hypothesis testing.
• Lean Canvas, customer interviews, MVP, and hypothesis testing are the core tools.
• Small, cheap experiments reduce uncertainty before large investments are made.
• Meesho and Rent the Runway are canonical examples of the method in action — study how each tool was used in both cases.
• Apply the same logic to any new venture: start with assumptions, test cheaply, validate before scaling.