Should You Gate Your Product Demo? For and Against

Gate the conversation, not the first look. If seeing the demo costs you a person's time, as a live call does, a short form is fair. If the demo is something a visitor can use alone, let them see it first and ask who they are when they want something that needs their details: a saved session, a follow-up, a call. A plain form is the right answer more often than the anti-gating crowd admits, and this post says when.

The default runs the other way. In our crawl of 198 B2B SaaS homepages on 2026-10-02, 99 (50%) led with a sales-led ask such as book a demo or talk to us, and only 11 (6%) linked to an interactive demo in the hero or main navigation. The method, limits and data are published. The sample is early-stage, technical companies, so do not stretch it to all of B2B. The crawl also measured what homepages offer, not what a gate does to conversion, so what follows about effects is judgement.

What counts as gating a demo?

Anything that asks a visitor to identify themselves before they see the product. There are two kinds, and they deserve different answers.

A form in front of a person. Book a demo, request a demo, talk to us. The visitor is asking for someone's time. Where we could follow the button to a form (49 sites), the median form had five fields.
A wall in front of the product. An email before a tour, a video behind a form, or an account before anything works. A free signup belongs here: 92 of the 198 homepages (46%) offered a free-signup path, and an account usually means identification plus setup before the visitor sees any value.

The first is easy to defend, because a person's time is scarce. The second is where the argument is, because showing a self-serve product costs you little.

What is the case for gating?

Four reasons, all real.

Contact data. For some teams a form is the only way to attribute anything to anyone.
Filtering. Sales time goes to people who raised a hand. This is strongest when each demo takes real time from a person.
Cost. If every demo spins up real infrastructure or needs a human on the other end, a gate caps what you spend on people who were never going to buy.
A number to be measured on. A gated demo produces form fills, and marketing teams are measured on form fills. That is an organizational reason rather than a customer one, but it explains why gating often stays even when nobody can show it pays.

Notice what is missing: keeping the product from competitors. It is the weakest reason. A competitor has colleagues and work email addresses, and a form stops none of them. If something should not be public, leave it out of the demo. That is a content decision, not an argument for a form.

What is the case against gating?

A form asks the most of a visitor at the moment they know the least. Someone who has not seen the product has no reason yet to hand over details, and a form filters on willingness to identify, not on fit. Those are different groups, and the group a form turns away includes people who would have been a good match and only wanted to look first. This is reasoning, not something our crawl measured.

The gate also hides its own cost. A visitor who leaves at the form is a visitor you never learn about, while a poor lead at least shows up in a report.

The alternatives are thin, too. In our crawl, only 11 of 198 (6%) showed a link to an interactive demo, tour or sandbox in the hero or main navigation, and 16 (8%) showed a chat launcher. A visitor who is not ready to talk to anyone can fill in the form, create an account, or leave.

When is a plain form the right call?

More often than the debate suggests. Keep the form in these cases.

The demo is a conversation. The product is complex, configured per customer or regulated, so a generic tour would mislead and every deal needs scoping. The form routes the request and the call is the demo.
Traffic is small, or each inbound is worth a call. If a handful of visitors a week arrive ready to buy, or there are few possible buyers and the deals are large, the form costs you less than a better funnel would earn. Put the effort upstream.
You cannot see what ungated visitors do. If nothing records an anonymous session, removing the form trades a mediocre lead for no information. Until that exists, keep the gate.

Either way, keep the form short. The median in our crawl was five fields. We have no evidence on what number converts best, so ask only what you need to route the request, and test.

How do you decide, page by page?

Ask what the visitor on that page has already decided.

Pricing page. They think you are a candidate. A gate here is cheap and the data is worth something.
Cold arrival from a search result. They have decided nothing, and the gate is the whole interaction.
A link from a person's email. Someone vouched for you. Let them straight in, and ask later.

Most teams have one demo and therefore one decision, and a single decision is probably wrong for at least one of their pages. The question is which demo, on which page, for a visitor at which stage.

Is there a middle path?

Usually, yes: let anyone reach the product, and ask for details when the visitor wants something that genuinely needs them, such as a saved session, a shareable link or a follow-up. The catch: it only produces good data if the ungated part reports something, and a visitor you cannot see is the gated team's best objection.

What does a live demo agent change?

It changes what the gate is for. A form identifies and qualifies a visitor before they see anything. A demo agent can do both while the visitor is looking at the product. Inkly is built this way: it asks the visitor's role and goal, shows the part of the product that fits, answers questions as they come up, and hands sales what the visitor asked and explored. How it works walks through the stages.

So the question shifts from form or no form to when to ask, and how much a conversation can replace. Role, goal and use case come out of a chat more naturally than a dropdown, in the visitor's own words, and by the time you want contact details the visitor has seen something.

The limits, plainly.

A visitor who chats and leaves is not a lead. You know what they asked and explored, not who they are. If your process needs a name and email on every opportunity, you still have to ask.
Inkly does not send email. Follow-up stays with your team, and what it hands you is the context for it: the questions asked, the workflows explored, the objections raised. That is buyer intelligence.
Visitor details and conversations start on Pro, not Free. On Free the agent runs, but you do not get the per-visitor record.
It takes setup, and someone has to keep the material it draws on accurate. A person still answers what it cannot.

We sell this, so weigh the section accordingly.

How do you test whether gating is working?

Split by traffic source rather than by visitor, and measure to pipeline rather than to leads. A visitor-level split mixes groups who arrive by different routes. A source-level split is coarser but easier to defend.

Leads will always favor the gate and reach the open version, so a test that counts leads has decided the outcome before it starts. Run it for a full sales cycle, because a few weeks of data on a quarter-long cycle measures form fills and nothing else. Agree in advance that form fills may fall while pipeline holds, or the test gets reversed for reasons unrelated to what it showed.

Where does Inkly fit, and where does it not?

Inkly is an AI demo agent that chats with each visitor, runs a personalized guided demo, answers questions inline and hands buyer intelligence to sales. Every plan includes the voice and chat demo agent, priced by active visitors, where one person counts once a month. Free is $0 for 30 visitors. Pro starts at $150 a month ($120 a month billed yearly) for 150 visitors and adds visitor details, tailoring and qualification. Enterprise is custom. See the pricing page.

It is the wrong tool when traffic is small, when the product is simple enough that a recorded walkthrough or a free account explains it, or when deals close on a call whatever the visitor saw first. A plain form, or even a gate, is the better fit there. What to use instead of a book-a-demo form compares the options, and what an interactive demo is covers the self-serve one.

FAQ

Should I gate my product demo?

Gate a demo that needs a person, and let a self-serve demo be seen first. If your product needs a call to make sense, keep a short form.

Is a free signup a gate?

Yes. It asks for an account, and usually some setup, before the visitor sees value. In our crawl of 198 homepages, 92 (46%) offered a free-signup path, which made it the most common alternative to a demo request in the sample. It works best where time to value is short.

How many fields should a demo request form have?

We do not have a number known to convert best. The median form in our crawl had five fields, across 49 forms. Ask only what you need to route the request, and test.

Does ungating mean losing leads?

It means fewer form fills and more anonymous sessions. Whether pipeline falls depends on your traffic and what you can see about anonymous visitors, and our crawl does not settle it. Test by traffic source against pipeline.

What should you do this week?

List every place a visitor is asked to identify themselves before they see the product, and write beside each what that visitor has already decided. Pick the one where the answer is nothing and put something visible in front of the ask. A recorded walkthrough will do. Then check whether the requests that arrive are better qualified. If your product needs a call, keep the form, shorten it, and move on.

See the Inkly demo agent in action across the full product.