Recipe R09
The AI Company
A company website for an AI product: one light source, the product working on screen, public numbers, a clear price and one confident ask.
AI labs, AI product companies and developer-tool startups that need to look credible to engineers and buyers at the same time.
ScenarioA company site for AI agents that draft support replies: a calm hero, an agent working a real ticket, what it does on every ticket, thirty days of public numbers, seat pricing and plain answers on security and data.
The page, section by section
- 01
Hero
Orbit DawnA ringed light rising over a dark horizon, with the nav and headline set inside it; the page's only bright surface.
- 02
Main action
Prism Rim ButtonA dark pill held in a hairline of graded colour, for the one action that matters.
- 03
Quiet actions
Phosphor Glass ButtonText links whose light turns toward the pointer: sign in, watch it work.
- 04
The product, working
Agent RunThe hero's promise proven immediately: the agent plans, searches, reads, drafts and checks, then waits for a person.
- 05
What it does
Signal TilesTen capabilities as quiet tiles that switch on as you point at them.
- 06
Thirty days of public numbers you can scrub through, with which direction is good news for each.
- 07
Pricing
Glow Base PricingThree plans whose bases glow in their own colour, with a monthly and yearly switch.
- 08
Questions
Focus FAQSecurity, data and model questions answered plainly, one at a time.
- 09
The ask
Ring Flood CTAA closing banner framed by the page's own colours; pointing at the action floods it.
Change first
The first things to replace to make this page yours.
- Replace the agent run with your product's real flow: your own task, steps and output.
- Publish numbers you measure and can stand behind, with the month they're from.
- Put your real plans, seat prices and what each includes into the pricing cards.
- Answer your real security, data-retention and model questions in the FAQ.
The build brief
Paste it into Claude, Cursor or ChatGPT with the component files, and ask for your own version: your name, your work, your product. It names each component and where to copy it from.
# Build brief: The AI Company A company website for an AI product: one light source, the product working on screen, public numbers, a clear price and one confident ask. For: AI labs, AI product companies and developer-tool startups that need to look credible to engineers and buyers at the same time. Scenario: A company site for AI agents that draft support replies: a calm hero, an agent working a real ticket, what it does on every ticket, thirty days of public numbers, seat pricing and plain answers on security and data. ## Direction - One light source: a violet dawn rising behind the hero (#05031a night, #7239ea glow, #ee9cf6 fringe). Everything below is near-black and quiet. - Instrument Sans for everything, tight at display sizes, with Instrument Serif italics for the one or two words that carry a claim. - Show, don't claim: the agent works a real ticket on screen before any adjective about it, and the numbers are public and scrubbable. - Buttons with character, used sparingly: a prism-rim pill for the main action, phosphor-glass text links for the quiet ones. - Never name a model or a lab you don't use. Components that print a third-party model name are left out. ## Choose by product and audience - Developer tool or API: lead with agent-run, inline-diff or a terminal-like demo; mono labels and real code; pricing by usage (usage-ruler or credit-tier-pricing). - Assistant or chat product: lead with cited-answer, ask-bar or thinking-mark; a paper palette reads warmer than black. - Research lab or model company: a typographic hero and long-form writing; numbers and charts (scrub-sparkline-stats, model-bench) over feature grids. - Enterprise buyers: put security, data handling and SSO in the FAQ and footer, and keep pricing honest (subtractive-pricing shows exactly what each plan leaves out). ## Curation: one of each, on purpose - One hero treatment: a background or a typographic hero, never both competing. - One navigation system for the whole site, and one primary button style repeated everywhere. - One AI interaction component on the home page; others belong on product pages. - Check every component's fixed text: a demo that names a model, a lab or a customer you don't have is a claim you're making. - If two components are both 'the impressive one', cut one. Restraint is what makes the remaining one feel expensive. ## Backgrounds: where they help and where they hurt - Ambient backgrounds belong behind the hero or the final call to action: moments with little text and one message. - Never put moving backgrounds behind paragraphs, pricing, forms or tables. Reading and motion compete, and contrast becomes unpredictable. - Check contrast at the background's brightest frame, and keep buttons off the brightest part. If body text drops below 4.5:1, move it or add a scrim; don't lighten the text. - Avoid fatigue: one ambient surface per page, slow, low contrast. Every Vitrine background pauses offscreen and in hidden tabs. - Reduced motion: every Vitrine background renders a designed still frame; check that it still looks intentional. - Performance: WebGL and canvas backgrounds cost GPU time and battery. Load one per page and confirm with /performance-pass on a throttled phone. ## Page map 1. Hero: Orbit Dawn. A ringed light rising over a dark horizon, with the nav and headline set inside it; the page's only bright surface. 2. Main action: Prism Rim Button. A dark pill held in a hairline of graded colour, for the one action that matters. 3. Quiet actions: Phosphor Glass Button. Text links whose light turns toward the pointer: sign in, watch it work. 4. The product, working: Agent Run. The hero's promise proven immediately: the agent plans, searches, reads, drafts and checks, then waits for a person. 5. What it does: Signal Tiles. Ten capabilities as quiet tiles that switch on as you point at them. 6. Proof: Scrub Sparkline Stats. Thirty days of public numbers you can scrub through, with which direction is good news for each. 7. Pricing: Glow Base Pricing. Three plans whose bases glow in their own colour, with a monthly and yearly switch. 8. Questions: Focus FAQ. Security, data and model questions answered plainly, one at a time. 9. The ask: Ring Flood CTA. A closing banner framed by the page's own colours; pointing at the action floods it. ## Change first - Replace the agent run with your product's real flow: your own task, steps and output. - Publish numbers you measure and can stand behind, with the month they're from. - Put your real plans, seat prices and what each includes into the pricing cards. - Answer your real security, data-retention and model questions in the FAQ. ## Components Copy each component's files from its page (Code tab) into your project before you start, and use them as given: change props and content, not internals. - Orbit Dawn: https://tryvitrine.dev/components/orbit-dawn (A ringed light rising over a dark horizon, with a white-hot core, thin pink striations and a wide halo, under faint orbit lines with drifting nodes and twinkling stars.) - Prism Rim Button: https://tryvitrine.dev/components/prism-rim-button (A dark pill held in a hairline of graded colour; on hover the colour flows round the rim and a faint glow spills from each end.) - Phosphor Glass Button: https://tryvitrine.dev/components/phosphor-glass-button (A liquid-glass pill that senses you coming: its rim light turns to face the cursor and the pill leans in to meet it.) - Agent Run: https://tryvitrine.dev/components/agent-run (A coding agent's work as a checklist that fills in while it happens — search, read, edit with a diff stat, run tests — where any finished step opens to show its output.) - Signal Tiles: https://tryvitrine.dev/components/signal-tiles (A grid of quiet black service tiles that switch on when you point at them: a field of dots twinkles up around the pointer, a lit blue arc slides round the border to the nearest edge, and the icon and label come up to white.) - Scrub Sparkline Stats: https://tryvitrine.dev/components/scrub-sparkline-stats (KPI tiles you can read back through: drag along a sparkline and the big number turns to that day — only the digits that differ roll — while the date and the change follow.) - Glow Base Pricing: https://tryvitrine.dev/components/glow-base-pricing (A three-plan pricing section on black where each card's base glows in its own colour, so its button sits in a pool of light, with rims tinted to match and a monthly/yearly switch that rolls the prices.) - Focus FAQ: https://tryvitrine.dev/components/focus-faq (An FAQ where choosing a question promotes it: it travels up and grows into the heading, its answer unfolds beneath, and every other question steps back into a compact list below.) - Ring Flood CTA: https://tryvitrine.dev/components/ring-flood-cta (A closing banner framed by a slowly turning gradient; point at the main action and the gradient floods out of the button across the whole banner, turning every word to ink as it arrives.) ## Build - Next.js (App Router), TypeScript, Tailwind CSS. No extra UI libraries. - Write real content for this site: real names, dates, numbers and sentences. No lorem ipsum, no "Feature one". - Compose the sections in the order of the page map. Keep each component's own spacing; add page rhythm with consistent section padding. - Mobile first: every section must work at 375px wide without horizontal scrolling. - Respect prefers-reduced-motion everywhere; every Vitrine component already does. ## Before you ship - Run `/landing-page-art-director` (https://tryvitrine.dev/workshop/skills/landing-page-art-director): Puts the product working near the top and gives every section one job. - Run `/template-tells` (https://tryvitrine.dev/workshop/skills/template-tells): AI company sites are among the most templated on the web; this finds the defaults. - Run `/copy-quality` (https://tryvitrine.dev/workshop/skills/copy-quality): Claims about AI need to be specific and true. - Run `/performance-pass` (https://tryvitrine.dev/workshop/skills/performance-pass): A WebGL dawn and a live demo share the first two screens. - Run `/responsive-audit` (https://tryvitrine.dev/workshop/skills/responsive-audit): The agent demo, the tiles and the pricing cards need to work at phone width. - Run `/accessibility-pass` (https://tryvitrine.dev/workshop/skills/accessibility-pass): The running demo must be pausable and its steps announced; the sparklines must work by keyboard.
Direction
- One light source: a violet dawn rising behind the hero (#05031a night, #7239ea glow, #ee9cf6 fringe). Everything below is near-black and quiet.
- Instrument Sans for everything, tight at display sizes, with Instrument Serif italics for the one or two words that carry a claim.
- Show, don't claim: the agent works a real ticket on screen before any adjective about it, and the numbers are public and scrubbable.
- Buttons with character, used sparingly: a prism-rim pill for the main action, phosphor-glass text links for the quiet ones.
- Never name a model or a lab you don't use. Components that print a third-party model name are left out.
Choose by product and audience
- Developer tool or API: lead with agent-run, inline-diff or a terminal-like demo; mono labels and real code; pricing by usage (usage-ruler or credit-tier-pricing).
- Assistant or chat product: lead with cited-answer, ask-bar or thinking-mark; a paper palette reads warmer than black.
- Research lab or model company: a typographic hero and long-form writing; numbers and charts (scrub-sparkline-stats, model-bench) over feature grids.
- Enterprise buyers: put security, data handling and SSO in the FAQ and footer, and keep pricing honest (subtractive-pricing shows exactly what each plan leaves out).
Curation: one of each, on purpose
- One hero treatment: a background or a typographic hero, never both competing.
- One navigation system for the whole site, and one primary button style repeated everywhere.
- One AI interaction component on the home page; others belong on product pages.
- Check every component's fixed text: a demo that names a model, a lab or a customer you don't have is a claim you're making.
- If two components are both 'the impressive one', cut one. Restraint is what makes the remaining one feel expensive.
Backgrounds: where they help and where they hurt
- Ambient backgrounds belong behind the hero or the final call to action: moments with little text and one message.
- Never put moving backgrounds behind paragraphs, pricing, forms or tables. Reading and motion compete, and contrast becomes unpredictable.
- Check contrast at the background's brightest frame, and keep buttons off the brightest part. If body text drops below 4.5:1, move it or add a scrim; don't lighten the text.
- Avoid fatigue: one ambient surface per page, slow, low contrast. Every Vitrine background pauses offscreen and in hidden tabs.
- Reduced motion: every Vitrine background renders a designed still frame; check that it still looks intentional.
- Performance: WebGL and canvas backgrounds cost GPU time and battery. Load one per page and confirm with /performance-pass on a throttled phone.