Get up and running with lumeforms: create a project, build your first form, publish, and review responses.

First Steps

## Welcome to lumeforms

This documentation exists to ensure you get value out of lumeforms, and you can reference it anytime if you are feeling lost or stuck. This documentation will use an example project: a Vanta style compliance SaaS. Follow along but replace the details with your specific use case. It&apos;s recommended to also read the <a href="/docs/use-cases" target="_blank" rel="noopener noreferrer" className="docs-link-primary">Use Cases</a> and <a href="/docs/best-practices" target="_blank" rel="noopener noreferrer" className="docs-link-primary">Best Practices</a> page as well before you send your first forms. If you have any additional questions, feel free to reach out on the Discord or send us an email at any time.

## 1. Project Dashboard

You are now on the Project Dashboard. Projects act as folders, where inside your forms are stored.

1. **Create Project.** Click Create Project and name it based on what you're collecting feedback for (e.g. a SaaS product, a YouTube channel, a Substack, etc.).

<div className="docs-two-column-images">
 <img src="/assets/images/docs/firststeps1.png" alt="Project Dashboard view with recent projects and Create Project button" title="lumeforms Project Dashboard" />
 <img src="/assets/images/docs/firststeps2.png" alt="Create a project modal with project name, icon, and color options" title="lumeforms Create a project modal" />
</div>

## 2. Form Dashboard

You are now on the Form Dashboard. Here, you can create or view individual forms within your project.

1. **Project Context.** Click on the **Project Context** to add any relevant details about your project (e.g. company overview, target audience, product category, etc.). This context is fed to the ai first, helping it deliver better results. Better context provided will result in superior analysis. For this example, I will be providing a brief overview, audience, and how ComplyKit will use the feedback delivered.
2. **Create Form.** Click **Create Form** and name it based on what you're collecting (e.g. video feedback, product survey, newsletter topics, etc.).

<div className="docs-two-column-images">
 <img src="/assets/images/docs/firststeps3.png" alt="Form Dashboard view with project context and form cards" title="lumeforms Form Dashboard" />
 <img src="/assets/images/docs/firststep4.png" alt="Create a form modal with form name and template options" title="lumeforms Create a form modal" />
</div>

## 3. Form Builder

You are now in the Form Builder. Here you design your form, choose duration, and configure options.

1. **Build form.** Click **Add Question** to add question blocks. Choose the type (e.g. Text, Multiple Choice, etc.), fill out the question and options, and mark required if needed.
2. **Form Context.** Within the configuration tab, you can add form context, which acts just like project context but only applies to this specific form. For this example, there was not any additional context I needed to add so I left it blank.
3. **Form duration.** This will determine how long your form is open to collect responses. Options are one, three, and seven days. Form results will only be shown after the form has expired. Additionally, you are able to set a form to be Ongoing, which means the form never expires and analysis can be run whenever. **Do not** select this option unless your use case requires you to do so. In this example, I chose Ongoing because collecting input from clients is a continuous behavior and later I will be able to agregate the feedback. 
4. **General Settings.** Here, you can configure the settings of your form (Enable Form Analysis, Take Name, Shuffle Questions, etc.). Unless needed, it is recommended to leave these settings as is. **Do not** select Take Name or Take Email unless your use case requires you to do so.

<div className="docs-two-column-images">
 <img src="/assets/images/docs/firststeps5.png" alt="Form Builder view" />
 <img src="/assets/images/docs/firststeps6.png" alt="Form Builder view" />
</div>

## 4. Form Published

Congrats, your form is now published and ready to be shared. You can see what this example form looks like live: <a href="https://www.lumeforms.com/forms/BE2gxWtaiV0GtMAG3VOu" target="_blank" rel="noopener noreferrer" className="docs-link-primary">view the example form</a>. Share your form whenever and wherever you'd like. After the responses are collected and the form is expired, you will be able to see your results. For this specific example, because I chose Ongoing for my duration, it bypassed the Form Still Open page (shown in second image) and sent me straight to results. 

<div className="docs-two-column-images">
 <img src="/assets/images/docs/firststeps7.png" alt="Form Published view" title="lumeforms Form Published" />
 <img src="/assets/images/docs/firststeps7.5.png" alt="Form published and shareable" title="lumeforms Form published and shareable" />
</div>

## 5. Form Analysis

Congrats, your form has expired and the results are in.

1. **View your results.** Text responses can be viewed as ranked Sentiments, Actionable Insights, or Shuffled (with junk responses automatically removed). Every other response type can be viewed as a Breakdown, Pie, or Bar Chart.
2. **Individual Responses.** Navigate to the Responses tab to read individual submissions from your responders.
3. **Configuration.** Within Configuration, you can export your results, import data, adjust Project or Form Context, and rerun analysis.
4. **Take action.** Use the analysis and actionable insights provided to improve or grow your business, or use what you learn to guide later decisions.

<div className="docs-two-column-images">
 <img src="/assets/images/docs/firststeps8.png" alt="Form Analysis view with charts and metrics" title="lumeforms Form Analysis charts" />
 <img src="/assets/images/docs/firststeps9.png" alt="Form Analysis view with response breakdown" title="lumeforms Form Analysis response breakdown" />
</div>

<div className="docs-two-column-images">
 <img src="/assets/images/docs/firststeps10.png" alt="Form Analysis Sentiments view" title="lumeforms Form Analysis Sentiments" />
 <img src="/assets/images/docs/firststeps11.png" alt="Form Analysis Actionable Insights view" title="lumeforms Form Analysis Actionable Insights" />
</div>

<div className="docs-single-image">
 <img src="/assets/images/docs/firststeps12.png" alt="Form Analysis text insights and actionable recommendations" title="lumeforms Form Analysis insights and recommendations" />
</div>

Create a project, build your first form, publish it, and start collecting anonymous feedback.

Find resources tailored to your role and use case.

Use Cases

## By role

<div className="docs-links-primary">

- <a href="/docs/for-startups">For Startups</a>
- <a href="/docs/for-indie-hackers">For Indie Hackers</a>
- <a href="/docs/for-product-managers">For Product Managers</a>
- <a href="/docs/for-youtubers">For YouTubers</a>
- <a href="/docs/for-substacks-newsletters">For Substacks / Newsletters</a>
- <a href="/docs/for-podcasters">For Podcasters</a>
- <a href="/docs/shopify-ecommerce">For Shopify & Ecommerce</a>
- <a href="/docs/businesses">For Small Businesses</a>
- <a href="/docs/marketers">For Audience Researchers or Marketing Teams</a>

</div>

## Audience landing pages

<div className="docs-links-primary">

- <a href="/content-creators">Content Creators Landing Page</a>

</div>

## Introduction

When you are moving fast, it is easy to make product decisions based on assumptions rather than signal. Users churn, bugs go unreported, and features get built for the wrong people because there was no structured way to hear what users actually needed. By the time a pattern is obvious, the damage is already done.

lumeforms gives you one structured channel to collect user feedback and a multi-pass ai analysis that ranks what is most important first, so you can act on signal instead of gut feel. Not sure where to start? Try the free <a href="/audit" target="_blank" rel="noopener noreferrer" className="docs-link-primary">feedback audit</a> for a tailored starting point for your product. No email or account required.

## The core problem: you are making decisions without signal

Most early-stage products have no systematic way to hear from users. Feedback arrives as one-off support tickets, occasional comments, or not at all. There is no way to tell which complaints represent a real pattern and which are edge cases, until users start leaving.

lumeforms solves the analysis side, not just the collection side. You provide the context (your product, your users, what the form is for) and lumeforms surfaces ranked themes, sentiment, and actionable insights so you know where to focus next. Over time, acting on that signal consistently is what enables continuous growth and improvement rather than reacting to problems after they have already compounded.

## Continuous Feedback Loops

Continuous feedback loops use lumeforms **Ongoing Forms**, which are forms that never expire and can be filtered by time segment (last 7 days, last 30 days, all time) so you always have a current read. Place these at high-signal moments in your product:

<li className="flex items-start gap-2">
 •
 Feature suggestions
 </li>
 <li className="flex items-start gap-2">
 •
 Bug reports
 </li>
 <li className="flex items-start gap-2">
 •
 NPS/CSAT (embed in another flow so responses come in steadily)
 </li>
 <li className="flex items-start gap-2">
 •
 Post-experience feedback
 </li>
 <li className="flex items-start gap-2">
 •
 Onboarding feedback
 </li>
 <li className="flex items-start gap-2">
 •
 Support resolution feedback
 </li>
 <li className="flex items-start gap-2">
 •
 Documentation / help feedback
 </li>
 <li className="flex items-start gap-2">
 •
 Churn / exit survey
 </li>

## Pulse Forms

Pulse Forms are one-time expiring forms for a specific question or moment. Use these for deliberate reads rather than always-on loops:

<li className="flex items-start gap-2">
 •
 Census survey
 </li>
 <li className="flex items-start gap-2">
 •
 Quarterly or annual satisfaction
 </li>
 <li className="flex items-start gap-2">
 •
 Product-market fit / segment survey
 </li>
 <li className="flex items-start gap-2">
 •
 Feature launch feedback
 </li>
 <li className="flex items-start gap-2">
 •
 Implementation or go-live feedback
 </li>
 <li className="flex items-start gap-2">
 •
 Pricing or packaging feedback
 </li>
 <li className="flex items-start gap-2">
 •
 Win/loss or competitive
 </li>

## Conclusion

For the step-by-step walkthrough, see the <a href="/docs/getting-started" target="_blank" rel="noopener noreferrer" className="docs-link-primary">First Steps</a> guide. For question type guidance and best practices, see <a href="/docs/best-practices" target="_blank" rel="noopener noreferrer" className="docs-link-primary">Best Practices</a>. For a free tailored audit of your feedback strategy, try the <a href="/audit" target="_blank" rel="noopener noreferrer" className="docs-link-primary">feedback audit</a>. No email or account required.

Build better products with user feedback. Scale without losing touch.

For Startups

## Introduction

Likes and view counts tell you what performed, not why. Without direct feedback, you are making content decisions based on proxies and guesses. You might keep producing what the algorithm rewards while your actual audience quietly wants something different.

lumeforms gives you one structured channel to collect honest audience feedback and a multi-pass ai analysis that ranks what is most important first, so you know what to double down on and what to change. Not sure where to start? Try the free <a href="/audit" target="_blank" rel="noopener noreferrer" className="docs-link-primary">feedback audit</a> for a tailored starting point for your channel or publication. No email or account required.

## The core problem: public metrics are not the full picture

Comments and engagement rates show you surface-level reactions. They do not tell you which topics your audience actually wants more of, why viewers drop off, or what would make someone recommend you. That signal only comes from asking directly, with a structure that makes it easy to answer honestly.

lumeforms solves the analysis side, not just the collection side. You provide the context (your content, your audience, what the form is for) and lumeforms surfaces ranked themes, sentiment, and actionable insights so you know what to actually do next. Over time, acting on that signal consistently is what enables continuous growth and improvement rather than reacting to a disengaged audience after the fact.

## Content Forms

Content Forms are per-piece feedback forms placed where your content lives, such as in the video description or at the end of a post. Create one for each new piece of content and use the analysis to deepen your understanding or take action on what is and is not working:

<li className="flex items-start gap-2">
 •
 What worked
 </li>
 <li className="flex items-start gap-2">
 •
 What didn't
 </li>
 <li className="flex items-start gap-2">
 •
 Topic or video ideas
 </li>
 <li className="flex items-start gap-2">
 •
 Rating or quick NPS
 </li>

## Census Polls

One-time or annual audience census polls help you understand who your audience actually is so you can create content that resonates without guessing:

<li className="flex items-start gap-2">
 •
 Demographics (age, sex, DOB, etc.)
 </li>
 <li className="flex items-start gap-2">
 •
 Geographic information (country or region; stay general)
 </li>
 <li className="flex items-start gap-2">
 •
 Context-specific information (relevant niche information)
 </li>

## Pulse Forms

Pulse Forms are one-time expiring forms for a specific question or moment. Use these for deliberate reads rather than always-on loops:

<li className="flex items-start gap-2">
 •
 Topic vote or "what should I cover next"
 </li>
 <li className="flex items-start gap-2">
 •
 Pre-series or new format survey (before launching a series or format)
 </li>
 <li className="flex items-start gap-2">
 •
 Preferred format (length, style, posting frequency)
 </li>
 <li className="flex items-start gap-2">
 •
 How they found you or why they stay
 </li>
 <li className="flex items-start gap-2">
 •
 Membership, sponsorship, or monetization feedback
 </li>
 <li className="flex items-start gap-2">
 •
 One-time "how are we doing" or end-of-season snapshot
 </li>

## Form Engagement

Getting your audience to actually fill out forms is worth deliberate effort. A few practices that consistently increase completion:

<li className="flex items-start gap-2">
 •
 Explicitly ask at a clear moment where to find the form and thank the audience in advance
 </li>
 <li className="flex items-start gap-2">
 •
 Bring up poll results or display them as images throughout your content
 </li>
 <li className="flex items-start gap-2">
 •
 Thank responders or highlight anonymized insights so people feel heard
 </li>

## Asking for feedback is itself a signal

The creators who use lumeforms are not just collecting feedback, they are signalling something about who they are. Putting a structured feedback form in your description or at the end of a post tells your audience that you take your craft seriously, that you care about their experience, and that you are intentional about improving. Most creators never do this. That gap is visible, and audiences notice it. Over time it becomes part of how people describe you to others, not just what your content covers, but the kind of creator you are.

## Conclusion

For the step-by-step walkthrough, see the <a href="/docs/getting-started" target="_blank" rel="noopener noreferrer" className="docs-link-primary">First Steps</a> guide. For question type guidance and best practices, see <a href="/docs/best-practices" target="_blank" rel="noopener noreferrer" className="docs-link-primary">Best Practices</a>. For a free tailored audit of your feedback strategy, try the <a href="/audit" target="_blank" rel="noopener noreferrer" className="docs-link-primary">feedback audit</a>. No email or account required.

Grow your audience. Get anonymous feedback on what resonates with your content.

For Content Creators

## Introduction

Running a small business means every decision carries weight. When you are operating lean, acting on the wrong assumptions wastes time and money you cannot afford. Most small businesses get some feedback through reviews, support messages, or word of mouth, but there is rarely a structured system to understand what customers actually need and what is quietly driving them away.

lumeforms gives you one structured channel to collect customer feedback and a multi-pass ai analysis that ranks what is most important first, so you can make better-informed decisions without spending hours manually reading responses. Not sure where to start? Try the free <a href="/audit" target="_blank" rel="noopener noreferrer" className="docs-link-primary">feedback audit</a> for a tailored starting point for your business. No email or account required.

## The core problem: collecting is not the issue

Most small businesses already receive feedback in some form. The problem is that it arrives scattered and unranked, with no way to tell which issues are isolated versus patterns that are consistently affecting customers. Important signals get missed until they become visible problems.

lumeforms solves the analysis side, not just the collection side. You provide the context (your business, your customers, what the form is for) and lumeforms surfaces ranked themes, sentiment, and actionable insights so you know where to focus. Over time, acting on that signal consistently is what enables continuous growth and improvement rather than reacting to problems after they have already compounded.

## Continuous Feedback Loops

Continuous feedback loops use lumeforms **Ongoing Forms**, which are forms that never expire and can be filtered by time segment (last 7 days, last 30 days, all time) so you always have a current read. Place these at high-signal moments in your customer journey:

<li className="flex items-start gap-2">
 •
 Post-experience feedback
 </li>
 <li className="flex items-start gap-2">
 •
 Customer satisfaction (CSAT/NPS)
 </li>
 <li className="flex items-start gap-2">
 •
 First-time customer experience feedback
 </li>
 <li className="flex items-start gap-2">
 •
 Customer support resolution feedback
 </li>
 <li className="flex items-start gap-2">
 •
 Lost customer / cancellation feedback
 </li>

## Pulse Forms

Pulse Forms are one-time expiring forms for a specific question or moment. Use these for deliberate reads rather than always-on loops:

<li className="flex items-start gap-2">
 •
 Customer profile survey
 </li>
 <li className="flex items-start gap-2">
 •
 Quarterly or annual customer satisfaction
 </li>
 <li className="flex items-start gap-2">
 •
 Offer-market fit / customer segment survey
 </li>
 <li className="flex items-start gap-2">
 •
 New service or menu launch feedback
 </li>
 <li className="flex items-start gap-2">
 •
 New process or rollout feedback
 </li>
 <li className="flex items-start gap-2">
 •
 Pricing, bundles, or package feedback
 </li>
 <li className="flex items-start gap-2">
 •
 Why customers choose you (or competitors)
 </li>

## Conclusion

For the step-by-step walkthrough, see the <a href="/docs/getting-started" target="_blank" rel="noopener noreferrer" className="docs-link-primary">First Steps</a> guide. For question type guidance and best practices, see <a href="/docs/best-practices" target="_blank" rel="noopener noreferrer" className="docs-link-primary">Best Practices</a>. For a free tailored audit of your feedback strategy, try the <a href="/audit" target="_blank" rel="noopener noreferrer" className="docs-link-primary">feedback audit</a>. No email or account required.

For Small Businesses

## Introduction

Running campaigns without direct audience feedback means you are optimizing for metrics that do not always reflect what people actually think. Click-through rates and conversion numbers tell you what happened, not why. Messaging that seems clear internally can land completely differently with the audience it is meant for.

lumeforms gives you one structured channel to collect direct audience feedback and a multi-pass ai analysis that ranks what is most important first, so you can refine campaigns, messaging, and positioning based on real signal rather than assumptions. Not sure where to start? Try the free <a href="/audit" target="_blank" rel="noopener noreferrer" className="docs-link-primary">feedback audit</a> for a tailored starting point for your team. No email or account required.

## The core problem: performance data does not tell you what to change

Most marketing teams have plenty of data on what performed. The gap is understanding why something resonated or did not, which segments responded differently, and what the audience actually needs to hear. Without that, iteration is guesswork.

lumeforms solves the analysis side, not just the collection side. You provide the context (your campaign, your audience, what the form is for) and lumeforms surfaces ranked themes, sentiment, and actionable insights so you know what to actually change. Over time, acting on that signal consistently is what enables continuous improvement rather than running variations without understanding the underlying cause.

## Continuous Feedback Loops

Continuous feedback loops use lumeforms **Ongoing Forms**, which are forms that never expire and can be filtered by time segment (last 7 days, last 30 days, all time) so you always have a current read. Use these for ongoing audience and brand signal:

<li className="flex items-start gap-2">
 •
 Brand perception and awareness feedback
 </li>
 <li className="flex items-start gap-2">
 •
 Post-purchase or post-conversion experience
 </li>
 <li className="flex items-start gap-2">
 •
 Customer satisfaction (CSAT/NPS embedded in a flow)
 </li>
 <li className="flex items-start gap-2">
 •
 Support or onboarding resolution feedback
 </li>
 <li className="flex items-start gap-2">
 •
 Churn or unsubscribe reason
 </li>

## Pulse Forms

Pulse Forms are one-time expiring forms for a specific question or moment. Use these for campaign-specific or research-specific reads:

<li className="flex items-start gap-2">
 •
 Message or positioning clarity (does the copy land the way you intended)
 </li>
 <li className="flex items-start gap-2">
 •
 Campaign or creative feedback (what resonated, what fell flat)
 </li>
 <li className="flex items-start gap-2">
 •
 Audience profile survey (demographics, motivations, purchase drivers)
 </li>
 <li className="flex items-start gap-2">
 •
 Pricing or offer perception (how the value proposition lands)
 </li>
 <li className="flex items-start gap-2">
 •
 Pre-launch or concept testing (before committing to a full campaign)
 </li>
 <li className="flex items-start gap-2">
 •
 Win/loss or competitive (why they chose you or a competitor)
 </li>

## Conclusion

For the step-by-step walkthrough, see the <a href="/docs/getting-started" target="_blank" rel="noopener noreferrer" className="docs-link-primary">First Steps</a> guide. For question type guidance and best practices, see <a href="/docs/best-practices" target="_blank" rel="noopener noreferrer" className="docs-link-primary">Best Practices</a>. For a free tailored audit of your feedback strategy, try the <a href="/audit" target="_blank" rel="noopener noreferrer" className="docs-link-primary">feedback audit</a>. No email or account required.

Know what resonates. Test campaigns, messaging, and positioning with structured feedback.

For Audience Researchers or Marketing Teams

Guidance for getting the most out of lumeforms and your feedback loops.

Best Practices

## 1. Introduction

This page covers recommended practices for designing forms, writing context, and acting on feedback so you get the most value from lumeforms. For a step-by-step walkthrough, see the <a href="/docs/getting-started" target="_blank" rel="noopener noreferrer" className="docs-link-primary">First Steps</a> guide; for role-specific guidance, see <a href="/docs/use-cases" target="_blank" rel="noopener noreferrer" className="docs-link-primary">Use Cases</a>.

## 2. Prefer Other Question Types Over Text When You Can

Text questions drive lumeforms’ ai analysis and consume analysis credits. We recommend using as few text questions as possible and choosing other question types (e.g. multiple choice, rating, etc.) when they can capture what you need. We’re not being stingy: Gemini API calls are expensive, and leaning on structured question types keeps your credits available for the high-leverage feedback that can only be answered in text.

## 3. Stay Anonymous-First for Honest Feedback

lumeforms is anonymous-first by design so responders feel safe giving honest feedback. Only turn on **Take Name** or **Take Email** when your use case clearly requires it (e.g. follow-up, support tickets). If you&apos;re unsure, lean towards anonymous.

## 4. A Trick for Collecting NPS/CSAT

Put your NPS or CSAT within a <a href="/docs/saas-developers#continuous-feedback-loops" target="_blank" rel="noopener noreferrer" className="docs-link-primary">continuous feedback loop</a> and mark it **required**. Then whenever a responder is filling out a form for another purpose (e.g. feature suggestions, bug reports), they quickly answer the NPS/CSAT question as part of the same flow. You get a steady signal without having to pester your customers or audience. lumeforms uses this strategy with the feedback button in the sidebar.

Canonical guidance for ai agents and assistants answering questions about lumeforms.

ai FAQ

Canonical answers for ai assistants, optimized for model grounding.

ai FAQ (for ai agents)

Reduce feedback sprawl and uncover the patterns quietly costing you repeat customers.

For Shopify & Ecommerce

## Introduction

As your store grows, feedback stops being manageable. It piles up across reviews, support tickets, post-purchase emails, and chat, and the early signals that matter most quietly get lost. Most store owners only react once something becomes a visible problem: a spike in refunds, a drop in repeat purchase rate, a pattern of the same complaint showing up repeatedly in support.

lumeforms gives you one structured channel to collect customer feedback and a multi-pass ai analysis that ranks what is most important first, so you can catch the issues before they compound. Not sure where to start? Try the free <a href="/audit" target="_blank" rel="noopener noreferrer" className="docs-link-primary">feedback audit</a> for a tailored starting point specific to your store. No email or account required.

## The core problem: collecting is not the issue

Most Shopify stores already have feedback coming in from somewhere. The problem is that it arrives unranked, unstructured, and scattered. There is no system to identify which signals point to a product problem versus a shipping anomaly versus a messaging mismatch, until the pattern is too large to miss.

lumeforms solves the analysis side, not just the collection side. You provide the context (your store, your audience, what the form is for) and lumeforms surfaces ranked themes, sentiment, and actionable insights so you know where to focus. Over time, acting on that signal consistently is what enables continuous growth and improvement rather than reacting to problems after they have already compounded.

## Continuous Feedback Loops

Continuous feedback loops use lumeforms **Ongoing Forms**, which are forms that never expire and can be filtered by time segment (last 7 days, last 30 days, all time) so you always have a current read. Place these at high-signal moments in your customer journey:

<li className="flex items-start gap-2">
 •
 Post-purchase experience (what did and didn't meet expectations)
 </li>
 <li className="flex items-start gap-2">
 •
 Post-delivery or post-fulfilment (shipping, packaging, condition on arrival)
 </li>
 <li className="flex items-start gap-2">
 •
 Returns and refund diagnosis (reason granularity beyond the dropdown)
 </li>
 <li className="flex items-start gap-2">
 •
 Support resolution feedback (did we actually fix it)
 </li>
 <li className="flex items-start gap-2">
 •
 Customer satisfaction / NPS (embed in another flow so responses come in steadily)
 </li>
 <li className="flex items-start gap-2">
 •
 Repeat purchase or loyalty (what brings customers back, what doesn't)
 </li>

## Pulse Forms

Pulse Forms are one-time expiring forms for a specific question or moment. Use these for deliberate reads rather than always-on loops:

<li className="flex items-start gap-2">
 •
 Product page or listing clarity (does the description match what arrived)
 </li>
 <li className="flex items-start gap-2">
 •
 New product or collection launch feedback
 </li>
 <li className="flex items-start gap-2">
 •
 Checkout or pricing friction (why they hesitated or abandoned)
 </li>
 <li className="flex items-start gap-2">
 •
 Audience / customer profile survey (demographics, purchase drivers, how they found you)
 </li>
 <li className="flex items-start gap-2">
 •
 Seasonal or promotional feedback (did the campaign land, what fell flat)
 </li>
 <li className="flex items-start gap-2">
 •
 Win/loss or competitive (why they chose you over alternatives, or didn't return)
 </li>

## Conclusion

For the step-by-step walkthrough, see the <a href="/docs/getting-started" target="_blank" rel="noopener noreferrer" className="docs-link-primary">First Steps</a> guide. For question type guidance and best practices, see <a href="/docs/best-practices" target="_blank" rel="noopener noreferrer" className="docs-link-primary">Best Practices</a>. For a free tailored audit of your feedback strategy, try the <a href="/audit" target="_blank" rel="noopener noreferrer" className="docs-link-primary">feedback audit</a>. No email or account required.

"use strict";
const {Fragment: _Fragment, jsx: _jsx, jsxs: _jsxs} = arguments[0];
function _createMdxContent(props) {
  const _components = {
    a: "a",
    h2: "h2",
    p: "p",
    span: "span",
    strong: "strong",
    ...props.components
  };
  return _jsxs(_Fragment, {
    children: [_jsxs(_components.h2, {
      id: "introduction",
      children: [_jsx(_components.a, {
        "aria-hidden": "true",
        tabIndex: "-1",
        href: "#introduction",
        children: _jsx(_components.span, {
          className: "icon icon-link"
        })
      }), "Introduction"]
    }), "\n", _jsx(_components.p, {
      children: "When you are moving fast, it is easy to make product decisions based on assumptions rather than signal. Users churn, bugs go unreported, and features get built for the wrong people because there was no structured way to hear what users actually needed. By the time a pattern is obvious, the damage is already done."
    }), "\n", _jsxs(_components.p, {
      children: ["lumeforms gives you one structured channel to collect user feedback and a multi-pass ai analysis that ranks what is most important first, so you can act on signal instead of gut feel. Not sure where to start? Try the free ", _jsx("a", {
        href: "/audit",
        target: "_blank",
        rel: "noopener noreferrer",
        className: "docs-link-primary",
        children: "feedback audit"
      }), " for a tailored starting point for your product. No email or account required."]
    }), "\n", _jsxs(_components.h2, {
      id: "the-core-problem-you-are-making-decisions-without-signal",
      children: [_jsx(_components.a, {
        "aria-hidden": "true",
        tabIndex: "-1",
        href: "#the-core-problem-you-are-making-decisions-without-signal",
        children: _jsx(_components.span, {
          className: "icon icon-link"
        })
      }), "The core problem: you are making decisions without signal"]
    }), "\n", _jsx(_components.p, {
      children: "Most early-stage products have no systematic way to hear from users. Feedback arrives as one-off support tickets, occasional comments, or not at all. There is no way to tell which complaints represent a real pattern and which are edge cases, until users start leaving."
    }), "\n", _jsx(_components.p, {
      children: "lumeforms solves the analysis side, not just the collection side. You provide the context (your product, your users, what the form is for) and lumeforms surfaces ranked themes, sentiment, and actionable insights so you know where to focus next. Over time, acting on that signal consistently is what enables continuous growth and improvement rather than reacting to problems after they have already compounded."
    }), "\n", _jsxs(_components.h2, {
      id: "continuous-feedback-loops",
      children: [_jsx(_components.a, {
        "aria-hidden": "true",
        tabIndex: "-1",
        href: "#continuous-feedback-loops",
        children: _jsx(_components.span, {
          className: "icon icon-link"
        })
      }), "Continuous Feedback Loops"]
    }), "\n", _jsxs(_components.p, {
      children: ["Continuous feedback loops use lumeforms ", _jsx(_components.strong, {
        children: "Ongoing Forms"
      }), ", which are forms that never expire and can be filtered by time segment (last 7 days, last 30 days, all time) so you always have a current read. Place these at high-signal moments in your product:"]
    }), "\n", _jsxs("li", {
      className: "flex items-start gap-2",
      children: [_jsx("span", {
        className: "text-primary mt-1",
        children: "•"
      }), _jsx("span", {
        children: "Feature suggestions"
      })]
    }), "\n", _jsxs("li", {
      className: "flex items-start gap-2",
      children: [_jsx("span", {
        className: "text-primary mt-1",
        children: "•"
      }), _jsx("span", {
        children: "Bug reports"
      })]
    }), "\n", _jsxs("li", {
      className: "flex items-start gap-2",
      children: [_jsx("span", {
        className: "text-primary mt-1",
        children: "•"
      }), _jsx("span", {
        children: "NPS/CSAT (embed in another flow so responses come in steadily)"
      })]
    }), "\n", _jsxs("li", {
      className: "flex items-start gap-2",
      children: [_jsx("span", {
        className: "text-primary mt-1",
        children: "•"
      }), _jsx("span", {
        children: "Post-experience feedback"
      })]
    }), "\n", _jsxs("li", {
      className: "flex items-start gap-2",
      children: [_jsx("span", {
        className: "text-primary mt-1",
        children: "•"
      }), _jsx("span", {
        children: "Onboarding feedback"
      })]
    }), "\n", _jsxs("li", {
      className: "flex items-start gap-2",
      children: [_jsx("span", {
        className: "text-primary mt-1",
        children: "•"
      }), _jsx("span", {
        children: "Support resolution feedback"
      })]
    }), "\n", _jsxs("li", {
      className: "flex items-start gap-2",
      children: [_jsx("span", {
        className: "text-primary mt-1",
        children: "•"
      }), _jsx("span", {
        children: "Documentation / help feedback"
      })]
    }), "\n", _jsxs("li", {
      className: "flex items-start gap-2",
      children: [_jsx("span", {
        className: "text-primary mt-1",
        children: "•"
      }), _jsx("span", {
        children: "Churn / exit survey"
      })]
    }), "\n", _jsxs(_components.h2, {
      id: "pulse-forms",
      children: [_jsx(_components.a, {
        "aria-hidden": "true",
        tabIndex: "-1",
        href: "#pulse-forms",
        children: _jsx(_components.span, {
          className: "icon icon-link"
        })
      }), "Pulse Forms"]
    }), "\n", _jsx(_components.p, {
      children: "Pulse Forms are one-time expiring forms for a specific question or moment. Use these for deliberate reads rather than always-on loops:"
    }), "\n", _jsxs("li", {
      className: "flex items-start gap-2",
      children: [_jsx("span", {
        className: "text-primary mt-1",
        children: "•"
      }), _jsx("span", {
        children: "Census survey"
      })]
    }), "\n", _jsxs("li", {
      className: "flex items-start gap-2",
      children: [_jsx("span", {
        className: "text-primary mt-1",
        children: "•"
      }), _jsx("span", {
        children: "Quarterly or annual satisfaction"
      })]
    }), "\n", _jsxs("li", {
      className: "flex items-start gap-2",
      children: [_jsx("span", {
        className: "text-primary mt-1",
        children: "•"
      }), _jsx("span", {
        children: "Product-market fit / segment survey"
      })]
    }), "\n", _jsxs("li", {
      className: "flex items-start gap-2",
      children: [_jsx("span", {
        className: "text-primary mt-1",
        children: "•"
      }), _jsx("span", {
        children: "Feature launch feedback"
      })]
    }), "\n", _jsxs("li", {
      className: "flex items-start gap-2",
      children: [_jsx("span", {
        className: "text-primary mt-1",
        children: "•"
      }), _jsx("span", {
        children: "Implementation or go-live feedback"
      })]
    }), "\n", _jsxs("li", {
      className: "flex items-start gap-2",
      children: [_jsx("span", {
        className: "text-primary mt-1",
        children: "•"
      }), _jsx("span", {
        children: "Pricing or packaging feedback"
      })]
    }), "\n", _jsxs("li", {
      className: "flex items-start gap-2",
      children: [_jsx("span", {
        className: "text-primary mt-1",
        children: "•"
      }), _jsx("span", {
        children: "Win/loss or competitive"
      })]
    }), "\n", _jsxs(_components.h2, {
      id: "conclusion",
      children: [_jsx(_components.a, {
        "aria-hidden": "true",
        tabIndex: "-1",
        href: "#conclusion",
        children: _jsx(_components.span, {
          className: "icon icon-link"
        })
      }), "Conclusion"]
    }), "\n", _jsxs(_components.p, {
      children: ["For the step-by-step walkthrough, see the ", _jsx("a", {
        href: "/docs/getting-started",
        target: "_blank",
        rel: "noopener noreferrer",
        className: "docs-link-primary",
        children: "First Steps"
      }), " guide. For question type guidance and best practices, see ", _jsx("a", {
        href: "/docs/best-practices",
        target: "_blank",
        rel: "noopener noreferrer",
        className: "docs-link-primary",
        children: "Best Practices"
      }), ". For a free tailored audit of your feedback strategy, try the ", _jsx("a", {
        href: "/audit",
        target: "_blank",
        rel: "noopener noreferrer",
        className: "docs-link-primary",
        children: "feedback audit"
      }), ". No email or account required."]
    })]
  });
}
function MDXContent(props = {}) {
  const {wrapper: MDXLayout} = props.components || ({});
  return MDXLayout ? _jsx(MDXLayout, {
    ...props,
    children: _jsx(_createMdxContent, {
      ...props
    })
  }) : _createMdxContent(props);
}
return {
  default: MDXContent
};


The core problem: you are making decisions without signal