Business Model Canvas Framework · CHAPTER 3 OF 6
Value propositions and customers
Step 1
Understanding the value proposition
Start With the Value the Product Must Deliver
The value proposition explains why customers choose the product.
Do not document only what the software does.
Understand what problem it solves, what outcome it creates, and why that outcome matters to the customer.

why that outcome matters

what outcome it creates

what problem it solves

Start With the Value the Product Must Deliver
The value proposition explains why customers choose the product.
Do not document only what the software does.
Understand what problem it solves, what outcome it creates, and why that outcome matters to the customer.

why that outcome matters

what outcome it creates

what problem it solves

Features Are Not Value Propositions
Features Are Not Value Propositions
Feature
Manage multiple electricity connections.
Value
Lets users view and pay bills for multiple connections from one place, reducing repeated effort and dependency on physical offices.
Feature
Manage multiple electricity connections.
Lets users view and pay bills for multiple connections from one place, reducing repeated effort and dependency on physical offices.
Value
Ask
What problem is the product solving?
What becomes easier, faster, safer, or more reliable?
What risk does the product reduce?
What outcome is the customer paying for?
Why would customers choose this product?
What becomes easier, faster, safer, or more reliable?
What problem is the product solving?
Ask
What risk does the product reduce?
What outcome is the customer paying for?
Why would customers choose this product?
Example: Telangana Electricity Bill App
The app is designed to make electricity services easier and more accessible for users.
Secure and easy bill payment
Managing multiple connections
Real-time usage and bill updates
Applying for new connections
Raising and tracking complaints
Accessing previous bills and receipts


The value for users is:
Example: Telangana Electricity Bill App
The app is designed to make electricity services easier and more accessible for users.
The value for users is:
Secure and easy bill payment
Applying for new connections
Managing multiple connections
Raising and tracking complaints
Real-time usage and bill updates
Accessing previous bills and receipts



Paperwork
Costs

Printing costs

Distribution costs

Dependency on physical offices

Overall operational effort
The same value benefits
the Electricity Board by reducing:
The same value benefits the Electricity Board by reducing:

Paperwork Costs

Printing costs

Distribution costs

Dependency on physical offices

Overall operational effort
Why You Need to Understand the Value Proposition
During a redesign, the value proposition helps designers understand what the product must ultimately deliver.
It guides which workflows to improve, which features to prioritise, and whether each design decision strengthens the value promised to users and the business.
Experience
Product
Value
Proposition
Brand
Why You Need to Understand the Value Proposition
During a redesign, the value proposition helps designers understand what the product must ultimately deliver.
It guides which workflows to improve, which features to prioritise, and whether each design decision strengthens the value promised to users and the business.
Experience
Product
Value
Proposition
Brand
Identify Customer Segments
Step 2
Identify the Target Audiences the Software Serves
Who are we designing and delivering this software for?

Customer Segments help answer:
Identify the Target Audiences the Software Serves
Who are we designing and delivering this software for?

Customer Segments help answer:
For the Telangana Electricity Bill App, the customer segments include

Residential users

Small-business users

Rural households

Senior citizen

Differently-abled users

Tech-savvy users
For the Telangana Electricity Bill App, the customer segments include

Rural households

Senior citizen

Small-business users

Differently-abled users

Residential users

Tech-savvy users
Understanding the Needs of Different Users Is Important
Each customer segment has different needs and behaviours.
Understanding these differences helps the redesign provide the right workflows, content, guidance, and accessibility for each segment.
A solution designed for one segment can also benefit other users in similar situations.





Understanding the Needs of Different Users Is Important
Each customer segment has different needs and behaviours.
Understanding these differences helps the redesign provide the right workflows, content, guidance, and accessibility for each segment. A solution designed for one segment can also benefit other users in similar situations.





Customer Segments Influence
Language and content
Accessibility
Account management
Guidance level
Workflow priorities
Notifications
Onboarding
Device support
Account management
Language and content
Customer Segments Influence
Device support
Guidance level
Accessibility
Workflow priorities
Notifications
Onboarding
Why Customer Segments Matter in Redesign
Knowing the specific customer segment helps designers understand who they are designing for.
This makes it easier to create workflows, features, content, and onboarding that match their needs, behaviours, and expectations.




Why Customer Segments Matter in Redesign
Knowing the specific customer segment helps designers understand who they are designing for.
This makes it easier to create workflows, features, content, and onboarding that match their needs, behaviours, and expectations.




Map the Channels
Step 3
Understand How Customers Reach the Product
Channels explain how users get to know about the software, access it, and continue receiving information from it.
Mapping these entry points helps designers create a connected journey from first awareness to continued use.
Discover the product
Evaluate it
Purchase it
Access it
Receive onboarding
Get support
Continue using it
Understand How Customers Reach the Product
Channels explain how users get to know about the software, access it, and continue receiving information from it.
Mapping these entry points helps designers create a connected journey from first awareness to continued use.
Discover the product
Evaluate it
Purchase it
Access it
Receive onboarding
Get support
Continue using it
Channels May Include
Channels are every touchpoint through which customers discover, evaluate, access, and receive support for the product.

Website

Sales team

Product demos

Mobile application

Desktop software


Customer support

Implementation partners

Training sessions

Physical service centres
Channels May Include
Channels are every touchpoint through which customers discover, evaluate, access, and receive support for the product.

Website

Sales team

Product demos

Mobile application

Desktop software


Customer support

Implementation partners

Training sessions

Physical service centres
The channel list for the Telangana Electricity Bill App:
Applying for new connections
Raising and tracking complaints
Accessing previous bills and receipts

Electricity Board website

WhatsApp notifications

SMS notifications

iOS Application

Mee Seva centres

Android application

Information printed on electricity bills
Applying for new connections
Raising and tracking complaints
Accessing previous bills and receipts


The channel list for the Telangana Electricity Bill App:

Electricity Board website

WhatsApp notifications
Applying for new connections
Applying for new connections

SMS notifications

iOS Application

Mee Seva centres
Raising and tracking complaints
Raising and tracking complaints

Android application

Information printed on electricity bills
Accessing previous bills and receipts
Accessing previous bills and receipts


The Software Experience Starts Before Login
Users might discover the app through the Electricity Board website or their bill.
The app should feel familiar, while SMS and WhatsApp continue the journey through reminders and updates. Otherwise, the experience will feel disconnected.

The Software Experience Starts Before Login
Users might discover the app through the Electricity Board website or their bill.
The app should feel familiar, while SMS and WhatsApp continue the journey through reminders and updates. Otherwise, the experience will feel disconnected.

Understand Customer Relationships
Step 4

Records Under review
Check records

Records Approved Successfully
Check records

Records Approved Successfully
Check records
Define How the Software Supports Its Users
Customer Relationships describe the level of support, communication, guidance, and personalisation users should receive throughout their journey.
Define How the Software Supports Its Users
Customer Relationships describe the level of support, communication, guidance, and personalisation users should receive throughout their journey.

Records Under review
Check records

Records Approved Successfully
Check records

Records Approved Successfully
Check records
For the Telangana Electricity Bill App, this may include
Easy self-service
Chatbot support
Due-date and outage
notifications
Personalised energy-
saving tips
Complaint registration
and tracking
FAQ and self-help
content
Complaint registration and tracking
Due-date and outage notifications
For the Telangana Electricity Bill App, this may include
Personalised energy- saving tips
FAQ and self-help content
Easy self-service
Chatbot support
Turn the Relationship Into Product Requirements
1
The chatbot should solve common queries and escalate when human support is needed.
2
Users should receive clear payment confirmations.
3
Complaint and new-connection requests should show progress.
4
Users should receive timely bill, outage, and service updates.
The product experience should support the relationship the business wants to build.
Turn the Relationship Into Product Requirements
The product experience should support the relationship the business wants to build.
The chatbot should solve common queries and escalate when human support is needed.
Users should receive clear payment confirmations.
Complaint and new-connection requests should show progress.
Users should receive timely bill, outage, and service updates.
1
2
3
4
A Mismatch Creates Operational Cost
A company may want a scalable self-service model.
But if the product requires repeated training and support, the actual customer relationship remains high-touch.
This mismatch increases onboarding time, support dependency, and cost.






A Mismatch Creates Operational Cost
A company may want a scalable self-service model.
But if the product requires repeated training and support, the actual customer relationship remains high-touch.
This mismatch increases onboarding time, support dependency, and cost.





