How Website Design Feedback Rounds Work
- Category:
- Process
- Updated:
- Oct 12, 2026
Will changes cost extra, how many revision rounds you get, and when you see real work. Here is how feedback, approvals and milestones work on a website project.
Artyum Grebenyuk Founder, AGR Studio How website design feedback rounds work is something every founder should understand before signing, because it decides whether a project feels collaborative or turns into a fight about change requests. The questions we hear most are simple: will changes cost extra, how many revision rounds do we get, and when do we see something real? Here is how feedback, approvals and milestones work on our projects.
Milestones tied to approvals
We split every project into a few milestones, and each payment is tied to an approval:
- Kickoff. A deposit starts the project. We map what you have, collect references and set the direction.
- Homepage. Around a week and a half in, you get your homepage as a real build in the browser. This is the biggest feedback round of the project.
- Remaining pages. The approved direction is applied to every other page, shared as each one is ready.
- Launch and handover. Final QA, the domain switch and a recorded walkthrough for your team.
This structure protects both sides. You never pay for pages built on a direction you have not approved, and we never build a whole site only to hear that everything needs to change.
Why the homepage carries the main feedback round
The homepage holds most of the components the rest of the site will reuse: navigation, section layouts, type styles, buttons and cards. Getting it right first makes every later page faster and keeps feedback on inner pages small.
We share it as a live preview link from the start, so you review it on your own phone and laptop. Static mockups hide motion and mobile issues, and those are exactly the details that cause late surprises. An early check on overall visual direction does not count against your revision rounds.
How revision rounds work
- Two consolidated rounds per milestone is typical. One feedback list per round, collected from your whole team, keeps reviews fast and avoids contradictory notes.
- Changes are expected. Adjusting a color or a type size after seeing the real homepage is normal, and the milestones are built to absorb it. We do not cut you off mid-process.
- Global changes are cheap. Because styles are systemized, making every button smaller or every heading tighter is a single change across the whole site.
- Live reviews are faster. For bigger changes, we often walk through the staging link together on a call and adjust in real time.
How we respond to feedback
Every point gets an answer. We reply inline and mark each item as done, already implemented, or not recommended, always with the reason. Where a change would hurt the result, such as breaking the type scale or making text harder to read, we say so and suggest an alternative.
The same goes for mockups made by stakeholders, including AI-generated ones. We treat them as visual guides and adapt them to the component system, so the site stays consistent.
FAQ
Will changes during design cost extra?
Changes within the agreed scope are part of the milestones. Anything new, such as an extra page type or integration, is quoted separately before work starts on it.
Can we see a design before we commit?
When it helps, we share an early concept direction after the first call. The full homepage is the first milestone, so a modest deposit is the only commitment before you see real work.
What slows feedback down the most?
Scattered notes from many people and slow channels. One consolidated list per round and a shared chat channel keep projects on schedule.
Blog
