Describe the outcome, not just the technology.
Instead of “make me a SaaS app,” explain who it serves, what problem it solves, and the main action someone should be able to complete.
Give the interface a point of view.
Describe the mood, colours, typography, spacing, and examples you like. “Clean” is vague; “dark editorial layout, lime accents, generous spacing, and restrained motion” gives clearer direction.
Build the core flow first.
Start with the main user journey. Make that work before asking for dashboards, advanced settings, integrations, and every possible extra.
Ask for one change at a time.
Small, specific edits make it easier to understand what changed and catch unexpected side effects. Group related changes, not the entire product.
Use real content early.
Replace placeholder text with realistic names, prices, descriptions, and longer labels. This helps expose layout issues before launch.
Check mobile before calling it done.
Test navigation, forms, buttons, text wrapping, and page spacing on a narrow screen. A good desktop preview doesn't guarantee a good phone experience.
Review the parts users won't see.
Check permissions, error states, validation, loading states, data handling, and security. A polished interface is only one part of a dependable product.