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. Below is a step-by-step guide for first time users. This documentation will use an example project: a Vanta style compliance SaaS. Follow along but replace the details with your specific use case. It is **strongly recommended** to first visit the <a href="/docs/use-cases" target="_blank" rel="noopener noreferrer" className="docs-link-primary">Use Cases</a> page to read the role-specific guide that applies to you most. 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. 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">
 •
 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">
 •
 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. 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

Articles and posts on feedback tools, SaaS, and product.

Blog


## Introduction

Implementing feedback infrastructure into your SaaS is one of the highest leverage decisions you can make. However, the landscape of feedback tools is vast and constantly evolving. I put together this guide to help you find the tool that is best for you. First, we'll walk through all the different categories and end with specific recommendations depending on your level.

## The Nine Categories

1. **Survey & Form Tools**
   - **Description:** Collect structured feedback by asking users direct questions. Best for churn surveys, onboarding surveys, NPS, and customer research. Low setup, high signal. Works at any stage. Pretty much every SaaS uses this category.
   - **Pros:** High signal, direct and honest, works at any stage, low setup, flexible for any use case.
   - **Cons:** Requires users to actively participate, low response rates can render this category useless.
   - **Tools:** lumeforms, Google Forms, TypeForm, SurveyMonkey, Tally, Jotform.
   - **Personal thoughts:** A must have for any SaaS.

2. **In-App Feedback & Behavior**
   - **Description:** Passively observe what users do inside your product without asking them. Session recordings, heatmaps, click tracking. Best for optimization once you have meaningful traffic.
   - **Pros:** Passive, no user effort required, catches issues users wouldn't think to mention, great for spotting friction.
   - **Cons:** Needs significant traffic to be meaningful, time consuming to analyze recordings, more observational than actionable, expensive.
   - **Tools:** Hotjar, FullStory, LogRocket, Mouseflow.
   - **Personal thoughts:** Great for optimization at scale but not going to help you find PMF or solve the difficult problems holding your SaaS back.

3. **Feature Request & Roadmap Tools**
   - **Description:** Let users submit and vote on feature ideas, then connect that to a public roadmap. Popular in SaaS but criticized for creating voting theater and abstracting founders away from real decisions.
   - **Pros:** Centralizes user requests, gives users a voice, public roadmap builds transparency and good will.
   - **Cons:** Voting theater, loudest users dominate, abstracts you from real decisions, creates process overhead, can lead you to build the wrong things.
   - **Tools:** Canny, Featurebase, Frill, UserVoice, Productboard.
   - **Personal thoughts:** The most controversial category on this list. You spend time managing public roadmaps and voting systems instead of talking to users and shipping. I personally would not bother with this category.

4. **NPS & Satisfaction Tracking**
   - **Description:** Measure customer sentiment over time with standardized scores (0–10). Best for tracking whether your product is trending in the right direction at scale.
   - **Pros:** Simple standardized score, easy to track over time, good for investor reporting.
   - **Cons:** Can be done better with category one.
   - **Tools:** Delighted, AskNicely, Retently, Wootric.
   - **Personal thoughts:** Category one does this better with richer signal, exists mostly for stakeholder reporting. I personally would not bother with this category.

5. **User Testing & Research**
   - **Description:** Watch real users attempt specific tasks to uncover usability issues. Best used at key product milestones rather than continuously.
   - **Pros:** Reveals deep usability issues, shows real behavior in context, great for validating new features before shipping.
   - **Cons:** Time intensive to set up and run, expensive, not continuous, hard to scale.
   - **Tools:** Maze, UserTesting, Lookback, Sprig.
   - **Personal thoughts:** Underused by small teams and overused by big ones. Watching how real users interact with your product instead of in abstract is game changing.

6. **Research Synthesis**
   - **Description:** Organize and analyze qualitative feedback from multiple sources (interviews, surveys, support tickets) into one place. Best for teams doing serious customer research.
   - **Pros:** Organizes qualitative data from multiple sources, great for teams doing serious research, surfaces patterns across interviews and surveys.
   - **Cons:** Only useful once you have large volumes of qualitative data, overkill for most early stage teams.
   - **Tools:** Dovetail, Aurelius.
   - **Personal thoughts:** Unless you're drowning in qualitative data and losing key insights, you can skip this category.

7. **Social & Community Listening**
   - **Description:** Monitor what people say about you outside your product on Reddit, X, HN, etc. Best for brand awareness and catching organic sentiment.
   - **Pros:** Captures organic unsolicited sentiment, catches things users would never say directly to you, good for brand awareness.
   - **Cons:** Noisy, hard to act on, only meaningful once your brand is big enough that people talk about you.
   - **Tools:** Brandwatch, Octolens, Mention.
   - **Personal thoughts:** Only worth it when you're big enough that people talk about you unprompted. If you know where your users hang out already, this category may not be for you.

8. **Customer Support Feedback**
   - **Description:** Feedback collected passively through live chat and support tickets. Best for catching acute pain points from users who are already frustrated enough to reach out.
   - **Pros:** Catches acute pain from users frustrated enough to reach out, real time signal, no setup required.
   - **Cons:** Biased toward angry or confused users, not representative of your whole user base, live chat can devalue product perception.
   - **Tools:** Intercom, Crisp, Zendesk, Freshdesk.
   - **Personal thoughts:** Live chat can greatly improve customer experience, but can hurt brand perception if done poorly (presents as scrappy, cheapens the async SaaS experience). Use your intuition whether this category is right for your SaaS.

9. **Enterprise VoC**
   - **Description:** End-to-end voice of customer programs combining surveys, analytics, and reporting for large organizations. Overkill for most SaaS teams until significant scale.
   - **Pros:** Comprehensive, combines multiple feedback streams, strong reporting and benchmarking for large orgs.
   - **Cons:** Extremely expensive, heavy to implement, complete overkill for anyone not at serious scale.
   - **Tools:** Qualtrics, Medallia, InMoment.
   - **Personal thoughts:** If you're at a scale where you need something like Qualtrics, you're not reading this guide.

## What's Right For You?

1. **For Indie SaaS / Solo Founders / MicroSaaS**
   - Category one is your bare minimum and maybe all you need. Taking the time to set up feedback infrastructure is one of the best decisions you can make early on. My SaaS, **lumeforms**, would work well here.
   - Consider category three if feature requests start coming in faster than you can track manually. The risk is adding it too early creates process overhead and voting theater before you've found product market fit. Most indie founders regret it.
   - Consider category eight for a high-touch approach and to create a white-glove experience or build loyalty and trust. For Indie SaaS, Crisp is your best bet.

2. **Mid Stage (Series A/B, growing team)**
   - Everything listed for Indie SaaS.
   - Consider category two once traffic is meaningful enough that direct user contact stops being feasible and you are in the optimizing phase.
   - Consider category seven once the brand is big enough to monitor.

3. **Large / Enterprise SaaS**
   - All categories are fair play here.
   - Consider category four for automated sending at scale, CRM integrations, role-based dashboards, and reporting for stakeholders who want a clean number without digging into raw data.
   - Consider category five once there's a dedicated product and design team.
   - Consider category six once qualitative research is happening at scale.
   - Consider category nine once there's a dedicated VoC team.


A quick guide to feedback tool categories (surveys, NPS, feature requests, session replay, and more) and what to use at each stage of your SaaS.

Best Feedback Tools For SaaS

"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
  }, {Alert} = _components;
  if (!Alert) _missingMdxReference("Alert", true);
  return _jsxs(_Fragment, {
    children: [_jsx(Alert, {
      type: "warn",
      className: "text-center",
      children: _jsx(_components.p, {
        children: "This page is still in progress. Reach out if you have any questions or suggestions."
      })
    }), "\n", _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", _jsxs(_components.p, {
      children: ["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 ", _jsx("a", {
        href: "/docs/getting-started",
        target: "_blank",
        rel: "noopener noreferrer",
        className: "docs-link-primary",
        children: "First Steps"
      }), " guide. Treat lumeforms like your personal research assistant, but remember to evaluate the analysis as needed before blindly acting on it."]
    }), "\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 take advantage of lumeforms ", _jsx(_components.strong, {
        children: "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:"]
    }), "\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"
      })]
    }), "\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: "general-feedback-forms",
      children: [_jsx(_components.a, {
        "aria-hidden": "true",
        tabIndex: "-1",
        href: "#general-feedback-forms",
        children: _jsx(_components.span, {
          className: "icon icon-link"
        })
      }), "General Feedback Forms"]
    }), "\n", _jsx(_components.p, {
      children: "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:"
    }), "\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: "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, see the ", _jsx("a", {
        href: "/docs/getting-started",
        target: "_blank",
        rel: "noopener noreferrer",
        className: "docs-link-primary",
        children: "First Steps"
      }), " guide."]
    })]
  });
}
function MDXContent(props = {}) {
  const {wrapper: MDXLayout} = props.components || ({});
  return MDXLayout ? _jsx(MDXLayout, {
    ...props,
    children: _jsx(_createMdxContent, {
      ...props
    })
  }) : _createMdxContent(props);
}
return {
  default: MDXContent
};
function _missingMdxReference(id, component) {
  throw new Error("Expected " + (component ? "component" : "object") + " `" + id + "` to be defined: you likely forgot to import, pass, or provide it.");
}
