Product-Led Growth

Business software was sold in a fixed order for a long time. The company signs a contract, accounts open, and then employees start using it. In that order, building a good product and selling it are separate jobs. How welcoming the first screen felt was a question that came up only after the contract was signed. Nobody had much reason to care whether a first-time user could find their way, because the list of accounts was already settled.

At early Pagedeck the order broke down. A five-person team asked about pricing and Sofia spent a thirty-minute call and an hour-long demo on it. The team was willing to pay $40 a month, so the labor cost of closing them ran past what they would pay in a year. Sofia said deals like that lost money the more of them she won, and Grace admitted there was no way to serve 300 small teams like this.

Product-led growth (PLG) exists to flip that arithmetic. Explaining, persuading and collecting payment become jobs the product does instead of a person. The order of use comes before the order of sale.

The backbone is inverting use and purchase. Instead of signing first and using later, people use the product first and pay later, and the product rather than a person fills the gap.

The loop has five steps.

1. Lower the door. An email address opens an account — no card details, no sales call. The fewer things standing in front of the product, the more people reach it.
2. Show the value quickly. The gap between signing up and feeling the value is called time to value, and in this model it is measured in minutes. At Pagedeck that means five minutes to create a document and edit it alongside a colleague.
3. Users bring users. Editing a document together requires inviting someone, so each user recruits the next. That circuit, where existing users pull in new ones, is a viral loop.
4. Payment appears where the free scope ends. The point that blocks the way until you pay is a paywall, and where it sits accounts for most of the design work in this model.
5. Sales arrives last. Someone picks the heaviest accounts among teams already using the product and reaches out. A prospect qualified by product usage rather than a form fill is a product-qualified lead (PQL).

The model stands under one condition: the price has to be something one person can decide alone. The money spent to land one customer is customer acquisition cost (CAC), and on a $25-a-month product a single sales rep pushes that cost past what the customer pays in a year. Companies choose this model because letting the product do the work is cheaper, not because the product is somehow better.

It fits products that are useful to one person and safe to leave open for free. Collaboration documents, design tools and developer tools are the usual examples. In all three, a practitioner has something to do with it today, and nothing about the free tier puts the company at much risk.

The places it fits poorly are just as clear. Enterprise contracts, the ones with companies of several thousand employees, run through security reviews and approvals from several departments, so signing up and paying alone is never on the table. A product that becomes useful only after existing data is migrated in has nothing to show in the first five minutes either.

In practice most companies run both. Small teams are served by the product and large annual contracts are served by people. The line between the two is drawn by price and by how many people have to approve the purchase. Pagedeck works that way.

You can spot a company that has chosen this model from the outside. The price list is published on the web, and the first screen offers a sign-up button rather than a contact form. It often pairs with freemium, where the basics stay free and only the advanced features are charged for. The numbers on the wall change too. Weekly meetings track the share of sign-ups that reached first value and the share that moved from free to paid, not the count of calls and quotes.

"The price list stays on the web. Switch it to a contact form and the self-serve path breaks."

Putting a sales conversation up front breaks the premise the model rests on.

"This feature only makes sense once sales explains it, which puts it at odds with how we grow."

A design that can't be understood inside the product is something to fix.

"Let's raise the free limit from 50 documents to 200. Right now people hit the wall before they see the point."

The paywall stands too early, blocking people before a reason to pay has accumulated.

At Pagedeck this line turns up wherever a decision splits. Of the teams Ravi brought in, the ones that converted were those where three or more people edited the same document within three weeks — 9 percent of the total. The rest tried it alone a few times and quietly disappeared.

So the work Mia picked was not a new feature but moving the invite step earlier. A teammate-invite field went on the screen right after sign-up, and creating a document surfaced the share button first. In the same quarter Sofia stopped new outreach and contacted only existing accounts that had passed ten members. The two did different things on the same premise: a record of product usage is where selling starts.

The most common reading is that the model removes sales. The name sounds like a declaration that people are being taken out of the loop. What actually changes is where sales stands. Instead of making the first introduction, they pick the heaviest accounts already using the product and discuss upper plans and annual contracts. Leave that seat empty and you keep only the small teams that paid on their own, while an account that grew to fifty members stays on a monthly plan nobody revisits.

The other reading is that opening a free tier makes growth happen by itself, since it sounds interchangeable with freemium. But the free plan is a door, and the design that walks someone through it into the value has to be built separately. Freemium describes the pricing; this model describes what has to happen inside the product. Skip that and sign-ups climb while payments don't.