One Module, Explained Like a Landing Page

Pivot's procure-to-pay page treats a single module with full landing page care. The hero promises "touchless invoices" next to a floating approval card (INV-001, $3,990, Decline or Approve) on a lime glow, then a logo strip and a pain statement: AP teams are still touching every invoice.

Alternating Feature Rows With UI Fragments

Six rows alternate text and product snippets: the full cycle connected, agents that clear the AP queue, inbox to approved, matching before problems, sourcing to settled. Each row has a headline, a short paragraph and an accordion of sub-points, with the active one marked by a thin gradient progress line.

Proof, Stack and Objections

The bottom half reuses Pivot's building blocks: a fanned customer story carousel, a two-row grid of integration logos ("Your stack, already connected"), a FAQ that tackles non-PO invoices and seat pricing, and resource cards. A great example of how to give each product module a self-contained page.