If you make outdoor structures and you have started shopping for software, two words keep showing up as if they were twins: CPQ and product configurator. They are not twins. Pick the wrong one and you either speed up quotes nobody can see, or you get a pretty model that never becomes a cut list.

What CPQ actually is

CPQ means configure, price, quote. It grew up inside CRM. Its job is to help a sales rep assemble a bundle, apply a discount, get an approval, spit a PDF, update a pipeline. The customer almost never touches it.

The "configure" is a list. Model, warranty, support tier. It assumes the product already exists. It answers what this bundle costs and who has to sign it.

What a configurator actually is

A product configurator asks a different question. What does this structure look like, can the line build it, and what does it cost.

The buyer sets span, height, roof, finish. The rules you already know sit in the model: profiles, hardware, when a post is required, what the machine can cut this week. The output is not a branded PDF for someone to retype. It is the visual, the price, and the spec the shop can cut from.

The center of gravity is the product, not the paperwork.

The difference, without the brochure

CPQ is sales-rep-facing and list-driven. Its output is a quote and a pipeline update.

A configurator is product-driven. Someone designs a real structure inside manufacturing law. Its output is a picture, a real price, and a production spec.

CPQ assumes the hard part is pricing and approvals. A configurator assumes the product does not exist yet. It gets created, validly, in the browser. For a pergola or a pool enclosure, that difference is the whole business. Your complexity is not a discount tier. Every yard is a different span. Half the questions are what it will look like against that wall.

Why the words got sticky

Both say configure. Both say price. Some configurators quote. Some CPQ tools bolted on a viewer. A simple product with a handful of variants can live in either.

The expensive mistake is at the edges. Thousands of stable SKUs through a sales team: CPQ's discount logic matters more than a 3D viewer. One-of-one outdoor structures: a list cannot hold infinite valid dimensions, and a PDF does not feed a saw. That is a configurator problem.

Ask three things. Where does the complexity live, in approvals or in the physical thing. Who should drive it, a trained rep or the buyer. What has to leave the other end, a polished PDF or a spec that does not get retyped.

Most outdoor shops do not have a quote-speed problem. They have a see-it-and-build-it problem. CPQ makes a broken motion faster. A configurator fixes the motion.

Molldi is not a CPQ tool

Molldi is the design-to-manufacturing OS for outdoor structures. The rules, the model, the order, the cut. Same object. If you sell standardized bundles through reps, a CPQ earns its keep. If every order is a yard, you need the product, not the paperwork.

Buy for the friction you actually have, not the acronym on the slide.

Join Molldi.