The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
"The website is 99% done.", These are the most expensive words in web development.
The Problem:
You finish the build and send the staging link to the client. They reply saying they love it! But then comes the email with 45 bullet points of "minor tweaks." You spend a day fixing them. Three days later, another email arrives with 20 more tweaks.
Suddenly, a 4-week project drags into its third month. Your effective hourly rate drops to pennies, your other projects get delayed, and you start dreading every time the client's name pops up in your inbox.
The Solution:
The issue usually isn't a bad client; it's a lack of a structured feedback process. If you leave the door open for endless, unstructured revisions, they will walk through it.
Here is the 3-step framework I use to handle client feedback and ensure projects actually launch on time:
The "Two-Round" Rule:
I state this clearly in the proposal and the kickoff call: "This project includes two consolidated rounds of revisions." If they want a third round, it requires a separate hourly billing agreement. This immediately stops the client from sending you single-sentence change requests every time they have a random thought in the shower.
Ban Email and WhatsApp Feedback:
Never accept design feedback via scattered text messages or a chaotic 30-reply email thread. I require all feedback to be put into a single, shared document (or a visual feedback tool). If it is not in the official document, it does not get fixed.
The "UI Freeze" Checkpoint:
Before I start writing heavy backend logic or connecting the database, I require a hard sign-off on the frontend design. I make it clear: "Once this is approved, any structural layout changes will require a change order and additional budget."
You are the professional. You have to dictate the process, or the process will dictate you.
How do you handle client revisions? Do you put a strict cap on them, or do you just ride out the endless tweak requests? Let's discuss in the comments! 👇
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
What should come first: the price or the value?
Version 1 presents the price immediately, making the offer transparent and easy to evaluate at a glance.
Version 2 introduces the program and its benefits first, giving users more context before revealing the investment.
One supports clarity and faster decision-making. The other builds interest before asking users to consider the price.
Which approach would make you more likely to explore the offer: seeing the price first or understanding the value first?
27 voted
47%
30 voted
53%
57 votes
Closed
My gut says value first, mostly because $497 cold with zero context reads like a paywall. Have you actually run this as a live A/B on real traffic, or is it more of a design gut-check for now?
NOMAD TRAILS — Travel & Tours Website
A modern travel website designed and developed by Usman DevHub.
Project Highlights:
✓ Modern UI Design
✓ Responsive Website Development
✓ Destination Showcase
✓ Smooth Booking Experience
Role:
Web Developer & UI/UX Designer
Have a website project in mind?
Feel free to reach out and let's discuss your requirements.
Built by Usman DevHub.
The design for a language app with 100K+ users has been in the dev team's hands for weeks.
They haven't messaged me once to ask what something should be.
That's the point of a proper handoff. Every version of every screen already drawn, including the ones nobody wants to think about. Every color and spacing tied to a rule the whole product runs on. Naming that matches what the engineers already use.
If a dev has to ask what a value should be, the file wasn't ready.
"If a dev has to ask what a value should be, the file wasn't ready" should be taped above every designer's monitor. Has a dev team ever pushed back on that level of rigor, or do they just quietly appreciate never having to ask?