Post-session resource · For early-stage founders

Value Proposition:
Design It. Embed It.
Articulate It.

Everything from today's session — deeper, with more examples, richer frameworks, and the thinking that usually only comes from being in the room. Use this to review, refine, and return to.

IA
Ismail Akbani
CEO, AIC Mahindra · Practitioner in Value Design
Value = Gain ÷ Sacrifice Outcome-in · Feature-out VP Design Canvas · 5 Lenses MadLib Template Sacrifice Audit Truth Bombs · Examples · FAQ

What Value Actually Is

And why you've probably only been solving half the equation — the half that matters less.

Here is the most important idea in this entire resource. Most founders, most VP training, and most pitch coaching focuses only on the numerator. The denominator is where most products quietly fail.

The value equation
Value = Gain (Benefits) ÷ Sacrifice (Cost + Friction + Risk + Effort + Identity)
The numerator — what they GET
  • Functional gains — tasks completed, problems solved, time saved
  • Emotional gains — confidence, relief, peace of mind, excitement
  • Social gains — status, recognition, trust from others
The denominator — what they GIVE UP
  • Money — direct cost, hidden costs, switching costs
  • Time — to learn, set up, adopt, and get results
  • Effort — cognitive load, behaviour change required
  • Risk — of failure, of looking foolish, of disruption
  • Identity cost — having to see themselves differently

The trap: more features = more value. Wrong. More features raise the numerator slightly — but if they add complexity, learning curve, or switching cost, they blow up the denominator. The ratio goes down. You worked harder and delivered less.

"A gym membership has enormous value — until you never go. Then it has the value of guilt, with a monthly direct debit. Your product is exactly the same. Until your customer experiences the outcome — it's just a promise."

— Ismail Akbani, CEO, AIC Mahindra

Value is always perceived value

Non-negotiable. If your customer doesn't perceive value — the value does not exist. Your VP's first job is to make value visible and believable — in the customer's language, through the customer's lens, about the customer's transformed life.

The identity cost — the sacrifice nobody maps

Of the five sacrifice types, identity cost is the most underestimated and the most powerful barrier to adoption. If your solution requires someone to admit they've been doing something wrong for years — managing their accounts wrong, running their operations wrong — that's not just a practical sacrifice. It's a blow to how they see themselves.

Design implication

Your product must give customers a face-saving way in. Not a narrative that makes them feel foolish for not finding it sooner — a narrative that makes them feel smart for finding it now.

What value is NOT

Not this

Your product or technology

"We use AI" is not value. Technology is the delivery mechanism. Value is what changes in the customer's life because of it.

Not this

Your team's effort

"We worked 18 months on this." Your customer doesn't care. They care about what changes for them — not how hard you worked.

Not this

What you think is valuable

Only what your customer perceives as valuable counts. Your judgment is irrelevant until it aligns with theirs.

Not this

A fixed thing forever

Value shifts entirely when your target customer changes. Same product, different segment = different perceived value = different VP.

What a VP Is and Is Not

Five things founders confuse it with — and the truth bomb that lands in the middle of it all.

Commonly confused with a VP
Why it's not the same thing
A tagline or slogan
"Swiggy for medicines" is a positioning shortcut. It compresses a category comparison into a phrase — it says nothing about what your customer gets, what they give up, or why you specifically.
A mission statement
"We want to transform healthcare in India" describes what YOU want. A VP is about what THEY get. Your ambition is not their value.
Your USP
USP is about you vs. your competitors. VP is about your customer's life before vs. after. Entirely different lens.
A feature list in disguise
"Fast, reliable, AI-powered, end-to-end" describes attributes. A VP describes the outcome those attributes make possible — in the customer's world, not yours.
One fixed sentence forever
When your TG changes, your VP changes. Same product, different segment = different perceived value = different VP. This is clarity, not confusion.
Mid-session truth bomb

"Your value proposition has nothing to do with your product. It lives entirely in your customer's world — in their transformed life after your solution, not in the solution itself."

The implication is real and practical: if you haven't deeply defined your target customer, you cannot have a VP. You only have a product description. The same product can have three completely different VPs for three different customer segments. Same features. Different lives. Different value. Different VP.

The drill insight — one level deeper than Levitt

Theodore Levitt said: "People don't want a quarter-inch drill. They want a quarter-inch hole." True — but even that's not deep enough.

Surface
They don't want the drill — that's the product
Output
They don't want the hole — that's the functional output
Object
They don't even want the shelf — that's still a physical object
Real job
They want the feeling the shelf creates — the compliment, the sense of competence, the end of the guilt of the undone job

"When you write your VP, ask: am I describing what my product does — or what my customer's life looks, feels, and sounds like after they use it?"

The VP Design Canvas

5 lenses. Outcome-in, feature-out. The only VP framework that starts where the customer's life actually is.

Most VP frameworks start with your product and work outward. This canvas starts with your customer's world and works inward. That's not a small difference — it's the entire point. You cannot design value by staring at your own product. You design it by understanding what needs to be true in a specific customer's life.

Direction of the canvas

Customer's Real Job → Sacrifice Audit → Outcome Craved → Value Gap → Value Embedded in Design. Always customer-in. Never product-out.

Lens 01 The Real Job What are they actually trying to get done?
  • Functional job — the task they're trying to complete. The surface level. What they'd write on a task list.
  • Emotional job — how they want to feel during or after. This is where loyalty lives — and where most founders never look.
  • Social job — how they want to be perceived by others. Status, recognition, trust from people they care about.
  • The problem behind the problem — the real anxiety or desire one level deeper than the obvious answer. This is where insight hides.
Worked example — legal contract tool for first-time founders
  • Functional: Create a valid client agreement
  • Emotional: Not feel vulnerable, incompetent, or exposed
  • Social: Look professional and trustworthy to the client
  • Real driver: Fear of missing something they didn't know to look for — and being taken advantage of
The question that unlocks this lens

"What is the emotional job behind the functional job?" Most founders stop at functional. The emotional job is where loyalty lives.

Lens 02 The Sacrifice Audit What are they currently giving up to get this done?

This is your denominator — fully mapped. Most founders map money and time. The other three are where most adoption failures hide.

  • Money — direct cost, indirect cost, switching cost from current solution
  • Time — to evaluate, learn, set up, and get results. Plus time lost if it fails.
  • Effort — cognitive load of a new system, behaviour change required, integration complexity
  • Risk — risk of the product failing, risk of looking foolish for choosing it, risk of disrupting what currently works even imperfectly
  • Identity cost — does adopting your solution require them to see themselves differently? To admit past error? This is the most underestimated barrier.
Sacrifice typeWhat it often looks like in Indian startup contextDesign implication
Money
A kirana owner switching from manual khata to software — ₹499/month isn't the real cost. The accounting role they'll no longer need a family member for is.
Budget conversations aren't just about price — they're about what else has to change.Make the full cost of switching transparent and small.
Time
A factory owner trialling a compliance tool during peak production season — even 2 hours of setup at the wrong moment is a dealbreaker.
When adoption is asked for matters as much as how much effort it takes.Offer progressive onboarding, not a cliff.
Effort
A D2C brand switching from WhatsApp order management to a dashboard — requires 6 people to change their daily routine simultaneously.
Behaviour change at scale is exponentially harder than individual change.Reduce the number of people who need to change at once.
Risk
A CA recommending a fintech product to clients — if it fails, it's their reputation on the line, not just the client's money.
For B2B, identify whose reputation is at stake — not just whose money.Make risk deniable: "Even if it doesn't work, you look smart for trying."
Identity cost
A second-gen family business owner adopting formal HR software — doing so implicitly says the informal way their parent built the business "wasn't good enough."
The most invisible barrier. Often explains inexplicable churn and stall.Give them a face-saving narrative for why now is the smart time.
Insight

Reducing sacrifice creates value just as much as adding benefits — often more. A product that removes one major sacrifice is more valuable than one that adds five minor benefits.

Lens 03 The Outcome They Crave What does success look, feel, and sound like to them?
  • Write this in their language — not yours. If you use technical terms, product jargon, or startup vocabulary — start again.
  • Describe the before state and after state — specifically and vividly. Not in category terms. In life terms.
  • The proof test: would your target customer say "that's exactly me" — or "sort of me"? Sort of means you've described a category. Exactly means you've described a person.
  • The 3am test: what is the problem your customer lies awake worrying about? That is your outcome — not the polite version they mention in a meeting.

Before / After example — compliance software for small manufacturers

Before your solution
  • Sunday afternoon lost to compliance paperwork
  • Anxiety between submissions about missing something
  • ₹8–12k every quarter to the CA, always reactive
  • One surprise notice away from a crisis
  • Never confident about what's due and when
After your solution
  • Zero mental energy spent on compliance
  • Proactive alerts — nothing sneaks up
  • ₹1.5k/month, handled in 12 minutes
  • Feels like someone who genuinely has this handled
  • Can walk into a bank meeting without dreading questions
Lens 04 The Value Gap Where does every current solution fall short?
  • Map all alternatives honestly — not just direct competitors. Include doing nothing, hiring a person, using a workaround, an adjacent tool. That's the real choice set.
  • Find the consistent failure — what is the one thing none of these deliver on Lens 3? That gap is your real differentiation — not your feature list.
  • Caution — table stakes aren't gaps: "We're cheaper" or "we're faster" can be copied in 6 months. Find the gap that requires structural advantage to close.
  • The honest test: could your top competitor read your value gap description and say "that's not us"? If they couldn't — you haven't found your real gap yet.
The question that finds the gap

"What is the one thing your customer needs that nobody — including you right now — is fully delivering?" If you can answer that precisely, you have your differentiation. If you can't, go back and talk to more customers.

Lens 05 The Value Embed How does your product's design actually deliver on lenses 1–4?

This is the lens nobody teaches. It separates products that earn loyalty from products that earn good reviews — and then get churned.

  • Value embed vs. value claim — anyone can claim value in words. Embedded value is felt without being told. The customer experiences the outcome; they don't just hear about it.
  • The sacrifice reduction test — go through your feature list. For each feature: does this reduce a sacrifice from Lens 2, or add a new one? Redesign or remove anything that increases sacrifice without proportional gain.
  • The first 90 seconds — a new user experiences your VP in their first 90 seconds with your product. What do they feel? Does it match what you promised?
  • The zero-word test — if a new user used your product for 5 minutes without reading any marketing, would they feel the value? If not — the value isn't embedded, it's described.
The hard truth

Any startup can hire a copywriter to articulate value. But articulation without embedded value is a promise your product can't keep. Customers forgive many things. They don't forgive feeling deceived by the gap between what you promised and what they experienced.

The MadLib Template

Articulation comes after design — not instead of it. Five blanks. Every blank maps to a lens. Every hard blank is diagnostic.

"We help specific customer in a specific situation get real job done / outcome craved without biggest sacrifice — unlike current alternative which fails to close the value gap."
We help
Who exactly? In what situation? "SMEs" is not a customer. "First-time founders signing their first client" is a customer.
Get
What outcome do they crave — in their words, not yours? If you're using product language here, start again.
Without
What is their single biggest sacrifice? Pick one — the most important. This is Lens 2.
Unlike
What alternative do they actually use today — not your direct competitor, their real current choice?
Which
The specific, honest way the current alternative fails them. One sentence. Precise. This is your value gap.
What the MadLib is actually for

This is not a magic sentence generator. It's a diagnostic tool. Every blank that's hard to fill is telling you exactly where your VP work is unfinished. A blank you can fill with vague language ("small businesses", "better experience") means that blank is still hollow. Ruthless specificity is the whole point.

Weak vs. Strong VPs

Same products. Completely different impact. Study the pattern — then apply it to yours.

Example 1 — Compliance software for small manufacturers

Weak VP
We provide an AI-powered compliance management platform for SMEs with real-time alerts, automated reporting, and end-to-end workflow management.
Strong VP
We help small manufacturing unit owners file their quarterly compliance without spending a single hour on it or losing sleep over surprise notices — unlike their CA, who they only hear from after something goes wrong.

What changed: The weak VP describes product attributes (AI-powered, real-time, automated). The strong VP describes the customer's life (no hours, no lost sleep, proactive vs. reactive). Notice — the strong VP doesn't mention AI. Technology is the how. The VP is what changes.

Example 2 — Legal contract tool for early-stage founders

Weak VP
A fast, easy, legally sound contract creation tool for startups. Generate professional agreements in minutes using smart templates.
Strong VP
We help first-time founders send their first client agreement without spending three hours on a Sunday piecing something together they're not sure is right — unlike Google Docs templates, which leave you wondering what you've missed that you didn't know to look for.

What changed: The weak VP is about speed and ease — features. The strong VP is about the Sunday afternoon, the uncertainty, the specific fear. That's the emotional job. That's where the customer actually is.

Example 3 — Inventory management for D2C brands

Weak VP
An intelligent inventory and order management system for D2C brands. Real-time sync across channels, automated reorder triggers, and actionable analytics.
Strong VP
We help D2C founders stop manually reconciling orders across WhatsApp, Shopify, and their warehouse every Monday morning — unlike spreadsheets and scattered screenshots, which mean they're always one missed message away from an angry customer and an out-of-stock crisis.

What changed: "Monday morning", "WhatsApp, Shopify, and their warehouse", "one missed message" — customer language. The founder didn't need to be told it's intelligent or real-time. They needed to feel seen. That's what a strong VP does.

"If your VP would be equally true said by your top competitor — it's not a VP. It's a category description with your logo on it."

The 3-sniff test — before you share with anyone

Test 01

The 3-second test

Read it to someone who doesn't know your startup. In 3 seconds — can they tell you who it's for and why they'd care? If they need context, it's not done.

Test 02

The customer test

Would your target customer say "that's exactly me" — or "sort of me"? Sort of means you've described a category. Exactly means you've described a person.

Test 03

The competitor test

Could your top competitor copy your VP and have it be equally true for them? If yes — your differentiation isn't in your VP yet. Keep going.

Dos, Don'ts & Truth Bombs

The distilled wisdom — from working with founders in the trenches, not from reading about it in comfort.

Do
  • Start with the customer's world. Then work back to your product.
  • Define your target customer before writing a single word of your VP.
  • Write from the outcome backward — what does their life look like after?
  • Test with actual potential customers — not co-founders or friends.
  • Have a different VP for each meaningfully different customer segment.
  • Revisit your VP every time your customer understanding deepens.
  • Reduce the denominator as deliberately as you increase the numerator.
  • Embed value in product design — not just in marketing language.
  • Look for the emotional and social job — not just the functional one.
Don't
  • Start with your features and work outward — that's a product description.
  • Use jargon, technical terms, or product language in your VP.
  • Confuse your mission ("what we want") with your VP ("what they get").
  • Mistake a tagline for a VP — "Swiggy for X" is positioning, not value.
  • Make "cheaper" or "faster" your differentiator without structural advantage.
  • Ignore identity cost — the most powerful and least visible adoption barrier.
  • Let your VP change every time you're asked — unfinished canvas work.
  • Write one VP and assume it covers all segments. It doesn't.
  • Confuse articulation with design — a beautifully written VP for a poorly designed product is a lie.

Truth bombs

"Your VP is not about what you built. It's about what changed."

"If you can't describe your customer's life before and after your product in their words — you don't have a VP yet. You have a feature hypothesis."

"A fancy articulation of a vague value proposition is just well-dressed confusion. The words got sharper. The thinking didn't."

"Adding features to increase value is like adding ingredients to a recipe that's already too complex. Sometimes subtraction is the innovation."

"If your VP would be equally true said by your top competitor — it's not a VP. It's a category description with your logo on it."

"Most founders build the product they want to build, then search for the customer who wants it. The VP Canvas forces you to reverse that — and that reversal is everything."

Witty but true

Every startup says they're 10x better. Customers are still using the thing they said they were 10x better than.
Your pitch deck has a beautiful VP slide. Your onboarding flow contradicts every word of it. That's the real problem.
Asking your co-founder if your VP is clear is like asking your mum if your business idea is good. They love you. They're not the customer.
The product you built is not the product they bought. Figure out what they actually bought — that's where your VP lives.
"We're building for everyone" means you've deeply understood no one. The more specific your VP, the larger your real market.

Your Action Plan

Three things to do before this session's energy fades. Not twenty. Three.

Tonight

Run the Sacrifice Audit

List every cost, friction, effort, risk, and identity cost your customer takes on to use your product. Ask: which of these am I genuinely reducing? Which am I accidentally making worse?

Tomorrow

Write your MadLib

Not perfect. Written. Share it with one potential customer — not a co-founder, not a friend. Ask: "Does this sound like your life?" Listen for "exactly" versus "sort of".

This week

Audit your feature list

For each feature: does it reduce sacrifice from your Sacrifice Audit — or add a new one? Redesign or remove anything that increases sacrifice without proportional gain increase.

Three questions to keep asking — forever

Question 01

Functional or emotional?

Am I solving the functional job, the emotional job, or both? The emotional job is where loyalty lives. The functional job is where initial adoption lives.

Question 02

Both sides of the equation?

Am I reducing sacrifice as actively as I'm adding benefit? Every product decision changes both sides of the equation — map both, every time.

Question 03

"That's me" or "sort of me"?

Would my target customer read my VP and feel seen — or feel approximately described? The difference between those two is the difference between conversion and consideration.

Questions Founders Always Ask

The ones people think are too basic to ask in a session. They're not. They're the most important ones.

My product has multiple customer segments. One VP or many? +
One per meaningfully different segment. "Meaningfully different" means the job, sacrifice, outcome, or gap is substantially different. Same product, different life context = different VP. Start with your highest-value or most traction-generating segment. Get that VP sharp. Then go to the next. This is not confusion — it's customer clarity.
I'm pre-product / pre-revenue. Can I even have a VP? +
Yes — and this is the most important time to have one. A pre-product VP is a hypothesis. It says: "We believe that [specific customer] needs [this outcome] and that no current solution delivers it." That hypothesis is what you're testing with every customer conversation, every build decision, every iteration. A startup without a VP hypothesis is building without a compass.
My VP keeps changing. Is that a problem? +
It means you're learning — which is correct at early stage. A VP that never changes means you've stopped listening to customers. The goal is a VP that gets more specific and more true over time. The problem is when it changes because you're adapting to whoever you're pitching to in the moment — that's shapeshifting, not learning. Know the difference.
How do I know if my VP is actually working? +
Three signals: (1) When you share it with your target customer, they say "that's exactly my situation" without you explaining further. (2) Your sales conversations get shorter — prospects self-select and arrive already partially convinced. (3) Your churn decreases because the customers you attract are the ones your product was designed for. If none of these are happening, either the VP is wrong or you're not reaching the right customer yet.
What's the difference between a VP and a positioning statement? +
VP is the promise of value to the customer — it's about their life. Positioning is about where you sit in the market relative to alternatives — it's about your competitive context. A good VP informs your positioning. Think of it this way: the VP answers "why should I use this?" and positioning answers "why should I choose this over that?" Build VP first. Positioning follows from it.
Do investors care about VP? +
Yes — but not in the way most founders present it. Investors don't care about your VP statement. They care about the evidence that you understand your customer deeply enough to have one. The signal they're reading: does this founder know exactly who they're building for, what that customer needs to be true, and why their approach closes the gap nobody else has? A sharp VP is evidence of that understanding.
How long should a VP be? +
Long enough to be specific. Short enough to be remembered. The MadLib is deliberately one sentence — not because one sentence is the goal, but because forcing it into one sentence reveals where your thinking is still vague. Vague areas expand to fill available space. If you need more than two sentences, you haven't found the specificity yet.