Lovable prompt for a feature grid section

Insert a feature grid section into the a project management SaaS landing page in this Lovable project, directly after the hero, leaving every other section untouched — this is a surgical addition, not a rebuild.

From the top:
1. Header block: an eyebrow of 2-3 words naming the category, a headline stating the outcome engineering managers at startups is buying (not a list of nouns), and one supporting sentence. Match the hero's alignment; do not introduce a second alignment system.
2. The grid: six equal cards, three across on desktop. Deliberately not a bento — no card spans two columns, no featured tile, no mosaic. Uniform cells build a scan rhythm; mixed spans build hierarchy, and this section's job is enumeration, not argument.
3. Under the grid: a single centered sentence inviting the next step, with "start a free trial" as the linked text.

Card recipe, identical for all six:
- Icon on top — one library, one size, and all six either enclosed in matching rounded containers or all bare. Mixed icon treatment is the clearest tell of a rushed grid.
- Title: the capability in 2-3 words.
- Body: one line answering "so what?" for engineering managers at startups — lead with the result ("Know which invoice is late before the client does"), mention mechanism only if space remains. Derive all six from what a project management SaaS actually does; no two bodies may open with the same verb.

Hover: the full card responds — background tint or a 2px lift, pick one and apply it consistently; pointer cursor only if cards truly link somewhere.

Visual direction:
Minimal dark style. Near-black canvas (#0A0A0B) with one elevated surface tone (#141416) for cards — never more than two surface steps. Hairline borders (1px, white at 8% opacity) instead of shadows; if a shadow is unavoidable use 0 1px 2px rgba(0,0,0,0.4) and nothing softer. Text in exactly three steps: white at 92% for headings, 60% for body, 40% for captions. Generous negative space — section padding at least 120px on desktop, 64px on mobile. The accent color appears only on interactive elements and one hero highlight, nowhere else.

Palette: a strict neutral ramp (white, #F5F5F5, #E5E5E5, #737373, #171717) carries the entire interface; pick one accent and use it only for primary CTAs, active states, and a single hero highlight. If the accent appears more than five times per viewport it stops being an accent. Keep semantic colors (success, error) desaturated so the accent stays in charge.
Typography: one geometric sans (a Futura/Poppins-class face) at three weights maximum (400/500/700). Scale: 64-88px hero, 32px section heads, 18px lede, 16px body, 13px caps labels with 0.08em tracking. Tight headline leading (1.05-1.1), relaxed body (1.6). Let the geometry carry the personality — no italics; weight and size do all hierarchy.
Motion: none. Zero scroll animations, zero entrance effects — the page is fully composed the instant it paints. Spend the motion budget on input feedback instead: 120-150ms ease-out color and transform transitions on hover and press states only. Hold this constraint absolutely; it is a statement, not an omission.

Spacing and mobile:
- Copy the vertical padding of the adjacent sections so the insertion is seamless; 3rem header to grid; 1.5rem grid gap.
- Phones: single column, icons one step smaller, and bodies rewritten to hold one or two lines rather than wrapping to three.

Verify after building: the new section sits between the hero and the section that used to follow it, both unchanged; all six cards match height at 1440px and 768px; no card spans columns; each body opens with a distinct verb; hover covers whole cards.