SaaS Website Prompts from Marketing to Product UI
A SaaS brief should connect the marketing promise to the first useful action inside the product. Keep the public website, authenticated workspace and billing boundaries explicit so the builder does not confuse a prototype with a working service.
UI Discovery editorial · Updated
How to use this guide
Define the first useful outcome
For a collaboration app, success might be creating a collection and adding one reference. Build that path before adding a sprawling settings area. Describe which details are required now and which can wait; every onboarding field should support a visible next step.
Specify workspace and permission states
An owner, member and invited visitor may see different actions. In a prototype, label those roles as simulated and do not represent a hidden button as authorization. A production app needs server-side access checks and real data boundaries outside the visual brief.
Connect plan copy to actual behavior
Show billing periods, relevant limits and the result of choosing a plan. Keep illustrative pricing visibly marked. Do not introduce live checkout, subscriptions or email invitations until their behavior and authorization are part of a separate implementation task.
Original prompt to adapt
An editorial starting brief, not a benchmarked model output. Replace fictional content and review the result before publishing.
Prototype a fictional SaaS app for shared design-reference collections. Include a public overview, a labelled sample pricing section and a workspace demo. The first useful path is: create a collection, add a URL and a note, then see it in the collection. Reuse the project's app shell and forms. Provide first-use, populated, validation-error and simulated read-only-member states. State clearly that demo data is local and roles are simulated, not real authorization. Do not add authentication, live billing, email or a database. Keep marketing claims consistent with the demonstrated workflow. Include clear back navigation, keyboard focus and a usable 390px layout. Report which production integrations remain.
A focused follow-up
Walk through the first collection flow without prefilled data. Remove any required field that does not support that task, then check that the read-only demo cannot edit items.
Review checklist
- Marketing promises correspond to a visible product workflow.
- Simulated roles and local-only storage are disclosed.
- Pricing and trial language do not imply a working payment integration.
Continue with real references
- SaaS website references →
Compare product positioning and page structure.
- SaaS dashboard guide →
Continue into navigation and workspace behavior.
Common questions
Can I use this prompt unchanged?
Use it as a starting brief. Replace fictional content, inspect the reference links and adapt constraints to your project. These are original editorial prompts, not benchmarked model outputs.
What should I check before publishing?
Marketing promises correspond to a visible product workflow. Simulated roles and local-only storage are disclosed. Pricing and trial language do not imply a working payment integration.