Scope the build before the fantasy

A project becomes easier to estimate when its essential user task is clear. For a business website, that could mean a visitor can understand the service, inspect relevant work, and contact the business.

The scope should name the pages, integrations, content responsibilities, supported devices, and handoff. It should also identify what is outside the first release.

Animation needs a business job. The homepage keeps its cinematic flight, but the identity, positioning, and next actions remain readable before the sequence loads and when motion is reduced.

A smaller release still needs complete behavior: useful content, clear errors, keyboard access, and an understandable next action. Reducing scope should reduce unfinished promises.