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/saas-developers">For SaaS</a>
- <a href="/docs/content-creators">For Content Creators</a>
- <a href="/docs/marketers">For Audience Researchers or Marketing Teams</a>

</div>

<Alert type="warn" className="text-center">
 This page is still in progress. Reach out if you have any questions or suggestions.
</Alert>

## Introduction

Integrating systematic feedback into your SaaS is an incredibly high-leverage action. Companies that continuously gather feedback on their users typically outcompete ones that don't. The main function of lumeforms is to help you make better data-driven business decisions. For a step-by-step walkthrough from project creation to results, check out the <a href="/docs/getting-started" target="_blank" rel="noopener noreferrer" className="docs-link-primary">First Steps</a> guide. For tips on question types and feedback loops, see the <a href="/docs/best-practices" target="_blank" rel="noopener noreferrer" className="docs-link-primary">Best Practices</a> page. Treat lumeforms like your personal research assistant, but remember to evaluate the analysis as needed before blindly acting on it. 

## Continuous Feedback Loops

Continuous feedback loops take advantage of lumeforms **Ongoing Forms** functionality, which are forms that never expire and can be configured to show responses that have only come in recently. Place these strategically around your application to gather high-impact feedback. Even a few high quality responses can be found very valuable. Below is a list of possible things you can add to your continuous feedback loops: 
<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
 </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>
## General Feedback Forms 

Send your users one-time feedback forms to get a clear read of a particular question. Below is a list of possible things you can add to your feedback forms:
<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, see the <a href="/docs/getting-started" target="_blank" rel="noopener noreferrer" className="docs-link-primary">First Steps</a> guide.

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

For SaaS

<Alert type="warn" className="text-center">
 This page is still in progress. Reach out if you have any questions or suggestions.
</Alert>

## Introduction

Audience feedback is incredibly high-leverage signal: it tells you what's working, what isn't, and what to do next so you can create content that resonates. By using lumeforms, you create an intentional space for the direct, honest feedback that drives better stats, higher quality content, and more sponsorships. lumeforms helps you gain clarity, signals to your audience you're serious, and gives you the next steps to take your craft to the next level. For a step-by-step walkthrough from project creation to results, check out the <a href="/docs/getting-started" target="_blank" rel="noopener noreferrer" className="docs-link-primary">First Steps</a> guide. For tips on question types and feedback loops, see the <a href="/docs/best-practices" target="_blank" rel="noopener noreferrer" className="docs-link-primary">Best Practices</a> page. Treat lumeforms like your personal research assistant, but remember to evaluate the analysis as needed before blindly acting on it.

## Content Forms

The main ritual of lumeforms is to create a feedback form for each new content posted (video, blog post, etc.). Place this form where your content lives, such as at the end of the content or in the video description. After receiving the feedback, either deepen your understanding or take actions to improve your work. Below is a list of possible things you can add to your Content Forms:
<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

Running one-time or annual census polls is highly recommended as it will help you gain a deeper understanding of your audience and make creating tailored content that resonates deeply effortless. Below are things you can add to your census polls:
<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>

## General Feedback Forms

Send your audience one-time feedback forms to get a clear read of a particular question. Below is a list of possible things you can add to your feedback forms:
<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

Taking steps to drive higher form completion is worth the effort or put more bluntly, a requirement. Below is a list of practices or techniques that help increase completion and show your audience their input matters:
<li className="flex items-start gap-2">
 •
 Explicitly ask at a clear moment for audience to fill out the form and where to find it. Be sure to thank the audience in advance
 </li>
 <li className="flex items-start gap-2">
 •
 Bring up poll results or display them as images throughout content
 </li>
 <li className="flex items-start gap-2">
 •
 Thank responders or highlight anonymized insights so people feel heard
 </li>

## Conclusion

For the step-by-step, see the <a href="/docs/getting-started" target="_blank" rel="noopener noreferrer" className="docs-link-primary">First Steps</a> guide.

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

For Content Creators

<Alert type="warn" className="text-center">
 This page is still in progress. Reach out if you have any questions or suggestions.
</Alert>

Documentation coming soon.

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.

"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: "1-introduction",
      children: [_jsx(_components.a, {
        "aria-hidden": "true",
        tabIndex: "-1",
        href: "#1-introduction",
        children: _jsx(_components.span, {
          className: "icon icon-link"
        })
      }), "1. Introduction"]
    }), "\n", _jsxs(_components.p, {
      children: ["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 ", _jsx("a", {
        href: "/docs/getting-started",
        target: "_blank",
        rel: "noopener noreferrer",
        className: "docs-link-primary",
        children: "First Steps"
      }), " guide; for role-specific guidance, see ", _jsx("a", {
        href: "/docs/use-cases",
        target: "_blank",
        rel: "noopener noreferrer",
        className: "docs-link-primary",
        children: "Use Cases"
      }), "."]
    }), "\n", _jsxs(_components.h2, {
      id: "2-prefer-other-question-types-over-text-when-you-can",
      children: [_jsx(_components.a, {
        "aria-hidden": "true",
        tabIndex: "-1",
        href: "#2-prefer-other-question-types-over-text-when-you-can",
        children: _jsx(_components.span, {
          className: "icon icon-link"
        })
      }), "2. Prefer Other Question Types Over Text When You Can"]
    }), "\n", _jsx(_components.p, {
      children: "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."
    }), "\n", _jsxs(_components.h2, {
      id: "3-stay-anonymous-first-for-honest-feedback",
      children: [_jsx(_components.a, {
        "aria-hidden": "true",
        tabIndex: "-1",
        href: "#3-stay-anonymous-first-for-honest-feedback",
        children: _jsx(_components.span, {
          className: "icon icon-link"
        })
      }), "3. Stay Anonymous-First for Honest Feedback"]
    }), "\n", _jsxs(_components.p, {
      children: ["lumeforms is anonymous-first by design so responders feel safe giving honest feedback. Only turn on ", _jsx(_components.strong, {
        children: "Take Name"
      }), " or ", _jsx(_components.strong, {
        children: "Take Email"
      }), " when your use case clearly requires it (e.g. follow-up, support tickets). If you're unsure, lean towards anonymous."]
    }), "\n", _jsxs(_components.h2, {
      id: "4-a-trick-for-collecting-npscsat",
      children: [_jsx(_components.a, {
        "aria-hidden": "true",
        tabIndex: "-1",
        href: "#4-a-trick-for-collecting-npscsat",
        children: _jsx(_components.span, {
          className: "icon icon-link"
        })
      }), "4. A Trick for Collecting NPS/CSAT"]
    }), "\n", _jsxs(_components.p, {
      children: ["Put your NPS or CSAT within a ", _jsx("a", {
        href: "/docs/saas-developers#continuous-feedback-loops",
        target: "_blank",
        rel: "noopener noreferrer",
        className: "docs-link-primary",
        children: "continuous feedback loop"
      }), " and mark it ", _jsx(_components.strong, {
        children: "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."]
    })]
  });
}
function MDXContent(props = {}) {
  const {wrapper: MDXLayout} = props.components || ({});
  return MDXLayout ? _jsx(MDXLayout, {
    ...props,
    children: _jsx(_createMdxContent, {
      ...props
    })
  }) : _createMdxContent(props);
}
return {
  default: MDXContent
};


2. Prefer Other Question Types Over Text When You Can

3. Stay Anonymous-First for Honest Feedback