How Revisions Work: Getting the Website You Actually Wanted

If you build websites for clients, you know the moment. The first design goes out, and the reply comes back with a list of changes. Some are small. Some quietly rewrite the scope. How you handle that list decides whether the project stays on track or drags on for weeks. This post is written for the business owners on the other side of that list. If you are the developer, share it with your client before the first design review, because most revision pain comes from mismatched expectations, not bad design.

What Are Website Revisions?

Website revisions are the changes you request after seeing a first version of your site. You might ask for a different headline, a warmer colour, a bigger photo, or a button moved to a place customers will actually notice. Each of those is a revision.

The point is simple. A website is built from your description of your business, and no description survives first contact with a real screen unchanged. Revisions close the gap between what you imagined and what the designer built. They also protect you. Without them, you would have to accept the first draft or start over, and neither is a fair deal.

Revisions also work both ways. A good agency will push back sometimes, and that is worth listening to. If a change would slow the site down, confuse visitors, or hide your phone number behind three clicks, the agency should say so and suggest a better option. That is part of what you are paying for.

How the Website Revision Process Normally Works

Most agencies run revisions the same way, in four steps. Knowing the steps in advance takes most of the stress out of the process.

Step 1: The agency shares the first design

You receive a preview of your homepage, or sometimes one or two key pages first. At aimEncoders we usually share the homepage design before building the rest of the site, because it sets the look for everything else. Take your time with it. Open it on your phone as well as your computer, since most of your customers will visit on a phone.

Step 2: You review it and collect your feedback

Go through the design page by page and write down everything you want changed. Do it in one sitting if you can, and keep the list in one place. A shared document or a single email works well. Sending one message today, a voice note tomorrow, and three more messages next week is how changes get lost.

Step 3: The agency makes the agreed changes

The agency groups your feedback, checks what fits inside the agreed scope, and applies the changes. If something you asked for is actually a new feature rather than a revision, this is the moment the agency should flag it and give you a separate estimate, before doing the work. No surprises later.

Step 4: You review the updated version and approve it

You look at the revised design. If it is right, you approve it and the project moves to the next stage. If a few things still need adjusting, they go into the next round. Each round is one collected set of feedback, not one comment at a time.

What Counts as a Revision, and What Counts as a New Request?

This is where most misunderstandings start. A revision changes or improves something that already exists in the agreed design. A new request adds something that was never part of the plan. Both are fine. They are just priced and scheduled differently, so it helps to know which is which.

Normal revisions include:

• Changing a colour, a font, or the spacing between sections
• Replacing a photo or a banner image with a better one
• Moving a button, a phone number, or a WhatsApp link to a more visible spot
• Rewriting a headline or correcting text on a page
• Making a section bigger, smaller, or easier to scan

New requests include:

• Adding pages that were not in the original plan
• Building an online booking system or a customer login area
• Adding an online store or a payment gateway to a site that had none
• Creating a dashboard, a portal, or any feature that needs new development

A dental clinic in Lahore gives a clear example. Asking the agency to make the appointment button bigger and to add the dentists' photos is a revision. Asking for a full booking system with time slots and automatic reminders is a new feature. The first takes an afternoon. The second takes a week of building and testing, and it should be quoted on its own.

The rule of thumb is short. If your request changes something that is already there, it is probably a revision. If it adds something new that has to be built, it is probably additional work.

How to Give Feedback Your Agency Can Actually Use

You do not need design words to give good feedback. You need to be specific. "I do not like the homepage" leaves the designer guessing. "The banner feels crowded, can we use one photo and make the heading easier to read" gives the designer a job to do.

Four habits make feedback much more useful.

Be specific about the problem. Point at the section, the line, or the button. "The services section feels long, can we cut it to four boxes" is clear. "Something feels off" is not.

Show, do not just tell. A screenshot with a circle drawn around the problem works wonders. If you saw a layout you liked on another website, share the link and say which part you liked. You are not asking the agency to copy it. You are showing them the direction.

Explain the business reason. A textile exporter in Faisalabad once told us his buyers abroad kept missing his export page, so we moved it to the top menu and put his WhatsApp number in the header. That one sentence told us what to change and why it mattered. Your reason helps the agency solve the real problem instead of just moving pixels around.

Send it all at once. One list, one document, one email. When feedback arrives in drips, the agency starts work, stops, restarts, and something always slips through. A single collected list also makes it obvious what counts as one revision round.

How Many Revision Rounds Are Reasonable?

There is no single number that fits every project. Many agencies include two or three design revision rounds in a standard package for a small business website, and larger projects often include more. The honest answer is that it depends on the size of the site and what was agreed before work started.

What matters more than the number is what a round means. One round should mean one collected set of feedback, reviewed and applied together. It should not mean one comment equals one round.

Ask these questions before you sign anything:

• How many revision rounds are included in the price?
• Do the rounds cover design only, or development too?
• What happens if I need changes after I approve a page?
• Are changes after launch charged separately?
• How long does each round usually take?

Get the answers in writing, in the quote or the agreement. A clear revision policy protects you and it protects the agency. It stops a small project from dragging on for months, and it stops you from paying for changes you thought were included.

What If You Still Do Not Like the Design?

Sometimes you go through two rounds and the site still does not feel right. The colours are fine, the layout is tidy, and everything you asked for got done, yet something is missing. Do not ignore that feeling. Step back and find the actual problem before asking for more changes.

Start by naming what is wrong in plain words. Is the site too crowded? Does it look old fashioned? Can visitors find your menu, your prices, or your location quickly enough? A restaurant owner in Karachi once told us his site looked good but customers could not find the menu or the ordering button. The fix was not a new design. It was moving the menu and the order button to the top of the homepage, where hungry visitors look first.

Then go back to your original goals. What did you want the website to do when you first talked to the agency? Bring in more walk-in customers, take orders, show your work, win export enquiries? If the design does not serve that goal, say so. That conversation is more useful than ten small tweaks.

If you are still stuck, ask for a short call. Ten minutes of talking often solves what five rounds of written feedback cannot. A good agency will explain why the design looks the way it does, listen to what bothers you, and suggest a way forward. If the fix sits inside the agreed scope, it gets done. If it means a new direction or new features, you should get a clear estimate first, and then you decide.

How aimEncoders Runs Revisions

At aimEncoders we keep revisions simple, because a confused client cannot give good feedback and a confused agency cannot build a good site.

We start with a short discovery call, so we understand your business, your customers, and what the website has to do before anyone opens a design tool. Then we share the homepage design first, and we wait for your collected feedback in one document. We group your notes, apply them, and share the updated version for your approval. Design rounds and development rounds are agreed up front, in writing, so nobody has to guess.

We also test every revised page the way we test everything else: on a real phone, on a slow connection, and through our QA checklist before it goes live. A change that looks good on a designer's screen and breaks on a customer's phone is not a finished revision.

If you are planning a website, or you are stuck in revision rounds with an agency right now, talk to a team that will explain the process before you pay for it. Our custom web applications and business websites are built the same way, with the revision process agreed before the work starts, so you always know where you stand.

A Note for Developers

If you are the one receiving the feedback, a few habits keep revision rounds short. Agree the number of rounds in writing before you start, and say clearly whether they cover design, development, or both. Ask for feedback in one collected document, not a stream of chat messages. Share a staging link the client can open on their phone, because half of all revision notes come from something that only looks wrong on mobile. When a request is really a new feature, say so early and quote it separately instead of absorbing it and resenting it later. And keep a short changelog of what changed in each round, so nobody argues about what was already approved. Clients who understand the process give better feedback, and better feedback means fewer rounds.

Frequently Asked Questions

Are website revisions included in the development cost?

It depends on the agency and the agreement. Most agencies include a set number of revision rounds in the quoted price. Extra rounds, or changes requested after final approval, are often charged separately. Ask before the project starts.

Can I request changes after my website is launched?

Yes. Post-launch changes are normal, but they usually fall under a maintenance agreement or a separate small job, rather than the original build. Small text and photo updates are quick. New features take longer and need their own estimate.

What happens if I do not approve the first design?

Share specific feedback and the agency will revise it within the agreed process. You are not expected to approve a design you do not like. The first version is a starting point, not a final answer.

Do website revisions affect the launch date?

They can. Large changes, late feedback, and extra requests all push the launch back. The best way to stay on schedule is to send your feedback in one collected list and reply within the time you agreed with the agency.

Can I ask for unlimited website revisions?

Some agencies offer flexible arrangements, but unlimited revisions are not standard. Confirm the number of rounds in writing before work begins, so both sides know what to expect.

About the author: Muhammad Asad Ullah is the founder of aimEncoders, a web development agency in Faisalabad, Pakistan. He leads a team that builds custom websites, web applications, and ecommerce stores for small businesses, and every site they ship goes through a full QA and testing process before launch. The team also writes about the practical side of hiring a web agency, so business owners know what to expect before they spend a rupee.