Honestly
Where the model is weakest for software
Capacity as revenue a head can serve per month is the worst fit in the whole table. In software the serving is done by a machine, and headcount constrains how fast you build and support rather than how much you can deliver. Treat the 16,000 dollar figure as a rough support and success ratio, replace it with your own, and do not read a capacity constraint in a software twin too literally.
There is no expansion revenue. A customer is a customer at a monthly value; there is no seat growth, no usage tier, no upsell path and no net revenue retention above one hundred percent. For a business whose whole model is land and expand, that is a material omission, and the run will understate growth from the existing base.
Pricing is one price level, not a packaging structure. Real software pricing decisions are usually about tiers, bundling and what moves between them, and an elasticity applied to a single price index cannot represent that. It can tell you the direction and roughly the size of a general increase, which is still more than most companies have.
There is no funnel and no free tier. Trials, conversion rates, product led signups and activation do not exist. New customers per month is one assumption, not a pipeline.
And the three customer segments, price led, mainstream and anchored, are a behavioural split rather than a cohort model. If your question is genuinely about cohort decay by signup month, this is not the tool.
- No expansion revenue, no seats, no usage, no net revenue retention above one hundred percent
- One price level rather than tiers and packaging
- No trial funnel, no conversion, no activation, no product led motion
- Capacity per head fits software worse than any other industry in the table