Jan. 2, 2023
Jack Newton, Founder of Clio | How to Run a Beta Program
If you're selling to businesses, you already know... before you publicly launch your product, you'll have to go through a private beta. But beta programs are not all made equal. Many founders go through the motion but get very little out of it. Others, like Jack (the founder/CEO of Clio, a $1.5B start-up) leverage it to get the right customers, helpful feedback, and a successful launch. Who should you let in and how do you get them? How early should you let customers in? When do you k...
If you're selling to businesses, you already know... before you publicly launch your product, you'll have to go through a private beta.
But beta programs are not all made equal. Many founders go through the motion but get very little out of it. Others, like Jack (the founder/CEO of Clio, a $1.5B start-up) leverage it to get the right customers, helpful feedback, and a successful launch.
Who should you let in and how do you get them? How early should you let customers in? When do you know you're ready to launch? Those are a few of the questions Jack answers on the show. If you're going through a beta, this is the episode for you.
02:01 - Cloud Computing in 2007
03:28 - Transforming Legal Technology
07:33 - The Customer Development Process
10:17 - How to Run a Successful Beta Launch
15:58 - Benefits to Working With a Smaller Team
19:10 - The Power of Constraints
24:00 - Being a Part of the Narrative
27:01 - Active Customer Feedback
32:33 - Prepare for Launch
35:26 - Serendipity in Fundraising
40:30 - True Product Market Fit
43:42 - Recap
WEBVTT
00:00:00.000 --> 00:00:06.759
What was really clear to Ryan and I, that cloud computing was going to transform every industry in a pretty profound way.
00:00:07.059 --> 00:00:21.120
What we went to work on was identifying an industry that we thought was ripe for transformation and especially amenable to the kind of transformation that the internet would bring.
00:00:21.120 --> 00:00:26.359
Welcome to the product Market Fit Show, brought to you by Mistrial, a seed-stage firm based in Canada.
00:00:26.980 --> 00:00:28.879
I'm Pablo, I'm a founder turned VC.
00:00:29.210 --> 00:00:32.719
My goal is to help early stage founders like you find product market fit.
00:00:36.250 --> 00:00:38.399
Welcome to the product Market Fit Show.
00:00:38.401 --> 00:00:41.960
Today we have Jack, the founder and CEO of Clio.
00:00:42.030 --> 00:00:44.920
Cloo is a startup in the legal tech space.
00:00:44.920 --> 00:00:49.200
They basically did vertical SaaS before it was cool, before it was a thing.
00:00:50.081 --> 00:00:52.799
They sell a product that helps lawyers run their firms.
00:00:53.329 --> 00:00:54.719
They're based in Vancouver.
00:00:54.720 --> 00:00:58.439
They have over 800 employees and are worth well over a billion dollars.
00:00:58.869 --> 00:01:01.439
Jack, it's a pleasure to have you here on the show.
00:01:01.439 --> 00:01:02.439
Hey, thanks for having me, Pablo.
00:01:03.090 --> 00:01:08.079
The topic of today's episode is how to run a beta program.
00:01:08.590 --> 00:01:11.640
I think beta programs are pretty well-known.
00:01:11.909 --> 00:01:19.359
I think most B2B SaaS companies that I speak with do them, but they're not all made equal is how I would summarize it.
00:01:19.361 --> 00:01:22.519
I think there's much better ways to do it, much worse ways to do it.
00:01:23.349 --> 00:01:27.280
Oftentimes it's something that people are just going through the motion.
00:01:27.281 --> 00:01:31.400
They know that you got to run a beta program, so you do it and then you just-- all you really want to do is launch the product.
00:01:32.060 --> 00:01:46.920
You seem to have done it really kind of thoughtful way that led to a really successful launch and obviously over time to a unicorn and a big company and one of the biggest successes to come out of Canada, so really looking to forward to diving into that with you.
00:01:47.390 --> 00:01:56.640
I think maybe to start, it'd be great to go a little bit backwards and kind of get started on early 2008 and how you came up with the idea in the first place.
00:01:56.801 --> 00:01:59.519
Then we can dive into the beta program and all those details.
00:01:59.519 --> 00:02:00.640
Sure, yeah, sounds great.
00:02:01.209 --> 00:02:20.080
So my co-founder, Ryan Govoro and I, back in 2007-- I sometimes describe us as two hammers looking for a nail because what we saw back in 2007 was this enormous technology transformation wave that was cloud computing.
00:02:20.441 --> 00:02:28.199
What was really clear to us, even though this is 15 years ago now, is pretty early innings for cloud computing.
00:02:28.430 --> 00:02:30.719
Salesforce was just starting to get some traction.
00:02:30.721 --> 00:02:36.680
This was before the first iPhone was released, so very different technological era in many industries.
00:02:37.210 --> 00:02:40.360
On-prem software was still, the dominant computing platform.
00:02:41.129 --> 00:02:50.400
What was really clear to Ryan and I is that cloud computing was going to transform every industry in a pretty profound way.
00:02:51.121 --> 00:03:04.719
What we went to work on was identifying an industry that we thought was ripe for transformation and especially amenable to the kind of transformation that the internet would bring.
00:03:06.080 --> 00:03:19.360
It didn't take us long in surveying these industries to hone in on legal as an area that that really had not changed how it operated in hundreds or maybe even thousands of years, the way lawyers--
00:03:19.759 --> 00:03:23.080
For context, you were doing what at the time?
00:03:23.600 --> 00:03:23.919
Were you working?
00:03:23.919 --> 00:03:24.719
Were you a student?
00:03:24.721 --> 00:03:26.800
Were you-- what kind of phase were you in?
00:03:26.990 --> 00:03:35.879
Yeah, so I was at the time working as a product manager at a company called Knenomics, which was a life sciences company.
00:03:37.401 --> 00:03:41.039
Ryan, my co-founder, he and I have been life- long best friends.
00:03:41.040 --> 00:03:48.800
We'd always been noodling on different business ideas and going back and forth on what we might be able to do together.
00:03:49.110 --> 00:03:59.080
Ryan was both pursuing his MBA and working as the IT manager at Gallings, which is one of Canada's largest law firms, about a thousand lawyers.
00:03:59.841 --> 00:04:17.519
He had a first row seat to how technology was being used in law firms or maybe better put was not being used in law firms, hallways full of paper-- filing cabinets full of paper and very manual processes.
00:04:18.699 --> 00:04:28.600
The other relationship that Ryan had that really helped us validate this instinct that we had that there was an opportunity in legal was with The Law Society of BC.
00:04:29.521 --> 00:04:33.879
They're, for US listeners, very analogous to US Bar Association.
00:04:34.839 --> 00:04:44.360
They're regulator of lawyers and if a lawyer does something wrong, it's the Bar Association or the Law Society that ends up having to discipline them.
00:04:44.778 --> 00:04:55.560
We had a relationship with the Director of Practice Standards at the LSBC that really helped validate this idea that lawyers, number one, struggle with using technology overall.
00:04:55.560 --> 00:05:02.838
At large law firms, they often compensate for that lack of technology use with sheer manpower.
00:05:02.839 --> 00:05:17.240
They've got a lot of paralegals and support staff and other folks to make sure that the engine is running and humming along and that they're not dropping balls like missing key limitation dates or mishandling trust accounts, for example.
00:05:18.279 --> 00:05:23.240
Solos and small firms didn't have this human infrastructure to help support them.
00:05:23.521 --> 00:05:51.000
Therefore that's what the Law Society of BC and many other law societies across Canada and bar associations across the US-- what they see is that this solo small firm segment of their membership is the one that struggles the most to stay on top of their practice and is therefore the group that they end up needing to discipline the most when they drop the ball on some key client deadline or maybe in mishandling trust accounts and so on.
00:05:52.180 --> 00:06:18.959
This is really the light bulb moment for Ryan and I was realizing that there's, number one, a huge opportunity to transform legal technology from on-premises software to cloud-based software and a gigantic opportunity in this solo and small firm segment, which we eventually realized was-- it sounds like a niche, but it's actually 80% of the legal market is lawyers practicing in firms of one to ten lawyers.
00:06:19.161 --> 00:06:27.399
Fully half of all lawyers practice in small firm-- in a solo environment with maybe one or two support staff.
00:06:27.850 --> 00:06:38.600
So even though we think about lawyers practicing in these big office towers in a nice AAA downtown office space of-- with a thousand lawyers and five floors of people, that's not the reality.
00:06:38.600 --> 00:06:42.319
The reality is it's a very entrepreneurial, very SMB market.
00:06:44.000 --> 00:06:56.720
Back in 2007-- to kind of set the stage for the discussion around the beta, 2007 was where Ryan and I built the conviction that this was a big market opportunity.
00:06:57.088 --> 00:07:00.800
We pulled shoot, we quit our jobs, and we started building Clio.
00:07:01.180 --> 00:07:03.920
Maybe on that, I mean, did you quit your jobs?
00:07:04.641 --> 00:07:23.560
A lot of this sounds like top-down market research, understanding cloud computing at a high level, understanding the makeup of the legal industry, dissecting that until you come up on a problem that you feel is worth solving versus, let's say, scratch your own itch or even customer discovery-driven effort.
00:07:24.480 --> 00:07:25.360
Was that the reality?
00:07:25.920 --> 00:07:32.920
With that, you decided let's jump off this cliff and quit our jobs, or was there a lot more customer discovery that kind of led to that moment?
00:07:33.589 --> 00:07:43.279
Yeah, one of the really influential books for me at this time of Clio's journey is a book called Four Steps to the Epiphany by Stephen Gary Blank.
00:07:45.069 --> 00:07:54.399
Much of the ideas that he puts forth in this book are kind of later built on and elaborated on with some of the concepts in the Lean s tartup, for example.
00:07:56.629 --> 00:08:10.279
What S tephen talks about in this book that I think is so important is this idea that you can have an idea for a product, which is great, but a t rap many founders fall into is a build it and they will come mentality.
00:08:10.281 --> 00:08:12.639
They're so excited about their product.
00:08:12.641 --> 00:08:23.720
They think it's obvious there's customers out there for that product and don't go through a really important step o f the process thathe talks about in this book that's called customer development.
00:08:24.050 --> 00:08:27.360
So go find the customers that you think will buy this product.
00:08:27.360 --> 00:08:32.519
Put your product in front of them and validate that they'll actually buy it.
00:08:33.120 --> 00:08:44.080
As obvious as that sounds, it's a step many startups skip only to find that they launched the product to an uninterested and un-buying audience.
00:08:45.400 --> 00:08:49.600
Where Ryan and I spent a lot of time-- and this was moonlighting, by the way, in the early days.
00:08:49.600 --> 00:08:58.320
We were working evenings and weekends, and I was spending late nights working on this idea and doing this customer development work alongside Ryan.
00:09:00.120 --> 00:09:08.840
We really built the conviction that this was an idea that was worth pulling shoot on on two great jobs to go and make a reality.
00:09:08.909 --> 00:09:38.759
What we were able to do in this early customer development process is just put prototypes in front of solo and small firm lawyers and say, hey, based on this wireframe and based on the capabilities that this product would deliver to you, would you give me your credit card number, not just is this interesting to you, is this something that makes you excited but is this something you would pay cold hard cash for and what would you pay if you were to pay for this product?
00:09:39.360 --> 00:09:52.360
That's a really important part of the product validation process and one that gave us a lot of conviction by the time it came to quiting our jobs and going full time on this thing that this had traction before we wrote a line of code.
00:09:53.120 --> 00:09:54.320
Perfect So that makes a lot of sense.
00:09:54.321 --> 00:10:00.678
So now you've got indications that firms really have this problem and are willing to pay for it.
00:10:01.190 --> 00:10:07.000
When do you start thinking about-- are you following this book, Four Steps of the Epiphany, which is a great book by the way, and I highly recommend it.
00:10:07.000 --> 00:10:14.240
Are you following step-by-step and therefore your next step is clearly okay, let's run a beta and extract dollars from these clients?
00:10:14.240 --> 00:10:16.558
Is that how you were thinking about the next step?
00:10:17.090 --> 00:10:33.360
So our approach was building out this beta-level product and where we were really deliberate was in framing the beta as something that we believe did not have full product market fit.
00:10:33.669 --> 00:10:38.080
I think there's-- you talked a little bit about how do you run an unsuccessful beta?
00:10:38.081 --> 00:10:39.200
How do you run a successful beta?
00:10:39.870 --> 00:10:51.519
I think many companies-- many, many early stage startups launch a beta with a presumption and maybe even the dependency that all that's being tweaked in the beta is bug fixes.
00:10:52.201 --> 00:10:55.879
You really don't want to learn anything new about your customer in the beta.
00:10:56.149 --> 00:11:01.960
You launch the beta and you're launching the full product two weeks later or a month later.
00:11:01.961 --> 00:11:06.159
It's more of a hardening step to make sure there's no catastrophic bugs.
00:11:05.669 --> 00:11:26.600
We took the approach with the beta and the way we engaged with our customers as we think we're 80% of the way there with the product and the product market fit, but we're going to really be open-minded about learning new things about what our customers need and building incremental functionality over the course of the beta.
00:11:26.899 --> 00:11:41.799
With that view, we launched the beta in March of 2008 and launched the final product, the paid version of the product, six months later in October of 2008.
00:11:42.360 --> 00:11:51.000
We really created this time box for ourselves to say, hey, we're going to bridge this last 20% over the course of this six months.
00:11:51.000 --> 00:11:58.960
We're going to work really, really hard over the six months probably, and we're going to need a lot of highly engaged customers to help us get over this last mile.
00:12:00.441 --> 00:12:25.120
With a view to rethinking how the beta program runs and really, again, leaning into this customer development framework that Stephen Blank talks about, we approached the beta as something that we would rather have a small handful or two of very highly engaged customers that are representative of our overall customer base than thousands of lightly engaged customers.
00:12:25.259 --> 00:12:37.678
The reality with a lot of beta programs is you get the tire kickers that just come along, sign in once, check out the user interface, and play around with it for five minutes and they never come back.
00:12:38.000 --> 00:12:42.039
You're obviously never-- you're not getting high information content.
00:12:42.041 --> 00:12:45.440
You're not getting good signal to noise feedback from those customers.
00:12:46.559 --> 00:12:59.250
The question Ryan and I asked ourselves is how can we really create a bit of a hurdle to getting into the beta so that the customers that are in there really care and are really going to give us valuable feedback.
00:12:59.971 --> 00:13:21.730
We came up with this pretty straightforward idea, which was you sign up for access to the beta, you request access to the beta, which is a concept lots of companies do, but the friction point we introduced was you sign up for the beta and to get into the beta, you need to attend a 30-minute live webinar with one of me or Ryan.
00:13:21.990 --> 00:13:32.970
We would walk you through the product, teach you how to use it, give you a bit of a tour, and give these beta customers a chance to give us real time feedback.
00:13:34.549 --> 00:13:35.808
Two things ended up happening.
00:13:35.809 --> 00:13:41.649
One, as you would expect, there was a huge drop-off in that the tire kickers were not willing to spend this half-hour.
00:13:42.190 --> 00:14:23.450
The customers that did spend this half hour with us ended up engaging with a product deeply, and we ended up having about a hundred very engaged, high information content, high value beta customers, giving us a ton of valuable feedback over those six months, not only that, but this 30-minute webinar ended up being something that turned into oftentimes a one hour, two hour, three hour information-gathering session with the customers where they actually gave us a huge amount of feedback in real time over the course of this tour of, oh, well, I can't use this product because you don't do X, Y or Z, or I find this flow a little bit confusing, or where do I go to do X?
00:14:23.710 --> 00:14:37.049
We were able to really quickly hone in on what are the key things they're trying to accomplish; what are the friction points of the product; And importantly, what are the gaps that don't exist in the product that we need to build in time for this full-blown October launch?
00:14:38.860 --> 00:15:11.080
It sounds obvious, maybe, in terms of like, hey, this is a good way to structure a beta program, but it ended up being transformative to us in terms of how high quality our October release ended up being and how willing a really substantial percentage of those hundred beta customers were willing to convert to paying customers on October 1st when we flipped the switch and said, okay, your free beta access period is over and here's the full product and you're now going to be one of our first hundred paying customers.
00:15:11.610 --> 00:15:12.600
It makes a lot of sense.
00:15:13.000 --> 00:15:14.440
I think that's what often gets missed.
00:15:14.441 --> 00:15:16.759
If you think about product market fit, there's really two sides to it.
00:15:16.760 --> 00:15:22.840
I mean, you have the product and you have the market, and oftentimes the focus is entirely on just changing the product, changing the product until things work.
00:15:23.629 --> 00:15:27.960
Half the battle at least is figuring out which market you should put this product into.
00:15:29.441 --> 00:15:39.000
There's a lot of talk about making things as frictionless as possible, which probably makes sense as your product matures, but in the early days, you really want to make sure you're driving tons of value for those early customers.
00:15:39.240 --> 00:15:41.840
That partially means having a really good product.
00:15:41.929 --> 00:15:45.080
It also partially means having the right customers for that product.
00:15:45.360 --> 00:15:47.799
I think that's what you're doing when up the bar like that.
00:15:48.220 --> 00:15:49.200
Few quick questions.
00:15:49.201 --> 00:15:57.919
I mean, the first thing, just to set the stage, was it just the two of you at that point that are doing all the work, the sales, the marketing, and building the actual product?
00:15:58.590 --> 00:15:59.080
Yeah.
00:15:59.081 --> 00:16:09.799
Over that first six months to launching a product in October, it was the two of us wearing every hat, coding, marketing, selling, doing these webinars.
00:16:11.081 --> 00:16:31.889
They obviously ended up being very time-consuming, but they were absolutely worth it because we could wrap up one of those customer calls and literally swivel our chair and start coding the feature or the bug fix or whatever the case might be that we needed to do to help make the product a better fit for that customer.
00:16:32.350 --> 00:16:44.809
These days, and I think things have changed a little bit, and I don't know if you had fundraised at that point, but these days it's pretty common that at that stage, you may have raised one, if not two, not$3 million and have a team of five, ten people doing that.
00:16:45.039 --> 00:16:46.169
What do you think about that?
00:16:46.331 --> 00:16:52.649
Would you have rather have a team of five or ten at that point and therefore have devs doing this and salespeople doing that?
00:16:52.659 --> 00:16:56.370
Or was there value to it just being the two you in those really early stages?
00:16:56.559 --> 00:16:57.970
Yeah, it's a great question.
00:16:59.931 --> 00:17:14.569
I think one of the things that's incredible about a two-person team that is able to hold everything in their head around what customers want, the customer conversations just had.
00:17:16.171 --> 00:17:23.009
Ryan and I, like I said, we've been best friends since we were eight years old, so extremely high bandwidth conversations.
00:17:23.010 --> 00:17:30.049
We were just able to hold everything about what Clio needed to do and what our customers were giving us feedback on in our heads.
00:17:30.891 --> 00:17:44.250
The communication overhead that comes with even a five-person team ends up being enormous compared to the kind of velocity that a really small team can move when you've got the clarity of vision of what you need to build.
00:17:45.819 --> 00:18:02.000
If I had to do it again, I'd probably do it the same way because I think we were just able to iterate and pivot and hold so much context in our heads that we were able to move at the right velocity with the right information.
00:18:02.721 --> 00:18:14.599
I think with five people, we might have actually had more bandwidth than we needed going into communicating and not enough torque going into actually building the product and writing and shipping code.
00:18:14.829 --> 00:18:22.118
Yeah, that definitely foots-- and I totally think there is that part of communication overhead that's totally diminished velocity.
00:18:22.380 --> 00:18:26.000
The other side to it too I find is there's power in constraints.
00:18:26.000 --> 00:18:29.759
When there's two of you, you can really only focus on so much because you're maxed out.
00:18:29.760 --> 00:18:32.640
You're probably working 12, 14 hour days or whatever it is.
00:18:32.641 --> 00:18:47.000
When there's 10 people, you want everybody to be doing something and the challenge is you might do more than you need to and go down wrong tangents that take up so much time and have so much higher trade-offs than you might see at a time.
00:18:47.119 --> 00:18:48.319
I think that makes a lot of sense.
00:18:49.380 --> 00:18:58.279
The other question I want to understand as well, because I think this is really important, is you talk about having access to a beta and then having a funnel to find the right ones.
00:18:58.681 --> 00:19:01.319
Moving up that funnel, top of the funnel, there's just two of you.
00:19:01.470 --> 00:19:04.079
What are you doing to get law firms in the first place?
00:19:04.080 --> 00:19:06.680
Are you smiling and dialing in your city?
00:19:06.740 --> 00:19:08.440
Are you doing online ads?
00:19:08.441 --> 00:19:09.400
What was the strategy?
00:19:10.509 --> 00:19:13.960
Yeah, so we had-- you talked about the power of constraints.
00:19:13.961 --> 00:19:15.680
We had the power of two constraints.
00:19:15.681 --> 00:19:19.920
One, there was only the two of us, and the second was we had almost no money.
00:19:21.269 --> 00:19:36.200
We'd raised a hundred thousand dollars from friends and family that really went mostly into legal and startup costs and our IT infrastructure and some of the very early kind of cloud infrastructure in those days.
00:19:37.809 --> 00:19:47.079
To answer one of the questions you asked, we hadn't done a fundraise at this point, so we're really working off of this hundred thousand dollars, which created a ton of constraints.
00:19:48.840 --> 00:19:54.358
Again, in retrospect, I think there were constraints that actually had a very positive outcome on the company.
00:19:54.858 --> 00:20:11.960
The other backdrop for this 2008/2009 period we were launching the product in was obviously we were in the depths of the financial crisis and in the worst fundraising environment that existed over the last 15 years.
00:20:12.161 --> 00:20:18.680
We're maybe in the midst of really the only other downturn right now that we've had in the last 15 years.
00:20:18.681 --> 00:20:27.680
So that made even fundraising that friends and family round challenging in the sense that people were really worried about where the financial system was headed.
00:20:28.201 --> 00:20:34.599
It feels like it was an alternate universe, but people were worried about the financial system as we knew it collapsing entirely.
00:20:35.119 --> 00:20:37.480
There was a lot of fear out there.
00:20:39.601 --> 00:21:09.480
We had a lot of constraints and the approach we took was let's tap into this audience of lawyers that, if you think about the technology diffusion curve and crossing the chasm, tap into this group of potential customers that are in the early adopters segment, the technophiles, the people that really are excited about new technologies and tap into that base as our first early segment of customers to go after.
00:21:10.201 --> 00:21:21.118
Then we got really deliberate about a PR campaign and a marketing campaign that-- where we got coverage on some of the top legal technology blogs like Bob Ambrosia's law sites is one example.
00:21:20.921 --> 00:21:35.680
Where we announced our initial beta and where we ended up getting the vast majority of our beta customers from in fact was just a blog post from a legal technology writer that everyone that cares about legal technology pays attention to.
00:21:36.329 --> 00:21:55.200
We also invested in trying to create a marketing or PR angle around the fact that Clio was really the first cloud-based practice management system to launch in beta form and in full form later in October in the world.
00:21:56.000 --> 00:22:00.680
We were really the first company to bring cloud computing to legal.
00:22:00.858 --> 00:22:11.799
What's very interesting about that is lawyers have very specific fiduciary responsibilities around how they manage and handle client data.
00:22:12.180 --> 00:22:17.279
They have an obligation to protect the confidentiality of client data.
00:22:17.430 --> 00:22:23.519
They have an obligation to have a reasonable expectation of privacy in where they store that client data.
00:22:23.809 --> 00:22:31.319
So there's a very open question in 2008 around whether cloud computing is an acceptable thing for lawyers to use.
00:22:32.119 --> 00:22:41.559
There was a pretty loud contingent of naysayers out there creating a bunch of fear, uncertainty and doubt around cloud computing for lawyers that we felt we had to counter.
00:22:42.441 --> 00:23:00.640
We realized we're either going to get dragged along by this narrative that cloud computing is somehow dangerous and unacceptable for lawyers to use, or we're going to be able to lead the narrative and chart the course for how lawyers should responsibly embrace cloud computing and leverage cloud computing to their advantage.
00:23:01.450 --> 00:23:09.200
We obviously chose the latter and created a story around cloud computing in general and what that means for lawyers.
00:23:09.921 --> 00:23:15.759
Then Clio ends up getting mentioned as an aside when I'm getting quoted or I'm giving a talk or whatever the case might be.
00:23:16.280 --> 00:23:19.680
That drove a lot of awareness and inbound interest in Clio as well.
00:23:20.130 --> 00:23:36.240
So our marketing budget for the first year of our launch over 2008 was basically a few hundred dollars per month that we were spending on some very experimental Google ads and otherwise free just with this PR effort
00:23:36.269 --> 00:23:44.839
That's really interesting and really unique because I would think in the early days, especially for something like B2B SaaS, your go-to thing would be, we'll just start calling.
00:23:44.840 --> 00:23:46.880
I mean, you got a list of law firms, right?
00:23:47.040 --> 00:23:58.519
They're pretty public, so just pick up the phone and start going because PR, I mean, there's a bit of a hit-and-miss element and it also, generally speaking, takes time to develop a strategy to get it going and so on.
00:23:59.730 --> 00:24:08.118
Do you think this is underutilized, this idea of tying onto a narrative, especially for people going after the long tail, maybe something that founders should be doing more of?
00:24:08.118 --> 00:24:22.599
I do think it's underutilized and I think too many founders-- and I certainly fit in this category in the early days-- expect that your company is exciting enough that reporters should be wanting to write about Clio.
00:24:23.608 --> 00:24:24.680
Of course, it's amazing.
00:24:24.681 --> 00:24:26.039
It's like your baby, right?
00:24:26.359 --> 00:24:28.720
Why isn't everyone writing stories just about Clio?
00:24:30.201 --> 00:24:37.039
What I came to realize was reporters aren't looking to write about specific companies with very rare exceptions.
00:24:37.040 --> 00:24:39.680
They're, of course, writing about Google and Uber and Airbnb.
00:24:39.681 --> 00:24:49.519
In general, they want to be talking about trends and they want to be talking about informing their audience around important trends that are happening in their industry.
00:24:49.279 --> 00:24:52.920
You want to be part of that story and part of that narrative.
00:24:52.921 --> 00:24:59.200
That's actually a much easier thing to do than to get a story written about you specifically.
00:24:59.201 --> 00:25:06.920
No reporter wants to be just helping publicize your company, at least most reporters don't.
00:25:07.240 --> 00:25:12.759
There's certainly some that will write about a specific company and there's blogs like Tech Crunch that do that almost exclusively.
00:25:12.760 --> 00:25:22.759
You want to figure out-- you really-- getting in Tech Crunch is about getting in front of your co-founder friends and feeling good that you've got your company covered in Tech Crunch.
00:25:23.039 --> 00:25:32.519
Where you really want to be getting covered is in the kind of publications that your prospective customers are reading and staying on top of what's going on in their industry.
00:25:32.779 --> 00:25:39.000
Again, I think that's where you can have very powerful customer acquisition economics.
00:25:39.000 --> 00:25:56.519
It's one of the places I think that vertical SaaS has a huge advantage relative to horizontal SaaS where you need to take a much more expensive horizontal and brand-based and advertising in the New York Times or other mainstream kind of media.
00:25:56.519 --> 00:25:58.799
You don't need to do that as a vertical SaaS player.
00:25:58.800 --> 00:26:14.039
You can get very targeted your approach, get in front of customers through these niche publications that reach maybe only a million or 2 million readers, but every single one of those million or 2 million readers is your target segment.
00:26:15.441 --> 00:26:18.480
Again, the headline can be cloud computing is coming to legal.
00:26:18.240 --> 00:26:24.440
You're catching the reader's attention, and then they're going to hear about Clio and they're going to read a soundbite from me in that article.
00:26:25.921 --> 00:26:28.400
Reporters are usually hungry for content.
00:26:28.401 --> 00:26:29.839
They're looking for a story.
00:26:29.840 --> 00:26:32.799
They're looking for a lead that they can sink their teeth into.
00:26:34.161 --> 00:26:47.160
I think more startup founders could be putting more energy into figuring out what's an exciting narrative that my company is part of as opposed to rying to get somebody to write an article specifically about your company.
00:26:47.460 --> 00:26:49.000
You use PR at the top of the funnel.
00:26:49.000 --> 00:26:58.640
You get that long tail, especially the ones that seem to be more interested in the funnel, and then you raise the bar through webinars to pick the right ones.
00:26:58.641 --> 00:27:00.160
You get a few hundred of them into the beta.
00:27:00.710 --> 00:27:02.640
What really happens in those six months?
00:27:02.800 --> 00:27:15.000
First of all, are you charging these customers or what's kind of the give and take and how do you set things up to get the appropriate amount of feedback throughout and really make the right changes over the six-month period?
00:27:15.108 --> 00:27:32.079
Yeah, that's a great question because there's the initial customer interview and again, something we paid really close attention to in that initial customer interview was trying to get a sense for whether this customer was representative of the wider customer base.
00:27:32.840 --> 00:27:49.599
This is really important when you're putting on your product manager hat as a founder, is you're going to get requests from customers, and some of those requests are going to be really esoteric, really specific requests that are not generalizable.
00:27:49.881 --> 00:27:58.358
They're looking for you to make basically custom software for their law firm and other requests are going to be much more generalizable and representative of the market in general.
00:27:58.961 --> 00:28:37.160
Again, I think the key approach that we took here that the-- again, this customer development framework espouses is if you can do a good job of finding ten representative customers in a large enough niche, you're going to be able to find-- if you build that product market fit for those ten customers and you do a good job of customer development, really understanding what those ten customers need and that they'll buy your product, you will be able to find a hundred and 1,000, and 10,000 and eventually a hundred thousand customers if you take that-- those early steps in the right way.
00:28:37.160 --> 00:28:45.839
So we were very, very selective and very careful in who we let into the beta in those first 10 and 50 and eventually hundred customers.
00:28:47.560 --> 00:28:56.119
The bargain that we negotiated with these customers was basically, look, we're-- let me give you the product for free for the beta period.
00:28:56.401 --> 00:28:58.160
It was open-ended as to how long it would be at that point.
00:28:58.161 --> 00:29:01.160
We hoped it would be about six months, but we knew it might take longer.
00:29:01.161 --> 00:29:06.359
Maybe it would be shorter, but likely around six months or longer.
00:29:08.769 --> 00:29:11.680
In exchange we'd love active feedback from you.
00:29:12.000 --> 00:29:23.200
We made it really low friction for them to just click a give us feedback button in the bottom right corner of the app and just send us a note around something that they liked or disliked about the app.
00:29:23.609 --> 00:29:34.559
We also asked that they engage with us regularly, and it was around once a month or so to have some level of follow-up call or webinar and just get feedback on how the product's working for them.
00:29:34.819 --> 00:29:39.839
Again, we got great initial feedback in that initial onboarding call.
00:29:41.089 --> 00:29:56.849
Again, a wealth of more deeply rooted feedback after a month or two months on the beta where they could really identify here's the friction points, here's the gaps, here's some of the places I'm struggling in the product, and similarly, here's some of the things I'm loving.
00:29:58.170 --> 00:29:59.250
There any major-- I'm curious.
00:29:59.250 --> 00:30:19.690
Those feedback points, was it mainly UI and small tweaks and here's how you could remove a step or were there any-- and I know it was a long time ago, so you might not remember, but do you remember any kind of major breakthrough type requests that really made you rethink some feature or add a feature or take away a feature, something that really changed the course of things?
00:30:20.460 --> 00:30:21.369
Oh, yeah, it was both.
00:30:23.010 --> 00:30:26.930
Lots of just hey, found this to be a little bit high friction.
00:30:27.651 --> 00:30:30.529
Can you help this workflow work a little bit better?
00:30:31.059 --> 00:30:45.970
So lots of that type of feedback, but we had actually yawning chasms of functionality missing from the product in that initial beta and some hypotheses that we had just gotten wrong around what the product needed to do.
00:30:46.891 --> 00:30:47.730
I'll give you one example.
00:30:47.950 --> 00:30:55.410
One was we didn't have an integrated document management system when we launched the beta and we figured, hey, there's Dropbox.
00:30:56.010 --> 00:31:01.490
There's some other relatively early cloud-based document storage options out there.
00:31:02.180 --> 00:31:10.170
We don't need to get in the document management business with Clio as a first launch vehicle or MVP.
00:31:12.050 --> 00:31:15.730
Our customers came back loud and clear over the course of that early beta.
00:31:15.730 --> 00:31:36.450
In fact, by the time we were a few days into boarding customers onto the beta and getting feedback on this half-hour walkthrough, Ryan and I were like, oh man, we missed the feature that customers are saying is mandatory in the product.
00:31:36.451 --> 00:31:38.450
They want document management integrated.
00:31:38.451 --> 00:31:44.089
When they're looking at their matter-based view, they want to see those documents that are linked and related to their case.
00:31:44.200 --> 00:31:47.410
They want to be able to attach billable time to those documents.
00:31:48.250 --> 00:31:53.890
We got to work on building a document management system and had it rolled out about a month into the beta.
00:31:53.891 --> 00:31:56.730
Again, we're able to get lots of live feedback on that.
00:31:56.730 --> 00:32:16.650
So that was an example of where we went in and said, rather than doing a really waterfall kind of process and fully specing out what the product's going to be out of the gate, we're going to build this kernel that we know is absolutely essential and take the approach of rapid iteration on that MVP to add this functionality.
00:32:16.650 --> 00:32:26.369
So there were I would say at least two or three major features that we developed over the course of the beta that we went in believing we didn't need to have as an integrated part of the product.
00:32:26.539 --> 00:32:27.210
Perfect.
00:32:28.290 --> 00:32:29.450
We fast-forward through these six months.
00:32:29.451 --> 00:32:32.490
You're getting feedback, some which is small, some of which is really big.
00:32:33.440 --> 00:32:38.809
When do you feel like you're really ready for launch and what does that look like?
00:32:38.810 --> 00:32:39.920
How do you set that up?
00:32:41.069 --> 00:33:03.799
Yeah, so one was when we felt like we were-- we'd move from that 80% to 90%, we actually circled a date for a major conference in legal on October 1, 2008 when we were--we had to commit to that conference and commit to the PR around launch about three months before the conference.
00:33:04.049 --> 00:33:32.640
So we were about halfway through our beta and we felt like we feel like we're tracking to a place where maybe we'll be ready by this conference and then circled the date, wrote the checks, committed to it, and got-- hired an actual PR firm, got on a retainer that felt extremely expensive to us at the time, which was$4,000 a month committing to a quarter of intense PR over Q4 of 2008, burned the boats and said we're launching on October 1st.
00:33:33.059 --> 00:33:38.960
Fast-forward to September and we're freaking out because we're not ready.
00:33:38.960 --> 00:33:40.519
We've got a lot left to build.
00:33:40.520 --> 00:33:54.039
We realized like a week before we were supposed to launch that we hadn't actually built any way to charge customers on their credit cards, all these things that when you really go through the pre-flight checklist, we realized we weren't quite ready.
00:00:00.000 --> 00:00:06.759
00:00:07.059 --> 00:00:21.120
00:00:21.120 --> 00:00:26.359
00:00:26.980 --> 00:00:28.879
00:00:29.210 --> 00:00:32.719
00:00:36.250 --> 00:00:38.399
00:00:38.401 --> 00:00:41.960
00:00:42.030 --> 00:00:44.920
00:00:44.920 --> 00:00:49.200
00:00:50.081 --> 00:00:52.799
00:00:53.329 --> 00:00:54.719
00:00:54.720 --> 00:00:58.439
00:00:58.869 --> 00:01:01.439
00:01:01.439 --> 00:01:02.439
00:01:03.090 --> 00:01:08.079
00:01:08.590 --> 00:01:11.640
00:01:11.909 --> 00:01:19.359
00:01:19.361 --> 00:01:22.519
00:01:23.349 --> 00:01:27.280
00:01:27.281 --> 00:01:31.400
00:01:32.060 --> 00:01:46.920
00:01:47.390 --> 00:01:56.640
00:01:56.801 --> 00:01:59.519
00:01:59.519 --> 00:02:00.640
00:02:01.209 --> 00:02:20.080
00:02:20.441 --> 00:02:28.199
00:02:28.430 --> 00:02:30.719
00:02:30.721 --> 00:02:36.680
00:02:37.210 --> 00:02:40.360
00:02:41.129 --> 00:02:50.400
00:02:51.121 --> 00:03:04.719
00:03:06.080 --> 00:03:19.360
00:03:19.759 --> 00:03:23.080
00:03:23.600 --> 00:03:23.919
00:03:23.919 --> 00:03:24.719
00:03:24.721 --> 00:03:26.800
00:03:26.990 --> 00:03:35.879
00:03:37.401 --> 00:03:41.039
00:03:41.040 --> 00:03:48.800
00:03:49.110 --> 00:03:59.080
00:03:59.841 --> 00:04:17.519
00:04:18.699 --> 00:04:28.600
00:04:29.521 --> 00:04:33.879
00:04:34.839 --> 00:04:44.360
00:04:44.778 --> 00:04:55.560
00:04:55.560 --> 00:05:02.838
00:05:02.839 --> 00:05:17.240
00:05:18.279 --> 00:05:23.240
00:05:23.521 --> 00:05:51.000
00:05:52.180 --> 00:06:18.959
00:06:19.161 --> 00:06:27.399
00:06:27.850 --> 00:06:38.600
00:06:38.600 --> 00:06:42.319
00:06:44.000 --> 00:06:56.720
00:06:57.088 --> 00:07:00.800
00:07:01.180 --> 00:07:03.920
00:07:04.641 --> 00:07:23.560
00:07:24.480 --> 00:07:25.360
00:07:25.920 --> 00:07:32.920
00:07:33.589 --> 00:07:43.279
00:07:45.069 --> 00:07:54.399
00:07:56.629 --> 00:08:10.279
00:08:10.281 --> 00:08:12.639
00:08:12.641 --> 00:08:23.720
00:08:24.050 --> 00:08:27.360
00:08:27.360 --> 00:08:32.519
00:08:33.120 --> 00:08:44.080
00:08:45.400 --> 00:08:49.600
00:08:49.600 --> 00:08:58.320
00:09:00.120 --> 00:09:08.840
00:09:08.909 --> 00:09:38.759
00:09:39.360 --> 00:09:52.360
00:09:53.120 --> 00:09:54.320
00:09:54.321 --> 00:10:00.678
00:10:01.190 --> 00:10:07.000
00:10:07.000 --> 00:10:14.240
00:10:14.240 --> 00:10:16.558
00:10:17.090 --> 00:10:33.360
00:10:33.669 --> 00:10:38.080
00:10:38.081 --> 00:10:39.200
00:10:39.870 --> 00:10:51.519
00:10:52.201 --> 00:10:55.879
00:10:56.149 --> 00:11:01.960
00:11:01.961 --> 00:11:06.159
00:11:05.669 --> 00:11:26.600
00:11:26.899 --> 00:11:41.799
00:11:42.360 --> 00:11:51.000
00:11:51.000 --> 00:11:58.960
00:12:00.441 --> 00:12:25.120
00:12:25.259 --> 00:12:37.678
00:12:38.000 --> 00:12:42.039
00:12:42.041 --> 00:12:45.440
00:12:46.559 --> 00:12:59.250
00:12:59.971 --> 00:13:21.730
00:13:21.990 --> 00:13:32.970
00:13:34.549 --> 00:13:35.808
00:13:35.809 --> 00:13:41.649
00:13:42.190 --> 00:14:23.450
00:14:23.710 --> 00:14:37.049
00:14:38.860 --> 00:15:11.080
00:15:11.610 --> 00:15:12.600
00:15:13.000 --> 00:15:14.440
00:15:14.441 --> 00:15:16.759
00:15:16.760 --> 00:15:22.840
00:15:23.629 --> 00:15:27.960
00:15:29.441 --> 00:15:39.000
00:15:39.240 --> 00:15:41.840
00:15:41.929 --> 00:15:45.080
00:15:45.360 --> 00:15:47.799
00:15:48.220 --> 00:15:49.200
00:15:49.201 --> 00:15:57.919
00:15:58.590 --> 00:15:59.080
00:15:59.081 --> 00:16:09.799
00:16:11.081 --> 00:16:31.889
00:16:32.350 --> 00:16:44.809
00:16:45.039 --> 00:16:46.169
00:16:46.331 --> 00:16:52.649
00:16:52.659 --> 00:16:56.370
00:16:56.559 --> 00:16:57.970
00:16:59.931 --> 00:17:14.569
00:17:16.171 --> 00:17:23.009
00:17:23.010 --> 00:17:30.049
00:17:30.891 --> 00:17:44.250
00:17:45.819 --> 00:18:02.000
00:18:02.721 --> 00:18:14.599
00:18:14.829 --> 00:18:22.118
00:18:22.380 --> 00:18:26.000
00:18:26.000 --> 00:18:29.759
00:18:29.760 --> 00:18:32.640
00:18:32.641 --> 00:18:47.000
00:18:47.119 --> 00:18:48.319
00:18:49.380 --> 00:18:58.279
00:18:58.681 --> 00:19:01.319
00:19:01.470 --> 00:19:04.079
00:19:04.080 --> 00:19:06.680
00:19:06.740 --> 00:19:08.440
00:19:08.441 --> 00:19:09.400
00:19:10.509 --> 00:19:13.960
00:19:13.961 --> 00:19:15.680
00:19:15.681 --> 00:19:19.920
00:19:21.269 --> 00:19:36.200
00:19:37.809 --> 00:19:47.079
00:19:48.840 --> 00:19:54.358
00:19:54.858 --> 00:20:11.960
00:20:12.161 --> 00:20:18.680
00:20:18.681 --> 00:20:27.680
00:20:28.201 --> 00:20:34.599
00:20:35.119 --> 00:20:37.480
00:20:39.601 --> 00:21:09.480
00:21:10.201 --> 00:21:21.118
00:21:20.921 --> 00:21:35.680
00:21:36.329 --> 00:21:55.200
00:21:56.000 --> 00:22:00.680
00:22:00.858 --> 00:22:11.799
00:22:12.180 --> 00:22:17.279
00:22:17.430 --> 00:22:23.519
00:22:23.809 --> 00:22:31.319
00:22:32.119 --> 00:22:41.559
00:22:42.441 --> 00:23:00.640
00:23:01.450 --> 00:23:09.200
00:23:09.921 --> 00:23:15.759
00:23:16.280 --> 00:23:19.680
00:23:20.130 --> 00:23:36.240
00:23:36.269 --> 00:23:44.839
00:23:44.840 --> 00:23:46.880
00:23:47.040 --> 00:23:58.519
00:23:59.730 --> 00:24:08.118
00:24:08.118 --> 00:24:22.599
00:24:23.608 --> 00:24:24.680
00:24:24.681 --> 00:24:26.039
00:24:26.359 --> 00:24:28.720
00:24:30.201 --> 00:24:37.039
00:24:37.040 --> 00:24:39.680
00:24:39.681 --> 00:24:49.519
00:24:49.279 --> 00:24:52.920
00:24:52.921 --> 00:24:59.200
00:24:59.201 --> 00:25:06.920
00:25:07.240 --> 00:25:12.759
00:25:12.760 --> 00:25:22.759
00:25:23.039 --> 00:25:32.519
00:25:32.779 --> 00:25:39.000
00:25:39.000 --> 00:25:56.519
00:25:56.519 --> 00:25:58.799
00:25:58.800 --> 00:26:14.039
00:26:15.441 --> 00:26:18.480
00:26:18.240 --> 00:26:24.440
00:26:25.921 --> 00:26:28.400
00:26:28.401 --> 00:26:29.839
00:26:29.840 --> 00:26:32.799
00:26:34.161 --> 00:26:47.160
00:26:47.460 --> 00:26:49.000
00:26:49.000 --> 00:26:58.640
00:26:58.641 --> 00:27:00.160
00:27:00.710 --> 00:27:02.640
00:27:02.800 --> 00:27:15.000
00:27:15.108 --> 00:27:32.079
00:27:32.840 --> 00:27:49.599
00:27:49.881 --> 00:27:58.358
00:27:58.961 --> 00:28:37.160
00:28:37.160 --> 00:28:45.839
00:28:47.560 --> 00:28:56.119
00:28:56.401 --> 00:28:58.160
00:28:58.161 --> 00:29:01.160
00:29:01.161 --> 00:29:06.359
00:29:08.769 --> 00:29:11.680
00:29:12.000 --> 00:29:23.200
00:29:23.609 --> 00:29:34.559
00:29:34.819 --> 00:29:39.839
00:29:41.089 --> 00:29:56.849
00:29:58.170 --> 00:29:59.250
00:29:59.250 --> 00:30:19.690
00:30:20.460 --> 00:30:21.369
00:30:23.010 --> 00:30:26.930
00:30:27.651 --> 00:30:30.529
00:30:31.059 --> 00:30:45.970
00:30:46.891 --> 00:30:47.730
00:30:47.950 --> 00:30:55.410
00:30:56.010 --> 00:31:01.490
00:31:02.180 --> 00:31:10.170
00:31:12.050 --> 00:31:15.730
00:31:15.730 --> 00:31:36.450
00:31:36.451 --> 00:31:38.450
00:31:38.451 --> 00:31:44.089
00:31:44.200 --> 00:31:47.410
00:31:48.250 --> 00:31:53.890
00:31:53.891 --> 00:31:56.730
00:31:56.730 --> 00:32:16.650
00:32:16.650 --> 00:32:26.369
00:32:26.539 --> 00:32:27.210
00:32:28.290 --> 00:32:29.450
00:32:29.451 --> 00:32:32.490
00:32:33.440 --> 00:32:38.809
00:32:38.810 --> 00:32:39.920
00:32:41.069 --> 00:33:03.799
00:33:04.049 --> 00:33:32.640
00:33:33.059 --> 00:33:38.960
00:33:38.960 --> 00:33:40.519
00:33:40.520 --> 00:33:54.039