# The "request a demo" form becomes a qualified conversation, instantly.

You automate SaaS data collection by putting a conversational agent in front of each moment that matters: demo requests, bug reports, security questionnaires and churn exits. It asks one question at a time, types every answer into a structured record, and posts that record straight to your CRM or database.

## The process this page is about

Not "AI for SaaS". One process, the one that decides whether a demo request turns into a qualified conversation or a form sitting in a CRM nobody reads: the qualification that happens the moment someone says what they actually need.

- **Who starts it**: A visitor who read the pricing page twice, clicked "request a demo," and is now looking at a six-field form that asks for a job title before it asks what they are trying to solve.
- **What it costs today**: A form that either asks too little, so sales spends its time on leads that were never going to buy, or asks too much, so the visitor abandons it before the submit button.
- **What it has to produce**: A qualified record: who they are, the team size, the tool they use today, the exact workflow they want automated, and how soon they need it live.
- **of a sales team's time goes to leads that were never qualified to begin with**: 40% (source: PreCallAI)

## What it asks, and what it never asks

You name the fields your demo form already has. It does the asking, in whatever order the story comes out, and it keeps asking until the required ones are filled.

| Field | Type | Required | Why |
|---|---|---|---|
| full_name | text | yes | Who to follow up with |
| work_email | email | yes | How the team reaches back out |
| company_name | text | yes | Routes the record to the right account |
| team_size | text | yes | Sizes the opportunity, honestly |
| current_tool | text | no | What they are replacing, if anything |
| primary_workflow | text | yes | The actual workflow, in their language, not "efficiency" |
| timeline | text | yes | How urgently this needs to happen |

### And what it will not do

- It never books a specific calendar slot, a rep, or a day and time. That is a person's job.
- It never quotes or estimates a price, a discount, or a contract term.
- It never commits to a roadmap item, a ship date, or says a feature is "coming soon."
- It never confirms a security or compliance answer on the company's behalf; it records the exact question instead.
- It never offers a discount or a win-back deal to reverse a cancellation.
- It never invents a field. If they did not say it, the record says "Not captured" instead of a guess.

## Try the run yourself

Six moments a SaaS team actually handles, each running its own agent with its own fields. Pick one and answer it the way a real user would, mid-thought and a little annoyed, and watch it ask the follow-up instead of accepting the blank.

- [We want to see a demo](https://joina.chat/l/quill-demo): Chat widget. Demo qualification, in the corner of your own pricing page.
- [Something is broken](https://joina.chat/l/quill-bug): Conversation page. A production bug report, with a hard stop to on-call for anything emergency-shaped.
- [Are you SOC 2 compliant](https://joina.chat/l/quill-security): Conversation page. A security questionnaire question, logged for the security team, not answered on the spot.
- [We cancelled last week](https://joina.chat/l/quill-churn): Conversation page. A churn exit interview with no win-back offer attached.
- [Our trial just ended](https://joina.chat/l/quill-trial): Conversation page. Where the trial stalled, and whether more time would even help.
- [Can it do this instead](https://joina.chat/l/quill-feature): Conversation page. A feature request from an existing account, logged honestly, not promised.

## Frequently asked questions

**How do I automate SaaS demo qualification?**

Name the fields your demo form already has, point the agent at your pricing and product pages, and put the link or widget on your site. The agent runs the conversation, produces a qualified record, and posts it to your CRM through a webhook, Zapier or Make. Setup is minutes, not an implementation project.

**Will it promise a feature, a roadmap date, or a price by accident?**

It is instructed never to commit to a roadmap item, a ship date, or a price, and never to say a feature is "coming soon." When someone asks, it says the request is logged for the product team, or that pricing is a conversation with a person, which is also the honest answer. Every conversation is stored with the sentence each value came from.

**Can it handle security or compliance questionnaires?**

It collects the exact question, the framework it references, and any hard requirements like data residency or SSO, then says plainly that the security team reviews and answers it in writing. It never confirms a compliance or certification answer itself, because that is not a conversational agent's call to make.

**What about churn interviews and cancellations?**

A separate agent runs the exit interview a week or two after cancellation, in a learning frame, not a save flow: it never offers a discount or a win-back deal. The bug report and feature request agents work the same way for existing customers, and neither one is trying to sell anything.

**Does it work with Salesforce or HubSpot?**

Through a webhook, yes. Gnosari posts a signed JSON payload the moment a record is complete, and Zapier or Make routes it into your CRM or helpdesk. There is no Gnosari app to install on either side.

## Five minutes from now your demo requests could be already qualified.

Build the agent, put it on your pricing page, and watch the first qualified record arrive. Free to start, no card.

Full page: https://gnosari.com/for/saas-tech