Monday morning, a client asked for the same pricing rules again

Last Wednesday night, I was in Hangzhou organizing contract templates for freelance photographer Lin Yue. She couldn’t find the old quote and asked whether I could pull together rules scattered across cloud storage, chat logs, and memos. I felt anxious too: if I wasn’t around, would clients have to ask everything again?

What I eventually understood was that the problem wasn’t another document tool. It was making existing materials easy to find, follow up on, and reuse.

What Inkling 2 Mini is, and who’s using it

Inkling 2 Mini is a lightweight knowledge-base product from Thinking Machines that turns team documents into a searchable, question-answering hub. It doesn’t do the work for you; it reduces the time lost to “the information exists, but nobody knows where it is.”

I know a client-management consultant, Zhou Ning, who meets clients in Beijing cafés. She put her pricing details, service boundaries, and FAQs into Inkling 2 Mini. When a new client asks whether two revision rounds are included, she can answer with the source instead of digging through chat history. She also reminded me to review answers regularly, because outdated rules can still mislead people.

Replicating it today: upload the most-requested material first

The replication cost isn’t high. Check the official site for current long-term pricing and how much material the free tier allows. Preparation and initial setup take about 1–2 hours. The technical hurdle is knowing which files can be exposed to the team or clients. The first step is to open the Inkling 2 Mini workspace, create a knowledge base, and upload one old contract or FAQ sheet.

I made the mistake of uploading a dozen messy folders at once, and the answers started contradicting each other. Keeping only verified versions, then testing edge cases one by one, made results much more stable. Redact or remove client-sensitive material first. If I weren’t ready to try it now, simply organizing the files would still be worthwhile.

Match it to your stage, don’t copy someone else’s setup

At the starting stage: I’d begin with one FAQ or pricing sheet and test the full “ask a question—find an answer—check the source” loop without rushing into a complex workflow.

With 1–2 clients: I’d add recurring questions, delivery boundaries, and links to materials first, reducing the time I spend answering the same things.

While scaling: I’d split knowledge bases by product line or client type and schedule an weekly answer review. Only after the team genuinely struggles to find information would I consider investing more.

If I didn’t yet have organized files, or there wasn’t even one person on the team willing to maintain them, I’d leave this for later. Solving the most frequently asked question often beats chasing an “all-in-one knowledge base.”