Use the Prompt
Add Your Brief
Add your context below. It will be included with the prompt when you copy or download.
Create a responsive HTML website using the existing project stack for [PROJECT] and [AUDIENCE]. The task is: B2B Demo Request Page.
Required content and structure
Explain the demo scope, intended audience, required company details and expected follow-up.
Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.
Design direction
Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: paper white, deep navy and quiet pale-blue panels; precise grid and spacious typography. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.
Content preparation
Define who the demo is for, what it covers and which company details are genuinely required. Supply the actual follow-up process instead of inventing a response-time guarantee.
Layout and behavior
Explain the demo scope beside a concise form. Use progressive detail only where it helps route the request, and make optional fields visibly optional.
Task-specific acceptance check
- Minimize required fields and show validation without inventing sales response guarantees.
- Test validation without losing entered values, a failed submission and a visitor outside the target audience.
- Confirmation should describe the real next step without implying an appointment is booked.
Implementation and review
Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.
Reference attachment and reconstruction goal
Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.
Reference composition and content
Use the attached reference.webp as the visual reference for B2B Demo Request Page. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Explain the demo scope, intended audience, required company details and expected follow-up. Use the following task-specific layout guidance when translating the image into editable elements: Explain the demo scope beside a concise form. Use progressive detail only where it helps route the request, and make optional fields visibly optional.
Visual direction from the example brief
paper white, deep navy and quiet pale-blue panels; precise grid and spacious typography.
Interaction specification
The reference is a static concept: the behavior below is a requirement to implement, not proof that the picture already works. Copy the customized prompt into your working project. Start with the core task: Explain the demo scope, intended audience, required company details and expected follow-up. Minimize required fields and show validation without inventing sales response guarantees. For each visible control, specify its trigger, affected state and feedback; implement local changes with consistent state across related views. Give search and filters real results, selection controls an explicit active state, and save actions visible pending/success/failure feedback where relevant. Do not add unrelated workflows. Use proper links for navigation, buttons for actions and accessible names for icon controls. Do not imply a backend operation succeeded when only a local demo changed.
Visual comparison and delivery
- Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
- Then test the narrow layout without squeezing desktop text into tiny labels.
- Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.
Download Prompt + Image
Includes the complete prompt and full-size reference image. Attach both in OpenDesign to guide the layout.
How to Write a B2B Demo Request Page Design Prompt
Use this b2b demo request page design prompt to explain the demo scope, intended audience, required company details and expected follow-up.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Explain the Demo Before Asking for Company Data
A demo request form asks for effort before the visitor has seen the product.
Explaining the session's scope helps the right person decide to submit without requiring an excessive qualification form. Explain the demo scope beside a concise form. Use progressive detail only where it helps route the request, and make optional fields visibly optional.
From the Prompt
Explain the demo scope beside a concise form.
Make It Your Own
State [DEMO_SCOPE] and [INTENDED_AUDIENCE] above the form. Collect only [REQUIRED_FIELDS], mark optional context and explain the actual follow-up process beside submission.
Prepare the B2B Demo Request Page Content
The form asks for work email, company and team size, and displays an inline email error. Define required fields and validation copy before designing the submit state.
Define who the demo is for, what it covers and which company details are genuinely required. Supply the actual follow-up process instead of inventing a response-time guarantee.
From the Prompt
Explain the demo scope, intended audience, required company details and expected follow-up.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this b2b demo request page. Define who the demo is for, what it covers and which company details are genuinely required. Supply the actual follow-up process instead of inventing a response-time guarantee. Identify missing inputs before replacing them with demonstration content.
Preserve the Request After Validation
The lower strip explains the audience, expected session, required information and next step. Check that the real follow-up process matches this promise.
Submit incomplete company information and correct one field. Keep the other values and avoid promising a response time unsupported by the sales process. Test validation without losing entered values, a failed submission and a visitor outside the target audience. Confirmation should describe the real next step without implying an appointment is booked.
From the Prompt
Minimize required fields and show validation without inventing sales response guarantees.
Make It Your Own
Review the b2b demo request page against this requirement: Minimize required fields and show validation without inventing sales response guarantees. Test validation without losing entered values, a failed submission and a visitor outside the target audience. Confirmation should describe the real next step without implying an appointment is booked. Preserve approved content and revise only the parts that fail this check.
Review Your B2B Demo Request Page Result
Generated copy, routes and visual structure require review. Do not connect real forms, payments or external services without implementing and testing those flows.
- Test validation without losing entered values, a failed submission and a visitor outside the target audience. Confirmation should describe the real next step without implying an appointment is booked.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current b2b demo request page. Test validation without losing entered values, a failed submission and a visitor outside the target audience. Confirmation should describe the real next step without implying an appointment is booked. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
