The black hole on your website

There is a 100-page product guide on your site. It looks expensive. You see the download count tick up. And then nothing. No context. No names. Just silent gravity.

I remember a QBR where a team celebrated 600 downloads. When I asked what those people needed, the room went quiet. We had activity, not understanding. A black hole.

From monologue to dialogue

The common belief: put detailed guides online so buyers self-educate and come prepared. Sounds helpful. In practice, you are broadcasting specs and asking the buyer to translate their business problem into your SKUs. That is work you should be doing, not them.

Your guide is not education. It is a monologue. The buyer has to run the discovery call in their own head. Most will bail before they get to a valid solution. The ones who stay often misconfigure and then argue price on the wrong thing.

A product guide is a monologue. Selling is a dialogue.

Here is the real shift: your website can host a guided conversation. It can ask questions, listen to inputs, apply logic, and explain trade-offs. It can arrive at a valid, tailored solution the way your best presales expert would. Not a quiz. A real discovery call.

Modern buyers prefer self-serve like self-checkout. They want progress without waiting for a rep. Give them a conversation, not a library.

CPQ is not about automation - it’s about correctness.

Make the website run the discovery call

1) Start with needs, not features. Turn pages into questions. What outcome, constraints, volumes, environments, approvals? Example: instead of listing motor sizes, ask load, duty cycle, voltage, IP rating. Let the system translate needs to options.

2) Use the same product logic you trust in CPQ. This is not a pretty web form. The site should use the same configuration rules that protect you in Tacton or your CPQ. If 480V and IP65 exclude a certain drive, it should be impossible to pick it. Correctness beats cosmetics.

3) Make the reasoning visible. People buy when they understand why. Show why options appear or disappear. Show conflicts and the rule behind them in plain language. Example: “IP65 requires sealed bearings. Option B removed.” Explainability builds confidence.

4) End with a budget-ready proposal. After a valid path, generate a proposal with assumptions, bill of material, price range, and next steps. Send it to the buyer and your CRM. You now have a qualified lead with a documented need, not a mystery download.

5) Name and avoid the Pretty Quiz anti-pattern. The Pretty Quiz feels interactive but passes junk to sales. No validation. No explainability. No proposal. It wastes buyer time and floods your team with weak leads.

Adoption is the only metric that matters.

6) Govern it like a product, not a campaign. Someone owns the logic, change requests, and test suite. New rules roll out safely. If changes still need a project plan, the field will route around it.

When I worked hands-on with a team selling configured equipment, we moved one product family from PDF to guided dialogue with their CPQ rules behind it. Same questions their presales used. Same constraints. The site started sending sales a proposal package the buyer could explain to their boss. Meetings got shorter. Deals moved faster because the work was already done.

AI does not replace logic - it depends on it.

Use AI to make the conversation natural and the documentation instant, but keep it inside the rails of explicit, testable logic. Fluent guesses are not helpful when the forklift shows up and the crate is wrong.

What to do next

Pick one complex offering and map the real discovery path. Take your top guide. Write down the 10 questions your best presales always asks. Mark the rules that never bend. That is your conversation backbone.

Put your CPQ logic on the site, not a brochure. Connect your product rules. If you use Tacton, expose a safe subset to web. Keep it small. One family. One path. Ship in weeks, not quarters. Improve weekly.

Measure learning, not vanity. Track completion to proposal, proposal correctness, and time to first qualified meeting. Read the proposals buyers send themselves. Tighten rules and language each week. Progress beats perfection.

Yes, long PDFs feel thorough. They are also where intent goes to die. Buyers want a clear path and a confident answer they can share. Give them that on the first visit.

Your website should not be a library. It should be your best, most tireless sales engineer.