Showing posts with label Finance. Show all posts
Showing posts with label Finance. Show all posts

Tuesday, April 19, 2016

modeling your business - projects, products, prospects, markets

What are the fundamental elements of modeling a business?


I often help people figure out how to model and value their business concepts.  A really common concern is "My business is different!"  That rallying call often serves as the number one roadblock people have when trying to build a business analysis.

The fact is this: No matter how different your business is, it's different in one of the same few ways.


All businesses expect to have customers.  All business hope to deliver something of value to their customers.  All businesses do some up-front work in order to have that valuable thing and to make sure their customers know about that valuable thing and to actually deliver the thing to them.  Whether the thing is physical (like a car, a microchip, a refrigerator, a satellite or a pencil) or a service (like a hair cut, consulting, vacation experience, healthcare), or something intangible like software doesn't matter.  The fundamental economics are the same.

If your business doesn't look like this--well you don't really have a business.


So let's take that "my business is different" issue another step.  How is your business not different?

Products

You have (or will have) something that you want to sell.  If it is a tangible, physical product, it probably has some sort of manufacturing cost associated with it.  You should get an idea of how much each unit you sell will cost to produce and deliver to customers.  This is the variable cost of manufacture, or "unit cost" for short.  Unit Costs will sometimes scale as a function of learning curves or economies of scale, and sometimes they'll just stay flat.  Sometimes (like software) this number will be zero.

Fixed Costs

In addition to the variable cost of manufacturing, you'll have overhead.  Maybe you need to build a factory in order to produce your product.  Maybe you need to build a brick and mortar store as a venue for providing haircuts.  Whatever it is, you will have some fixed costs.   This is often called PPE for Property, Plant and Equipment.  PPE will almost always scale with your expected volume, but with the critical distinction that you have to make your investment in PPE before your volume starts to realize.

Projects

Your business will probably require some spending up front that doesn't go into PPE.  Sometimes this is called RND (Research 'n' Development), sometimes it's called NRE (Non-Recurring Engineering), sometimes it's just called "Spending".  Whatever you call it, this is what you have to invest in time and people-hours and other expense items in order to get to the point where you're ready to start bringing your product to your customers.

Markets

You have customers who are (presumably) going to find your product valuable and pay you for it.  Smart companies undergo an exercise called "Market Segmentation", where they try to group their customers together into meaningful groups called markets.  Members of these markets have similar buying behaviors.  They typically value the same aspects of the products and are willing to pay similar amounts.  For purposes of business forecasting, you should take an "outside in" look at your markets and a great deal of your analytical work will be done just trying to size these markets.  How many potential customers are there in each market?  How many of them will make a buying decision in any specific quarter (or year)?

Prospects

To build a predictive business model you need to make forecasts about how well the products you're creating will be received by the markets you have characterized.  This is a "Prospect" -- the specific economic expectations for an individual product with an individual market.  You will spend most of your business analysis time on forecasting prospects.  When will this product hit this market?  How much market share can we hope to achieve?  How quickly do we think we will achieve our peak market share?  How long before we see that peak share get eroded away--either cannibalized by our own subsequent products or defeated by competitive ones?  What sort of prices will we be able to command for the products?  How will the price and the market share forecasts interrelate?

These are the fundamental elements of analysis for any business.  

Before folks should start thinking about how their business is different and how their model won't fit into a typical analysis, they should address these questions and frame the business through these lenses.  After these basics are sorted out, you should start worrying about things like competitive timing, synergies and roadmap effects, market saturation and disruptive effects, complex pricing structures and so on.  Normally those sorts of details won't move the needle on the big analysis.

This isn't to say that the more detailed analyses aren't necessary.  If you're in the middle of negotiating tiered pricing discounts with an important customer you should really figure out what those will mean to your revenue and NPV expectations.   Those things can wait until later.

Next time I'll put up some materials one the mechanics of using these essential entities to create an NPV.

Tuesday, February 23, 2016

Will your project survive in a big company?

This is based almost completely on work by this guy:
http://www.thomasthurston.com/

He found 8 questions that will effectively predict whether your new business line will succeed in a large organization.  I've paraphrased them and reworked them a little according to my experiences.  It has been a while since I've seen the originals...

  1. Are the margins big enough to be interesting?  (Interesting >= current margins)
  2. Are the markets you're serving big enough to be interesting? (Revenue contribution >= current revenue * 1%)
  3. Does the project help sell products the biz is already selling?
  4. Is the product in a market category we already participate?
  5. Does the program help combat a top competitor?
  6. Is the target market available through current primary channels?
  7. Is there no perceived threat to an existing top customer?
  8. Is there no perceived threat to an existing, power internal group?
If you can answer "YES" to everything, congrats!  You may survive the business funding cycle!
If you score one "YES" you're looking at a 50/50 chance of surviving each funding cycle.
If you score two "YES" answers... well, forget about it.

You might have a great business concept, a wonderful go-to-market strategy, and competitive products that serve a real market need.  If the corporate anti-bodies are going to reject you... you'll be rejected.

I have seen this happen several times.  There are reasons for a lot of this behavior.

For example, if this margins are too small, it will drag down the company's margins and starts to look like a growth trap.  From a strict-finance perspective, you're lowering the effective return for shareholders.

Most of what you see there are questions that are associated with diversifying the business.  Expanding into new markets, serving new customers (or pissing off old ones), attacking new competitors, etc. -- these are all outside the core and scary and difficult to do.

This is why big companies often fail to thrive.

Tuesday, January 12, 2016

Important questions to ask when reviewing an analysis

Over the years I have had the opportunity to participate in many, many valuation exercises.  I have been asked to review or assist with many more.  In time, I have built up the following list of "review concepts" -- questions to ask and things to look out for when checking out somebody's work.  It's a good list to check my own work, too.

I'll just dump the list here, and maybe add some commentary in the comments.

Sources of Data
  • Are all sources for inputs cited, with the name of the source and the date of collection?
  • Is the data still recent?
  • Do the numbers align with commonly accepted inputs from other sources, especially those that are "company dogma"?
  • Is there good, historical research to support the forecasts?
  • When estimating market sizes, are the market segments in the model defined specifically enough to be meaningful?

Time Horizon

  • Does the model forecast the full spending horizon (or is there a spending hockey stick that occurs just after the model cuts off)
  • Does the spending model comprehend all required spending (or just direct spending in this organization), common pitfalls I have seen in the past include:
    • make sure you don't forget software spending!
    • make sure you don't forget support spending!
  • Does the model exclude terminal value (there is no excuse for terminal value these days)

Uncertainty

  • Is there a "Tornado"?
    • are the drivers of critical uncertainty at the top of the tornado well understood?
    • Are all the "usual suspects" present in the tornado?  From my experience, these are:
      • Market Share
      • Price
      • Completion Date
  • Do all of the important inputs have ranges defined for their inputs?
  • Is the Prospect start date (first volume) mechanically tied to the Project completion date (it should be!)

Interdependencies

  • Are key dependencies on other programs or investments comprehended?
  • Are major sources of risk external to the program identified?
    • "Roadmap Risk" -- the risk that key ingredients from other partners will not be done on time or will be cancelled outright.
    • "O/S Risk" -- the risk that the assumed operating system for the product will be irrelevant by the time it's done
    • Competitive Risk -- the risk that a new competitor will appear, or that an existing competitor will change strategies
    • Technical Risk -- the outright risk that we won't be able to complete the product at all.

Business model drivers (for new ideas)

  • Is the value proposition for the product or service well understood?
  • Do we understand what our customers want and how to reach them?
  • Is the cost structure realistic?
  • Are there regulatory issues we need to be aware of?
  • Is the idea easily digestible by customers/management?