Sign inJoin Orvio
Join
Use case 02 · LaunchExample

Launch a product.

A small team ships an agent platform on Monday and has a weekend for the site. Sparvek supplies the pages and the system; the agent adapts them to the product, its pricing and its screenshots.

Use Sparvek Copy the prompt
Starting point
A product, a pricing table and a week of screenshots
Orvio product
SparvekWebsite · 0.1.0
Ran in
Codex
Access
CLI
Run
9 Nov 2026 · 47 min
Before and after
Drag to compare
Before · exampleAfter · Sparvek
The starting point

The brief and the product.

What the team asked for, and the Orvio product the agent worked from.

The briefExample client

We launch Tasklane on Monday: an assistant that triages a team's inbox. We need a home page, pricing and a page for each of the three agents. Every launch site we looked at is a purple gradient and a stock dashboard. Ours should look finished.

brief.md · from the founder, example
Keep
Hero, agent pages, approval run
Screens
Home, agents, pricing, docs
Stack
Static HTML, CSS and JS
Sparvek, a screen of the product
SparvekWebsite · technology0.1.0
Tokens
Volt and ink palette, type, spacing
Components
Hero, agent cards, pricing, approval run
Screens
Home, Agents, Pricing
In a member's words

“The previews sold me, but the source kept me. Every product feels art-directed, and getting it into a project takes minutes, not a weekend.”

Karim C.CTO, Promy
The prompt

Exactly what the agent was told.

Copy it, swap the highlighted parts for your product and folders, and run it in your own tool.

LaunchLaunch a product on a finished siteRan in Codex
Using Orvio, run orvio pull sparvek into ./launch, then read css/tokens.css and the Home, Agents and Pricing pages. Build the launch site for Tasklane: three agents (Inbox, Calendar, CRM), the plans in ./pricing.md and the screenshots in ./shots. Keep Sparvek's structure, type and the approval-run section; rename the agents and rewrite the copy so it describes our product and nothing else. Don't add pages Sparvek doesn't have. List what you changed when you're done.
Remote MCP or CLIHighlighted parts are yours to replace
The breakdown

Who did what.

What came from the product, what the agent built from it, and what still needed a person.

Orvio supplied

What Orvio supplied

  • A launch site: home, agents, pricing and docs
  • A complete token set, with the approval-run section
  • Hero, agent cards and pricing components
  • Light and dark themes, with hover and focus states
The agent built

What the agent built

  • Home page rewritten around the product's one promise
  • Three agent pages from the team's own notes
  • Pricing from the plans in the brief
  • Screenshots placed in Sparvek's device frames
A person did

What needed a manual touch

  • The headline, tightened by the founder
  • A changelog page Sparvek doesn't include
  • Open Graph images for the launch posts
  • A review on desktop and phone before Monday
Next steps

Do it on your app.

Use this product

Start from Sparvek

Preview every screen free, then pull the source with MCP or the CLI.

Open Sparvek Live preview
Copy the prompt

Run it on your own app

Swap the highlighted parts for your folders and screens.

Using Orvio, run orvio pull sparvek into ./launch, then read css/tokens.css and the Home, Agents and Pricing pages. Build the launch site for Tasklane: three agents…
Copy the promptPrompt library
Related use cases

Keep going.

01 · Client work

Build a client website

Start from a complete site and make it your client's: their words, their photos, their pages.

VoicelabsClaudeCodex
03 · Redesign

Redesign an existing interface

Give an inherited app a real design system without rewriting its logic.

CalyxClaudeCodex
05 · Your stack

Bring a design to your stack

Rebuild a product's pages as components in the framework you already use.

XfieldClaudeCodex
© Orvio · 2026