Pergola visualizer vs configurator: one closes, one just looks good
A buyer is sitting in front of a free pergola visualizer at half past eleven on a Tuesday night. They have rotated the model four times. They have changed the colour from natural oak to anthracite and back. They have widened it from 3 metres to 4 metres and decided the bigger one looks right against the patio in their head. The pergola on the screen is beautiful. They have no idea how much it costs, who builds it, or whether it will actually fit the awkward 30-degree corner of their garden.
They close the tab. The session ends. The brand running the visualizer has no record they were ever there.
That is the gap a pergola configurator closes. A visualizer renders. A configurator renders, prices, and routes. The naming is close. The outcome on the website is not.
What a pergola visualizer does#
A pergola visualizer is a focused tool with one job: render a pergola on screen and let the buyer change a few things about it. It usually does four things, in order:
It loads a 3D model of a pergola, built on WebGL, the same browser graphics standard that powers most modern 3D on the web. It lets the buyer pick a colour, a size band, and a roof type from a small set of options. It re-renders the result, often with a smooth transition, so the buyer can see the new version. And it sometimes drops the pergola into a stock garden scene with grass, a deck, and a string of lights, so the buyer can imagine it in a real setting rather than against a grey backdrop.
That is the whole product. A visualizer ends at the visual. There is usually a contact form below the canvas, where the buyer can ask for a quote by typing their name, email, and phone number. There is usually no price. There is usually no spec sheet, no PDF, no CRM record, and no tracking event firing back to the ad platforms. The buyer designs. The buyer leaves. The seller, if there is one, hears nothing unless the contact form is filled in.
For a category like outdoor living, where the buyer is making a five-figure decision and wants to feel something about the product before they commit, a visualizer is genuinely useful at the awareness stage. It shows a pergola in a way a brochure cannot. The buyer can pick up a phone with a picture in their head, instead of a vague idea of “something modern.” For brand-building tools, free utilities, and inspiration galleries, the visualizer is the right shape of thing.
The problem is when a seller mistakes a visualizer for a sales tool, embeds it on the homepage, runs ad spend at it, and waits for the contact-form inquiries to come in. The buyer designs a beautiful pergola. The buyer leaves. The seller, again, hears nothing.
What a pergola configurator additionally does#
A pergola configurator does everything a visualizer does, then keeps going. The 3D render is the surface. The work happens underneath it, in four blocks that a visualizer does not have.
It applies the seller’s real configuration rules. Not just “you can pick anthracite or oak”, but the rules that catch the buyer specifying something that cannot be built. The maximum span between posts for a louvred roof at 4.5 metres. The accessory that is incompatible with the integrated lighting kit. The post height that needs reinforcement at a given size. The visualizer does not know any of this. The configurator does, because the rule library is wired in.
It calculates a real price from the seller’s pricing engine. Not a “starting from” number on the brochure. A specific price for a specific build, in the buyer’s currency, with the seller’s real margin, real installation modifiers by region, and any active promotions baked in. The buyer designs the pergola they actually want, the price lands on screen, and the buyer either says yes or asks a follow-up. The number ends the speculation.
It produces a designed PDF the buyer and the seller both receive. The PDF carries the seller’s logo, lists the spec line by line, shows the rendered pergola, and reads as a serious quote document, not a screenshot with a price stuck to it. The buyer downloads it. The seller’s CRM stores it. Two days later, when a slower competitor is still putting together a hand-written quote, the buyer already has a designed document with the right logo on it.
It fires events into the seller’s stack. The moment the buyer designs, prices, and submits, the configurator pushes the event to GA4, Meta, Google Ads, and the seller’s CRM. Without those events, the seller cannot tie ad spend to actual configurator engagement. With them, the marketing team can see exactly which campaign brought the buyer who configured a 4 by 5 metre louvred pergola in anthracite at 23:47 on a Tuesday. The loop closes.
And it changes what Monday morning looks like in the seller’s inbox. Instead of twenty contact-form lines that say “interested in pricing, please call,” the sales team opens the week to a stack of configured PDFs, each one with a buyer, a spec, and a price already on it. The conversation starts where it used to end. For a longer breakdown of how that shift plays out across a sales week, the pergola configurator guide walks through it section by section.
Side by side: same buyer, two outcomes#
The same buyer lands on two different pergola sellers in the same evening. Both sites lead with a 3D pergola the buyer can change. The buyer plays with both. The outcomes diverge.
On the visualizer site, the buyer rotates the model, picks a size, picks anthracite, picks a louvred roof. The render updates. Below the canvas there is a button that says “Ask for a quote.” The buyer hesitates. They are not ready to be on a sales call. They close the tab. The visualizer logs a 3-minute session. No name. No spec. No follow-up. The seller’s Monday inbox is unchanged.
On the configurator site, the same buyer does the same thing. The render updates. A price appears next to it: €11,400 for the 4 by 5 metre build they designed. The buyer pauses. The number is higher than they hoped, but not crazy. They click “Email me the quote.” A designed PDF lands in their inbox within seconds with the same render at the top, the spec laid out, the price clearly stated. The seller’s CRM also gets it, with the buyer’s email, the time spent in the configurator, and the exact spec. Monday morning, a salesperson opens the configured PDF, calls the buyer, and starts the conversation with “I see you designed a 4 by 5 metre louvred build last Tuesday.”
The buyer ended up in two different places. Not because the buyer made a different choice. Because the website did.
331 quotes generated in four months. 166 hours saved across the team in the same window.
The 166 hours belong to the configurator side of the line. It is the time the team used to spend translating a buyer’s visualizer screenshot into a real quote, by hand. The configurator takes that work off the desk. A visualizer cannot. A visualizer ends one step before the work that would have produced the time-back number. The full pattern across teams running configured funnels lives in the case studies, where the named numbers sit next to the named customers.
When a visualizer is the right pick#
A visualizer is the right tool for a real set of jobs. Pretending otherwise is dishonest, and the rest of this argument falls apart if a configurator is treated as a universal answer.
A visualizer is the right tool when the audience is in inspiration mode, not buying mode. A DIY homeowner planning a future garden makeover, two seasons away from a real purchase, does not want a quote. They want to see what an aluminium louvered pergola might look like in a green space, decide whether they like the silhouette, and bookmark the page. A configurator that hits them with a price the moment they pick a size is the wrong shape of tool for the wrong moment in the buying journey.
A visualizer is the right tool when the goal is brand awareness or category education, not conversion. A trade body, a design magazine, or a manufacturer running a free public utility to attract backlinks and social reach can ship a visualizer that produces no leads at all, and still earn its keep. The point is the visibility, not the inbox.
A visualizer is the right tool when the product is genuinely a kit and the buyer fulfils the spec themselves at a hardware store. There is no seller to send the lead to. The visualizer is the product.
For everyone else who actually sells pergolas, the visualizer is the wrong tool. It looks similar to the right tool, which is the problem.
When you need the configurator#
The threshold is clear. Any seller running pergolas at €5,000 or more average ticket needs the configurator, not the visualizer, because the unit economics of a single closed deal pay for the configurator stack many times over and the unit economics of an inspiration tool do not.
Any seller with a dealer network needs the configurator, because the dealer needs the priced PDF, the spec, and the lead routed to the right branch on the day the buyer designs the build, not after a back-and-forth that the visualizer does not even start.
Any seller running paid traffic to the configurator page needs the configurator events firing back to Meta, Google Ads, and GA4, because without those events the ad spend optimises on the wrong signal and the cost per qualified lead climbs without explanation. A visualizer has no events to send.
Any seller competing on speed, the only competition that matters in outdoor living, needs the configurator. The buyer who left the visualizer at 23:47 with no quote and no follow-up is the same buyer who signed with the competitor at 09:14 the next morning, because that competitor produced a priced PDF before breakfast.
And any premium seller worried that publishing a number will commoditise their product still needs the configurator. The fix is not to skip the price; it is to gate it with the intent questions the configurator can ask before the number appears. The right configurator can hold prices private, route the priced PDF to the sales rep first, and start the conversation with a configured spec, not a tag.
The single-question test#
If a seller is staring at a 3D pergola tool and trying to decide whether it is a visualizer or a configurator, the test is one sentence long.
Did the buyer leave with a price?
Not a guide price. Not a starting-from number on a banner. A specific price for the specific pergola the buyer designed, in their currency, that they can quote to a partner or a spouse over breakfast the next morning without doing any extra work. If the answer is no, the tool was a visualizer. The interaction looked like selling and did not actually sell.
A second test sharpens it. Did Monday morning’s inbox change because that buyer was on the site? On a visualizer, the answer is almost always no. The buyer left no trace, no spec, no contact, no event. On a configurator, the inbox is different. The PDF is in it. The spec is attached. The CRM has the buyer, and the ad platform has the event. The buyer was on the site, and the seller knows what they wanted and what it would cost.
The technology behind both tools looks similar. The 3D models, the colour swatches, the rotating canvas, the size sliders. The technology is not the question. The question is what the buyer and the seller hold in their hands when the session ends.
The buyer rotating a pergola at midnight is the same buyer either way. What changes is whether the morning after is silence or a priced PDF in two inboxes. That is the difference between a visualizer and a configurator, sitting in plain sight, and that is the difference between an inspiration tool and a sales system. If the goal is selling pergolas, the choice is made.
If the wider category buying decision is on the table, the pergola configurator guide covers what a real one does, the eight things to test on a vendor demo, and the customers behind every claim. The configurator gallery holds the live working examples from the teams already on the other side of this line.
People also ask.
What is the difference between a pergola visualizer and a pergola configurator?
A pergola visualizer is a 3D viewer. It shows a pergola model on screen and lets the buyer change colours, sizes, and roof types so they can see what it might look like. A pergola configurator does all of that, then applies the seller's real configuration rules, calculates a real price from the seller's pricing engine, and produces a designed PDF that lands in the buyer's inbox and the seller's CRM. The visualizer ends at the screenshot. The configurator ends at a priced quote and a lead.
Is a pergola visualizer enough if I just want to inspire buyers?
Yes, for that single job. A visualizer is fine as a brand-building tool, a DIY inspiration board, or a free utility that gets shared on social. If the goal is awareness and there is no expectation of a quote, a visualizer does the work. The moment the goal becomes selling pergolas at €5,000 or more, a visualizer is the wrong tool, because the buyer leaves the page without a price and without anywhere obvious to go next.
Do pergola visualizers calculate prices?
Usually not. A visualizer is built to render. Pricing belongs to a configuration engine that knows the seller's costs, margins, regional installation modifiers, and accessory rules. Some visualizers tack on a starting-from number, but a starting-from price is not the same thing as a real quote for a specific build. If the buyer cannot leave with a price for the pergola they just designed, the tool is a visualizer.
Can a buyer book a quote through a visualizer?
Most visualizers end at a contact form. The buyer designs a pergola, sees it on screen, then has to submit name, email, and phone to ask for pricing. That is the slow loop the visualizer was supposed to remove. A configurator skips the form because the price and the PDF are already produced, and the lead lands in the CRM with the full spec attached.
When should a pergola seller pick a visualizer over a configurator?
When the audience is genuinely top of funnel and the goal is brand awareness, not conversion. Free public visualizers can earn backlinks, social reach, and design-inspiration traffic that a configurator gated by qualification questions would not. For any seller running ad spend, dealer networks, or a website built to produce inquiries, the visualizer is a half-build and the configurator is the full one.
Will a pergola configurator publish my prices to anyone who lands on the page?
Only if the seller chooses to. A serious configurator can hide public prices, gate the number behind a qualification flow, and send the priced PDF privately to the seller and the buyer after a sales-rep review. The configurator still designs, still prices, still produces the PDF. The difference is whether the public page shows a number or holds it back for the conversation.
Can I run a visualizer first and a configurator later?
Some sellers do, on the theory that a visualizer is easier to ship. In practice it doubles the work. The visualizer needs a 3D pipeline, the configurator needs the same 3D pipeline plus the rules, the pricing engine, the PDF, and the CRM handoff. Sellers who start with the configurator skip the second build entirely, because the visualizer is already inside the configurator.
What happens to the lead after the buyer designs a pergola?
On a visualizer, in most cases nothing. The buyer sees the render, maybe takes a screenshot, then leaves. On a configurator, the configured spec, the priced PDF, and the buyer's contact details fire to the seller's CRM, to GA4, to Meta, and to Google Ads at the moment of submission. Monday morning, the sales team opens the inbox to a designed PDF with a price on it, not to a contact-form line asking for a callback.