> ## Documentation Index
> Fetch the complete documentation index at: https://formbricks.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Product-Market Fit Survey

> Measure product-market fit with the Superhuman method.

The Superhuman product-market-fit survey asks how disappointed someone would be if they could no longer use your product. Above 40% answering "very disappointed" is the usual signal of fit.

## Purpose

The number is only meaningful if you ask people who have actually used the product. Asking everyone, including people who signed up yesterday, produces a number that measures your signup flow rather than your product.

## 1. Start from the template

Open **Surveys**, click **New Survey** and choose **Choose a template**. Search for **Product Market Fit**, then click the card to create the survey.

![The Product Market Fit template in the template picker](https://mintcdn.com/formbricks/5gmPPlpgcBxnNfUX/images/surveys/best-practices/pmf-survey/template.webp?fit=max\&auto=format\&n=5gmPPlpgcBxnNfUX\&q=85\&s=039f2eb50011b84d16f9a1da29aef7af)

The template is the Superhuman question set. Do not reword the first question — the 40% benchmark only means anything against the standard wording.

## 2. Trigger it at the right moment

Ask people who have used the product enough to have an opinion. That is easiest as a **code action** fired from your own app once a user reaches, say, their third session — a page view cannot tell you that.

Open the **Settings** tab, find **Survey Trigger** and add the action. See [Code Actions](https://formbricks.com/docs/surveys/website-app-surveys/actions.md#setting-up-code-actions) for firing it with `formbricks.track()`.

![The Survey Trigger section with the action attached](https://mintcdn.com/formbricks/5gmPPlpgcBxnNfUX/images/surveys/best-practices/pmf-survey/trigger.webp?fit=max\&auto=format\&n=5gmPPlpgcBxnNfUX\&q=85\&s=f1c9a6033ae8594a91e479aece606274)

> [!TIP]
>
> A code action is two halves that have to agree: the action you create here carries a **key**, and your
> app fires that same key with `formbricks.track("<key>")`. Nothing happens until both exist — the survey
> stays silent if the key never fires, and the call is a no-op if no action carries it. The no-code
> alternatives (Click, Page View, Exit Intent, 50% Scroll, Time on Page) are walked through on the
> [Feedback Box](https://formbricks.com/docs/surveys/best-practices/feedback-box.md) page; the full reference is the
> [Actions manual](https://formbricks.com/docs/surveys/website-app-surveys/actions.md).

## 3. Decide how often it may appear

Still on **Settings**, open **Display & Recontact**. Choose **Show only once**. Asking the same people to take the survey repeatedly is how you get a number that drifts for reasons unrelated to your product.

> [!NOTE]
>
> Recontact Options and the workspace-wide [Cooldown Period](https://formbricks.com/docs/surveys/website-app-surveys/cooldown-period.md)
> are two separate gates and a survey has to pass both — Recontact Options first, then the cooldown. If
> your workspace shows at most one survey a week, this survey inherits that unless you set **Ignore
> Cooldown Period**.

## 4. Activate

**Activate** starts it. The widget picks up the change within a minute.

> [!NOTE]
>
> This is an app survey, so it needs the Formbricks widget running in your product. If you have not
> installed it yet, follow [the quickstart](https://formbricks.com/docs/surveys/website-app-surveys/quickstart.md) first.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.