Last Wednesday afternoon, I was waiting for a client’s reply in a café

I was staring at the chat window, with a quote, a contract, and another revision request waiting beside me. Suddenly, it felt like most of my day went into “getting the point across.” This is an easy drain for freelancers and small teams to overlook: it’s not that there aren’t enough clients. The same questions get answered again and again, while the work that actually pays gets pushed to the back of the day.

I used to get stuck here too. I bought several template packs, but the categories were so complicated I never even opened them. Now I keep one lightweight reply library with answers to common questions, pricing details, delivery boundaries, and delay messages. It isn’t a new tool. The core method is to turn what I keep saying into copy-and-paste “reply blocks,” then pull them up by scenario.

Chen Yu in Hangzhou has been using one for a month

Chen Yu handles brand visuals and short-form video editing. Clients often ask, “How long will delivery take?” “Can you make three revisions?” or “Can we see a rough first draft?” From her shared studio in Yuhang, Hangzhou, she has turned those answers into a few fixed versions: delivery timelines, revision limits, upfront fees, and delay wording. When a client follows up, she no longer rewrites the answer from scratch. She just swaps in the client’s name and project details.

This isn’t only for designers. A friend who maintains websites puts “confirming requirements,” “how to respond when the server goes down,” and “how monthly payments renew” into his reply library too. Customer support, product inquiries, and course Q&A can all borrow the same approach. Not everyone needs it, though. If your communication is highly customized or you almost never get the same question twice, there’s no rush to build one.

Your version today: almost free, about 45 minutes, no technical barrier

Money: Use a regular document or a free online spreadsheet: ¥0. Time: Spend 30 minutes collecting recent chat logs, then 15 minutes writing four types of replies. First step: Create a document called “Common Client Questions,” paste in ten recent real conversations, and highlight the questions that keep appearing.
If I want to level up later, I can try an AI assistant with a knowledge base or automated replies. Pricing and rules vary by service, so I’d test the free version first to see whether it actually saves time. I also wouldn’t upload contracts, ID cards, bank card details, or other sensitive information right away—and I wouldn’t publish a client’s exact words online.

Match it to my stage—there's no need to build it all at once

If I’m just starting: Today, I’ll organize only the three questions I answer most often. Even two sentences for each will be more useful than creating a massive, all-purpose template.
If I have one or two clients: I’ll add my pricing range, payment milestones, and revision limits, then add one newly asked question after each conversation. I used to leave out how clients would confirm requirements, which led to repeated revisions—I got this part wrong too.
If I’m scaling: I’ll let customer support or an assistant use the reply library so our tone and commitment boundaries stay consistent. I’ll also clear out outdated content each month. Refunds, contracts, and pricing still need a human check.
If I’m not ready, that’s fine. I’ll watch for three days and note the three sentences I type most often. If they really are annoying, I’ll build from there.