What this page is
We don't sell software seats. We deliver a finished asset: your scattered documents turned into a knowledge base that answers with citations and passes acceptance — then wired into your customer service and public content.
So this page covers two things only: what each service delivers and what counts as delivered. Pricing is quoted per project — email savant0196@126.com.
Service 1 — Enterprise knowledge base
| Deliverable | What it contains |
|---|---|
| Inventory & cleaning report | What you have, duplicates and expired items flagged, usability tiering |
| Structure design | Bucket scheme (FAQ and policy clauses in separate indexes), metadata fields |
| Ingestion & retrieval setup | Chunking rules, index isolation, citation back-fill |
| Evaluation set | Real questions with expected answers and sources |
| Operations manual | Routine maintenance, incremental ingestion, self-troubleshooting |
Acceptance: re-run the evaluation set — accuracy, citation correctness and empty-answer count reported. We fix and re-submit until it passes.
Service 2 — AI customer service & national-standard compliance
Handover rules and audit trails designed against GB/T 47746—2026, not just a chat widget.
| Deliverable | What it contains |
|---|---|
| Self-check sheet | All 61 check items (48 shall / 4 should / 9 may) with verdict and clause reference; the 5 one-vote items flagged separately |
| Gap list & remediation advice | Ranked by cost × risk, each item mapped to a clause |
| Handover rule file | Which scenarios must escalate, emotion triggers, what the customer is told — configurable and traceable |
| Regression acceptance report | Resolution rate, wrongly-escalated count, missed-escalation count, empty answers |
Acceptance: spot-check 10 items against the standard text; re-run the regression set on site and compare.
Service 3 — Answer-layer optimisation (AEO, also called GEO)
Making AI search able to find you, answer about you and cite you — assets, not ranking games.
| Deliverable | What it contains |
|---|---|
| Fact base & 9-column provenance ledger | Every public claim carries source, collection date and verification method |
| Source-tier escalation plan | Own site first (structured data + fact pages), then authoritative platforms and public registries |
| Process verification record | Regression re-runs, rule-change log, monthly observations (same question ≥3 samples per week) |
Acceptance: facts can be spot-checked back to source; process records can be re-run by the client. We do not promise rankings or citation rates — the applicable standard, T/CAPT 026—2026, explicitly prohibits service providers from promising such outcomes.
Before you sign: three things that are easy to leave vague
These are the three vaguest points in this kind of service. We state ours outright. You can take these three questions to any provider — if they can't answer them, that vagueness is the product.
- 1. Name the AI platforms, one by one. Never "all platforms". Our verifiable scope is primarily the major Chinese engines (Doubao and others), and every observation log states which ones were tested that round. Anyone writing "indexed across all platforms" without a list is keeping the interpretation to themselves.
- 2. List the deliverables, file by file, so you can check each one off. For the website answer layer the deliverables are named:
llms.txt,llms-full.txt,sitemap.xml, in-page JSON-LD, plus monthly observation logs. We don't accept "structured data support" as a substitute for a deliverable list. - 3. Say up front what happens if publishing stops. AI citations depend on continuously updated sources and re-testing. If content stops, index coverage declines — that is how the systems work, not a vendor's fault. So we don't sell "pay once, permanent results"; that can't be honoured. What we deliver is this: the assets and the process records stay with you, so you or anyone else can keep running them.
Why we don't offer "guaranteed page-one rankings": AI recommendations are dynamic and no provider can lock them down. Anyone promising that outcome is planting a dispute for later.
Self-serve tools
What we don't take on
- Projects requiring enterprise qualifications we don't hold (we quote within our real capability)
- Hardware, motion control, model training
- Any promise of rankings, citation rates or blanket coverage
- Restricted data (personal data, contract floors) is never sent to overseas APIs
How quoting works: document inventory first → problem list and plan → then a quote. Remote-first; on-site in Chongqing available.
For pricing, email savant0196@126.com.
FAQ
Why don't you publish prices?
Because a knowledge-base project's price depends on volume, structure and integrations. A public number would not be meaningful for your case. We inventory, then quote.
What should I prepare before asking for a quote?
Company size, the scenario (internal Q&A or customer-facing), and the rough volume and formats of your documents.
How do I reach you?
Email savant0196@126.com, or use the contact form.