For Sales

Short version

There is nothing in this PR to pitch to a prospective clinic. It doesn't add, change, or remove any feature of the Dentolize product itself — no new screen, report, integration, or workflow a clinic user would ever see. It's purely an internal engineering process change (how pull requests are opened).

If a technically-curious prospect asks about engineering process

Some prospects (larger clinic groups with an in-house IT/ops evaluator, or partners doing technical diligence) do ask about release process and quality practices. This is fair, low-risk context for that conversation:

• Dentolize's engineering team reviews every change against a live,

fully-seeded preview of the app before it ships — not just automated tests.

• That preview infrastructure is configurable per change (extra regions,

WhatsApp integration on/off, demo data depth), and this PR is what makes those settings discoverable to every contributor instead of a few people who happened to know about them.

What to avoid saying

• Don't present this as a customer-visible feature or a competitive

differentiator on its own — it's table-stakes engineering process, not a product capability.

• Don't imply it addresses a security gap; it doesn't touch authentication,

data isolation, or compliance (ZATCA, insurance, etc.) in any way.

• If a prospect's real question is "how do you test changes before they

ship," this is supporting color, not the headline answer — the headline answer is the preview-environment system itself (which already existed before this PR).