Development criteria
It turns the relationships and states of workspaces, tasks, and members, key user flows, recovery paths, and completion conditions into an implementable specification.
SAAS PROMPTS
B2B SaaS website prompts
How should a B2B SaaS site be designed? Model the relationships and states of workspaces, tasks, and members first, then treat information density and repeat-task speed as a primary risk. Each service guide below combines an implementation specification with design standards.
- Primary goal
- team workflows and subscription tools
- Core entities
- workspaces, tasks, and members
- Design risk
- information density and repeat-task speed
10 REAL SERVICES
B2B SaaS · 10 real services
Development prompts and DESIGN.MD for 10 real services designed around team workflows and subscription tools.
ANSWER GUIDE
B2B SaaS How to choose a prompt
Choose the service whose core screen and repeated behavior most closely match the product you are building. Apply only information priority and state design, never the reference brand assets.
Design criteria
Start from A dashboard interface for B2B SaaS, centered on workspaces, tasks, and members, with a [reference] brand impression led by [color], while avoiding the original logo, proprietary copy, images, and pixel-level layout.
Risk to validate
Treat information density and repeat-task speed as a primary design risk and define loading, empty, error, partial-data, and success states.