Monday morning: a client was waiting for a quote, but the internal system locked me out

At 9:30 last Monday, I was about to send a client the quote when our internal ticket system kept spinning. Three people had already asked in the team chat, “Has the proposal gone out?” I had to write the client’s name, request, and deadline on paper first, then send the missing replies one by one. That was when I realized the real time sink in a team isn’t one particular tool; it’s the chaos after a connection drops, when nobody knows where everything is.

If you’ve also hit temporary login failures, messages scattered across group chats, or file versions that don’t match, I wouldn’t rush to replace your entire tool stack. We now maintain a shared “clients waiting” list in Google Docs, paired with a Tencent questionnaire for new requests. Xiaozhou, our customer service colleague, updates each item’s status before Tuesday follow-ups. Lin Yue, a former colleague who runs a freelance photography business in Hangzhou, borrowed the same approach for bookings: location, date, and deliverables each get their own row. When a client changes the time, the assistant marks the request “Needs confirmation” directly in the group chat.

Replication cost: zero budget, two hours, no coding

The cheapest version starts with a copied Google Docs template. If Google isn’t convenient for your clients, a Feishu spreadsheet, Tencent Docs, or Excel works too. The monetary cost is RMB 0. Organizing it the first time takes about two hours. The technical barrier is simply editing spreadsheet text; no coding knowledge is needed. For the first step, I open the online document tool we already use, create a table, and fill in the first row with “Client name, current item, last reply time, next step, owner.” Then I add a form clients can access, or that I can fill in for them. I initially created five separate spreadsheets, and nobody even filled in the “Next step” field. Later I cut it down to three columns, and people actually used it.

Match the setup to your stage—don’t build the whole system at once

If I’m just getting started with a scattering of clients each month, I’d begin with a one-page checklist and a fixed message template, checking it each morning and before the end of the day. With only a few clients, manual records in WeChat or email are enough; it’s also fine not to try this yet. With one or two steady clients, I’d keep separate lists for quotes, delivery, and follow-ups, and agree on who updates each one so nobody is left waiting. If I’m scaling and the team has more than three people, I’d add “Owner” and “Deadline” columns and use a form to collect everything automatically. Only once that workflow feels stable would I consider connecting it to a proper ticketing or client management system. Not everyone needs this setup. For us, it’s more like a thin emergency blanket: simple enough not to fuss over on a normal day, but useful when things break because it helps the team avoid a missed request or another argument.