<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: xiaoxin</title>
    <description>The latest articles on DEV Community by xiaoxin (@xiaoxin0103).</description>
    <link>https://dev.to/xiaoxin0103</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4031676%2Febbda2f9-efe9-4004-a54d-b3f5aca8ae74.png</url>
      <title>DEV Community: xiaoxin</title>
      <link>https://dev.to/xiaoxin0103</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/xiaoxin0103"/>
    <language>en</language>
    <item>
      <title>How I stopped losing money on client revisions — a system that works for any freelance project</title>
      <dc:creator>xiaoxin</dc:creator>
      <pubDate>Thu, 16 Jul 2026 08:16:57 +0000</pubDate>
      <link>https://dev.to/xiaoxin0103/how-i-stopped-losing-money-on-client-revisions-a-system-that-works-for-any-freelance-project-4m48</link>
      <guid>https://dev.to/xiaoxin0103/how-i-stopped-losing-money-on-client-revisions-a-system-that-works-for-any-freelance-project-4m48</guid>
      <description>&lt;p&gt;I'm a freelancer. Last year I sat down and actually calculated how much time I'd spent on revision rounds beyond what I'd originally scoped. The number made me sick — roughly $8,000 in unbilled hours across a dozen fixed-price projects.&lt;/p&gt;

&lt;p&gt;The worst part? Most of the extra rounds weren't even meaningful changes. They were:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"Can we try a different font?" → switched back to the original&lt;/li&gt;
&lt;li&gt;"The CEO wants to see a blue version" → CEO never looked at it&lt;/li&gt;
&lt;li&gt;11 separate emails over 4 days instead of one organized batch&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I built a system to stop this. Here it is — every step is free to implement.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: State revision limits in the proposal, not the contract
&lt;/h2&gt;

&lt;p&gt;Don't bury this in legal text. In my proposal email I literally write:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"This project includes 3 rounds of revisions. Each round = one consolidated batch of feedback from your team. Additional rounds: $X each."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Clients skim contracts. They read proposals. Put the limit where they'll actually see it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Acknowledge the round number every single time
&lt;/h2&gt;

&lt;p&gt;Client sends changes? My reply template:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Received — incorporating these as revision round 2 of 3. One round remaining after this."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This does three things: reminds them the counter exists, incentivizes consolidated feedback, and eliminates the "I didn't know" conversation later.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Give options, not ultimatums
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Bad:&lt;/strong&gt; "You've used all your revisions. Pay me."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Good:&lt;/strong&gt; "We've completed the 3 included rounds. The current version is final-ready. If you'd like additional changes, I can do those at my hourly rate — or we can wrap here. Your call."&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Make the counter visible to both sides
&lt;/h2&gt;

&lt;p&gt;If you track revisions in your head, the client doesn't feel the cost. When they see "2/3 rounds used" — whether on a shared doc or a tool — their behavior changes instantly. Feedback becomes focused because every round is finite.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this works
&lt;/h2&gt;

&lt;p&gt;Unlimited revisions feel free. A visible counter changes the psychology. Same reason buffets have more waste than à la carte.&lt;/p&gt;

&lt;h2&gt;
  
  
  Results after ~20 projects
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Average revision rounds: from ~5 to exactly 3&lt;/li&gt;
&lt;li&gt;Zero "can we just try one more thing?" after the final round&lt;/li&gt;
&lt;li&gt;I stopped dreading my inbox&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The tool I ended up building
&lt;/h2&gt;

&lt;p&gt;I eventually built &lt;a href="https://revision-desk.xiaoxinhq.com" rel="noopener noreferrer"&gt;Revision Desk&lt;/a&gt; to automate this — project pages with visible counters, client share links, file uploads, and a separate client revision log. 14-day free trial if you want to try it.&lt;/p&gt;

&lt;p&gt;But a shared Google Sheet works too. The system matters more than the software.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What's your revision policy? Drop it in the comments — I'm curious how other freelancers handle this.&lt;/strong&gt;&lt;br&gt;
freelance webdev design productivity tutorial&lt;/p&gt;

</description>
      <category>career</category>
      <category>freelance</category>
      <category>productivity</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
