Create the journey shell
Build the shared page structure and navigation for the visitor flow.
Zero to MVP AI Bootcamp
Turn the blueprint into a public journey that a visitor can complete without explanation.
Today you ship
A responsive public prototype with a lead form, sample recommendation, and peer-tested journey.
Scroll to move through the presentation.
Build, test, checkpoint, and ship.
A good journey gives the visitor one clear decision at a time. Before coding, decide what they see when they begin, answer, wait, succeed, or encounter a problem.
The visitor opens the introduction, answers six questions, reviews the answers, submits, waits briefly, and sees one recommendation with a next action.
Apply the concept
Use this prompt
Turn this AI Lead Assistant journey into at most five screens. For each screen, list its purpose, visible information, primary action, and possible error state. Keep it suitable for a complete beginner.
Success looks like
A partner can follow the screen map from beginning to result without asking where to click next.
Watch for
A form is a conversation. Each question should be easy to understand, explain why it matters, and help the assistant produce a better recommendation.
Instead of asking 'Budget?', ask 'What budget have you set aside for this project?' and provide realistic ranges the visitor can choose.
Apply the concept
Use this prompt
Build one accessible lead-question component using the existing project styles. It needs a visible label, helpful example, required-field message, keyboard support, and no database connection. Show me the changed files when done.
Success looks like
All six questions are readable, usable with keyboard or touch, and clearly explain missing information.
Watch for
Before using real AI, prove that the result screen communicates value. A useful recommendation tells the visitor what fits, why it fits, and what to do next.
Recommended: Website Audit. Why: your site receives traffic but few inquiries. Next step: book a 30-minute review with the agency.
Apply the concept
Use this prompt
Create a responsive recommendation card using sample data. Show recommended service, two-sentence reason, confidence label, and next-step button. Include loading, unavailable-result, and retry states. Do not connect an AI service yet.
Success looks like
A visitor can explain the recommendation and next action after viewing the result for ten seconds.
Watch for
Usability testing is watching what people do, not asking whether they like the design. Silence reveals where the product fails to explain itself.
Ask a partner to find the best service for their business. Do not tell them where to start. Record every pause, wrong click, and question.
Apply the concept
Use this prompt
Here are my usability-test notes. Group them into blockers, confusion, and polish. Recommend only the single highest-impact fix and define how I should verify it.
Success looks like
The second tester completes the core journey with less hesitation and no help at the corrected point.
Watch for
Build brief
Build and publish the complete visitor-facing journey using realistic sample recommendations.
User story
As a potential customer, I can answer a few clear questions and receive a useful next-step recommendation.
Build the shared page structure and navigation for the visitor flow.
Implement the six questions with labels, examples, and required-field feedback.
Make the current step, remaining effort, and back action easy to understand.
Display the recommended service, explanation, confidence, and next action.
Add loading, empty, validation, error, retry, and reset experiences.
Open the public link on another device and fix the first observed blocker.