Business: Roadmap to Success

Frameworks are not answers. They are a basis on which to ask better questions — and to take action without feeling stuck.

If you know where you start (value proposition) and where you are headed (vision), the work in between is a roadmap: a series of dots you fill in as you take risk out of the venture and put value in. You cannot connect those dots looking forward — Steve Jobs was right — but if you do not know where you are going, any road will get you there.

Source note: This article synthesises a Harvard iLab Startup Secrets workshop led by Michael Skok, with guest stories from Paula Long (EqualLogic / DataGravity) and the Neoclosure team, plus contributions from Stephan Schambach (Demandware). It is a practitioner summary, not a transcript. Materials and related workshops live on startupsecrets.com.

---

Two anchors, one path​

Simplify the literature to two anchors:

Anchor	Role
Value proposition	Where you start — the problem, for whom, and why they will pay
Vision	Where you are headed — how the market evolves and how you lead it

The roadmap sits between them. Operationally and for investors (or any stakeholder who must buy in), you are trying to do two things continuously:

1. Take risk out — make success more likely (true for for-profit and social ventures)
2. Put value in — build something sustainable or self-sustaining

A pitch deck, napkin sketch, or product roadmap is useful mainly because it aligns energy. When everyone runs in the same direction, hard paths become traversable. When they do not, little is possible.

---

The stages (know them — do not trust the straight line)​

Almost every venture moves through stages that look roughly like this:

Idea → Create → Validate → Repeatable → Scalable → Sustainable / profitable → Predictable

Stage	What you are proving
Idea	There is a problem worth solving that you are uniquely placed to tackle
Create	You can build something real enough to put in front of users
Validate	You are validating value, not just testing features
Repeatable	The same use case works beyond the first few friendly users
Scalable	Delivery, product, and economics work at the next order of magnitude
Sustainable	The model can fund itself (profit or another durable revenue stream)
Predictable	Outcomes are stable enough for serious capital and exits

Public-company grade businesses add predictability — customers who stick, metrics outsiders can underwrite. Demandware’s premium came in part from that kind of durability.

Reality is a squiggle​

In the real world the path looks like a messy curve: pivots, stalls, near-death quarters, team changes. Expect that. If validation says you are serving the wrong side of a marketplace, you may flip the product (buy-side to supply-side) and still keep the vision — or decide to quit. If “repeatable” means only expensive direct sales, you may not have a scalable business. Those are decisions along the way, not failures of the framework.

---

Surprises on the road (so they stop surprising you)​

Euphoria → reality​

Early euphoria (“the world will beat a path to our door”) meets the fact that it usually will not. Ideation itself often includes hard iteration — including with VCs who expect more than you have. Conviction is yours to hold. Some of the worst-sounding ideas (early eBay, early Google) could not get funded. Outsiders do not get to decide whether your vision is worth your life’s energy.

Outlier customers: market of one​

Landing a marquee early customer (a Fidelity, a Cisco, a lab-driven bank) feels like winning. It can be a trap. Outliers often pull you onto a feature roadmap that is not repeatable. They seek differentiation precisely because they are different. Hold your value proposition and vision so customer pull does not erase the business you meant to build.

The funding mirage​

A large check is not proof you are a genius. The only money that really counts is customer money. VC capital is abundant in some cycles; that makes the mirage worse. Prefer a business that can live on customers. Investors would rather hear of your success without writing a check than fund a marketplace that never forms.

Business-model challenge​

Gross-margin profit and rising sales still leave open questions: Does the delivery model work? Can the stack scale from 1,000 to 100,000 users? What does support cost? Re-architecting under load can feel like starting the company again — including the question of whether existing customers can migrate. You often do not know the full model until you hit larger, more repeatable demand.

Valley of death​

Nearly every lasting company Skok has been close to hit a near-death stretch: a zero-revenue quarter, a lawsuit, a product scare, a forced CEO change. Passing through that valley often means you have reached a place where the real company can be built. Team, model, and operating mode may all change. That is normal — prepare for it instead of fearing it.

Bigger than you dreamed​

Markets are routinely underestimated. Online advertising once looked “too small” to justify Google’s early market cap; the opportunity proved an order of magnitude larger. Many survivors end up larger than anyone imagined — after the squiggle and the valley.

---

Where you + the story intersect​

A compelling pitch is a story, not a feature list. The world remembers stories. Two ingredients matter:

1. You — background, unfair advantage, depth
2. The story — the problem and the change in someone’s life
3. The intersection — where you are uniquely qualified to tackle this opportunity

Paula Long’s EqualLogic origin was deliberate: many cooler ideas on the whiteboard, but the team kept returning to storage automation because Peter knew storage, Paula knew storage and distributed systems, Paul knew network protocols. Unfair advantage made real.

Contrast the common anti-pattern: “cool app,” little domain time, hope that downloads stick. Most apps die in the first ten seconds of attention. Prefer the nurse who has lived a post-surgery failure mode for a decade over the phone-tinkerer with a novelty idea.

Incomplete standouts beat complete standups. A crystal-ball business plan is not believable. A founder who deeply owns a big problem and asks for help on the rest is a complete basis to start.

---

Value proposition: validate value, not features​

Valueless proposition​

Ideas you “just want to build and test” without knowing who, why, or what problem are valueless propositions. More testing does not fix a missing target. Prefer qualitative and quantitative user research early — many founding teams skip it and pitch conviction without evidence.

Skok avoids the word “test” on the roadmap for a reason. The job is to validate value.

Flip the Field of Dreams​

• Weak: If you build it, they will come (hope is not a strategy)
• Stronger: If they come, will you build it? — you already know who they are and that they will pay

MVP is not enough if you do not know the problem. Ask for a minimum viable problem: the smallest valuable problem that, if solved, pulls people in. For a billion-dollar business, start with a multi-billion-dollar problem (or a cause large enough to spend a life on).

EqualLogic’s before / after​

Storage was manual: disks, Fibre Channel, new security models, specialist skills. Everything else in IT was automating; storage was still an erector set. EqualLogic’s prop: set-it-and-forget-it — provision size and access; the system manages itself. Metaphor: build your own car for fun, or drive one off the lot.

Lived demo: SEs carried ~100 lb arrays into sales calls and stood up a SAN in the meeting. Industry incumbents had already evangelised SANs; mid-market buyers could not pay for the complexity. EqualLogic made “you can’t do that” into “you just did.”

Demandware’s problem size​

In 2004, e-commerce was growing but retailers could not run it well — thin or post-bubble eng capacity. Schambach’s bet: commerce platform as a service over the internet (early “cloud” without the label). Retailers want merchandising and brand, not infrastructure. Commerce is a multi-trillion market, lightly penetrated, growing hard — that is the scale of problem that supports a category winner.

---

Vision: not a hallucination​

Customers, partners, and OEM checks will yank you sideways. Vision is how you stay on a path when millions appear on the wrong track.

Step back from the technology. Ask how the market evolves (storage, healthcare, education, …) and how you might lead that evolution. Related workshop: vision and mission (see also Vision, Mission and Culture).

Startup secret: check that your vision is not a hallucination. The two letters that settle the argument: PO — purchase order. Love is cheap until someone writes a check. Ask early what they would pay for; some customers will fund the first version for competitive advantage (Salsify and others have done this).

VCs talk out of both sides of their mouths: too big a vision and they fear you cannot start simple; too simple and they fear you cannot get big. Manage both with today’s focus vs tomorrow’s destination and an explicit roadmap between them.

---

Case study: EqualLogic’s real roadmap​

Paula Long’s “box score” before EqualLogic: Bright Tiger (base hit — beautiful product that did not scale to real customer size), Ironstream (rained out — seed returned when the climate turned), Heartland / Rethink Robotics (traded in the first inning — wrong fit), then DataGravity (shipping with POs). The home run was EqualLogic → Dell, $1.4B, with ~3,000 customers, ~40% repeat business, ~98% satisfaction — and calls to the 2% who were unhappy.

How they chose the idea​

April 1, 2001, Purgatory Road: cool ideas on the board; they chose what they were uniquely qualified to solve — storage automation for the mid-tier (fast growth, drowning in complexity). Mission later found a better “arms dealer” in Dell when an IPO roadshow was days away.

Conviction under pressure​

First-time founders took early term sheets in a gloomy market. Smart money pushed alternatives: be a switch, software-only, InfiniBand not iSCSI, avoid SATA. They held: iSCSI over Ethernet, SATA for mid-tier cost, all-inclusive pricing (not dim-sum feature SKUs), and a channel motion others called insane. Listen, assess, stay true — if you fail, own it.

Squiggles that actually happened​

• Tranches they did not understand as newbies — then the fastest tranche checklist they ever ran so they could hire
• Early VAR conversations without a deck → story drifted with every whiteboard; they formalised a customer deck for consistency
• Down round despite on-time product and good betas — 100% of the team stayed; focus stayed on happy customers, not VC valuation theatre
• Playbook CEO swap: cultural mismatch (“country vs hard rock”) → Paula quit as founder/product leader → interim CEO → helped hire Don Bulens, then returned to product
• Scale bugs (one-in-a-million becomes frequent at volume), chip delays, inventory risk, a broken “up and to the right” quarter, VP churn
• Fear of success: decisions that were easy on the penny slots got heavy at the $100 table
• S-1 approved; Dell’s offer won; customers stayed through the transition

What she would tell new founders​

Lesson	Detail
Pick VCs carefully	Reference-check them; if they will not give references, walk
2× time, 2× money	They already expect the slip; do not let the slide date own your psyche
Listen hard, dismiss fast	Obsessive second-guessing burns the hours that should build the company
Never burn bridges	Network is how you learn vendors, competitors, and product truth
Culture is top-tier	EqualLogic was customer-obsessed (3 a.m. calls included); “sitcom not drama” — remove people who need to win every argument
Could / should / money	Not only can you build it — should you, and can you make money (or fund the people another way)?
You can do anything; you must do something	Broad ideation, laser execution — especially when advisors invent ten markets

Enterprise checklist she distilled: large addressable market, big vision with later execution focus, radical simplification or business-model change, leveraged sales access, great team, happy customers. Innovate enough that buyers should not just buy the incumbent. Make money so you can stay. Tune relentlessly. Build a culture that survives the ups and downs.

---

Live application: Neoclosure (early-stage)​

Neoclosure grew from an MIT summer programme designing clothing for people with disabilities. A Tufts professor who uses a wheelchair had worn tear-away basketball pants for a decade so he could toilet independently; limited hand function made re-snapping hard. The team built magnetic seams — discreet, self-sealing, quieter than Velcro, less hand demand than zippers — and a mission to expand designers’ vocabulary for accessible openings without ugly “adaptive” aesthetics.

On Skok’s curve they sat between creation and validation: strong single-client confirmation, not yet broad user proof; many magnet and washability iterations still open.

Audience pressure made the roadmap questions concrete:

• Robustness across garments and seasons (winter airtightness)
• End customer vs licensor vs sew-it-yourself strips (changes product and business)
• Disability beachhead vs broader markets (baby clothes, industrial uses) — expand thoughtfully without losing the core
• Paula’s counterweight: economics decide the beachhead; a $50 unit will not live in disposable baby clothes; disability may bear cost if value is high. Cost-to-scale will rewrite the market.

Without some roadmap — even a napkin — helpers cannot engage productively. With one, “help” means better questions, not answers imposed from outside.

---

How to start (even knowing you will be wrong)​

1. Napkin, product roadmap, or pitch deck — form matters less than a shared picture
2. Value prop + vision — so you can measure what changed when reality hits
3. Story checklist — team, value prop, business model, go-to-market — then make it a story of lives changed, not a feature dump
4. Unique advantage — filter ideas by who you are, as EqualLogic did
5. Minimum viable problem — then validate value; chase POs, not compliments
6. Expect the squiggle — outlier customers, funding mirages, model breaks, valley of death, team changes
7. Stay incomplete on purpose — bring the deep problem; recruit help for the rest
8. Ask questions in public — a roadmap without questions is hard for mentors to improve

If you are missing capital, first ask whether you should raise at all — see Funding Strategies to Go the Distance. If you are missing product or GTM pieces, start from unfair advantage and clear problem ownership; fill the rest with intentional help.

---

Closing​

The linear slide is a teaching aid. The lived path is Paula’s chart: as many unhappy faces as happy ones on the way to thousands of customers and a life-changing exit. Expect that shape. Hold the intersection of you and a real problem. Validate value with money. Keep vision honest with POs. And remember: incomplete clarity on a huge problem you own beats a perfect plan nobody believes.

For adjacent Startup Secrets playbooks on this site, see Value Proposition, Turning Products into Companies, Vision, Mission and Culture, Go-to-Market Strategies, and How to Get Your First 10 Customers.