For a freelancer, the client update is part of the work, not an extra. Yet it is often the part that gets pushed to the end of the day, because opening a formal email composer feels like changing hats. This article sketches an illustrative workflow for writing those updates the way you already think about them: as a conversation.
A note before we begin: what follows is an illustration of how the MailCircle preview could fit a freelancer's day. It is not a case study, and the people in it are imagined.
The situation: progress is easy to describe, hard to send
Imagine a freelance illustrator working on a set of book-cover options for a small publisher. By late afternoon she has three rough sketches ready, one question about the colour palette and a note that the final files will need two more days.
If the publisher's editor were a friend on chat, she would type it out in a minute. But the editor prefers email, because the updates get forwarded to the author and kept with the project records.
So the update waits. It waits while she finishes one more sketch, while she thinks of a better subject line, while she wonders whether "Hi" is too casual for a publisher. By the time she writes it, the editor has already asked, "Any news on the covers?"
The tension: switching modes costs more than the message
Freelancers tend to work in short, focused stretches. A client update sits awkwardly between them. A conventional email composer asks you to stop, open a blank window, rebuild the context of the project from memory, and then present it formally.
The update itself might be four lines. The pause before it is the expensive part. Multiply that by several clients a week and the pause becomes a habit of delay, and delay is what clients notice.
The insight: keep each client as a conversation
Most freelancers already hold each client in their head as an ongoing conversation: what was agreed, what was sent, what is pending. The formal composer breaks that mental model into separate, disconnected emails.
A chat-style view keeps it intact. Each client becomes a place you return to, with the thread of the project visible, and each update becomes the next turn in that conversation rather than a fresh document.
An illustrative workflow in the MailCircle preview
1. Give each client a conversation
The preview has a chat-style layout with channels, groups and direct-message draft views. Our illustrator could use a direct-message draft view per client, or a group view for a client where she deals with both an editor and a designer. Threads and mentions views give side questions somewhere to sit. See the conversations preview.
2. Write the update the way you would say it
In the email draft composer she fills in the editor's address, Cc's the publisher's designer, and writes a plain subject line such as "Cover options: three sketches and one question". The body stays short and direct:
- Three rough options are ready for review.
- One question: should the palette stay close to the series' earlier covers, or can it move further?
- Final files expected in two working days after feedback.
That is a complete client update. It does not need three paragraphs of preamble.
3. Preview before saving
The composer's preview shows the email as the editor would read it. This is where she checks the recipient, the Cc and the subject. Then she saves the draft, which in the preview is stored in her browser's local storage.
4. Reuse the sentences you write every week
Freelancers repeat themselves more than they realise: "Sharing this week's progress below." "Received your feedback, revising now." "Please confirm so I can move to final files." The preview's local quick replies hold this kind of reusable wording, so the next update starts from words she has already got right.
5. Find the draft later
Draft list and conversation views, filtered by mine, unassigned or all, let her see which updates are drafted and waiting. For a solo freelancer, "mine" is likely the only filter that matters. More on these views on the email drafts preview.
Where the illustration stops: the edge of today
This is the honest part, and for a freelancer it matters a great deal. In the current preview:
- Send is disabled. The draft does not go to the editor from MailCircle.
- No mailbox connection. The preview does not connect to Gmail, Outlook or any other mailbox.
- No attachments. The sketches themselves could not be attached in the preview.
- Replies do not return. If the editor answered the palette question, that answer would not appear in the chat view.
- Drafts are browser-local. They are not synced, backed up or available on another device. A freelancer who works from a laptop at home and a different machine at a co-working space would not see the same drafts.
- No AI writing. The preview does not write or rewrite your update for you. The words are yours.
In short: the draft is real. The delivery is not connected.
What a freelancer should take from the preview
The preview is useful for one specific question: does writing client updates in a conversation view feel lighter for you? If you try the flow with an imaginary client and find yourself writing the update in a minute instead of putting it off, that tells you something about how you work.
It also helps you list what you would need before trusting any tool with real client email. For most freelancers that list includes sending from their own address, attachments, replies landing in the same conversation, and drafts available on every device they use. Write that list down. It is the most useful thing to bring to a conversation with us, or with any vendor.
The freelancers page covers the fit in more detail, and the evaluation page explains how to test a preview without real client data.
