Garrett Adams

I've been dealing with a post-launch headache lately where a client approves the final build but then keeps dropping "quick 10-minute edits" into my inbox every couple of days.

At first saying no feels like overkill for a tiny fix but after a month those quick edits eat up hours of unbilled time. I'm trying to figure out the best way to handle this without ruining the relationship.

Do you usually set a hard limit on post delivery fixes in your initial agreement or do you transition them to a paid monthly maintenance setup once the main work is wrapped up?

It's super when customers quietly slip away and you have no idea why because everything looks fine on paper. Users hate filling out long feedback forms so they won't email support just to say a button layout is annoying they'll just quietly switch to something else. Hopping on quick user calls or looking at session replays always shows the tiny blind spots you completely missed.

What is your go to method for spotting those silent usability issues before people churn?

There's a big difference between a weakness that actively breaks your business and one that just makes you uncomfortable.

If your writing is terrible, that hurts your sales copy so you have to improve it enough to get by. But trying to turn a C-grade skill into an A-grade skill usually takes way too much effort for a tiny payout. I've had much better results doubling down on my core strengths while keeping my weaknesses just non fatal.

Where do you draw the line between a flaw you need to fix and one you can safely live with?