## 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/lorikeetcx-ai/66a45b6c-3f5c-4089-bde2-7a0aa025402f-1789142170-5.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/lorikeetcx-ai/66a45b6c-3f5c-4089-bde2-7a0aa025402f-1789141728989-full.webp
- Component on Kage: https://kage.design/component/lorikeetcx-feature-grid

## Before you start
Ask what channels, workflows, and product capabilities matter to the user's customers, then express them through original examples.

Build a two-column feature section that explains the product through contrasting use cases. Each column should have a concise serif title, one or two lines of supporting copy, and a large visual mockup beneath it. The pair should communicate both the problem and the product's ability to resolve it.

Design rules:
- Layout: two equal columns with a 24–40px gap; stack vertically on mobile.
- Typography: serif feature titles around 25–32px; sans-serif descriptions at 13–15px with a restrained line length.
- Visuals: use original chat, email, dashboard, or workflow mockups in softly rounded frames; keep UI text legible but secondary.
- Colour: mostly white UI surfaces with pale grey #F2F2F2 and pale mint #E7F4E9 accents; subtle blurred colour glow may sit behind visuals.
- Spacing: align titles and descriptions, then give each visual generous vertical room; include a small tab or progress indicator below if the section is interactive.
- Interaction: tabs can switch examples; animate content with a short fade/slide and preserve keyboard access.

Never:
- Never reuse the reference copy, UI screenshots, product name, or imagery.
- Never invent a complex dashboard when a simple illustrative state communicates better.
- Never let decorative glow reduce contrast or readability.