# Product-led onboarding

Product-led onboarding is an approach in which the product itself, rather than a salesperson or onboarding specialist, takes a new user from sign-up to first value, through in-product setup, sensible defaults, guidance and prompts.

## How is product-led onboarding different from sales-led onboarding?

The difference is who does the work of getting a customer to value. In sales-led onboarding, people do it: a kickoff call, an implementation specialist, training sessions. In product-led onboarding, the product does it, and people step in only where it can't.

| | Sales-led onboarding | Product-led onboarding |
|---|---|---|
| Who drives setup | An onboarding or implementation team | The product, with help available |
| When it starts | After the contract and a scheduled kickoff | The moment the user signs up |
| How it scales | With headcount | With the product |
| What it costs per account | High, mostly people's time | Low once built |
| Where it fits | Complex setups, regulated buyers, large rollouts | Products where one person can reach value alone |

Most B2B companies run both. Product-led onboarding for the self-serve path and for every user who joins an existing account; sales-led onboarding for the large accounts that need it.

## What does product-led onboarding need to work?

Four things matter most. The first is the one teams most often skip.

1. **A first result that one person can reach.** If value needs three colleagues and an admin, the product has to fake the first part with sample data or templates until they arrive.
2. **Context about what the user is trying to do.** From sign-up answers, the source they came from or what they do in the first minutes.
3. **Instrumentation on every step,** so the team can see where users stall without asking them.
4. **A path to a person** that doesn't make the user start over, triggered by a signal such as a stalled setup or a large company domain.

Picture a design collaboration product. A product manager signs up, picks "Review a design," and lands in a sample file with comments already in it. They upload their own file, leave a comment and invite a designer to reply. Value arrives in the first session, and nobody from the vendor was involved.

## Where does product-led onboarding stop?

Product-led onboarding stops where setup needs a decision the user can't make alone or a step the product doesn't guide: configuring permissions across teams, mapping data from another system, choosing settings with financial or security consequences. At that point most teams fall back to a call, and the onboarding becomes sales-led again.

An in-product agent can keep more of those steps inside the product, by explaining each choice in context and doing the configuration once the user decides. Foldspace's Product Agent does both in the conversation: it [answers questions, navigates and acts](https://docs.foldspace.ai/start/introduction/), explaining a choice when the user asks and applying the configuration through the product's backend APIs once they decide, inside that user's own access, so onboarding doesn't have to turn sales-led.

## Learn more

- [Product Agent](/platform/product-agent)