When customer chats felt riskier than the contract

Last winter, I was in Hangzhou building a website for a two-person consulting company. A client sent me ID photos and a contract draft over WeChat. I transferred them to my own computer, and the next week my colleague left. She exited the group chat, but the files stayed on her old phone. That was when I realized our problem wasn’t a lack of powerful tools. We simply hadn’t created a controlled path for sensitive material.

The symptoms are familiar: clients aren’t sure where to send sensitive files, old conversations scatter across replacement phones, and the boss wants visibility without another daily meeting. Matrix is a self-hosted instant-messaging system where we control the message history. The European Commission has used it for cross-agency communication involving more than 40,000 employees. That example showed me that a small team doesn’t need to copy a large institution wholesale. We could start with a handful of sensitive files and one work group.

What Matrix is—and who is already using it

In plain terms, Matrix is like building our own WeChat, but with more of an organizational and collaboration focus. We can choose where the server, account management, and file storage live, rather than handing everything to one platform. The European Commission didn’t simply have employees register personal accounts. It connected them through a unified entry point and linked institutional identities, directories, and messaging.

I know an independent developer, Chen Lin, who took on three design clients in Chengdu last year. She created project groups on a self-hosted server where clients could review quotes, delivery versions, and revision histories. Conversations no longer disappeared into a feed built like a social network. She also hit a wall: following the technical documentation, she spent two straight hours on the first installation before returning to Element’s official client installation page and finally understanding the sequence. Chen Lin later recorded the process as a one-page checklist for other indie developers.

What it costs to reproduce this today

I did the math. A test version costs 0 yuan per month. A basic cloud server runs roughly 30–80 yuan per month, plus another 10–20 yuan for a domain. Preparing the server, domain, and accounts takes about 2–4 hours. If synchronization or permissions cause trouble, allow another 1–2 days.

The technical barrier is simple to describe: coding isn’t required, but someone has to be willing to work through domain settings, email verification, and backups. For a smooth experience for everyone, it helps to have someone familiar with servers.

The first step isn’t buying a server. It’s opening Element’s client download page on the Matrix website and installing the client for the device. After installation, I’d create a test account and confirm that text, images, and files send and receive correctly before committing to a production server. This tool isn’t for everyone. If our business doesn’t handle sensitive files and we don’t plan to preserve conversation histories long term, there’s nothing wrong with waiting.

How I’d start, depending on the stage

Just starting: I’d avoid paying for a system at first. I’d use a test group for quotes and delivery notifications, run it for seven days, and see whether the team genuinely wants to move conversations there.

With one or two clients: I’d centralize contract drafts, payment details, and final versions in a work group, with regular backups enabled. For identity documents, I’d still tell clients which materials shouldn’t be sent through chat.

Scaling up: I’d have a technical person document accounts, permissions, domains, and backup procedures, then gradually connect additional departments. I wouldn’t migrate every conversation on day one or delete the old platform before completing a restoration test.

If I tried this tonight, I’d start with one experiment: create a test group, invite the most demanding client to send a dummy file, and personally complete the full “send—find—back up—restore on a new device” loop. That gives us more than a tool overview. It gives us a concrete answer about whether this fits our operation.