The most beautiful aspect of a SaaS business is that your monthly revenue is more or less stable. Unlike buying a soap, an automatic monthly or a yearly subscription means that customers aren’t frequently re-evaluating their decision for what to purchase.
However, when times are hard, people do think deeply about where their money is going. This year’s pandemic forced everyone to do such introspecting, including customers of VWO – a product that my company builds.
Even though the impact of economic slowdown due to coronavirus pandemic was not existential for our business, we did get impacted.
Our least committed customers decided they no longer want to pay for the subscription. Online travel industry was a non-trivial client base for us and business from them disappeared overnight.
I’m sure this story is similar for most businesses – barring a few like Shopify or Zoom where shock was in the reverse – but for enterprise software businesses, this year has been quite a teacher.
Determined to never let a crisis go to waste, I and rest of the leaders at my company reflected on how the year went by for us and the lessons that stood out. I decided that it’ll be a good idea to publicly share these learnings, so here they are. (As you know professional and personal dimensions can differ widely, these ones are for the professional context only. This year has given me many personal lessons too but they’re not documented in this essay).
20 (professional) lessons I learned from the year of the pandemic
1/ Beware of mood-based decisions. For most projects, knowing the impact is impossible. You need thumb rules for deciding in such cases, otherwise you will end up using the mood-of-the day for such decisions.
2/ When was the last time you talked to a customer? Deciding the course of action for critical projects without customer input can be fatal. We need to make a good business case and attach proof-of-value that’s derived from multiple such customer calls. (E.g. opening a local office internationally case needs to be supported via call transcript where it’s clear that doing this will help the customer)
3/ The point is to not stay busy. The point is to execute few projects that will create significantly higher business impact than the average project.
4/ Demand a business-case for each project. Do not green-light/prioritize a project until the business case for it is written down, and it’s measured against other potential initiatives. Remember: all ideas are good ideas.
5/ Build rigor for business experiments. Start product experiments. Insist on A/B testing before rolling out any change in marketing, product, sales, pricing. (E.g. even things like pricing tweaks should be done as an A/B test).
6/ One-level thinking isn’t enough. For anything where >30 minute combined org effort is to be invested, it will pay to close eyes for a couple of minutes and think hard by visualizing the people involved in receiving the value (what circumstances they’re in) and people creating the value (their circumstances and ability). Visualize the creators and receivers in the project to see if it makes sense to pursue that project.
7/ Your job is of coaching, not performing. My job (as the founder and the chairman) should be to not pursue my own ideas but to focus on coaching, selecting, prioritizing and enabling and pushing through key company projects
8/ Seek clarity on customer circumstances. Should have developed clarity on customer circumstances first, and then thought of ideas/projects (rather than the other way around.)
9/ All ideas are good ideas. There have been so many ideas that I’ve had and all of them good. The point should have been to focus on few that were truly aligned to creating impact for the customer. We need to make ideas compete with each other before execution.
10/ Focus on North Star Metric (NSM) / customer value. Should have started focusing on NSM / customer value metrics way earlier because that is the only way financial metrics move. Revenue growth doesn’t happen by focusing on revenue growth – it happens by focusing on whether you’re creating more value in the world over time.
11/ Our R&D should be focused around customer jobs and not technology. R&D should be in response to a customer job/pain point and not for its own sake.
12/ Propose your ideas as experiments. For ideas I believed in, if I faced resistance by others, instead of giving up or forcing through, I should have tried them via small experiments with clear concluding criteria.
13/ Program manage initiatives that show evidence of impact. Should constitute proper program management and reporting of progress/metrics for projects that truly matter (so that you make the org accountable for delivering them).
14/ No notes = no learning. If after reading or listening to something, you’ve not reflected by transcribing your own notes, you’ve not learned anything.
15/ Time is more valuable than money. While deciding on a project, consider that you have finite time but potentially unlimited money. If you can buy time or bandwidth, do it. (Relevant for investing in talent, software, products).
16/ When was the last time you talked to an expert? We do not talk to enough experts. Every time we’ve talked to an expert about a subject, we’ve learned something new.
17/ Building a product is not enough, its distribution is equally important. Unless anyone is aware about it, there’s no point to building things.
18/ We focus too much on what’s not going well, and ignore what’s going well. Even for things that are going well, ask regularly: what’s preventing us from going even faster and improving them further?
19/ Bootstrapping is playing the game of business in the hard mode. If the choice of bootstrapping is a conscious one, realize and accept the constraints that come with it. You cannot and should not operate like a VC business.
20/ An organization can only execute a few projects simultaneously. The constrain for good execution is never ideas or even capital. It’s almost always the leadership bandwidth. Wherever leadership is focused gets done, and by definition, leadership can only focus on very few initiatives each quarter.
That’s it. Hope these lessons were useful to you.
Template for doing this exercise
If you want to reflect on your year as well, you can use this Google Sheets template.
I’m curious to hear about lessons you’ve learned, so do email them to me. I read and reply to all emails.
Have an opinion on this essay? You can send your feedback on email to me.