By industry

B2B SaaS website: the demo request

A business buyer wants a demo a teammate can see, on a form that does not stop them. Find the field, email rule or blank calendar that ends the request before your team reads it.

5 visitors try to .
First test free with an accountRun it from your coding agent

Why do B2B SaaS visitors leave a website without requesting a demo?

Business buyers leave a B2B SaaS website without requesting a demo when the form asks for things they cannot give yet, rejects a personal email address without a way forward, or shows a calendar that never loads. They arrive with a problem and a manager who will ask why they chose you, so a form that stops them looks like a bad vendor. A simulated visitor shows which field, rule or screen stopped them, and whether the confirmation reached their inbox.

What this looks like in a report

Who
Kwame, runs operations at a logistics firm with a few dozen staff
How they arrived
Clicked a LinkedIn ad for dock scheduling software
Where they stopped
Demo form, on the phone number field

“It wants a phone number and a text code before I can even pick a time. I do not want a vendor texting me before I have seen the product. I will book with the one that emails me.”

The fix. Make the phone number optional and remove the text code from the demo form, then show the open times on the same screen. Replace any blank calendar box with a plain link to the scheduler, and send a confirmation email that names the time.

An illustration. Run a test to see your own.See a real sample report

A demo form that fails a buyer before anyone on your team sees it

A buyer on a work laptop wants to see whether your product solves one problem before a meeting. The demo form asks for a phone number that must be confirmed by text, a company size chosen from ranges they do not recognize, and a job title list with no option for their role. If they use a personal email address, the form may refuse it with a message that does not say what to do next. Each of these ends the request before a person on your team reads it. The sales report shows only the requests that got through, so the lost ones never appear.

  • Does the demo form ask only for what a first call needs, with the rest marked optional?
  • Does a personal email address get a clear message and another way to ask for a demo?
  • Does any step need a text code sent to a phone, which a visitor cannot receive?
  • Does the calendar show open times, or a blank box when it fails to load?
  • Does the confirmation email reach the visitor's inbox and name the next step?

The form asks for what a first call does not need

A demo form often carries fields the sales team wants for its own reports. Company size arrives as ranges that a buyer cannot place themselves in, the phone field is marked required, and a question about how they heard of you sits above the time picker. A first call needs a name, a work email, a company name and a note on the problem they want solved. The rest can be asked on the call. Mark each required field and ask whether the rep needs it before the first conversation. A field that only fills a report should not stop a buyer who is ready to talk.

Work email rules that refuse a personal address with no route

Some B2B forms accept only a company domain, to keep the list clean. That filter can be reasonable, but the message it shows is often the whole problem. A buyer who writes from a personal address, or from a home office, sees a line that says the address is not valid, with nothing to click. The buyer may be right about their own situation, and the form is wrong about what to do next. Test the form twice, once with a personal address and once with a company-style address you control, then read the message each time. If a personal address is refused, the message should name another route, such as a contact address.

A calendar that loads after the form, or not at all

Some B2B sites embed a scheduling calendar on the demo page, loaded from another service. The page looks finished while the calendar is still a blank box, and a buyer who waits a moment may leave. Some calendars also need a cookie choice before they show times, and a visitor who declines it may see nothing. Check the page on a phone and on a laptop, and note whether open times appear without a second click. If they do not, offer a plain link that opens the scheduler in a new tab, plus a short form that asks for a preferred window.

What you get with Mimiq

  1. 01

    Run it by hand, or on every pull request

    Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.

  2. 02

    Bugs and usability problems in one report

    The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.

  3. 03

    Visitors that behave like your audience

    Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.

  4. 04

    A prompt to fix each problem

    Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.

  5. 05

    Follow every visitor

    See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.

The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.

A second demo form on the pricing page can fail on its own

The first run finds the field, message or blank calendar that stops the buyer. The fix may be a shorter form, a route for personal addresses or a calendar link that opens reliably. Run the same buyer from the homepage and from the pricing page, since each may use a different form. Repeat it after each change to your sales tool and before a new ad sends buyers to the demo page.

Starter

Try it on one launch

$9 once
120 credits, never expire

About 4 tests of 5 visitors

  • Visitors on your landing page, signup and checkout
  • Where they left and why, with a fix to copy for each problem
  • Run it in the app or on every pull request
  • Ask any visitor a question, included
  • Test accounts and protected previews
Buy 120 credits

Builder

Test every build

$19 a month
500 credits every month

About 20 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Builder

Pro

Test every release, as a team

$49 a month
1,500 credits every month

About 60 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Pro

Scale

Test at scale, every day

$149 a month
6,000 credits every month

About 240 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Priority support
  • Cancel anytime
Choose Scale
$0for your first test, with a free account (Google sign-in, no card). It includes 50 credits, enough for 10 visitors. After that a visitor uses 5 credits, and packs start at $9 for 120 credits.
See a sample report

Questions

Does this tell me how many demo requests I will get?

No. Mimiq does not predict how many buyers will request a demo, and it does not forecast your pipeline. It shows the step where a simulated buyer stopped and the message the form showed there. Conversion rates come from your analytics and your CRM, from real traffic.

Will a test submission reach my sales team?

It can. If the form sends to your real inbox or CRM, a test submission creates a lead your team may follow up. Tell your sales team before a run, or use a test mode or staging copy of the form if your tool offers one.

Can a visitor pass a text code on a phone?

No. A visitor has a working email inbox but cannot receive a text message. A form that needs a text code stops there, and the report shows that step. If you need a phone number, make it optional, or confirm by email instead.

Does the test check whether my product claims are true?

No. The test follows the buyer's path and records what the page and form do. It does not judge whether a claim, a case study or a feature is accurate, so keep those checks with the people who own your product and your references.

Can I test a demo form from a third-party tool?

Yes, if it loads in a normal browser at a public address. If a bot check or CAPTCHA stops the visitor, the report marks it as blocked by the site, and every real buyer meets the same check. Treat that as a problem with the form, not only with the test.

Keep reading

Send visitors and see what breaks first.

Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.

5 visitors try to .