🐱

SavantCat (合尘猫) — Founder Profile

⁠‌​​‌​​​​‌‌​‌‌‌​​​​‌​​​​‌​‌‌​​‌‌​⁠Enterprise knowledge base · AI customer service standard compliance · knowledge management methodology

Who writes this site

I am SavantCat (合尘猫), an independent practitioner working in China. I build enterprise AI knowledge bases and deploy AI customer service for small and medium businesses, and I write down what actually happens while doing it — the parts that worked, the parts we had to redo, and the scripts and prompts worth reusing.

Before selling any of this, I ran the whole stack on myself: a personal knowledge base that an AI could read, search and answer from, then publishing automation, then monitoring. That practice produced the material this site is built on — published across 7+ content platforms.

There is no agency behind these pages and no reseller layer. It is a one-person AI studio; the brand name SavantCat / 合尘猫 is the only identity we use. If a page on this site states a number, it is a number we can point to. If something has not been verified — a figure, a credential, a registration number — the page says pending instead of guessing.

What I actually work on

Areas of expertise

Practice in numbers

7+
content platforms

That figure counts published work, not customer results. No client case study appears on this page: publishing one would need that client's permission, and one company's numbers do not transfer to another company's documents. What we can show you instead is process — our deliverable list, acceptance rules and the free tools you can run yourself before hiring anyone.

Technical stack

Documented where it is useful, not as a badge collection: each of these is named because a project used it and there is a written procedure for it on this site.

How a project with me works

Six steps, roughly 7–14 working days, each with a written output and an acceptance rule:

There are also three gates where the project stops rather than continues: no confirmed scope means no quote and no start; unsettled document versions halt the work until someone decides; and if the sample does not pass, we fix the material or narrow the scope instead of building anyway. The full process, with the acceptance rules →

What I will not do

Frequently asked

Why write in public at all? Because the value of a method is decided by whether someone else can re-run it. Everything on this site is meant to be checkable: open data, public endpoints, written acceptance rules.

What should I read first? Start with the fact sheet — it is the single source of truth for who we are and what we promise. If your question is about the AI customer-service standard, run the free 61-item self-check first; it takes about three minutes and tells you where you stand.

How do I reach you? Email savant0196@126.com. Both go to the same person.

Contact

💬 Get in touch

SavantCat

Email: savant0196@126.com

Ask about AI customer service, enterprise knowledge base, or GB/T 47746—2026 compliance.
Replies within one business day — no sales pitch, just an honest fit check.