Saturday, July 16, 2016

From "A as in Amiga" to "Z as in Zendesk"

In the last few weeks I participated in a few interviews/discussions to talk about SaaS, entrepreneurship, venture capital and related topics that are near and dear to my heart. If you're interested in me rambling about some of my earliest entrepreneurial adventures (hint: C64, Amiga,...) and how I found Zendesk (hint: luck), and if you don't mind listening to a heavy German accent and lots of "UMs" and "HMMs", here you go. :-)

1. The Twenty Minute VC
Listen to the podcast on ProductHunt, in iTunes or download the MP3.

2. "Managing your startup with data" at B2B Rocks in Paris




3. Interview with Seedcamp's Carlos Espinal 



Thanks to Harry, Carlos and Alexander for inviting me!

Sunday, June 26, 2016

A better way to visualize pipeline development? (WIP)

When founders show me their sales pipeline, the data is typically visualized in some variations of one of these formats:






When I see charts like this, I often find it hard to quickly wrap my head around the data and draw meaningful conclusions. Sometimes, important numbers are missing altogether. In other cases, they are there but are shown on another page or in another report.

I then find myself wonder about questions such as:

  • The pipeline is growing nicely, but how much are they actually closing?
  • How long does it take them to move leads through the funnel?
  • Are they purging their pipeline or are they accumulating a lot of "dead" pipeline value?

With this in mind I tried to come up with a new way for high-level pipeline development visualization, one that makes it easier to quickly get to the key take-aways. If you're interested in the (preliminary) result only, check out this mockup. If you'd like to learn more about my thought process and some additional details, read on.

The key problem that I have with the standard ways of looking at pipeline development is that it's hard to follow how deals move through the funnel. I've always thought that pipeline development charts should work a bit more like a cohort analysis that allows you to follow a customer cohort's development over time, and so I mocked up this:



The "pipes" give you a better understanding of what happened to the leads in a certain stage and month. For example, you can see that of the $1.6M that was in "prospect" stage in January:

  • $750k (47%) stayed in "prospect" stage
  • $500k (31%) were moved to the next stage ("demo/trial")
  • $350k (22%) were lost/purged

The next step was to add a few additional months to the mockup:



This unfortunately made things a little messy, and people will probably feel overwhelmed by the amount of numbers. One solution, if someone decides to build a little application like a Salesforce.com add-on, could be to hide all of the pipe numbers by default and show them on-hover (maybe with an option to show them all at once):



What's still missing are some aggregated key metrics ...



... and a better way to quickly grasp how these numbers have changed month over month:



Here's one mockup with all three elements on it:



What you can quickly see in this example is that this imaginary startup is adding an increasing dollar amount of prospects to the pipeline and keeps closing deals, but the rate at which it moves leads to the bottom of the funnel is declining. At the same time, the percentage of lost deals has been growing slowly, while the percentage of deals that remained in the same stage has increased sharply, indicating an increase in sales cycle and/or a poor job of pipeline purging. This has already led to a shrinking bottom-of-the-funnel pipeline, and if the company can't figure out and fix the cause of that development, it will soon close less and less deals.

All of this is something that you can immediately see by looking at these charts and numbers and which I think is usually harder to see by looking at traditional pipeline charts. What do you think? Looking forward to your comments!






















Friday, June 03, 2016

SaaS Funding Napkin, the mobile-friendly edition

My "SaaS Funding Napkin", published a few days ago, got lots of love on Facebook, Twitter, etc. Thanks everybody! Some people (rightfully) mentioned, though, that the image is hard to read on mobile devices. So if a napkin has a good format for a desktop or laptop screen, which real-world-analogy could be a fit for mobile screens?

You guessed right.

Here you go (please scroll down or click here).


Tuesday, May 31, 2016

What does it take to raise capital, in SaaS, in 2016?

When we invest in a SaaS startup, which almost always happens at the seed stage, the next big milestone on the company’s roadmap is usually a Series A. If you carry this thought further and assume that the biggest goal after the Series A is to get to the Series B (and so on, you get the idea) it sounds like turtles all the way down. But financing rounds are obviously not a goal in itself. They are a means to a bigger goal. Some SaaS companies got big without raising a lot of capital – Atlassian, Basecamp and Veeva are probably the most famous examples. But they are exceptions, not the rule. According to this analysis of Tomasz Tunguz, the median SaaS company raises $88M before IPO.

So what does it take to raise money for a SaaS company in 2016? With constantly rising table stakes and a fundraising environment that looks quite a bit less favorable than last year’s, I believe the bar is higher than in the last 18-24 months (although raising money is still much easier than it was in “Silicon Valley’s nuclear winter” in 2008).

Below is my back of a (slightly bigger) napkin answer to this question.

A few important notes:

  • The assumption of the information in the table is that the founding team is relatively “unproven”. Founding teams with previous large exits under their belts can raise large seed rounds at very high valuations on the back of their track records and a Powerpoint Keynote presentation.
  • Some of the information is tailored to enterprise-y SaaS companies. If you have a viral product (like Typeform or infogram), some of the “rules” don’t apply.
  • If you have virality and a proven founder team, you’re Slack and no rules whatsoever apply. :)


(click here for a larger version)

PS: Thanks to Jason M. LemkinTomasz Tunguz, Nicolas Wittenborn and my colleagues at Point Nine for reviewing a draft of this post!

[Update 1: Here's a mobile-friendly version of the napkin.]

[Update 2: And here is a Google Sheet version for better readability. :) ]



Monday, April 11, 2016

Introducing the French Cloudscape

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!




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.

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:

=(W87-U87)*$E$124+X96

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):

=0,5*(Costs!J62+Costs!J96+Costs!J104+Costs!J112+Costs!J122)/I49

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.]