Skip to content
Founder Tools

Founder storiesCustomer validation

How Joel Gascoigne found Buffer’s first paying customer

Before Buffer had a working product, Joel Gascoigne put a price on a page. The first subscription answered a question those clicks left open.

What each Buffer milestone measured
Two-page test
Readers left an email address
Pricing test
Some visitors selected a paid plan
Four days after launch
A customer had paid for the working product

Gascoigne described the sequence in his February 2011 account. The first two tests collected interest.[1]

Lessons for founders

  • Gascoigne began with a specific nuisance. He wanted to queue links for Twitter without choosing a posting time for every link.
  • A click on a paid plan helped him decide what to build. A subscription after launch gave him the first evidence that someone would pay to use it.

A product hiding inside one feature

Joel Gascoigne would read several pieces of startup news in the morning and want to share them all. Publishing five links together crowded his followers’ feeds. Scheduling them one at a time meant choosing five posting times. What he wanted was a queue. He could add each link as he read it and let it go out later.

Gascoigne had suggested the feature to other apps. Eventually he started coding it himself. In his account of Buffer’s launch, he describes stopping when he realized how little he knew about whether anyone else wanted it. A few pages would let him ask before he spent his evenings writing the rest.

Sources12

What a click on a price can tell you

Gascoigne shared a two-page site on Twitter and collected email addresses from interested readers. Then he put a choice of plans before the email form. Some visitors selected a paid option and went on to leave their addresses. They had seen a price and still wanted to hear from him.

There was no subscription to use yet. Someone might click a plan to inspect its features, leave an address for updates and never buy. For Gascoigne, the result justified building a version that could settle the question. It gave him a short list of people he could ask about their current routine as well.

Sources1

The first receipt changed his calendar

Gascoigne spent seven weeks working evenings and weekends toward a public November 30 launch. A guided signup flow missed the cut. Within four days of putting the working product online, he had a paying customer. His next decision was to spend more time on marketing and talking to customers.

That change in priorities is easy to miss. One person had crossed the distance from hearing about a queue to paying for it. Adding more features would teach him little about where to find a second person with the same problem. A conversation with the first buyer could tell him what they had been doing the week before.

Sources1

A version you can run with one customer

Say you want to sell invoice reminders to freelance designers. Ask one designer to walk you through the last invoice that went overdue. If they can show you the email they wrote, offer to draft and schedule their next reminder for a stated fee. Explain exactly what you will deliver and which parts you will handle by hand.

Keep three numbers separately. How many people shared a real overdue invoice? How many accepted the offer? How many paid and brought you another one? A long list of email addresses and a single repeat buyer lead to different next steps. The repeat buyer can show you which part of the job is worth automating.

Tools for this article

  • Buffer

    Try the publishing queue at the center of Gascoigne’s first paid product.

Sources

2 references