There are hundreds of startup advice blog posts. Many of them are based on a couple of experiences the respective founders made which are sometimes being presented as universal truth applicable to every startup. What frequently is missing is the context of the writer. So here’s my context: I’m an entrepreneur, I established a single successful (aka profitable) software boutique with my brother before we started to work on Usersnap (a B2B SaaS product), and we failed with another business idea. I’m older than the average startup founders and I did not drop out of university. I’m living in Austria, and I prefer the term “starting a business” instead of “running a startup”.
Disclosing this background, I’d like to share 3 observations I made in the last months.
Thoughts about finding Advisors
Limited life experiences + Over-generalization = Advice
Paul Buchheit, Founder of FriendFeed and creator of GMail
I’m amazed how many people show the self-confidence to call themselves startup-advisors. At some point I even got the impression that some failed startup entrepreneurs believe they’ll be able to advise other startups with a rationale that a set of experienced mistakes empowers them to guide fellow startups.
To me, that’s a misconceived plan B. Whereas I strongly believe that sharing failure with other entrepreneurs is very valuable I don’t think this is what advising is about.
In the early days of Usersnap we got a lot of unsolicited advice and we soon realized, that this will get us nowhere. We asked ourselves: What advice are we seeking and what specifically do we want to know? Moreover, we have also asked ourself: What’s in for our advisors? Why would someone share their experience?
We came up with following profile: Our advisors should be seasoned entrepreneurs, with a proven track-record. Ideally they are survivors of the first dot-com bubble and are still operating in a similar market segment we are approaching. And last-but-not-least, they should not be self-proclaimed startup-advisors.
After some research, we identified three people we wanted to listen to and we were lucky enough that they agreed to meet us. Surprisingly, they spent way more time to listen to us than to share their very own story. All of them wanted to understand every detail of our business before they even started to share their opinion. Despite their own success, they all were humble when they shared the key events of their own success.
We heard stories not being told on Twitter or Facebook and go-to market strategies you’ll not find on any blogs or learn in a business school. These strategies were not directly applicable to our business but they were inspiring and followed a pattern: consistent effort and a pinch of luck will take you a long way.
Understanding your business metrics
Recently, I’ve overheard a conversation between to startup-entrepreneurs on a so-called startup-event. One of them almost proudly claimed “I’m not good at math” and a couple of minutes later: “We at HipsterStartup Inc. are extremely data-driven and track everything.”
How could one possibly being bad at math and believe to be able to run a business? I’m not saying one needs to enroll in a post-graduate course for advanced mathematics but understanding the basics of statistics and finance is not optional for entrepreneurs, specifically if you are running a SaaS business.
The SaaS theory
We are offering our service in a subscription model.
If this is all you know about Software-as-a-Service and you believe that’s sufficient to start your SaaS startup, I strongly recommend the following crash course:
- Read David Skok’s blog post about SaaS Metrics.
- Read Joel Yorks’ blog. Fast lane: download at least his SaaS cheat sheet.
- Read Christoph Janz’ blog and set up a KPI Dashboard similar to his template.
I absolutely recommend to understand David Skok’s post, the formulas in Joel Yorks cheat-sheet or Christoph Janz’ simple KPI Dashboard. Do not just skim over it, but try to generate a thorough comprehension of the concepts and the (little) math which is included. Embrace the numbers and match your expectations with reality in your sheet.
Analyzing data vs. asking questions
Regularly question the significance of your tracked data with regards to your business aims. In your early days, you might not have enough data to really learn what’s working and what’s not. Sometimes you will see nice numbers (“+50% visits!”) – Start asking yourself: “Why?” and “What has happened?”. These simple questions are a good start to actually learn from your data.
The simple conclusion “We had 50% more new traffic” while looking at Google Analytics dashboard does not translate data into know-how. Rather simply try to find detailed answers: “Last week we had 50% new visitors because we put the latest blog post on Twitter and it got retweeted by @thanks-for-boosting-usersnap and at the same time our sign-up rate has tripled and we believe that there is a correlation”. Now go ahead and proof it.
Focus on your weak spots
If you are a co-founder of a startup with a background in software development, writing code is an excellent method to create satisfaction. It keeps you busy and you will end your day happy as you give yourself the impression that you made progress with your code which is not automatically progress in growing your business.
It’s very rare that the founding team of a business covers every single aptitude being required to be successful. Identifying the weak spots of a founding team does hurt. It requires honesty and you need to concede that there is maybe something missing.
One of the very first prototypes we put live got an amazing amount of attention – we got a lot of positive feedback – until we received an email from one of our very early alpha testers:
First we were annoyed but after we’ve discussed the admittedly harsh feedback we concluded: UX and UI was not our weak spot at this time. And as you can see, this advice is printed on real paper and motivates us to eliminate our weak spot every single day.
I think it is more difficult to find the weak spots of your team than identifying where your team is strong anyway.
Don’t leave your comfort zone. Just extend it.
Rather than “Leaving your comfort zone” I suggest to try hard to grow your very own comfort zone until the weak spots are covered.
The bottom line
This post is not a comprehensive how-to start my SaaS startup – rather it just covers three lessons I wanted to share. Finding the right advisors can save you quite some time when you start your business. Also, knowing and understanding as much as possible about your business model and your metrics is not optional, specifically if you start a SaaS business. Finally, focus on the weak spots of your team: Extend your comfort zone and embrace the challenge your team is facing.