The client wanted proof, and I was digging through old folders
Last Wednesday afternoon, I was sending revisions to a client in Hangzhou. They asked, “Do you still have that case from last time?” I spent 20 minutes searching my cloud drive and found only one screenshot. I used to rely on improvised searches, and whenever a client pushed, I felt like I was submitting homework on the spot. Then it hit me: the material wasn’t missing—it just hadn’t become a reference library I could pull up immediately.
I built a lightweight case table in Airtable
This wasn’t some sophisticated method. It was essentially a searchable table, with one case per row and fields for client type, problem, approach, result, publishable materials, and last contact date.
Chen Yan, an independent consultant in Chengdu, splits her frequently used proposals into 12 categories. When a client asks for examples, she filters by industry first, then pulls the relevant cases. I built my first version the same way—and made a few mistakes. At first, I put sensitive client information into everything. I later switched to anonymous summaries and restricted team access. The table doesn’t write proposals for me; it just saves me half an hour of searching.
Replication cost: $0 to start, about 1 hour, low technical barrier
I used Airtable’s free plan, so the budget was $0, and building the first table took about an hour. The technical barrier is “knowing how to type and drag fields”—no programming required.
The first step: sign up for a free account, create a table, and add five fields: client industry, problem, my approach, final result, and material link. Then import only three completed projects; I wouldn’t organize the entire archive on day one.
If I didn’t want to switch tools, I could have started with Excel or Feishu’s multidimensional table. Not everyone needs this setup. If I’m only taking occasional jobs and have very few cases, postponing the cleanup is perfectly fine.
I match the setup to my stage instead of aiming for perfection
When I was just starting out, I would have created a five-row table and recorded only the services I repeatedly explained. Once I had one or two stable clients, I would add industry tags and keep a sanitized version for public sharing. Now that I’m scaling, I’d set team entry rules—for example, adding a row within 10 minutes of completing a new project—while separating access permissions.
I don’t want organization to become another form of procrastination. I also spent two evenings making my table look nicer before solving the core question: “When a client sends me a message, can I find the answer immediately?” I can spend 30 minutes testing a table and then decide whether it’s worth continuing.