You can answer a friend on chat in a few seconds. Yet the same two lines, when they have to go out as an email, somehow need a fresh cup of tea, a careful subject line and a second read before you dare to press anything. This article looks at why that happens, and why MailCircle is exploring a way to write emails like chat.
The situation: a message you already know how to say
Imagine a tailoring studio owner who needs to tell a customer that the blouse fitting has moved from Thursday evening to Saturday morning. She knows exactly what to say. On a chat app she would type it in one breath: fitting moved to Saturday, 11 am, same address, please bring the dupatta so we can check the length.
But this customer asked for confirmations on email. Perhaps she forwards them to family, perhaps she keeps a folder of every order. Either way, the message now has to become an email, and that is where the studio owner slows down.
Nothing about the information has changed. The date is the same, the address is the same, the request about the dupatta is the same. What has changed is the place she has to write it.
The tension: the composer asks for ceremony before content
A conventional email composer opens with empty boxes. Before she writes a word of the actual message, she is looking at:
- Recipient fields that need the right address, and a Cc line she has to decide about.
- A subject line, which for a two-line update feels like writing a headline for a postcard.
- A blank body with no conversation around it. The earlier back-and-forth about the fitting sits somewhere else, in another thread or another app.
- An unspoken expectation of formality. Greeting, paragraph, sign-off. Email feels like a record, and records feel like they deserve care.
None of this is wrong. Email is a durable, addressable record, and the fields exist for good reasons. The difficulty is the order of things: the frame arrives before the thought, and the frame is heavier than the thought.
The insight: the weight is in the frame, not the words
When people say a quick email feels heavier than a chat message, they rarely mean the words are harder. They mean the setting is different.
Chat is a conversation. You see what was said a moment ago, you reply in turn, and the reply only has to make sense next to the previous message. An email composer is closer to a fresh document. It asks you to rebuild the context from nothing, and then to dress it up.
That gap matters most to people who spend their working day in conversations: small-business owners answering enquiries between jobs, freelancers updating clients in between work, and customer-facing teams who think in terms of "who said what, and who is handling it". For them, switching into formal-composer mode is a small tax paid many times a day.
From the CEO's desk: the problem we are exploring
The question MailCircle starts from is deliberately narrow. It is not "replace email" and it is not "build another inbox". It is this: can people who already think in conversations write a proper email without first switching into a different way of writing?
That framing, set at the leadership level, keeps the product direction honest. Email stays email, with recipients, a subject and a body that the other person receives as normal. What is being explored is the writing surface: a familiar conversation view where the email is drafted, rather than a blank composer that stands apart from the conversation.
The decision: keep the email, change where you write it
MailCircle's positioning sums this up as "A familiar conversation. A proper email—our product direction." The working motto is shorter still: Start with a chat. See the email.
In practice, that means the conversation and the email are meant to stay close together. You should not have to leave the place where you think in order to produce the thing the recipient needs.
It also means being clear about what the email is at every moment. A draft is a draft. A sent message is a sent message. A chat-style interface must never blur those two, because a customer waiting on a fitting confirmation does not care how pleasant the writing felt if the message never left.
The mechanism: what the preview shows today
MailCircle is currently a concept and interface preview. The screens come from the Business OS source, so they still carry Business OS branding. Within that local preview, you can already explore:
- A chat-style layout with channels, groups and direct-message draft views, plus threads and mentions views. See the conversations preview.
- An email draft composer with to, cc, subject and body, and a preview of how the email reads. See the email drafts preview.
- Saving a draft to your browser's local storage, so it is still there when you come back on the same browser.
- Local quick replies, which hold wording you use again and again.
- Draft lists and inbox-style views filtered by mine, unassigned and all.
The full walk-through is on how it works, and the step-by-step version is in from chat draft to email preview.
The outcome: what changes, and what does not yet
What changes is the writing experience. The tailoring studio owner in our example could draft her Saturday fitting update in a conversation-style view, fill in the recipient and subject, and look at the email preview before saving it.
What does not change yet is delivery. In the current preview, Send is disabled. MailCircle does not connect to Gmail, Outlook or any mailbox. It does not deliver chat messages as email, and replies do not come back into the chat. Drafts live only in that browser and are not synced or backed up. There are no attachments and no AI writing or rewriting.
We call this line the edge of today: the boundary between what works now and what is still product direction. The draft is real. The delivery is not connected.
Who should care about this problem
If you recognise the pause before a simple email, you are the person this direction is for. That includes:
- Small-business owners sending quotation updates, appointment details and replies to repeated enquiries.
- Freelancers keeping clients updated without stopping work to compose something formal.
- Customer-facing teams who need to see who is handling a conversation and what has already been said.
The most useful thing you can do is tell us how your own email workflow runs today: where it slows down, which messages repeat, and what would have to be true before you trusted a chat-style tool with real customers.
