Skip to main content

Sales Traction

Fred has a good post to open the discussion over at AVC today on sales traction vs product-market fit.

Go read that. Here's my two cents:

I'm generally optimistic about the possibilities of a product given the right team and plan. When I started Mission Research (GiftWorks) with my co-founders, I felt we should take our time, map things out, develop the framework, etc.

But my impatience exceed that feeling, and I pushed for an early release, which led to a total of 2 customers (more or less) in the first month. The product wasn't right. There were bugs. There were features the customer base thought should be standard that weren't in there. Some of our usability assumptions were wrong.

It was a slog for the first year.

But it was an invaluable year: by the next release, we had a much better product-market fit. We listened. We spent time on site with customers, documenting how crappy their experience with GiftWorks was. We refined it and made it a lot better. And then we did it again over the following two years, continually improving the product based on real usage of the product--not just our inflated opinions about it.

Three years after that we had 6,000 customers, a strong brand that led to consistent referrals, industry respect, and repeatable sales and marketing processes.

You have to pay attention to the details. You have to listen to your customer--not just at the moment of failure or complaint, but from the time they try your product through each and every click, every raise of the eyebrow, and every time they get that glassy-eyed look because you screwed something up in your assumptions and delivery.

The first year after release can be a real slog, especially if you can only attract a few customers. So build a decent base of beta customers, convert at least 30 of them, then stop trying to sign up new customers.

Yeah. Sounds wrong but you need to figure out how to serve those 30 really well before you try to scale and serve 3,000.

Hang in there.


Popular posts from this blog

Beta Signup

I've been working for quite a while on a new search concept, though the further in I get, the closer the rest of the world gets to what we're doing. So today I'm inviting you to sign up for the rather modest beta, which will be ready soon if we can nail down a few difficult  details. Jawaya is a way of navigating the web and getting better results. And that's as much as I can say right now, because we're not a funded startup, and things are moving really fast in this space--it's going to be very competitive. I predict there will be about 10 funded startups in the next 6 months doing something similar. One of them will be mine, and we aim to make it the best. We're raising a round of capital to fund the team, and are shooting for early sustainability. This is my fifth company; my fourth in the tech space, and my third software company. I think it will be the biggest and can possibly have a positive impact on the world by reducing the amount of time it takes

Where Innovation Happens

As I get closer to a go/no-go decision on a project, I've been thinking about the difference about my vision for the project and the supportive innovations to enable the core innovations The vision combines (in unequal parts) product, core innovation as I imagine it, the application of that core innovation, design, marketing,  developer ecosystem, and business development. The core innovation enables everything else, but it's the application of the innovation that makes it meaningful, useful, and in this case, fun. This week we're testing initial approaches to the implementation for our specific application, and that's where we'll develop the enabling innovations, which is basically where the rubber meets the road. The difference is that the enabling innovation happens at the source of real problems only encountered in the making of something, and in a project like this just getting the essence of it right isn't enough; it also has to be safe, the compone

Disqus Digests

This morning my phone dinged with a fresh notification--a new email! What oh what could it be?  I rush over to check while thinking "I need to unsubscribe to a lot of stuff so I get fewer non-urgent dinging notifications." Well shoot, that's disappointing. It's Disqus Digests, one of the biggest wastes of dopamine anticipation ever.  It simply sucks.  Disqus itself is great as a commenting system. I've been there since the beginning and have mostly enjoyed its evolution.  And then they did this interruptive, irrelevant email. Well why does it suck, you say.  Every one of these "Digests" sends a few comments from a blog conversation in which I've already participated. That means it's very, very likely that I've seen the comments before.  So I open the mail, see something I've already read, and curse Daniel and Company for enticing me into wasting my time, and cursing myself for falling for it.  So I unsub