The right business model for your product

How would you decide what is the best business model for your product?

Deciding on the right business model is very important for the product. It does not necessarily mean what is the price of your product.

There could be no price for your product - though that is a myth. For example, we think google or Facebook is free. However, we are never the customers for Google or Facebook. It is the advertisers that are its customers.

What we need to figure out when we decide on a business model are as follows:

Who is my target audience?
Who is my customer
What is the price.
How is the support model going to work
Who are my partners

While we do not absolutely need to price a product, we need to understand how we would make money. For example Open ERP does not price its product. However, its product is not the ERP software but really the hosting, service and training that it offers.

While pricing is an important part, what is more important is in realising who is your real customer and what is your real product.

You might not have your product till you are working on your by-product - which is the software that most of the IT product managers like me are working on.

Check out the following to help you out:

Business Model Generation: A Handbook for Visionaries, Game Changers, and Challengers

Lean Canvas

Comments

My Journey in Inquiry and Advocacy - An experience report

It is recently that I have consciously started practicing Inquiry. Let me explain. I am a consultant who constantly looks at the situation and comes up and implements the solution to progress from there. While I do that, I constantly use Inquiry as a means to progress - one of the key facilitation technique specifically in multiple stakeholder situations.

Principles for developing systems that are anti-fragile

I have been trying to make sense of what anti-fragility means and how do I use that in my day job. As a Business Principal, I tend to work with the abstract but orchestrate a program of work that needs details. This makes my job a little difficult in the terms of designing for more self-preserving systems that preserve the spirit of the abstracted strategy or vision. I came across an article from Daniel Russo on anti-fragility and his attempt at creating a manifesto similar to the manifesto for agile software development. For more reading on Daniel Russo, here is his profile: http://djrusso.github.io More reading from his paper here: https://www.sciencedirect.com/science/article/pii/S1877050916302290 This post is an attempt for me to understand what goes into developing a program that uses every opportunity to strengthen itself and achieve its objective - the vision. I liked the approach of principles for developing systems that are anti-fragile. It is a very valua

User Personas

User Personas are a very good tool for the product owners, business analysts or product managers to be able to co-create with designers. It is predominantly a product of the user research and should not be an amalgamation of demographic data. It is the best way for us to list all scenarios that a persona would take when they want to attain a goal. It is predominantly used to build empathy with user, focus the team and build consensus in a large diverse stakeholder group. The website I referred to is here: https://www.smashingmagazine.com/2014/08/a-closer-look-at-personas-part-1/

Life of a Business Principal in Consulting

Search This Blog