Ask visitors what they want to accomplish before explaining the product. Their answer makes a broad platform personally relevant.
Examples studied: Pipedream, Lovable, v0, ReplitLast updated
The communication idea
Ask visitors what they want to accomplish before explaining the product. Their answer gives them a personal frame for understanding everything that follows.
People usually understand the job they need done better than they understand a broad product category or its architecture. Starting with that job makes a complex platform feel relevant before the visitor has learned its vocabulary.
The communication move: begin with the visitor's intended outcome, respond meaningfully to it, and use the rest of the page to prove that the product can support that job.
The page layout, section order, visual treatment, or component styling. Those remain implementation choices, and the selected Design Kit remains the visual source of truth.
Source evidence
These are dated observations, not endorsements or claims about conversion performance. Each example contributes a different part of the transferable idea.
Captured Pipedream opens with "What do you want to automate?", a large composer, and example jobs. The visitor starts with a recognizable task before learning how the platform works.
Captured Lovable asks for the app or website the visitor has in mind. The composer reads like the start of a conversation, not a request to study the product first.
Captured v0 asks "What do you want to create?" and follows the composer with example tasks and templates. Visitors can start from their own words or recognize a useful starting point.
Replit asks what the visitor wants to build and connects that request to examples of working applications.
What the examples share
All four products begin with something the visitor already understands: the workflow, application, site, or interface they want. Product machinery comes later, once that intent gives the explanation a useful frame.
Adapt it
The recipe is the communication decision. These are different ways an agent could express it after understanding the product and the selected Design Kit.
Ask one focused question in the first screen and respond with the most relevant product path or result.
Offer a few genuinely different example jobs for visitors who recognize their need but do not know how to phrase it.
Let visitors select the result they need, then adapt the explanation and demonstration to that choice.
Expose a safe, bounded version of the product's first action when it can return something meaningful without setup.
Implementation guidance
These are inputs, constraints, and observable checks. They are not a page sequence.
Use it with a Design Kit
The kit still controls the visual system. This handoff adds the communication idea and the condition that makes it honest.
Use the selected Design Kit as the visual and interaction source of truth. Introduce the product by asking what the visitor wants to accomplish, then adapt the explanation, examples, or product evidence to that job. Do not begin with platform architecture or a broad feature list. Use this idea only when the product can respond meaningfully to the visitor's answer.The vocabulary an agent can use to find this communication idea.