<?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: ztrx</title>
    <description>The latest articles on DEV Community by ztrx (@ztrx_febb1a49041b23a5125a).</description>
    <link>https://dev.to/ztrx_febb1a49041b23a5125a</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%2F3864578%2Fe0f6b9ba-d005-4e17-825c-cc91088f6881.jpg</url>
      <title>DEV Community: ztrx</title>
      <link>https://dev.to/ztrx_febb1a49041b23a5125a</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ztrx_febb1a49041b23a5125a"/>
    <language>en</language>
    <item>
      <title>The follow-up email that gets a reply (and the three that do not)</title>
      <dc:creator>ztrx</dc:creator>
      <pubDate>Sat, 14 Nov 2026 16:10:21 +0000</pubDate>
      <link>https://dev.to/ztrx_febb1a49041b23a5125a/the-follow-up-email-that-gets-a-reply-and-the-three-that-do-not-2j20</link>
      <guid>https://dev.to/ztrx_febb1a49041b23a5125a/the-follow-up-email-that-gets-a-reply-and-the-three-that-do-not-2j20</guid>
      <description>&lt;p&gt;Most follow-ups fail for one reason: they give the reader nothing new to respond to.&lt;/p&gt;

&lt;p&gt;"Just following up on my last email" asks the client to remember the original message, open it again, re-decide, and then write something back. That is a lot of work for someone who has already decided to put it off.&lt;/p&gt;

&lt;p&gt;The follow-ups that work are shorter, not longer. One new piece of information. One decision.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three that do not work
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;"Just checking in."&lt;/strong&gt; No ask, no date, no reason. It is a reminder that you exist, which the client already knows.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;"Bumping this to the top of your inbox."&lt;/strong&gt; Reads as guilt. People do not reply to guilt, they file it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The full recap.&lt;/strong&gt; Five paragraphs summarising a thread they can already read. You are asking them to re-read the project before answering a two-line question.&lt;/p&gt;

&lt;h2&gt;
  
  
  The one that works
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;Hi Sam,&lt;/p&gt;

&lt;p&gt;The quote for the landing page is still open until Friday. If you want it, reply "yes" and I will book the slot. If the timing is wrong, tell me and I will close the file for now.&lt;/p&gt;

&lt;p&gt;Either way, you will hear from me on Friday.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Why it works:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;One decision, not a summary.&lt;/li&gt;
&lt;li&gt;A date, so silence has a consequence.&lt;/li&gt;
&lt;li&gt;An easy exit. Most people can send "not now". Far fewer can send "we are not proceeding".&lt;/li&gt;
&lt;li&gt;It does not pretend to be urgent when it is not.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Three situations, three templates
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;After a proposal goes quiet&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Hi Sam, the proposal is still on the table until the 28th. If the budget is the issue, I can split it into two phases. If the timing is wrong, say so and I will close it out.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;After a client goes silent mid-project&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Hi Sam, the next milestone is ready to start on Monday. I need the copy from you by Thursday to keep that date. If it slips, the new date is the following Wednesday.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;After an invoice is late&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Hi Sam, invoice 0142 is now 14 days past due. The contract adds 5% a month after 30 days. I would rather not charge it, so if something is wrong with the invoice, tell me today and I will fix it.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  When to stop
&lt;/h2&gt;

&lt;p&gt;Five working days after a dated follow-up is enough. If there is no reply, close the loop in your own head and move on. One more email after that is fine if you have something new to say. A sixth "just checking in" is not.&lt;/p&gt;

&lt;p&gt;The uncomfortable part is that silence is usually an answer. The follow-up exists to make it cheap for the client to say that answer out loud, so you stop paying rent on the thread in your head.&lt;/p&gt;




&lt;p&gt;I built a small board that shows which client threads are waiting on me and which are waiting on them, because remembering was the harder half of this. It is called Zappd and it is linked in my profile. The templates above are the part that matters.&lt;/p&gt;

</description>
      <category>email</category>
      <category>freelance</category>
      <category>productivity</category>
    </item>
    <item>
      <title>The client follow-up cadence that actually gets replies</title>
      <dc:creator>ztrx</dc:creator>
      <pubDate>Sat, 14 Nov 2026 10:35:45 +0000</pubDate>
      <link>https://dev.to/ztrx_febb1a49041b23a5125a/the-client-follow-up-cadence-that-actually-gets-replies-2icd</link>
      <guid>https://dev.to/ztrx_febb1a49041b23a5125a/the-client-follow-up-cadence-that-actually-gets-replies-2icd</guid>
      <description>&lt;p&gt;You sent the proposal. Then silence.&lt;/p&gt;

&lt;p&gt;Most freelancers do one of two things: nothing, or a long "just checking in" that reads as anxiety. Both lose the deal. The problem is rarely the wording. It is that nothing tells you &lt;em&gt;when&lt;/em&gt;, so every follow-up becomes a decision you make in the moment, and decisions made in the moment get deferred.&lt;/p&gt;

&lt;p&gt;Here is the version that survives contact with a real client list.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three touches, fixed dates
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Touch&lt;/th&gt;
&lt;th&gt;When&lt;/th&gt;
&lt;th&gt;What it does&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Day 3&lt;/td&gt;
&lt;td&gt;Confirms the proposal arrived. One question, no new pitch.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Day 7&lt;/td&gt;
&lt;td&gt;Restates their outcome and offers a decision: proceed or park it.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;Day 14&lt;/td&gt;
&lt;td&gt;Closes the loop, and leaves a two-line way back in.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The second one is the only one that matters. The first is politeness, the third is housekeeping. Day 7 is where a quiet client either becomes a project or becomes a "not now", and both are better than silence.&lt;/p&gt;

&lt;h2&gt;
  
  
  The wording
&lt;/h2&gt;

&lt;p&gt;Day 3:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Just checking this landed. Is anything unclear on the scope?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Day 7:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;You mentioned the launch is in March. If we start by the 20th we still make it, after that it gets tight. Want me to hold the slot?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Day 14:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;I will close the file for now. If it comes back, a two-line reply is enough to restart.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Three rules make those work:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;One question per message. Two questions get neither answered.&lt;/li&gt;
&lt;li&gt;Never re-send the proposal. Restate one sentence and ask for a decision.&lt;/li&gt;
&lt;li&gt;Give them a graceful exit. It produces more replies than pressure, because it removes the cost of saying "not now".&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Why the spreadsheet dies
&lt;/h2&gt;

&lt;p&gt;A sheet can hold the dates. It cannot tell you to look. Every tracker I have built by hand failed the same way: it went stale in week three, not because I was disorganised, but because nothing triggered a look.&lt;/p&gt;

&lt;p&gt;What made it stick was moving the three dates from a status column into actual calendar dates, one row per client conversation, and checking it once in the morning before opening email. A status of "waiting" is a feeling. A date is a decision.&lt;/p&gt;

&lt;h2&gt;
  
  
  The uncomfortable part
&lt;/h2&gt;

&lt;p&gt;You will still lose some of them. A fixed cadence does not create demand. What it does is make sure the loss is a decision rather than an accident, and it takes the emotional weight out of the second message, which is the one people avoid sending.&lt;/p&gt;




&lt;p&gt;If you want the cadence applied to your own Gmail history, that is what I am building at &lt;a href="https://followup-tracker-frontend.faresbeddou0.workers.dev" rel="noopener noreferrer"&gt;Zappd&lt;/a&gt;. It reads the last 90 days and shows which client conversations have gone quiet. Free while in early access.&lt;/p&gt;

</description>
      <category>productivity</category>
    </item>
  </channel>
</rss>
