Which Renaissa product fits this job?

Why a quiz, not a catalogue dump

Renaissa ships a suite of industry products plus custom builds. A visitor who needs hearing alerts does not need RenAura. A tyre counter does not need Lex. This page asks four questions — role, industry, team size, main problem — and scores products from the same registry the rest of the site uses.

The scoring table is in config, not in the React tree. Change a weight there and the quiz changes. We will not hard-code “if legal then Lex” in the component. If a slug leaves the registry, it cannot be recommended.

Recommendations are reasons, not ratings. We do not invent stars, review counts or “9 out of 10 firms.” If two products tie, you will see both. If nothing scores, you will see an empty state — better than a fake match.

After you see a result you can open the product page, book a demo, or email yourself the recommendation (intent=tool). Custom software still goes through /contact?intent=scoping.

The quiz is not a substitute for a scoping call. A chambers that also wants expense tracking may need Lex and Xpenzo. A dealer who wants WhatsApp quotes may need Tyren and ReNovaX. We show at most two rows so the page stays honest. If your job is a custom agent inside an existing product, skip the quiz and use the AI-in-existing intent on the contact form.

Scoring is additive. Picking “legal” on industry and “hearings” on problem will beat a weak default. Changing weights later will not require a React rewrite. That is the point of keeping the table in config: marketing can adjust reasons without inventing a new product that is not in the registry.