For some reason we keep finding great early-stage SaaS startups in France, and it's not because of my command of the French language. In the last few years we've invested in four awesome SaaS companies from France: Algolia, Front, Mention and Critizr. We recently did #5, which hasn't been announced yet, and are in advanced talks with a potential #6. Besides our SaaS investments, we're also proud investors in StarOfService, an online marketplace to hire a wide range of professionals. Something is clearly going on in France, and we like it.
Our good connection to the French startup ecosystem was one of the reasons why we picked France as the first country for our "European SaaS Landscape" project. Another reason was that Clément not only speaks French, he IS French, and knows the market very well.
Without further ado, here it is: an industry map of the most important SaaS startups founded in France.
To learn more about our methodology and some of the insights we got while doing the research, check out Clément's post on Medium. If you have any questions, comments or suggestions, give us a shout!
Thoughts on Internet startups, SaaS and early-stage investing from Christoph Janz @ Point Nine Capital.
Monday, April 11, 2016
Wednesday, April 06, 2016
Truffle pig reloaded – Point Nine is looking for an Associate
About three years ago, we were looking for an Associate to join Point Nine and put up this landing page:
We called the position "truffle pig", because just like a truffle pig is digging up the best truffles from the ground, we as an early-stage VC try to find the best startups among a large number of potential investments. I have to give full credit for the truffle pig analogy to Mathias Schilling and Thomas Gieselmann of e.ventures, by the way. "Truffle pigs" is what they (young VC Associates at that time) called themselves when they approached my co-founder and me back in 1997 after having stumbled on this website. Fast-forward almost 20 years and we still haven't found a better way to describe the role. :)
Anyway, our search three years ago led to two fantastic truffle pigs, Rodrigo and Mathias, both of whom got promoted to Principals at Point Nine in the meantime. And today we're excited to kick-off the search for a new Associate. Here are all the details.
This is an incredible opportunity for a young, super-smart, super-driven person with outstanding analytical skills and a solid user interface. I'm pretty sure that it took me more than 10 years to get the expertise and network which you'll get during three years in this job.
If you're interested, please take a look at our job ad. If you know somebody who could be great fit, please pass on the link. Thanks!
Tuesday, March 29, 2016
SaaS Financial Plan 2.0 - bug fixes
Since I published v2 of my SaaS Financial Plan a few days ago, two alert readers have kindly pointed out two formula errors in the Excel sheet. Sorry about that.
=(W87-U87)*$E$124+X96
=0,5*(Costs!J62+Costs!J96+Costs!J104+Costs!J112+Costs!J122)/I49
Here's a corrected version. The Excel sheet that was linked from the original post has been corrected as well.
In case you've started to modify the template already and want to keep working with the previous version, here are the two bugs that you need to correct:
1) Cell U124 on the Costs tab, i.e. the costs for external recruiters in December 2016, contained:
The +X96 part has been added accidentally and needs to be removed. So the correct version is:
=(W87-U87)*$E$124
2) Row 55 on the Revenues tab, i.e. the CACs for the Pro plan, is completely wrong. It should be, for column I (with the other columns following analogously):
Once again, apologies for the inconvenience. If I or somebody else finds any other bugs, I will fix them ASAP and update the change log here.
PS: Before you ask – yes, I'm aware that it's ironic that I have to post an on-premise software style bug patch to a SaaS financial planning template. Ironic in an Alanis Morissette kind of way, that is, because "ironic" actually means something completely different. Google it if you don't believe me.
[Update 06/30/2016: I've fixed two further small issues that were reported by two kind readers in the comments below.]
[Update 06/30/2016: I've fixed two further small issues that were reported by two kind readers in the comments below.]
Wednesday, March 23, 2016
SaaS Financial Plan 2.0
Almost exactly four years ago I published a financial plan template for SaaS startups based on a model that I had created for Zendesk a few years earlier. I received a lot of great feedback on the template and the original post remains one of the most viewed posts on this blog up to this day.
In the last few weeks I've finally found some time to create a "v2" of the template ... just in time for a little Easter gift to the SaaS community. ;-) I'd recommend that you read this post first since it includes some important notes, but if you prefer to check out the template right away click here to download the Excel sheet.
The original v1 model was a very simple plan for early-stage SaaS startups with a low-touch sales model. As I wrote in the original post:
The new version comes with a number of improvements:
The downside of these improvements is that the spreadsheet has become significantly larger and more complex, but I tried my best to find the right balance. Also, the vast majority of the numbers in the sheet are calculated and the number of input cells is fairly limited.
In the last few weeks I've finally found some time to create a "v2" of the template ... just in time for a little Easter gift to the SaaS community. ;-) I'd recommend that you read this post first since it includes some important notes, but if you prefer to check out the template right away click here to download the Excel sheet.
The original v1 model was a very simple plan for early-stage SaaS startups with a low-touch sales model. As I wrote in the original post:
It's a simple plan for an early-stage SaaS startup with a low-touch sales model – a company which markets a SaaS solution via its website, offers a 30 day free trial, gets most of its trial users organically and through online marketing and converts them into paying customer with very little human interaction. Therefore the key drivers of my imaginary startup are organic growth rate, marketing budget and customer acquisition costs, conversion rate, ARPU and churn rate. If you have a SaaS startup with a higher-touch sales model where revenue growth is largely driven by sales headcount, the plan needs to be modified accordingly.
The new version comes with a number of improvements:
- Support for multiple pricing tiers
- Support for annual contracts with annual pre-payments
- Much more solid headcount planning
- Better visibility into "MRR movements"
- Better cash-flow planning
- Charts galore :-)
The downside of these improvements is that the spreadsheet has become significantly larger and more complex, but I tried my best to find the right balance. Also, the vast majority of the numbers in the sheet are calculated and the number of input cells is fairly limited.
The spreadsheet should be pretty self-explanatory but I've included a number of comments in the spreadsheet. Make sure to check them out - some of them are important in order to understand the model (in case you're not familiar with that Excel feature, hover over the little red triangles).
Here are a some additional notes:
1) General comments
- The sheet is hot off the press and given the large amount of formulas I can't rule out that there are bugs. If you find one, please email me at and I'll fix it ASAP.
- Blue numbers indicate data-entry cells. Black and grey numbers are computed.
- The model contains a lot of simplifications. Don't expect that it will perfectly fit your specific business - consider it a starting point.
2.) "Summary" tab
- The "Summary" tab contains only two types of input cells: Your starting bank balance and cash injections from financings. Everything else is calculated, mostly using data from subsequent tabs.
- As with all input cells in the model, consider the values that I've put in to be dummy data. Fill those cells with your own data and assumptions.
- The model doesn't take into account interest or taxes (except for payroll taxes).
- The "Revenues" line shows your end-of-month MRR for the respective month. This is not compliant with the US GAAP definition of "revenues", which uses different revenue recognition rules, but since SaaS companies live and breathe MRR I think it's the right approach for a SaaS financial model.
3.) "Revenues" tab
- The model assumes that you have three pricing tiers. I've called them "Basic", "Pro" and "Enterprise". If you have more or fewer pricing plans you can of course adjust the model accordingly (with some effort). It is further assumed that all Basic and Pro customers are on monthly plans and that all Enterprise customers are on annual plans.
- The model assumes that you're getting signups organically and via paid marketing and that you're converting a percentage of them into Basic customers and Pro customers. You can change the key assumptions such as your organic growth rate and your conversion rates in the grey area on the left.
- The Enterprise customer segment follows a different logic, based on the assumption that Enterprise customer acquisition is sales-driven as opposed to the marketing-driven low-touch sales model for Basic and Pro customers. The key drivers in the Enterprise segment of the model are your revenue targets, sales team quotas and your assumptions for churn and upsells.
- The spreadsheet shows the impact of e.g. Basic customers who upgrade to Pro and Pro customers who upgrade to Enterprise, but to keep things simple it doesn't support each and every possible movement between plans. For example, I didn't include the option for Basic customers to upgrade to Enterprise straight away or for Enterprise customers to downgrade. If this is a relevant factor in your business, you can of course accommodate for that by adding a few extra rows.
- For Basic and Pro customers, the model allows you to project ARPA development using a given ARPA at the beginning of the planning period along with assumptions on monthly ARPA increases. For Enterprise customers, the model assumes pricing increases at the time of renewal but not during the term of the subscription. Depending on your specific pricing model you'll have to modify that, e.g. to allow for Enterprise customers to add more seats continuously.
- In order to be able to calculate churn for Enterprise customers in the 1st year of the plan, it is assumed that existing Enterprise customers have been acquired over the course of the previous 12 months. This is of course a somewhat theoretical assumption and you need to adjust the model to include your actual numbers.
- As you can see in one of the charts below the numbers, the model allows you to calculate your "MRR movements". It's worth pointing out that the model currently doesn't show "Expansion MRR" and "Contraction MRR" separately but only the delta of the two, which I've called "Net Expansion MRR". In order to calculate Expansion MRR and Contraction MRR separately I'd have to add a couple of additional rows. To avoid making things too complicated, I decided against doing that for now. Fortunately ChartMogul (a Point Nine portfolio company, sorry for the plug) makes it super easy to drill down into all of your MRR movements.
- Please note that the CAC data and "CAC payback time" calculation are based on pretty crude simplifications. A solid planning of CAC payback times, CAC/LTV ratios etc. would require a lot of additional input data.
- The rows with the "Thereof bonuses..." label contain matrix formulas. Handle with care. :)
4.) "Costs" tab
- In order to adjust headcount planning in the G&A, R&D and marketing departments, change the assumptions for start date, base salary and bonus in the grey "Assumptions" area. You can remove, change or add roles in column H.
- With the exception of the VP of Sales role, sales staff headcount planning is done on the separate "Sales Team Hiring Plan" tab (re-using a model that I've built for this post). It calculates the number of sales people that you need based on the growth targets for your Enterprise customer segment, the quota of your sales people and a few other variables.
- Headcount planning for the Customer Success team is (again with the exception of the VP) done formulaically as well, based on assumptions on how many customers a customer success team member can handle.
- It is assumed that there's only one team, which I've called Customer Success, which does both customer support and customer success. Many SaaS companies have different teams for the two functions; if you're one of them you can adjust the plan accordingly.
- The costs for the Customer Success team are attributed to CoGS. This is debatable – if your Customer Success team plays an important role in converting signups or upselling customers you should consider allocating at least a portion of these costs to S&M and include those costs in your CACs. Please note that changing the "cost type" in column I will not automatically move the costs to a different category on the "Summary" tab so you'll have to do that manually.
- The model assumes that payroll tax is the same for all employees. This may have to be adjusted, e.g. if you have people in different countries.
- Regarding the cash impact of expenses, the model assumes that:
- payroll taxes are paid monthly
- bonuses are paid yearly (except for the sales team)
- sales team bonuses are paid quarterly (since bonuses/commissions play a much stronger role in sales compared to other departments)
- The model (somewhat simplistically) assumes that there are no capital expenditures. If you make investments into things like servers, computers or office furniture you should add these expenses accordingly.
If you've made it this far and haven't downloaded the Excel sheet yet: Here it is.
If you have any questions, comments or suggestions, let me know in the comments or email me. And if you like the model, tweet it out. :)
Finally, big thanks to Chris Amani, Sr. Finance Director at Humanity, as well as to Pawel and Dominik of Point Nine, for reviewing drafts of the model and for providing valuable feedback.
Friday, March 11, 2016
Building any business is hard
Judging from the number of Facebook likes and retweets, as well as comments on Twitter and elsewhere, my last post resonated with quite a lot of people. Some people thought it was provocative though, and some chimed in with good feedback:
Therefore I thought it would be worth following up on the topic to make sure that my message is clear.
The provocative sentence, I think, was this one:
@hunterwalk building ANY business is hard— Jonathan Abrams (@abrams) March 5, 2016
Therefore I thought it would be worth following up on the topic to make sure that my message is clear.
The provocative sentence, I think, was this one:
"Building a SaaS business with $1-2 million in ARR is not that hard and not that valuable."
It's important to point out that I took it back in the next sentence ...
"Let me rephrase that. Starting a new company is always hard and most SaaS startups never get to $1-2 million in ARR. Every founder who accomplishes this deserves a huge amount of respect."... and tried to explain the real point I was trying to make in the next one:
"The point is that getting to $1-2 million in ARR probably has less predictive value concerning a company’s ability to get to true scale than most people think – or at least thought some years ago."
As you can see, I don't disagree at all with Jonathan Abrams' s comment that building any business is hard. The reason why I wrote the sentence above, only to rephrase it in the following sentence, was that it was a reference to Josh Hannah's post about "nice little $40M eCommerce companies", which my post was inspired by.
To be as clear as possible about the subject, let me sum up my view again:
1) Building any business is hard. It requires a much broader skill set, more hard work and much more persistence than most normal jobs. (Let me refine that to "normal office jobs" - I don't want to get into an argument with heart surgeons or firefighters.) And since most businesses fail (at least when it comes to tech startups) it also requires a huge tolerance for risk.
2) Getting a SaaS company from 0 to $1-2M in ARR is hard. For the reasons mentioned in the original post, I think it has become significantly easier in the last 5-10 years but that doesn't mean that it isn't still very hard. Maybe a better way to put it would be "more likely" than "easier".
2) Getting a SaaS company from 0 to $1-2M in ARR is hard. For the reasons mentioned in the original post, I think it has become significantly easier in the last 5-10 years but that doesn't mean that it isn't still very hard. Maybe a better way to put it would be "more likely" than "easier".
3) As hard as it is to get to $1-2M in ARR, getting to that level doesn't say much about a company's ability to get to $100M in ARR. For most companies which didn't raise venture capital this is completely irrelevant. If you're a bootstrapped company or raised only a small amount of outside funding and eventually get to a few million dollars in ARR that's an amazing outcome, and calling a company like this a "lifestyle business" is ignorant and stupid. If you're a VC-funded company, the prospects of getting to $100M matter, though – at least to some of your shareholders. :)
In case it's still not clear, maybe this funnel diagram helps to explain what I mean. :-)
In case it's still not clear, maybe this funnel diagram helps to explain what I mean. :-)
Saturday, February 20, 2016
That’s a nice little $1-2M SaaS company you have here. Call me to discuss if it will scale!
About two years ago, Josh Hannah of Matrix Partners wrote an excellent article titled “That's a nice little $40M eCommerce company you have there. Call me when it scales.” In it he argues that an eCommerce business with $10 to $20 million in revenues is not that hard to build and also not very valuable. I would recommend that you read the full article, but one of the key points of the article was that if you fill a niche and have distinctive product/market fit with a set of customers, you can acquire customers very cheaply - up until a certain point, when you’ve maxed out the cheap customer acquisition channels and need to tap into more scalable channels. At that point it becomes a lot harder because the next set of customer acquisition channels will likely be much more expensive.
As a side note I’d add that the value of an eCommerce business with $10-20 million in revenue can be even more deceptive if a company has burned a lot of money to get to this level and has very low (or even negative) gross margins. The reason is that in most categories online shopping has become ultra-transparent (something which I’m not completely innocent of ;-) ) and that there’s a group of highly price-sensitive customers which always goes for the lowest price. So if you start an online shop, offer products at a loss, get listed on some of the biggest comparison shopping sites and do some affiliate marketing, you can easily get to tens of millions in revenue.
Now let’s talk about SaaS. In the last few years I’ve come to the realization that Josh’s observation can also be applied to the SaaS world: Building a SaaS business with $1-2 million in ARR is not that hard and not that valuable. Let me rephrase that. Starting a new company is always hard and most SaaS startups never get to $1-2 million in ARR. Every founder who accomplishes this deserves a huge amount of respect. The point is that getting to $1-2 million in ARR probably has less predictive value concerning a company’s ability to get to true scale than most people think – or at least thought some years ago.
The reason, I think, is that over the last 5-10 years it has become much easier to build a SaaS product and get initial traction:
So – it has become much easier to develop and launch a SaaS application and get initial traction, but if you have product/market fit in a small niche, which many SaaS companies do, it may be very hard to expand beyond that niche. And even if your market is large in principle, keeping growth up after you’ve picked the low-hanging fruits and reached a few million dollars in ARR will become increasingly difficult. In order to go from a $1-2 million in ARR to $10 million and eventually $100 million, you’ll have to find highly repeatable and reasonably profitable ways to acquire customers at huge scale. With few exceptions that means you either need to have a viral product (a.k.a. as hunting mice) or you have to go upmarket and dramatically increase your ACV over time.
Some SaaS businesses manage to do this and have a shot at building a $100 million ARR company, but for the majority of SaaS companies growth will taper off once they’ve reached a few million dollars in ARR, making it hard to ever grow significantly beyond $10-20 million. In a way, this isn’t surprising – not everyone can become a unicorn. :-) The non-trivial part of what I’m saying is that 5-10 years ago, many of these companies wouldn’t have gotten to a few million dollars in ARR. Put differently, there are more $100 million ARR SaaS companies today, but the number of companies in the $1-10 million ARR range has grown disproportionately faster. That’s my theory at least, it’s not scientifically proven.
If my theory is true, will this be bad news for people in the SaaS industry? It’ll depend on who you ask. It could make seed and Series A investing harder because the percentage of seed and Series A funded SaaS startups that becomes really big would decrease - and VCs need large outcomes in order to make their business model work. But it would also lead to the generation of a large number of small-ish but still very viable SaaS businesses, many of which could generate very decent profits for their founders. From that point of view, there’s never been a better time to start a SaaS company.
PS: You may have noticed that I’ve changed Josh’s “call me when it scales” to “call me to to discuss if it will scale”. Being a seed investor I’m trying to find SaaS companies that can scale before they have scaled.
PPS: If you’re wondering why Josh talks about revenues in the $10-40 million range when he refers to sub-scale companies while I talk about $1-2 million in ARR: The reason is that besides the fact that SaaS revenues are recurring, SaaS margins are almost an order of magnitude higher than eCommerce margins. $1 in SaaS revenues is much more valuable than $1 in eCommerce revenues (all revenue is not created equal!).
[Update 03/11/2016: I wrote a followup post to the post above.]
As a side note I’d add that the value of an eCommerce business with $10-20 million in revenue can be even more deceptive if a company has burned a lot of money to get to this level and has very low (or even negative) gross margins. The reason is that in most categories online shopping has become ultra-transparent (something which I’m not completely innocent of ;-) ) and that there’s a group of highly price-sensitive customers which always goes for the lowest price. So if you start an online shop, offer products at a loss, get listed on some of the biggest comparison shopping sites and do some affiliate marketing, you can easily get to tens of millions in revenue.
Now let’s talk about SaaS. In the last few years I’ve come to the realization that Josh’s observation can also be applied to the SaaS world: Building a SaaS business with $1-2 million in ARR is not that hard and not that valuable. Let me rephrase that. Starting a new company is always hard and most SaaS startups never get to $1-2 million in ARR. Every founder who accomplishes this deserves a huge amount of respect. The point is that getting to $1-2 million in ARR probably has less predictive value concerning a company’s ability to get to true scale than most people think – or at least thought some years ago.
The reason, I think, is that over the last 5-10 years it has become much easier to build a SaaS product and get initial traction:
- Building a web application has become much easier, faster and cheaper. Whether starting an Internet startup has really become 10x cheaper depends on how exactly you phrase the question and is debatable. But creating and launching a SaaS product has without a doubt become much cheaper in the last ten years. Moore’s Law, cheaper hardware and more bandwidth are one factor, but the even more important factor is that today there are great products for so many of the issues which the previous generation of SaaS founders had to worry about (billing, analytics, server monitoring, application performance, live chat, to name just a few … even AWS didn’t exist 10 years ago!).
- Ten years ago, there was nobody who SaaS founders could ask in order to learn how to do, for example, inbound marketing, low-touch sales or customer success. Many of the tactics that everybody is using today hadn’t been invented yet. In the last ten years the playbook has been written and subsequently published. As I wrote in my post about the rising table stakes in SaaS, today an abundance of knowledge about any imaginable SaaS topic is readily available online and events like the fantastic SaaStr conference last week allow founders to learn from people who’ve done it before.
- As SaaS is quickly becoming the norm, it’s now much easier to get initial traction. In any given category, the number of potential customers who considers (and in most cases prefers) a SaaS solution is much higher than it was some years ago. This and the fact that almost everybody owns a smartphone today has given rise to new categories which previously weren’t software categories at all because people used pen and paper to get the job done.
So – it has become much easier to develop and launch a SaaS application and get initial traction, but if you have product/market fit in a small niche, which many SaaS companies do, it may be very hard to expand beyond that niche. And even if your market is large in principle, keeping growth up after you’ve picked the low-hanging fruits and reached a few million dollars in ARR will become increasingly difficult. In order to go from a $1-2 million in ARR to $10 million and eventually $100 million, you’ll have to find highly repeatable and reasonably profitable ways to acquire customers at huge scale. With few exceptions that means you either need to have a viral product (a.k.a. as hunting mice) or you have to go upmarket and dramatically increase your ACV over time.
Some SaaS businesses manage to do this and have a shot at building a $100 million ARR company, but for the majority of SaaS companies growth will taper off once they’ve reached a few million dollars in ARR, making it hard to ever grow significantly beyond $10-20 million. In a way, this isn’t surprising – not everyone can become a unicorn. :-) The non-trivial part of what I’m saying is that 5-10 years ago, many of these companies wouldn’t have gotten to a few million dollars in ARR. Put differently, there are more $100 million ARR SaaS companies today, but the number of companies in the $1-10 million ARR range has grown disproportionately faster. That’s my theory at least, it’s not scientifically proven.
If my theory is true, will this be bad news for people in the SaaS industry? It’ll depend on who you ask. It could make seed and Series A investing harder because the percentage of seed and Series A funded SaaS startups that becomes really big would decrease - and VCs need large outcomes in order to make their business model work. But it would also lead to the generation of a large number of small-ish but still very viable SaaS businesses, many of which could generate very decent profits for their founders. From that point of view, there’s never been a better time to start a SaaS company.
PS: You may have noticed that I’ve changed Josh’s “call me when it scales” to “call me to to discuss if it will scale”. Being a seed investor I’m trying to find SaaS companies that can scale before they have scaled.
PPS: If you’re wondering why Josh talks about revenues in the $10-40 million range when he refers to sub-scale companies while I talk about $1-2 million in ARR: The reason is that besides the fact that SaaS revenues are recurring, SaaS margins are almost an order of magnitude higher than eCommerce margins. $1 in SaaS revenues is much more valuable than $1 in eCommerce revenues (all revenue is not created equal!).
[Update 03/11/2016: I wrote a followup post to the post above.]
Saturday, December 12, 2015
A simple tool to improve your 2016 planning
In my last post I wrote about the problem with month-over-month growth rates. One of the issues I talked about was that when your revenue plan numbers are based on a constant m/m percentage growth figure (i.e. you're projecting to grow exponentially), your short-term objectives are likely too low relative to your longer-term goals.
As an example, I showed a (fictional) SaaS startup that wants to grow from $1,000 in MRR to ~ $85,000 in MRR within one year. If that company projects exponential growth, it will have to add less than $7,000 in net new MRR in the first half of the year in order to be on track ... but to stay on track, it needs to add more than 10x that amount in the second half of the year!
To follow-up on the topic, I've put together a very simple (Google Sheets based) calculator which startup founders might find useful when they work on their plan for 2016. The purpose of this simple sheet is not to replace a thorough bottom-up planning which is based on the key drivers of your business. Instead, the idea is that it might be a useful input or cross-check for a more detailed plan.
Click here to check out the tool.
Here's what it does:
- You enter your start MRR in the orange field at the top left
- You enter your target growth for the year in the orange field in the middle
- The sheet will then calculate three alternative paths to your target MRR for the end of the year
The first one is based on linear growth. It just takes the total net new MRR that you want to add throughout the year and assumes that you're adding 1/12th of it each month.
The second one is based on an exponential growth assumption, i.e. it assumes that you're growing at a constant percentage growth rate every month.
The third alternative, which I've called "Happy Medium", has a growth curve that sits between the linear and the exponential option. You can see that well if you take a look at the charts below the numbers.
I think most early-stage startups should project a trajectory which, like the "Happy Medium" path", is somewhere between the linear and the exponential option. What do you think?
I think most early-stage startups should project a trajectory which, like the "Happy Medium" path", is somewhere between the linear and the exponential option. What do you think?
Monday, November 30, 2015
The problem with month-over-month growth rates
Most fundraising decks contain a slide with a chart that looks roughly like this:
Or this:
I’ve also seen charts that look like this:
Or this:
Chart #3 and #4 are good for a LOL (or a “WTF!”, depending on your sense of humour), and fortunately we’re not getting too many of these (if you don’t know what I’m talking about, take another look at the charts). A chart that looks similar to #1 or #2 is something we look at on a daily basis, though.
What all of these charts and their headlines have in common is that they’re trying to convey exponential growth. Since traction is the #1 factor that determines fundraising success, it’s understandable that founders try hard to show exponential growth (which talking about a m/m growth rate implies). This is especially true if you’re one out of 50 startups that present at a “demo day” and you have three minutes to get investors excited. At some of the demo days that I’ve attended, I felt like this led to an arm’s race for the highest growth rates and sometimes made me feel like this:
Let’s look at the numbers behind chart #1 and #2.
Chart 1:
As you can see, chart #1 shows very strong signs of exponential growth: this (fictional) company’s MRR is growing at a relatively steady rate of 18-21% per month, and the amount of net new MRR which the company is adding is growing every month. Mathematically this looks clearly exponential, and yet, since the absolute numbers are still so low, unless you understand the drivers behind the growth you don’t know if there’s real, sustainable exponential growth (e.g. due to product virality) or if it’s just a series of step changes which makes the numbers look like exponential growth.
If this sounds like an academic question to you, think about its impact on the company’s growth projections. If there’s true exponential growth at a rate of around 20% per month, the company’s numbers will quickly go through the roof. If, on the other hand, the growth isn’t driven by inherently exponential drivers, you should expect the growth rate to decline quickly, leading to much lower projections.
Now let’s turn to the data behind chart #2:
If you take a closer look at the numbers, you can see that in contrast to chart #1, in spite of the chart’s headline and trendline, it doesn’t look like something’s growing exponentially here. The monthly growth rate is higher than 10% in all but two months, but it’s fluctuating heavily and the amount of net new MRR is going up and down. You can calculate a growth rate of 40% per month on average or a compound monthly growth rate (CMGR) of 35% without having to lie, and you can have Excel draw a trendline using an exponential regression. But I believe this is highly misleading. A more reasonable way of describing this company’s revenue growth would be to say that the company has been adding between $300 and $700 in net new MRR per month in the last ~ 12 months.
Again, all of this may sound somewhat academic, but I think it has practical relevance in two ways: The first one is about how you communicate your numbers to potential investors when you’re fundraising. The second one is about how you’re projecting growth and what targets you’re setting for your team. Let’s take a closer look at both of them.
1) When you’re talking to investors you of course want to show your numbers in the best possible light, and to say that you’re increasing revenue by $300-700 per month (to use the example from above) may not sound as exciting as a CMGR of 35%. However, keep in mind that experienced investors have very fine-tuned BS antennas, and if an investor gets the impression that you’re getting too creative in your interpretation of your data, that’s a huge turn-off. Therefore I’d recommend the following:
2) As far as your internal goal-setting goes, the problem with an exponential growth assumption is that for early-stage startups it makes short-term goals too easy and longer-term goals too hard (unless you’re one of the 0.0...1% of startups that have a viral growth engine with a viral coefficient greater than 1).
Let’s say you’re starting (almost) from zero and your goal is to be at roughly $80k in MRR in 12 months. If you’re assuming a constant m/m growth rate it looks like this:
The blue line shows the total MRR at the end of the month; the orange bars show the net new MRR added in each month; and the red line shows your monthly growth rate in %. As you can see, you have to add pretty tiny amounts of net new MRR per month until around month 6 in order to reach your goals. Then it goes up quickly, and in the last two months of the year you’ll have to add $20-30k per month. The problem with a plan like this is that if you’re at $8000 after month 6 you think you’re on track, but actually you’ve only achieved 1/10th of what you have to achieve in the year.
You can of course expect that you’re getting better throughout the year as your product matures and as you’re doing more sales and marketing, but I think the slope of plan #1 is too steep. A more helpful and more realistic plan would look like this:
In this version you reach the same result after 12 months, but how you’re getting there is different. In contrast to plan #1, plan #2 doesn’t assume a constant m/m percentage growth rate. It assumes that the amount of net new MRR that you’re adding per month is growing, but on a linear basis. That may make the chart look less exciting, but I believe plan #2 is much more useful. If you use plan #2 and you’re on track after 6 months, it’s much more likely that you will still be on track after month 12.
To sum up, my recommendations for modeling growth:
As you may have noticed, my recommendations for how you should manage your targets internally are very much aligned with my recommendations for how you should communicate your numbers to investors. Isn’t that nice? :)
[Update 12/12/2015: As a followup to this post, I created a simple (Google Sheets based) calculator which you might find helpful for your planning.]
![]() |
| Chart #1 |
Or this:
![]() |
| Chart #2 |
I’ve also seen charts that look like this:
![]() |
| Chart #3 |
Or this:
![]() |
| Chart #4 |
Chart #3 and #4 are good for a LOL (or a “WTF!”, depending on your sense of humour), and fortunately we’re not getting too many of these (if you don’t know what I’m talking about, take another look at the charts). A chart that looks similar to #1 or #2 is something we look at on a daily basis, though.
What all of these charts and their headlines have in common is that they’re trying to convey exponential growth. Since traction is the #1 factor that determines fundraising success, it’s understandable that founders try hard to show exponential growth (which talking about a m/m growth rate implies). This is especially true if you’re one out of 50 startups that present at a “demo day” and you have three minutes to get investors excited. At some of the demo days that I’ve attended, I felt like this led to an arm’s race for the highest growth rates and sometimes made me feel like this:
Let’s look at the numbers behind chart #1 and #2.
Chart 1:
As you can see, chart #1 shows very strong signs of exponential growth: this (fictional) company’s MRR is growing at a relatively steady rate of 18-21% per month, and the amount of net new MRR which the company is adding is growing every month. Mathematically this looks clearly exponential, and yet, since the absolute numbers are still so low, unless you understand the drivers behind the growth you don’t know if there’s real, sustainable exponential growth (e.g. due to product virality) or if it’s just a series of step changes which makes the numbers look like exponential growth.
If this sounds like an academic question to you, think about its impact on the company’s growth projections. If there’s true exponential growth at a rate of around 20% per month, the company’s numbers will quickly go through the roof. If, on the other hand, the growth isn’t driven by inherently exponential drivers, you should expect the growth rate to decline quickly, leading to much lower projections.
Now let’s turn to the data behind chart #2:
If you take a closer look at the numbers, you can see that in contrast to chart #1, in spite of the chart’s headline and trendline, it doesn’t look like something’s growing exponentially here. The monthly growth rate is higher than 10% in all but two months, but it’s fluctuating heavily and the amount of net new MRR is going up and down. You can calculate a growth rate of 40% per month on average or a compound monthly growth rate (CMGR) of 35% without having to lie, and you can have Excel draw a trendline using an exponential regression. But I believe this is highly misleading. A more reasonable way of describing this company’s revenue growth would be to say that the company has been adding between $300 and $700 in net new MRR per month in the last ~ 12 months.
Again, all of this may sound somewhat academic, but I think it has practical relevance in two ways: The first one is about how you communicate your numbers to potential investors when you’re fundraising. The second one is about how you’re projecting growth and what targets you’re setting for your team. Let’s take a closer look at both of them.
1) When you’re talking to investors you of course want to show your numbers in the best possible light, and to say that you’re increasing revenue by $300-700 per month (to use the example from above) may not sound as exciting as a CMGR of 35%. However, keep in mind that experienced investors have very fine-tuned BS antennas, and if an investor gets the impression that you’re getting too creative in your interpretation of your data, that’s a huge turn-off. Therefore I’d recommend the following:
- If your numbers look similar to chart #2 from above, don’t try to read exponential growth into the chart.
- If your numbers look more like chart #1, i.e. your monthly percentage growth is pretty stable and your monthly $ growth (or user growth, if you’re a consumer startup and pre-monetization) is going up consistently, it’s fair to talk about exponential growth. That said, as long as you’re at a very low absolute levels (say below ~ $20k in MRR if you’re a SaaS startup) it doesn’t make too much sense to talk about percentage growth rates, and talking about growth in terms of net new MRR per month may be more useful.
- When you’ve reached what Jason M. Lemkin calls “Initial Traction” – around $1-2M in ARR – consider talking about y/y growth instead of m/m growth. There’s no strong rationale for that, but I think if you’re talking about longer periods of time, y/y growth is more intuitive to understand.
2) As far as your internal goal-setting goes, the problem with an exponential growth assumption is that for early-stage startups it makes short-term goals too easy and longer-term goals too hard (unless you’re one of the 0.0...1% of startups that have a viral growth engine with a viral coefficient greater than 1).
Let’s say you’re starting (almost) from zero and your goal is to be at roughly $80k in MRR in 12 months. If you’re assuming a constant m/m growth rate it looks like this:
![]() |
| Plan #1 |
The blue line shows the total MRR at the end of the month; the orange bars show the net new MRR added in each month; and the red line shows your monthly growth rate in %. As you can see, you have to add pretty tiny amounts of net new MRR per month until around month 6 in order to reach your goals. Then it goes up quickly, and in the last two months of the year you’ll have to add $20-30k per month. The problem with a plan like this is that if you’re at $8000 after month 6 you think you’re on track, but actually you’ve only achieved 1/10th of what you have to achieve in the year.
You can of course expect that you’re getting better throughout the year as your product matures and as you’re doing more sales and marketing, but I think the slope of plan #1 is too steep. A more helpful and more realistic plan would look like this:
![]() |
| Plan #2 |
In this version you reach the same result after 12 months, but how you’re getting there is different. In contrast to plan #1, plan #2 doesn’t assume a constant m/m percentage growth rate. It assumes that the amount of net new MRR that you’re adding per month is growing, but on a linear basis. That may make the chart look less exciting, but I believe plan #2 is much more useful. If you use plan #2 and you’re on track after 6 months, it’s much more likely that you will still be on track after month 12.
To sum up, my recommendations for modeling growth:
- In the first 12-24 months or so after launch, plan to get to your target number by assuming a curve similar to the one shown in plan #2.
- After that, start using a m/m or y/y percentage growth target (ideally roughly in line with the T2D3 concept)
As you may have noticed, my recommendations for how you should manage your targets internally are very much aligned with my recommendations for how you should communicate your numbers to investors. Isn’t that nice? :)
[Update 12/12/2015: As a followup to this post, I created a simple (Google Sheets based) calculator which you might find helpful for your planning.]
Friday, October 23, 2015
What sucks about fundraising
Last week I wrote a post titled “What makes fundraising so stressful?” and asked founders to tell me which parts of the fundraising process suck. As of this writing, about 110 founders have completed the Typeform survey. The results are very interesting, and in some cases shocking. More on that below, but let’s start with the responses to the first question:
More than 60 founders took the time to answer the additional free-form question (“What else has stressed you out?”). In their comments, many people emphasized and provided additional detail on some of the topics shown above, but several founders also pointed out additional issues. Reading through all of the comments has been very enlightening (and in a few cases humbling). Here’s a small selection of the answers:
The next question was “Which of the following things have happened to you already?”. Here are the results:
The final question was: “Anything else you want to point out? Any other input on what VCs can do to make fundraising less stressful for founders?”. More than 45 people answered this question. The comments included:
The top issues, that is the issues which founders said suck the most, are:
Interestingly these issues are precisely the ones that could be avoided if VCs did a better job. In contrast, things that cost time and energy but are a natural part of the fundraising process – creating a deck, preparing numbers, having many meetings, getting rejections – suck significantly less.
This theme – founders can deal with rejections, but they need clarity – is also what has been mentioned the most in the free-form questions and is the clearest take-away of the survey.
To my fellow VCs’ defense, if you get 300 or more inbound requests per month it’s very hard to give each founder a timely response, so unless an investor intentionally strings founders along in order to keep optionality (or the illusion thereof) I don’t want to blame him or her. But knowing that this is the #1 issue which stresses founders in the fundraising process, VCs should try very hard to become as responsive and transparent as possible. For us at Point Nine, these results served as a good reminder that we have to further improve our internal processes to make sure that each and every entrepreneur gets a swift answer from us.
We also asked founders to tell us what stage they’re in. 59% said that the last round they’ve raised (or tried to raise) was a seed round. 30% said Series A, 11% said Series B.
The only question which showed a statistically significant correlation with the stage was the question about “Getting initial meetings”. For earlier-stage founders, getting initial meetings has been significantly harder than for later-stage founders. That doesn’t come as a surprise, and maybe it shows that there’s at least one thing which VCs are good at: Getting their portfolio founders meetings with other VCs. :-)
In the world of private equity and M&A, signing a term sheet may have a different meaning but I’ve always thought that if a VC signs a term sheet it means they are fully committed to making the investment. And they ought to be. The purpose of the final due diligence that takes place after a term sheet is signed is to rule out “skeletons in the closet”. By the time you sign a term sheet, you should have made up your mind and should be done with your “commercial due diligence”.
Apparently that’s not the case. 14 people, a shocking 14% of the respondents, said they’ve already experienced an investor backing out after a term sheet has been signed. Unless these 14 founders had skeletons in their closets, that’s 14 too many. As one founder said in the comments, if this happens it can kill a company.
Based on these findings, founders are well advised to do more due diligence on their part before they sign a term sheet with a VC. One of the things you should do is ask the VC what kind of due diligence they’re still planning to do after the term sheet is signed.
Huge thanks to all founders who took the time to participate in the survey! If you want to dive in even deeper into the survey results, please drop me a line and I’ll send you the Excel sheet with the complete data set.
“Your optionality is an illusion”
More than 60 founders took the time to answer the additional free-form question (“What else has stressed you out?”). In their comments, many people emphasized and provided additional detail on some of the topics shown above, but several founders also pointed out additional issues. Reading through all of the comments has been very enlightening (and in a few cases humbling). Here’s a small selection of the answers:
"The big egos"
"Everything takes 4x more time than initially thought"
"Associates who constantly want calls without involving a partner who can actually get the deal done (or not)."
“It's venture capital but I have the feeling no VC will take risks. There is always a reason not to invest.”
"Rejection from seed investors saying 'come back once you have X' (where X is in essence enough to raise Series A)."
"Some investors haven't mentioned at all that they invested in similar company. I found that after the meeting."
"Startup/investor fit. Finding people who understand the business and can support / advise us going forward, vs. wasting time talking to people who don't understand the venture potential of the business."
"Investors using their lawyers as bad cops."
"Radio silence and/or stringing me along, in service of ‘maintaining optionality’. Hint: if you do this, I won't come back to you next time I'm raising. Your optionality is an illusion."
"Had an investor back out after a long negotiation that culminated in a SIGNED term sheet. This is outright destructive, and all but killed the company."
The next question was “Which of the following things have happened to you already?”. Here are the results:
The final question was: “Anything else you want to point out? Any other input on what VCs can do to make fundraising less stressful for founders?”. More than 45 people answered this question. The comments included:
"If you are not interested, say it right away (I had some of the best meetings with VCs that said it out early in the conversation)."
"Don't waste our time or yours. Be very upfront about interest or not. Give succinct feedback, and don't sugar-coat why you're reacting the way you are."
"Had an investor back out after a long negotiation that culminated in a SIGNED (but obviously non-binding) term sheet. This is outright destructive, and all but killed the company. Never, ever, ever do this to a young company. I literally hate this firm now. They are the worst!"
"If you're transparent, direct, clear and fair, I will respect you and come back to you in the future. If you're weaselly, arrogant, or try to manipulate me, I won't."
What are the take-aways?
1) Founders understand that fundraising takes time and they can deal with rejections. But they hate being left in the dark.
The top issues, that is the issues which founders said suck the most, are:
- "Not knowing where I am in the process, i.e. no ‘yes’ but also no clear ‘no’"
- "Not understanding why VCs have passed"
- "Having to answer dumb questions by VCs who didn’t understand our business"
Interestingly these issues are precisely the ones that could be avoided if VCs did a better job. In contrast, things that cost time and energy but are a natural part of the fundraising process – creating a deck, preparing numbers, having many meetings, getting rejections – suck significantly less.
This theme – founders can deal with rejections, but they need clarity – is also what has been mentioned the most in the free-form questions and is the clearest take-away of the survey.
To my fellow VCs’ defense, if you get 300 or more inbound requests per month it’s very hard to give each founder a timely response, so unless an investor intentionally strings founders along in order to keep optionality (or the illusion thereof) I don’t want to blame him or her. But knowing that this is the #1 issue which stresses founders in the fundraising process, VCs should try very hard to become as responsive and transparent as possible. For us at Point Nine, these results served as a good reminder that we have to further improve our internal processes to make sure that each and every entrepreneur gets a swift answer from us.
2) Fundraising sucks across all stages
We also asked founders to tell us what stage they’re in. 59% said that the last round they’ve raised (or tried to raise) was a seed round. 30% said Series A, 11% said Series B.
The only question which showed a statistically significant correlation with the stage was the question about “Getting initial meetings”. For earlier-stage founders, getting initial meetings has been significantly harder than for later-stage founders. That doesn’t come as a surprise, and maybe it shows that there’s at least one thing which VCs are good at: Getting their portfolio founders meetings with other VCs. :-)
3) Backing out after a term sheet has been signed is much more common than we thought
In the world of private equity and M&A, signing a term sheet may have a different meaning but I’ve always thought that if a VC signs a term sheet it means they are fully committed to making the investment. And they ought to be. The purpose of the final due diligence that takes place after a term sheet is signed is to rule out “skeletons in the closet”. By the time you sign a term sheet, you should have made up your mind and should be done with your “commercial due diligence”.
Apparently that’s not the case. 14 people, a shocking 14% of the respondents, said they’ve already experienced an investor backing out after a term sheet has been signed. Unless these 14 founders had skeletons in their closets, that’s 14 too many. As one founder said in the comments, if this happens it can kill a company.
Based on these findings, founders are well advised to do more due diligence on their part before they sign a term sheet with a VC. One of the things you should do is ask the VC what kind of due diligence they’re still planning to do after the term sheet is signed.
Huge thanks to all founders who took the time to participate in the survey! If you want to dive in even deeper into the survey results, please drop me a line and I’ll send you the Excel sheet with the complete data set.
Tuesday, October 13, 2015
What makes fundraising so stressful?
In theory, raising venture capital could roughly look like this:
- You create an investor deck and send it to 5-10 VCs that you like (1 week)
- You meet the ones that are interested and quickly figure out the 3-4 that are really bullish (1-2 weeks)
- You have a few more meetings with those 3-4 VCs and answer their questions (2 weeks)
- You negotiate with 2-3 of them and sign a term sheet with your favorite one (a few days)
- You hand it over to your lawyer for the final due diligence and the legal paperwork (3-4 weeks)
So ideally it's a couple of trips to Sand Hill Road (or San Francisco or London or Jaegerstrasse) over a period of 4-6 weeks to get a term sheet, and after another 3-4 weeks you've got the money in your bank account.
In practice, things rarely go so smooth. More often than not, raising venture capital is a huge distraction for the founding team. Even if things go reasonably well, it usually means that one of the founders spends half of his time talking to VCs for several weeks – time that he or she can't spend on building the business. If things go less well, it's not only a huge time sink but can also be an extremely stressful experience.
Why is that, and does it have to be this way?
To some extent, it's in the nature of things that convincing other people to give you a lot of money (and to commit to supporting you for the next 10 years) for a small stake in your risky early-stage startup is not an easy feat. The vast majority of startups fail, VCs can invest in only 1% or less of the startups they see, fundraising involves a lot of relationship-building, it's a complex process – that's all pretty obvious so I won't elaborate on that.
But the question is if fundraising really has to suck as much as I think many or most founders experience it, and what investors can do to make it suck less. (I've already written about what founders can do on their end, e.g. by having clarity about their numbers and by pre-empting most DD questions.)
To shed some light on that question I put together a short Typeform survey. If you are a founder or CEO and have raised venture capital it would be awesome if you could participate in the survey. It's anonymous and takes only a few minutes to complete (and thanks to Typeform, you can do it on your iPhone :) ). I will share the results in another post shortly.
Open the survey!
Thanks in advance!
In practice, things rarely go so smooth. More often than not, raising venture capital is a huge distraction for the founding team. Even if things go reasonably well, it usually means that one of the founders spends half of his time talking to VCs for several weeks – time that he or she can't spend on building the business. If things go less well, it's not only a huge time sink but can also be an extremely stressful experience.
Why is that, and does it have to be this way?
To some extent, it's in the nature of things that convincing other people to give you a lot of money (and to commit to supporting you for the next 10 years) for a small stake in your risky early-stage startup is not an easy feat. The vast majority of startups fail, VCs can invest in only 1% or less of the startups they see, fundraising involves a lot of relationship-building, it's a complex process – that's all pretty obvious so I won't elaborate on that.
But the question is if fundraising really has to suck as much as I think many or most founders experience it, and what investors can do to make it suck less. (I've already written about what founders can do on their end, e.g. by having clarity about their numbers and by pre-empting most DD questions.)
To shed some light on that question I put together a short Typeform survey. If you are a founder or CEO and have raised venture capital it would be awesome if you could participate in the survey. It's anonymous and takes only a few minutes to complete (and thanks to Typeform, you can do it on your iPhone :) ). I will share the results in another post shortly.
Open the survey!
Thanks in advance!
Thursday, October 08, 2015
The importance of doing reference checks (2/2)
This is part two of Jenny's article about the importance of reference checks. If you haven't read the first part yet, start here.
Last time we spoke about WHY you should do reference checks and what impact a bad hire can have on your organization. In this second part I’d like to share my personal experience as well as some outcomes that have recently been discussed within the Point Nine family around the HOW.
General thoughts on the HOW:
Now how to do them well?!
Here are some random questions that might be helpful for your day to day reference check. I usually use a mix of those and tailored ones to the specific candidate and role. Remember we’re trying to find inconsistencies, so use a good mix of questions for every reference check.
Some general questions that I find helpful:
There is plenty of reading out there with good stuff on that topic. One post that I can highly recommend is Mark Suster’s post “How to make better reference calls”.
What are your thoughts? What are your favorite questions that you use in reference calls to cut through thebullshit politeness?
Last time we spoke about WHY you should do reference checks and what impact a bad hire can have on your organization. In this second part I’d like to share my personal experience as well as some outcomes that have recently been discussed within the Point Nine family around the HOW.
General thoughts on the HOW:
- If you do reference checks, make sure they are one of the last steps of your recruitment process. Because if you do them right (I’ll explain further what that means) it will cost you time. You want to make sure that time is invested in the right candidate.
- The number of reference checks people do varies greatly between 1 to 15 checks per person. You want to find inconsistencies within the feedback you receive about the person. Depending on how senior the candidate is, ask for more references. A good start is 2 references for junior/entry roles that you want to increase to 3 to 5 references for middle management positions and 6 to 10 references for a senior leadership position.
- Make sure you have a mix of suggested references by the candidate as well some that you happen to know or you proactively approach to give you feedback. A good way to start is with the suggested ones. You can ask those guys who else they find you should talk to. Make sure you still top that up with your own research e.g. via LinkedIn or your personal network.
Now how to do them well?!
- Have questions prepared. Make sure you know what to ask rather just go for the “So, tell me something about John” kind of question. Ask specific questions about the candidate. Remember, you want to find inconsistencies! Don’t be okay with foggy answers, worst case rephrase the question.
- Try to establish a relationship with the reference you are talking to. Do a video call if possible and try to avoid written references. Take your 2-5 minutes small talk time at the beginning. Why? It’s much harder to lie into your face when I like you :)
- Don’t only ask direct peers. It’s much more interesting to talk to people e.g. that got fired by that person (they are usually much more honest and open) or in general someone that has worked below him and got directly impacted by that person. A good mix of people above, around and below works quite well!
- Obviously try to avoid asking someone at the current company the person works unless he got recommended by the candidate.
- A good way to challenge the integrity upfront is to ask the following question once you’ve received the suggested references: “Would you mind If I talk to Peter, Fran and George as well”? Watch the reaction closely!
- Always remember: You hire someone for his strengths not lack of weaknesses so tailor your questions about the strengths you are looking for and make sure that you weigh the feedback you receive according to what you really need. Example: Reference says: “Steve, in his role as Head of Sales, was too pushy in his general approach and sometimes went too fast for the Executive Team and the organization, so it was really hard to follow”. This is generally not the best feedback, but if your company is currently trying to attack a market, someone like Steve might be just the right fit for this period of time ;)
Here are some random questions that might be helpful for your day to day reference check. I usually use a mix of those and tailored ones to the specific candidate and role. Remember we’re trying to find inconsistencies, so use a good mix of questions for every reference check.
Some general questions that I find helpful:
- What is your relationship with Peter like?
- What was it like to work with Peter?
- What was Peter’s management style like?
- Can you describe a tough/very challenging moment Peter was in and how he has managed to get ouf it?
- If you think about the time you and Peter have worked together, what’s the first memory that pops up your mind?
- Would you say Peter is more a team player or does he excel more when he’s on his own? Can you give a specific example for it?
- Would you describe Peter as a hands on person?
- Do you regret that Peter has left your company? Why?
- Should I hire Peter? Why?
There is plenty of reading out there with good stuff on that topic. One post that I can highly recommend is Mark Suster’s post “How to make better reference calls”.
What are your thoughts? What are your favorite questions that you use in reference calls to cut through the
Tuesday, October 06, 2015
The importance of doing reference checks (1(2)
This is a guest post by Jenny Buch, who recently joined us as a Talent Manager. It's the first in a series of two posts. The second one will appear here soon.
To follow up on the recently posted interview with Netflix CEO Reed Hastings, I’d love to share my experience about reference checks with you.
So, many of you probably made the experience of hiring someone that you would have stated as “a really promising candidate” upfront. But after four months into the job it turns out that the hire was actually a total fail, that your staff is thinking you’re an idiot for bringing him on board (even if they don’t tell you) and that you now have to pay the debts by firing that person and start a whole new time consuming hiring process again to reduce the mess you’ve just done to your organization.
Well, even though things like these sometimes just happen and can have many reasons, there are ways to dramatically reduce the likelihood. One of them is to have a strong hiring process in place with its most important asset, you can guess it – reference checks!
Reference checks have been quite common in the US and most of the English speaking countries ever since but are still fairly new to many of the European countries. This is due to cultural differences and different common practice that was established in each country years ago. So why changing that good old practice and do references checks? Here is why:
There is only so much you can get out of a certificate, a CV or an interview. Your goal is to get to know your new “promising candidate” as best as you can within a short period of time to make sure you don’t mess things up! Today, and especially in the startup scene, there’s a different need for different skills than there was when “written references” were the way you did it. Here are some classics of the “must have skills” for any kind of candidate that can only really be proved by a good reference check:
I guess I don’t have to tell you how big the impact of a bad hire can be for your organisation. Simply do the math. Really do it! Sit down and calculate how much time and money it takes you to get rid of the wrong hire and find a new person and tell the people that you are sorry rather than using this time to talk to 5 people for 10 minutes upfront. If you do that math correctly you’ll figure out that doing reference checks is going to be the easy, cheap and most efficient way for busy startups to get the right people on their rocket ship!
To follow up on the recently posted interview with Netflix CEO Reed Hastings, I’d love to share my experience about reference checks with you.
So, many of you probably made the experience of hiring someone that you would have stated as “a really promising candidate” upfront. But after four months into the job it turns out that the hire was actually a total fail, that your staff is thinking you’re an idiot for bringing him on board (even if they don’t tell you) and that you now have to pay the debts by firing that person and start a whole new time consuming hiring process again to reduce the mess you’ve just done to your organization.
Well, even though things like these sometimes just happen and can have many reasons, there are ways to dramatically reduce the likelihood. One of them is to have a strong hiring process in place with its most important asset, you can guess it – reference checks!
Or, to say it with Christoph’s words “In God we trust, all others bring references”
Reference checks have been quite common in the US and most of the English speaking countries ever since but are still fairly new to many of the European countries. This is due to cultural differences and different common practice that was established in each country years ago. So why changing that good old practice and do references checks? Here is why:There is only so much you can get out of a certificate, a CV or an interview. Your goal is to get to know your new “promising candidate” as best as you can within a short period of time to make sure you don’t mess things up! Today, and especially in the startup scene, there’s a different need for different skills than there was when “written references” were the way you did it. Here are some classics of the “must have skills” for any kind of candidate that can only really be proved by a good reference check:
- Interpersonal skills: Interpersonal skills for any kind of role matter much more these days than they did in the past (or to state it correct: people are more aware of them, they’ve always mattered). The interview situation is not the best way to find out whether or not your candidate is actually a great fit since some candidates are extremely good at selling themselves during an interview.
- Integrity: Today, an intern can become the CFO. Maybe the company sucks and he only became CFO because he went to the same university as one of the founders. As Ben Horowitz likes to say in his amazing book “The Hard Thing about Hard Things”. “There are two kinds of companies in this world. One where matters what you do and one where matters who you are. You can either be the first one or suck.” You want to make sure that his previous company was out of the first category and that besides his great university connections, he actually was the best candidate for the role and that’s why he got it - because he knows shit, works hard and is an awesome guy. I’m not saying that hiring from your university environment is bad, but it shouldn’t be the only reason for a hire - which it is sadly in many startups these days.
- Right kind of ambition: You are looking for people with the right kind of ambition. So people that love your idea, bring a “get shit done mentality to work” and that thrive to make your company successful. As a side effect it will help them grow their career - not the other way around.
- Right kind of person: You are not looking for “the Facebook Head of Sales” or the “CMO from Google”. Even though those guys do an amazing job at their current companies, every company is different and every time in every company is different. You need to find the right candidate for your company at this time. So one of your challenges is to make sure that your candidate has the right skillset for YOUR COMPANY.
I guess I don’t have to tell you how big the impact of a bad hire can be for your organisation. Simply do the math. Really do it! Sit down and calculate how much time and money it takes you to get rid of the wrong hire and find a new person and tell the people that you are sorry rather than using this time to talk to 5 people for 10 minutes upfront. If you do that math correctly you’ll figure out that doing reference checks is going to be the easy, cheap and most efficient way for busy startups to get the right people on their rocket ship!
Saturday, October 03, 2015
PNC SaaS Founder Meetup, Edition #4
![]() |
| Jack Newton, co-founder & CEO of Clio, at the 1st PNC SaaS Founder Meetup in 2012 |
The success of the first meetup, which took place in San Francisco at the end of 2012, encouraged us to do another, bigger event in 2013 in Berlin and an even bigger one in 2014, again in San Francisco. By now it has become a tradition, and last week the 4th annual PNC SaaS Founder Meetup took place in Berlin. Thanks to all the great people from our portfolio and our guest speakers it has once again been fantastic. Here are some (visual) impressions.
One of the reasons why the event is so effective is that it gives early-stage SaaS founders an opportunity to learn from later-stage SaaS founders and other SaaS experts who have already been through many of the challenges faced by the early-stage guys. Especially for founders from Europe and other places outside of the Bay area, this is a pretty unique opportunity to learn from some of the best people who've done it before. Therefore we're incredibly grateful to people like Mikkel Svane (co-founder & CEO of Zendesk), Jack Newton (co-founder & CEO of Clio), Paolo Negri (co-founder & CTO of Contentful), Olly Headey (co-founder & CTO of FreeAgent) and many others who participated in the first meetup in 2012 and keep coming to the PNC SaaS Founder Meetups ever since. Thanks guys, the startup world is a better place with you in it. :-)
PS: If you're a co-investor or friend of Point Nine and wondered why you didn't get an invitation this year: It's nothing personal, we've made it a portfolio-only event this time.
Wednesday, September 30, 2015
Introducing Jenny Buch, Talent Manager at Point Nine
Once a startup has released the first version of its product, raised some funding, started to get the word out and is getting some traction, the biggest challenge almost always becomes hiring. No matter how great the founders are and how much good advice they get from investors and advisors: You need people to get shit things done. And before long, you need more people (AKA managers) to help other people get shit things done, too. Recruiting great people can be extremely time-consuming and difficult, but if you don’t manage to build a great team, you are guaranteed to fail.
Or, as Michael Wolfe put it in his awesome talk at our 4th annual SaaS Founder Meetup last week:
Given that hiring is the #1 challenge for almost all of our portfolio companies, it has always bugged me that we’re not better at helping our founders find great people. It’s not like we haven’t been trying it and sometimes we’ve been able to find someone in our network for an open position at a portfolio company. But I’ve always wished that we’d be able to provide much more help.
That’s why we’re thrilled that we’ve hired an experienced recruiter with a strong network, Jenny Buch, to focus on this challenge full-time. In her role at Point Nine, Jenny will (besides taking care of internal HR issues) advise our portfolio companies on anything related to recruiting, culture, employee engagement and HR strategy and will help them hire awesome people. In her previous roles, Jenny has recruited dozens if not hundreds of people for fast-growing tech startups and we can’t wait to see her magic unfold in the Point Nine family.
Welcome, Jenny!
Or, as Michael Wolfe put it in his awesome talk at our 4th annual SaaS Founder Meetup last week:
All companies start differently but end up the same:
Success depends on hiring and managing a great leadership team.
Given that hiring is the #1 challenge for almost all of our portfolio companies, it has always bugged me that we’re not better at helping our founders find great people. It’s not like we haven’t been trying it and sometimes we’ve been able to find someone in our network for an open position at a portfolio company. But I’ve always wished that we’d be able to provide much more help.
![]() |
| Jenny sent me two pics ... and forgot to tell me that I should pick one. ;-) |
Welcome, Jenny!
PS: Hiring a talent manager isn’t a new idea in the VC world, and large firms like A16Z have built big teams to support their portfolio companies in a variety of areas. We can't compete with that, but we’re a little proud that we’re one of the first (the first?) micro VC funds to invest heavily into this role. :)
Monday, September 28, 2015
What animals are WE hunting?
[This article first appeared as a guest post on VentureBeat. Thank you for publishing it, VentureBeat. I'm re-posting it here with a few small edits.]
Of all posts that I’ve written so far, the one in which I asked what kind of animals you’re hunting was one of the most popular ones. That begs the question: What kind of animals are we hunting?
Paul Graham wants to farm black swans. Dave McClure likes ugly ducklings, little ponies and centaurs. Almost all large VC funds are looking for unicorns, while some people argue that investors should hunt dragons and others talk about decacorns.
If you have no idea WTF I’m talking about, here’s a quick refresher. The term unicorn was coined by Aileen Lee about two years ago to describe those rare and magical tech startups that have reached a valuation of $1 billion or more. Since then, $1B valuations have become somewhat less rare and there are now several private tech companies valued at $10 billion or more, for which the industry has come up with another name: decacorns. Before unicorns were called unicorns, people used to call these rare outlier companies, which create massive returns for their early investors, black swans (or homeruns – back then, it wasn’t mandatory to borrow terms from the animal kingdom). Duckling is Dave McClure’s name for companies that don’t become quite as as huge, and ponies and centaurs is what he calls the ones that have reached valuations of $10 million and $100 million, respectively. Finally, a dragon is a company that returns an entire VC fund.
So – what I mean by the question in the title of this post is what kind of exits we are aiming for. It’s a question which every VC needs to think about: If you have, say, a $250M fund and your goal is to return $1B before costs, should you aim for one huge outlier, e.g. a $10B exit in which you own 10%? Or are you better off shooting for 20% stakes in 50 companies which exit at $100M each? Or something in between?
For large funds the answer is pretty clear. Although the number of smaller exits is of course much bigger than the number of large exits, the exit value is highly concentrated on a small number of huge winners. This power law distribution of venture returns, which Peter Thiel has spoken about extensively, is what makes it almost impossible to return a large fund without hitting one or more outliers. Or as Jason M. Lemkin put it: VCs need multiple unicorns just to survive.
But what about a small (~$60M) early-stage fund like ours? We spent a lot of time thinking about this question in the last years, and our conclusion – or, let’s say working assumption, because it’s still early days for us – is that (sticking to the terminology described above) we’re hunting for dragons, hoping for unicorns.
In spite of the growing number of unicorns in the last years it’s still exceedingly rare for a startup to reach a valuation of $1B or more. According to Aileen Lee’s research, only 0.14% of venture-backed tech startups become unicorns. We can make around 30-40 investments with our fund, so statistically the chances of hitting a unicorn are very low. That doesn’t mean that we’re not trying hard to beat the odds – and if you don’t believe that you can beat the odds you should never become a founder or a VC in the first place – but it means that our business model is not dependent on having a unicorn in every fund that we raise.
We’re small enough for not being dependent on unicorns, but – and that’s the big difference to angel investing – we’re too big for generating a great performance by piling up a larger number of small exits. If we tried to get to, say, $240M in exit proceeds in chunks of $10M (corresponding with e.g. 20% of a $50M exit) we’d need 24 of these exits. It’s not realistic that 60-80% of the companies, in which we invest at a stage when there’s often just a handful of people and a few thousand dollars in revenues, will go on to become $50M exits though. That’s why we need a few of the animals which in the beginning of this post have been called dragons and which we internally just call “fund-makers”: Investments which return an entire fund, which in our case means, for example, 20% of a $300M exit or 15% of a $400M exit.
The final question is if all of this has any practical implications at all. Isn’t it impossible to look at a seed-stage startup and predict how large it can become anyway? Those are very hard prediction to make indeed, but still, knowing what kinds of exits we need informs several important decisions that we have to make – how many companies we want to invest in, what ownership stakes we’re aiming for, how much capital we reserve for follow-on financings, and so on. It also makes it clear that we shouldn’t invest in companies which for some reason we feel don’t have enough potential to move the needle for our fund.
The very last thing I want to say, just to be sure that I’m not misunderstood, is that I have absolutely nothing against unicorns. :-) In fact, we love ‘em. We’ve found two so far, Zendesk and Delivery Hero, so we’ve seen the beautiful side of the power law distribution first-hand. So: Hunting for dragons, hoping for unicorns.
Paul Graham wants to farm black swans. Dave McClure likes ugly ducklings, little ponies and centaurs. Almost all large VC funds are looking for unicorns, while some people argue that investors should hunt dragons and others talk about decacorns.
If you have no idea WTF I’m talking about, here’s a quick refresher. The term unicorn was coined by Aileen Lee about two years ago to describe those rare and magical tech startups that have reached a valuation of $1 billion or more. Since then, $1B valuations have become somewhat less rare and there are now several private tech companies valued at $10 billion or more, for which the industry has come up with another name: decacorns. Before unicorns were called unicorns, people used to call these rare outlier companies, which create massive returns for their early investors, black swans (or homeruns – back then, it wasn’t mandatory to borrow terms from the animal kingdom). Duckling is Dave McClure’s name for companies that don’t become quite as as huge, and ponies and centaurs is what he calls the ones that have reached valuations of $10 million and $100 million, respectively. Finally, a dragon is a company that returns an entire VC fund.
So – what I mean by the question in the title of this post is what kind of exits we are aiming for. It’s a question which every VC needs to think about: If you have, say, a $250M fund and your goal is to return $1B before costs, should you aim for one huge outlier, e.g. a $10B exit in which you own 10%? Or are you better off shooting for 20% stakes in 50 companies which exit at $100M each? Or something in between?
For large funds the answer is pretty clear. Although the number of smaller exits is of course much bigger than the number of large exits, the exit value is highly concentrated on a small number of huge winners. This power law distribution of venture returns, which Peter Thiel has spoken about extensively, is what makes it almost impossible to return a large fund without hitting one or more outliers. Or as Jason M. Lemkin put it: VCs need multiple unicorns just to survive.
But what about a small (~$60M) early-stage fund like ours? We spent a lot of time thinking about this question in the last years, and our conclusion – or, let’s say working assumption, because it’s still early days for us – is that (sticking to the terminology described above) we’re hunting for dragons, hoping for unicorns.
In spite of the growing number of unicorns in the last years it’s still exceedingly rare for a startup to reach a valuation of $1B or more. According to Aileen Lee’s research, only 0.14% of venture-backed tech startups become unicorns. We can make around 30-40 investments with our fund, so statistically the chances of hitting a unicorn are very low. That doesn’t mean that we’re not trying hard to beat the odds – and if you don’t believe that you can beat the odds you should never become a founder or a VC in the first place – but it means that our business model is not dependent on having a unicorn in every fund that we raise.
We’re small enough for not being dependent on unicorns, but – and that’s the big difference to angel investing – we’re too big for generating a great performance by piling up a larger number of small exits. If we tried to get to, say, $240M in exit proceeds in chunks of $10M (corresponding with e.g. 20% of a $50M exit) we’d need 24 of these exits. It’s not realistic that 60-80% of the companies, in which we invest at a stage when there’s often just a handful of people and a few thousand dollars in revenues, will go on to become $50M exits though. That’s why we need a few of the animals which in the beginning of this post have been called dragons and which we internally just call “fund-makers”: Investments which return an entire fund, which in our case means, for example, 20% of a $300M exit or 15% of a $400M exit.
The final question is if all of this has any practical implications at all. Isn’t it impossible to look at a seed-stage startup and predict how large it can become anyway? Those are very hard prediction to make indeed, but still, knowing what kinds of exits we need informs several important decisions that we have to make – how many companies we want to invest in, what ownership stakes we’re aiming for, how much capital we reserve for follow-on financings, and so on. It also makes it clear that we shouldn’t invest in companies which for some reason we feel don’t have enough potential to move the needle for our fund.
The very last thing I want to say, just to be sure that I’m not misunderstood, is that I have absolutely nothing against unicorns. :-) In fact, we love ‘em. We’ve found two so far, Zendesk and Delivery Hero, so we’ve seen the beautiful side of the power law distribution first-hand. So: Hunting for dragons, hoping for unicorns.
Thursday, August 27, 2015
6 reasons to be bullish on SaaS
Yesterday I argued that SaaS founders and investors shouldn’t worry about short-term movements of SaaS stocks and said that there are a lot of reasons to be bullish about the Cloud. Here are some of them.
1) SaaS is quickly becoming the norm
In the last years there’s been a dramatic shift in deployment preferences of software buyers. According to a survey by technology evaluation business Software Advice, 88% of buyers with a deployment preference preferred on-premise solutions in 2008. Just six years later, the results were completely upside-down: In 2014, 87% of all buyers with a deployment preference preferred Cloud solutions.
2) Billions of dollars of on-premise revenues are still up for grabs
In spite of this tectonic shift of deployment preferences, IDC estimates that in 2015 the market share of on-premise deployments in the enterprise applications market is still almost 80%. That means that billions of dollars will move from on-premise to the Cloud in the next ten years.
3) Millennials will move up through the ranks
In the near future, more and more IT decision maker positions will be taken over by millennials. For this generation, which grew up with Facebook and Gmail, SaaS will be the default choice. In fact, most of them will laugh at the idea that software could not be Cloud-based.
4) The entire software market will continue to grow
It’s not only about increasing the Cloud’s piece at the expense of the on-premise piece, though. Pen & paper or Excel sheets are still used by myriads of people for all kinds of business processes, especially in SMBs. Building better, Cloud-based solutions for these use cases will significantly increase the size of the total software cake.
5) Mobile expands the market to non-desk workers
About ten years ago, the number of smartphone users was negligible. Today there are more than two billion smartphone users worldwide. This development, which I think is nothing short of amazing, has (almost) suddenly increased the number of target users for B2B software companies by tens of millions in the industrialized countries alone. People in industries like construction, landscaping, hospitality and many other areas of “non-desk work”, who previously weren’t using any software, are now getting mobile apps that help them become more efficient.
6) New technologies will catalyze adoption
SaaS has always been more than just a better deployment option. It has enabled the creation of new ecosystems (Salesforce.com), new business models (Zenefits), new distribution strategies (Zendesk) and much more. The next wave of enterprise software will likely be powered by machine learning (check out this TechCrunch post for a good primer) and continued consumerization (and in some cases, new hardware). These and other innovations will allow SaaS applications to get even wider adoption and to provide even more value to its customers.
This is by no means meant to be an exhaustive list, and there are many more reasons to be bullish on SaaS. Want to let me know what you’re most bullish about? Tweet it to me!
1) SaaS is quickly becoming the norm
In the last years there’s been a dramatic shift in deployment preferences of software buyers. According to a survey by technology evaluation business Software Advice, 88% of buyers with a deployment preference preferred on-premise solutions in 2008. Just six years later, the results were completely upside-down: In 2014, 87% of all buyers with a deployment preference preferred Cloud solutions.
2) Billions of dollars of on-premise revenues are still up for grabs
In spite of this tectonic shift of deployment preferences, IDC estimates that in 2015 the market share of on-premise deployments in the enterprise applications market is still almost 80%. That means that billions of dollars will move from on-premise to the Cloud in the next ten years.
3) Millennials will move up through the ranks
In the near future, more and more IT decision maker positions will be taken over by millennials. For this generation, which grew up with Facebook and Gmail, SaaS will be the default choice. In fact, most of them will laugh at the idea that software could not be Cloud-based.
4) The entire software market will continue to grow
It’s not only about increasing the Cloud’s piece at the expense of the on-premise piece, though. Pen & paper or Excel sheets are still used by myriads of people for all kinds of business processes, especially in SMBs. Building better, Cloud-based solutions for these use cases will significantly increase the size of the total software cake.
5) Mobile expands the market to non-desk workers
About ten years ago, the number of smartphone users was negligible. Today there are more than two billion smartphone users worldwide. This development, which I think is nothing short of amazing, has (almost) suddenly increased the number of target users for B2B software companies by tens of millions in the industrialized countries alone. People in industries like construction, landscaping, hospitality and many other areas of “non-desk work”, who previously weren’t using any software, are now getting mobile apps that help them become more efficient.
6) New technologies will catalyze adoption
SaaS has always been more than just a better deployment option. It has enabled the creation of new ecosystems (Salesforce.com), new business models (Zenefits), new distribution strategies (Zendesk) and much more. The next wave of enterprise software will likely be powered by machine learning (check out this TechCrunch post for a good primer) and continued consumerization (and in some cases, new hardware). These and other innovations will allow SaaS applications to get even wider adoption and to provide even more value to its customers.
This is by no means meant to be an exhaustive list, and there are many more reasons to be bullish on SaaS. Want to let me know what you’re most bullish about? Tweet it to me!
Tuesday, August 25, 2015
Is SaaS doomed?
If one looks at the stock price development of public SaaS companies in the last few weeks, one could come to the conclusion that SaaS is over the hill. Salesforce.com: 17% down from its 52 week high. Veeva: 30% down from its 52 week high. Workday is 29% down, Box 47%, Hubspot 22%. Everyone got hit, as you can see in Tomasz Tunguz' post about the topic.
There are several reasons why this conclusion (that SaaS is past its prime) is wrong. Firstly, it's not just SaaS stocks which took a dive. The NASDAQ and the Dow Jones are both down more than 13% from their 52 week highs, too. Secondly, as this chart of the BVP Cloud Computing Index shows, SaaS stocks have outperformed the market significantly in the last couple of years, and it's not surprising that when the market corrects, stocks that went up more strongly than others are going down more strongly as well.
More importantly though, while public markets are good at valuing companies in the very long run, short term movements are – if not random – the result of all kinds of factors, most importantly supply and demand for stocks as an asset class, which itself depend on all kinds of factors that are not related to a specific company's ability to generate profits in the long run. That's why long-term public markets investors – let alone SaaS founders or VCs – shouldn't worry about the short-term movements of SaaS stocks.
Fundamentally, there are lot of reasons to be bullish about the Cloud. I'll follow-up on that with another post soon.
Friday, July 17, 2015
The evolution of the SaaS landing page
When you look at the landing pages (or homepages or marketing sites, however you want to call them) of today's SaaS companies, they usually look quite beautiful. They typically have a clean, simple and friendly look, with very little text and a lot of images or videos. In many cases, these websites could just as well advertise a consumer product. This doesn't come as a surprise, since the consumerizaton of enterprise software has been one of the most important driving forces in the software world in the last years. But B2B software websites haven't always looked like this and it's fascinating to see how much things have changed. Join me as I go back in time and take a look at how SaaS landing pages looked like some years ago.
The SaaS Stone Age
Fast-backward about 16 years. This is how the website of Salesforce.com - the most innovative software company of that time – looked like in 1999:
Interestingly, as horrible as the site looks by today's standards, it does have a bit of a consumer-ish feel and it actually became more enterprise-y over time (you can browse the history on the Internet Archive, which I've used to take these screenshots). So maybe in 1999 and the early 2000s the world wasn't ready for consumerization yet, or Salesforce.com didn't figure out the right approach or they just saw more success with a top-down enterprise sales approach.
The Beginnings of Modern (SaaS) Times
Not much happened on the SaaS design front in the following years. Until 2004, that is, when a small, Chicago-based web design agency called 37signals launched its project management tool called Basecamp:
Basecamp looked radically different from any other piece of B2B software. If it's possible to pinpoint the beginning of modern SaaS to a specific company or product, I think this honor is due to Jason Fried and his colleagues at 37signals. As much as I disagree with Jason on many things he writes about how to build a business – kudos to 37signals for their focus on product, design and usability. No other SaaS company had a bigger influence on SaaS design.
It took a few years – which shows how much ahead of its time 37signals was – but eventually other SaaS companies redesigned their websites or rebuilt them from the ground up:
The trend was clear: Less and less text, bigger font sizes, larger images, videos. SaaS companies which were founded at that time had a stronger focus on design from the get-go:
Contemporary SaaS Design
In the years that followed, the trend towards simplicity, focus on design and consumerization continued, and I'd say that since around 2012 or 2013, having a reasonably beautiful and conversion-optimized marketing website is more or less table stakes. Today you can buy a SaaS landing page template for $18. A $18 design which looks better than every B2B website that was built before 2004 – makes me wonder if Moore's law applies in design, too. ;-)
Since most people are trend-followers rather than trend-setters, SaaS landing pages started to look more and more alike in the last few years: A navigation bar at the top; 1-2 devices that were made in Cupertino, with product screenshots on them; a large headline and smaller sub-headline; 1-2 call-to-action buttons; some customer logos. This (plus a few other things) was the anatomy of almost every SaaS landing page in 2014. Not bad, don't get me wrong, but if everyone follows that recipe it gets harder and harder to stand out and build something memorable.
But just when things started to get boring, some cutting-edge design-led SaaS companies pushed the envelope further:
Both examples make heavy use of video so the screenshots don't do them justice. Please go to Geckoboard and Typeform to see them in action. While still being focused on conversion, I think these websites are almost indistinguishable from art. Using high-quality video footage, very little text and beautiful typography, crafted with incredible attention to detail, these websites bring across a value proposition in a fresh, unique and highly emotional way.
This little journey through time has shown that up until now, the evolution of the SaaS landing page has been a development towards ever more simplicity. It will be interesting to see if this trend continues in the coming years.
Disclosure: I'm an investor in Clio, Zendesk, Geckoboard and Typeform.
The SaaS Stone Age
Fast-backward about 16 years. This is how the website of Salesforce.com - the most innovative software company of that time – looked like in 1999:
![]() |
| Salesforce.com in 1999 (click for a larger version) |
Interestingly, as horrible as the site looks by today's standards, it does have a bit of a consumer-ish feel and it actually became more enterprise-y over time (you can browse the history on the Internet Archive, which I've used to take these screenshots). So maybe in 1999 and the early 2000s the world wasn't ready for consumerization yet, or Salesforce.com didn't figure out the right approach or they just saw more success with a top-down enterprise sales approach.
The Beginnings of Modern (SaaS) Times
Not much happened on the SaaS design front in the following years. Until 2004, that is, when a small, Chicago-based web design agency called 37signals launched its project management tool called Basecamp:
![]() |
| Basecamp in 2004 (click for a larger version) |
Basecamp looked radically different from any other piece of B2B software. If it's possible to pinpoint the beginning of modern SaaS to a specific company or product, I think this honor is due to Jason Fried and his colleagues at 37signals. As much as I disagree with Jason on many things he writes about how to build a business – kudos to 37signals for their focus on product, design and usability. No other SaaS company had a bigger influence on SaaS design.
It took a few years – which shows how much ahead of its time 37signals was – but eventually other SaaS companies redesigned their websites or rebuilt them from the ground up:
![]() |
| Campaign Monitor in 2008 (click for a larger version) |
The trend was clear: Less and less text, bigger font sizes, larger images, videos. SaaS companies which were founded at that time had a stronger focus on design from the get-go:
![]() |
| Clio in early 2009 (click for a larger version) |
![]() |
| Zendesk in 2010 (click for a larger version) |
Contemporary SaaS Design
In the years that followed, the trend towards simplicity, focus on design and consumerization continued, and I'd say that since around 2012 or 2013, having a reasonably beautiful and conversion-optimized marketing website is more or less table stakes. Today you can buy a SaaS landing page template for $18. A $18 design which looks better than every B2B website that was built before 2004 – makes me wonder if Moore's law applies in design, too. ;-)
Since most people are trend-followers rather than trend-setters, SaaS landing pages started to look more and more alike in the last few years: A navigation bar at the top; 1-2 devices that were made in Cupertino, with product screenshots on them; a large headline and smaller sub-headline; 1-2 call-to-action buttons; some customer logos. This (plus a few other things) was the anatomy of almost every SaaS landing page in 2014. Not bad, don't get me wrong, but if everyone follows that recipe it gets harder and harder to stand out and build something memorable.
But just when things started to get boring, some cutting-edge design-led SaaS companies pushed the envelope further:
![]() |
| Geckoboard's current website Go to www.geckoboard.com to see it live |
![]() |
| Typeform's current website Go to www.typeform.com to see it live |
![]() |
| Another view of Typeform's current website Go to www.typeform.com to see it live |
Both examples make heavy use of video so the screenshots don't do them justice. Please go to Geckoboard and Typeform to see them in action. While still being focused on conversion, I think these websites are almost indistinguishable from art. Using high-quality video footage, very little text and beautiful typography, crafted with incredible attention to detail, these websites bring across a value proposition in a fresh, unique and highly emotional way.
This little journey through time has shown that up until now, the evolution of the SaaS landing page has been a development towards ever more simplicity. It will be interesting to see if this trend continues in the coming years.
Disclosure: I'm an investor in Clio, Zendesk, Geckoboard and Typeform.
Subscribe to:
Posts (Atom)

























