Three weeks of research saved significantly more than three weeks in rework — every revision during prototyping was rooted in a specific finding, which made changes fast and defensible rather than slow and contested. Building the CMS schema before designing dynamic pages prevented the costly retrofit most Framer projects encounter, because any content type that will change post-launch belongs in the CMS from the first design conversation, not added once static pages are already built. Salifact's visual distinctiveness comes from what it does not do: one typeface family, one hue, a strict spacing scale, with the consistent temptation to introduce variety resisted at every decision point — restraint is what makes the outcome feel considered rather than assembled. Starting every layout at 375px forced content prioritisation at the design stage rather than the build stage, turning the mobile constraint into a content editing tool that produced a cleaner desktop design as a consequence. And launching core pages before paid acquisition began created a window to find and fix conversion problems before budget was committed — a phased sequence that saved a material amount of wasted spend in the first campaign cycle.