Business: Value Proposition
One of the hardest early challenges is deciding whether an idea is worth building a business around. A sharp value proposition is how you answer that — qualitatively first, then quantitatively — before you plough into product and go-to-market.
Source note: This article synthesises a Harvard iLab Startup Secrets workshop led by Michael Skok, with case contributions from Apperian, Akiban, Disqus (Rick Farnell), uTest (Doron Reuveni, Matt Johnston, Fumi), and Diagnostics for All. It is a practitioner summary, not a transcript. Slides and templates live on Startup Secrets / related Michael Skok materials.
The unfair advantage of this series is scar tissue shared before you hit the wall: define the value prop, evaluate it, then build on it — moving from gut feel to numbers that justify a cheque.
What a value proposition looks like
Start at the end so you know where you are headed. The typical form:
For [target customers] who are dissatisfied with [current alternative], our product provides [differentiated problem-solving] that, unlike everything else, does something unique.
In one line: what you do uniquely well, for whom.
You will iterate this many times in the real world. Apperian is a reminder: they did not start with today’s subscription platform. They began as an enterprise app shop, then customers spending hundreds of thousands of dollars refused to put apps in the public App Store — which forced the Enterprise App Services Environment (EASE). Value props often evolve from customer pain, not from day-one genius.
Park the idea. Own the problem.
Ideas are free-floating and cheap. Most never see daylight because they are not oriented to a fundamental problem.
Worst move: get carried away with an idea before you define the problem space.
Better move: park the idea until you can say what problem it applies to — then develop the problem with discipline.
The Four U’s of a problem worth solving
Not the only ways to describe problems — a mnemonic to hone what you will do uniquely well. Look for problems that are:
| U | Meaning | Signal you are onto something |
|---|---|---|
| Unworkable | Broken process or experience that needs fixing | Costly or painful consequences — lost customers, lost revenue |
| Unavoidable | Cannot skip it (taxes, audits, FDA, Basel, HIPAA…) | Must-do compliance or accounting work |
| Urgent | Top of the buyer’s priority stack now | Relative urgency vs other needs — ideally top three |
| Underserved | White space; few others fighting for the same budget | Zero-sum fight for dollars, time, people, attention |
The more U’s you stack, the more likely the problem rises to attention. One is enough to start; four is rare and powerful.
Unworkable
Broken business processes are gold. Early iPhone onboarding was so broken that phones sat unactivated for days — Active Endpoints fixed AT&T’s provisioning workflows and got paid millions.
Acid test: can you name someone who gets fired if this is not fixed? That person becomes your champion, educator, and map to the pain. Marginal dissatisfaction is not enough.
Unavoidable
Death, taxes — and everything that flows from them. Accounting software succeeded early because payroll and audits were not optional. Regulations keep creating markets (HIPAA, Basel, FDA, derivatives accounting).
Reval example: Fortune 5000 firms tracked derivatives on spreadsheets; the problem was complex, necessary, and regulated. GE took a ~$340M valuation adjustment from bad derivatives accounting — hundreds of millions of dollars of measurable consequence. That is the kind of signal you want in early investigation.
Aging populations (Medicare, care, longevity) are another unavoidable wave.
Urgent (especially for startups)
Startups die one way: they run out of cash. Your urgency must match the customer’s.
A beautiful future vision that depends on three platform shifts outside your control may never arrive on your runway. Urgency is also relative: if your pain is #42 on their list, you will not get attention.
As a startup you are pure risk — even listening costs them. Aim for problems in their top three priorities.
Underserved
Enterprises budget ~12 months ahead (planning starts ~3 months before that). You were probably not in last year’s plan. Buying you means taking budget from something else — a zero-sum game for finite dollars, time, people, and attention.
Compete where few others are already fighting for those same resources. That open area is white space.
Consumers still live under the same constraints
Consumers make more purchase decisions than most businesses — and they do not have infinite dollars. After tax, utilities and subsistence come first. Ask: are you competing for must-have spend or nice-to-have entertainment?
Human-need frames (security, social, physical, economic, recognition, responsibility…) help name addressable problems. Dating industries and Facebook’s early college network both ride the need to connect.
Black-and-white consumer needs
| Type | Character | Example instinct |
|---|---|---|
| Latent | Not on the surface until tapped | iPad — you did not hunt for it five years earlier; remove it now and you are sad |
| Aspirational | Want to look / live a certain way | Fashion, home aesthetics |
| Blatant + critical | Obviously must solve | What B2B investors usually hunt |
White space = blatant critical need that is still underserved, capturable, and defensible uniquely. That is where serious customer and investor attention concentrates.
Disqus: multi-sided consumer value
Disqus became the large commenting layer across ~2M sites — modern “letters to the editor,” real-time community under articles (Wired, CNN, Time…).
- Users: voice opinion, community, loyalty (one click from leaving; a comment pulls them back)
- Publishers: engagement, time on site, ad value — without users leaving the site
- Advertisers / discovery: cross-site interest graph → relevant content discovery (~900M uniques/month at the time of the talk)
Primary product truth: stay user-centric first or the publisher network never forms. Differentiation vs Facebook comments or white-label SaaS: a publisher-centric network you never leave. Grew friction-free (embed tag, often free initially), then monetised discovery and premium at scale. Multifaceted value props are hard to find — and powerful when they work.
Defining the solution: avoid “faster, better, cheaper”
Incremental improvements invite copycats. Faster / better / cheaper lays out the axes on which someone beats you (open source often wins that race in search and elsewhere).
Hunt a breakthrough that changes the game — 2D to 3D. The 3 D’s:
| D | Ask |
|---|---|
| Discontinuous innovation | Is the way of doing it completely different — not a linear step? |
| Defensible advantage | Hard problem → IP, network, data, or process others cannot casually copy |
| Disruptive business model | New economics (SaaS, free + ads, marketplace) that incumbents struggle to match |
uTest: testing used to mean in-house labs or offshore hourly bodies. They built a global community of professional testers (tens of thousands across ~190 countries) and moved from pay-per-hour to fixed monthly SaaS — discontinuous model and discontinuous delivery.
Business-model disruption is underused by founders. Open source and Google’s “software free; users + ads valuable” broke Microsoft’s Wintel comfort — not primarily on technology, but on who captures value.
Startup secret: pick a big fight
Hard problems take similar work whether the market is small or large. If you have done the Four U’s and a real breakthrough, go after a big problem. Game-changers with defensible IP and customer value create room for interesting models and growth.
Evaluate before you fundraise
You are ready for funding when someone will pay for the value prop — not when the slide looks good. Two layers: qualitative, then quantitative.
Qualitative: before → after
Describe the world before your product and after it.
| Frame | Before | After |
|---|---|---|
| Emotion | Acute pain | Absolute joy |
| Product test | Vitamin (nice to skip) | Penicillin (must take) |
Akiban / dating app: complex real-time profile search was slow and forced ~$250k/year re-architecture cycles. Akiban plugs into existing architecture and runs problem queries ~100× faster — relief without rewrite.
uTest evolution (honesty required):
- Early focus: startups in software (discipline + screaming pain in 2008)
- First story: elastic testing (3 → 30 → 300 → 3 testers in a week)
- Real breakthrough (found by asking “why do you keep paying us?” and rejecting polite answers): in-the-wild testing — outside the lab, closer to where users work, live, and play — unlike isolated “crowdsource” that is still a room in Bangalore
Before: build a giant device lab; cannot keep up with carriers, locales, OS, and 200–300 Android combinations (HBO Go–style apps).
After: mirror your user base in the tester pool; catch what lab QA never will (“it worked for us”). Absolute joy for product quality; penicillin for public-facing apps users delete after one bad experience.
Narrow first segments still matter — uTest’s solution spanned verticals later; most startups should start tighter (see Go-to-Market).
Quantitative: the gain–pain ratio
Customers get gain. Founders forget pain of adoption.
Gain (examples)
- Revenue lift, cost savings, time, headcount
- Competitive advantage (leapfrog rivals even if cost-neutral)
- Reputation / community (e.g. Disqus loyalty)
Pain (examples)
- Find → try → buy → implement → deploy → own
- Total cost of ownership (laser printer vs toner)
- Organisational overhead of using you
Apperian: early rollout took 2–3 weeks; customers loved the concept and said “call back in six months.” Live-in-5 cut onboarding to minutes; conversion through the funnel doubled.
uTest pain (rare honesty): good testing is a bad-news business — 40–60 bugs create work for QA and engineering; early crowd meant 35 testers across 14 time zones. They added professional services to wrap results, maximise in-the-wild coverage, and minimise incremental overhead. Things clicked when they stopped maximising gain alone and started minimising pain.
Inertia
Default for buyers facing a startup: do nothing — or build it themselves (often feels less risky than betting on you). Factor “good enough” alternatives into the ratio.
Target ratio: ~10∶1
Order-of-magnitude better gain than pain + risk. One-to-one feels like a vitamin. Iterate until the ratio is significant — eat your own cooking (uTest tested uTest with their own community from day one).
Google Chrome team ROI (shared by uTest): same week, same 300 URLs —
| Traditional onsite vendors | uTest | |
|---|---|---|
| Effort | 8 testers × 40h × 5 days | 30 testers × 10h, done in 2 days |
| Fix-worthy issues | 19 | 129 |
| Cost | ~$15,000 | ~$10,000 |
| Cost per fix-worthy issue | ~$789 | ~$78 |
~10× on cost-per-issue, plus time-to-market and quality — composite gain, not “cheapest vendor” alone.
Estée Lauder / Apperian: push updates to thousands of counter iPads vs ~$2.5M DIY; initial New York tests saw ~400% sales lift because customers trusted guided recommendations from the device more than a pushy associate. Gain–pain made the buy obvious.
Ask these questions long before you hire a sales team or ask for the cheque.
Breakthrough output, non-disruptive adoption
Breakthroughs break things — and broken adoption kills deals. The great pattern: disruptive results, non-disruptive install.
Most database startups demanded application rewrites against billions of SQL investment. Akiban used replication: plug alongside the existing DB, redirect problem queries — no rewrite, fits 24/7 ops, evaluable with low risk. Value prop hinge word: unlike NoSQL-style rip-and-replace.
Results cited: Name Media ~200% revenue lift on performance-bound apps; Citrix security queries ~100× faster enabling viral go-to-market — with no application change.
Put that “unlike” into your template. It is often the line that removes risk.
Building the statement (including not-for-profit)
Same template: who → dissatisfied with what → what you do differently → why unique.
Diagnostics for All (nonprofit): patterned paper (~penny at scale) for point-of-care tests in rural developing-world settings with no conventional medical infrastructure. Dissatisfaction is not “expensive alternative” — it is no diagnosis. Easy to use without US-style clinical staffing. Liver-function enzymes (ALT/AST) for patients on medicines that can destroy the liver; field tests (e.g. Vietnam) backed by governments and foundations (Gates) because payers ≠ patients.
Gain–pain here includes literal medical pain. White space exists partly because beneficiaries cannot pay — so the business/mission model must include governments, NGOs, and philanthropy. The template still works; the actors shift.
The human piece
Slides are not the product. The best value props come from people whose background and experience create an insight advantage, who are passionate about the problem, and who can deliver discontinuous innovation or a disruptive model for reasons they believe.
Believe in yourself. Unlikely stories become companies when founders have conviction in their understanding of a problem. The frameworks then fall into the background as scaffolding — not as the substance.
Recap: what to remember
- Template — for whom, vs what, differentiated solve, unique “unlike”
- Problem before idea — Four U’s; stack as many as you can
- Consumers — same scarcity; latent / aspirational / blatant-critical; hunt white space
- Solution — not faster/better/cheaper; 3 D’s; pick a big fight
- Qualitative eval — before/after → acute pain to absolute joy; penicillin over vitamin
- Quantitative eval — gain vs adoption pain + inertia; aim ~10∶1; reduce friction (slippery products)
- Adoption — breakthrough results with non-disruptive install when you can
- Iterate in the field — Apperian, uTest, Disqus all evolved; listen to why they won’t as hard as why they will
- You — insight, passion, persistence turn the framework into a company
Define tightly, evaluate honestly, then build. Funding and GTM come after the gain–pain story can survive daylight.
Discussion
Comments
Share feedback or questions about this page. No account required.
Loading comments…