There are certain topics that even some of the smartest people I talk with who aren’t startup oriented can’t fully grok. One of them is whether profitability matters. It’s common cocktail party chatter to hear people confidently pronounce that some well known startup is sure to blow up.
Or you know the other one — the one where Snapchat lost $2 billion in just one quarter. Two-fucking-billion! What a disaster! Except that they didn’t actually lose $2 billion in cash. It was a stock option incentive related “expense” but I bet you didn’t know that because in an era where we only read the headlines — they must be a train wreck losing billions. (They actually lost about $175 million in cash in that quarter, FWIW. See appendix if you want to know more on this.)
“How could they succeed when they’re not even profitable!”
If you hire 6 senior sales reps in January at $120,000 / year salary then you’ve taken on an extra $60,000 per month in costs yet these sales people might not close new business for 6 months. Your profitability will go down for 2 quarters while your growth may increase dramatically in quarters 3–12.
I know this seems obvious but I promise you that even smart people forget this when talking about profitability. 70–80% of the costs of most startups are employee costs so what you’re really talking about when a company is unprofitable is that they are growing their staff ahead of their revenue.
Enterprise applications are complex — there is an insane amount of information that is to be displayed that contains data from various sources, modules and users. There are complex graphs, usage patterns, and lists of data that need to be skimmed through before one can make sense of what the console is getting at.
“The biggest challenge with designing enterprise applications is the lack of examples of patterns that work or don’t work in specific scenarios.”
Since most enterprise applications contain sensitive data pertaining to the company, there are very few examples out there that talk to some of the common problems faced while designing enterprise apps. There exists pattern libraries that talk in-depth about how each component should work but very little on when to use them. The patterns we see in design libraries are often oversimplified and does not work in real enterprise applications where data and the use-cases are more complex in nature.
What you see below is a typical enterprise application. The working window is dense with information with a crazy number of panels each indicating information that is contextual to any other selection made on the screen.
As a founder, product lead at Pinterest and PM for a couple products at Google, as well as a growth partner for Initialized Capital, I’ve seen many product teams struggle to grow. Many products start out with a bang. Some find product-market fit with sustained growth. A few have gone through spurts of hyper-growth. But more often than not, I’ve seen most of them linger then fizzle.
“Founders launch their product, wonder why it isn’t growing like gangbusters and then immediately try to fix their growth problem.”
They turn to growth tactics like optimizing their on-boarding funnel, SEO or push notifications before really understanding what they are building and who they are building for. This may create an initial burst of short-term growth.
But it ultimately leads to high churn of your possible customers, while ignoring problems in the core product.
Before trying different growth tactics like throwing spaghetti at a wall, startups need to take a fresh look at their users, evaluate their product end goals and re-define the journey they want their users to take to get there. Here are some tips that can help define a path which will clarify the different steps needed to unlock product growth.