Business Model Canvas
Who are our Key Partners?
Who are our Key Suppliers?
Which Key Resources are we acquiring from partners?
Which Key Activities do partners perform?
MOTIVATIONS FOR PARTNERSHIPS
Optimizations and customer
Reduction of Risk and Uncertainty
Acquisition of particular resources and systems
Who Key Activities do our value propositions require?
Our Distribution Channels?
What Key Resources do our Value Propositions require?
Our Distribution Channels?
TYPES OF RESOURCES
Intellectual (brand patents, copyrights, data)
What value do we deliver to the customer?
Which one of our customer's problems are we helping to solve?
What bundles of products and services are we offering to each Customer Segment?
Which customer needs are we satisfying?
"getting the job done"
What type of relationship does each of our Customer Segments expect us to establish and maintain with them?
Which ones have we established?
How are they integrated with the rest of our business model?
How costly are they?
Dedicated personal assistance
Through which Channels do our Customer Segments want to be reached?
How are we reaching them now?
How are our Channels integrated?
Which ones work best?
Which ones are most cost-efficient?
How are we integrating them with customer routines?
How do we raise awareness about our company's products and services?
How do we help customers evaluate our organization's Value Proposition?
How do we allow customers to purchase specific products and services?
How do we deliver a Value Proposition to customers?
How do we provide post-purchase customer support?
For whom are we creating value?
Who are our most important customers?
What are the most important costs inherent in our business model?
Which Key Resources are most expensive?
Which Key Activities are most expensive?
IS YOUR BUSINESS MORE:
Cost Driven (leanest cost structure, low price value proposition, maximum automation, extensive outsourcing)
Value Driven (focused on value creation, premium value proposition)
Fixed Costs (salaries, rents, utilities)
Economies of scale
Economies of scope
For what value are our customers really willing to pay?
For what do they currently pay?
How are they currently paying?
How would they prefer to pay?
How much does each Revenue Stream contribute to overall revenues?
TYPES OF PRICES:
Product feature dependent
Our mission is simple; develop a UI friendly web platform that helps people manage, monitor, finance, and transfer risks simply. We aim to enable monitoring of a risk portfolio holistically and dynamically. As our platform grows in functionality, our aim to use the data collected and insights gleaned from the Risk Management process to build, provide, and support our clients with valuable data and risk reduction resources such as checklists, SOP’s, inferences, etc.
1 year deductible claims period
Claim after the fact coverage, come and get on payback plan, returns split into pool and grows pool, then funds beyond added are available as risk capital, and able to use supply chain network in built. Build in supply chain.
Include all and vendors can sign up to take control for account, and then make bids and help on cases easily.
diamond facets 1-8
Main Iteam - description
○ State the problem
○ Have you experienced the problem yourself
○ Can you define the problem narrowly
○ Who's your customer
Who's the ideal first customer
Create system with code access for access to NDA & review of business, make special biz cards to give access for tracking access via code implementation - sensitive area
○ The product marketing mix (or 7p's)
Premium vs. Low cost pricing
Price sensitivity - how much customers willing to pay - optimal price point - indifference price point - elasticity
○ Legal structure
Server + costs
○ Customer Model
Android App Dev (deprecated, to keep as Web App only for the time being)
iOS App Dev (deprecated, to keep as Web App only for the time being)
Also known as technical spec
People working on
High Level summary
Descripttion of problem at hand
Goals and non goals
Describe user driven impact of project
Specify how to measure success using metrics. Bonus points linking to dashboard
Sign off process
Current user interaction and how data will flow through it
User story is great way to frame
Proposed solution (technical architecture)
testabilitiy, monitoring, alerting
cross team impact
detailed scoping and timeline
Partner Social Sites for Product marketing