## Reference images

Study these alongside the description below: hierarchy, rhythm, spacing, colour. Build for the product you are asked about, using this design language.

- Component: https://kage-design-assets.t3.tigrisfiles.io/components/descript-com/c210b18a-1678-4bef-91b5-c444a8589f04-1789146911-5.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/descript-com/c210b18a-1678-4bef-91b5-c444a8589f04-1789146857587-full.webp
- Component on Kage: https://kage.design/component/descript-feature-grid-2

## Before you start
Ask whether the user's product sells to teams or enterprises, which certifications are real, and which outcomes can be substantiated. Use only verified claims.

Build a light enterprise proof section with a centered eyebrow, large dark editorial headline, supporting sentence, and a dark secondary CTA. Under it, create a three-column grid of six cards. The first row should communicate security/compliance capabilities with small circular badges; the second row should foreground large numeric outcomes and identify the associated customer or source. Use a warm near-white background #fff8fa, dark plum text #3a101c, pale gray-pink card fill #f1ebed, dark button #4b2b36, and restrained borders #e1d9dc. Use 20–28px card padding, 8–12px radius, 24px grid gaps, and strong numeric typography. On mobile, stack cards while retaining the distinction between compliance and outcome cards. Add a link or tooltip for evidence and a visible focus state for the CTA.

### Never
- Never invent certifications, statistics, company names, or audit claims.
- Never copy the reference's badge artwork, card text, or exact metrics.