## 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/fastlane-2-0/959a4273-adb0-42a9-9dfc-df0ea320e78d-1792735312-9.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/fastlane-2-0/959a4273-adb0-42a9-9dfc-df0ea320e78d-1792735248580-full.webp
- Component on Kage: https://kage.design/component/fastlane-2-0-faq

## Before you start
Ask which buying objections, security concerns, implementation questions, and audience-fit questions the user's product receives. Use those answers to author the FAQ structure.

Create a dark FAQ section with a near-black background #090909 and a restrained coral-red glow or gradient along the top edge. Use a two-column desktop layout: a left column with a 36–52px white heading, one compact CTA, and optional supporting sentence; a right column with 5–7 accordion items. Each item should be a white or near-white rounded row with dark text, 14–16px question text, a plus/close icon, and 16–20px padding. The first item may be open and taller, with 13–14px muted answer text and a clear divider. Use 12–16px radii and 10–14px gaps. On mobile, stack the heading above the questions. Implement keyboard-accessible disclosure buttons, aria-expanded state, smooth height transitions, and reduced motion support.

Never: copy logos, product names, copy, illustrations, or imagery from the reference.