A website is not finished when every section exists. It is finished when the intended visitor can recognize themselves, understand the offer, trust the evidence, and complete the right next step.
Each stage has an output and an exit criterion. Do not advance because the artifacts look polished; advance when the evidence is sufficient for the next decision.
Identify the audience, situation, alternative, objection, desired action, and evidence they need.
Exit when: the team can name who the page is for, what they must understand, and which action matters.
Turn the decision into information hierarchy, proof sequence, routes, content requirements, and acceptance criteria.
Exit when: every planned section has a job and every claim has evidence or is removed.
Build the smallest path that proves the message, proof, interaction, and inquiry mechanism together.
Exit when: one visitor can move from first impression to a working next step without a placeholder.
Review the rendered journey at real sizes, speeds, input modes, and failure conditions.
Exit when: the intended visitor can explain the offer and complete the action across supported conditions.
Use behavior and conversations to improve the message without chasing superficial activity.
Repeat when: new evidence changes the audience, proposition, proof, or journey.
The vague request is “redesign the homepage.” Auteur turns it into a decision trace.
Visitors see several capabilities but cannot tell which engagement fits their situation.
Lead with one fixed direction offer and position custom delivery as a separate later path.
Ship the hero, problem signals, offer, evidence, qualification, and working booking path.
Ask unfamiliar people what is sold, for whom, for how much, and what happens next.
Test navigation, booking, responsive layout, accessibility, search metadata, and analytics.
Use qualified-call questions to improve the decision path—not add indiscriminate sections.
Result: not “a more modern site,” but a more understandable and credible route to one business decision.
Visual polish is one part of the quality bar, not a substitute for comprehension or reliability.
Move to the SaaS playbook when the main challenge is no longer only comprehension, but authenticated behavior across interface, service, and data.