v0 prompt for an agency landing page

Build a landing page for a project management SaaS, aimed at engineering managers at startups. Generate it in v0 as a Next.js page assembled from separate components with Tailwind and shadcn/ui — one component per section (Nav, Hero, WorkGrid, Capabilities, Process, Manifesto, ContactFooter) — so any section can be regenerated on its own later.

Sections, top to bottom:
1. Nav — wordmark left; links to Work, Capabilities, Process, Contact; a small availability note on the right.
2. Hero — one oversized positioning line naming what a project management SaaS does and for whom, plus a one-sentence subline naming the specialty. No stock imagery.
3. WorkGrid — 6 selected projects in an asymmetric 2-column grid alternating tall and wide cards; each card carries project name, client type, one outcome metric, and a hover reveal with a one-line summary.
4. Capabilities — 5 services as full-width rows: index number, service name, 10–14 word description.
5. Process — 4 numbered steps in a horizontal band, each with a label and two lines on what the client receives.
6. Manifesto — a 3-sentence belief statement set large, then a compact team row (name, role) for up to 5 people.
7. ContactFooter — the email address at display size, studio location, social links.

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 responsive rules:
- Vertical padding py-24 desktop / py-14 mobile; internal grid gaps step between gap-4 and gap-8, nothing arbitrary.
- Below md, WorkGrid collapses to one column and hover reveals become permanent captions; Process stacks vertically along a left rule.

Derive the hero line and all card copy from a project management SaaS — name the specialty concretely; "we craft digital experiences" is banned. The primary call to action is "start a free trial", shown as a Nav button and repeated above ContactFooter.

After building, check that: each section is its own component file; WorkGrid renders exactly 6 cards, each with a visible metric; the hero wraps to no more than 3 lines at 1280px; at 375px there is no horizontal scroll; "start a free trial" appears exactly twice on the page.