FAQ

What should an enterprise prepare before deploying AI agents?

Four preparations, and we advise against starting without any of them. (1) Scenario selection: pilot on a workflow that is frequent, comparatively rule-clear and verifiable — not the most glamorous one. (2) Knowledge and data foundations: govern the knowledge base first (deduplication, versioning, permissions); a dirty knowledge base only scales errors. (3) Governance design: permission boundaries, human approval points and audit logs decided before launch, not after. (4) A measurement baseline: record the manual process's time and error rates before the pilot, or value can never be proven afterwards. Negency's method is a small controlled pilot, verified before scaling, with governance as a design input rather than a patch.

Figure 01 · Nine-point pre-launch checklist

  • Scenario
  • ✓Named scenario, named owner, expected volume
  • ✓Negative list agreed
  • Knowledge
  • ✓Docs deduplicated, stale versions retired, every doc owned
  • ✓Sensitive content classified, read scope matches permissions
  • Governance
  • ✓Approval list final, approvers named
  • ✓Log fields and retention set
  • ✓EU classification and GDPR assessment done first
  • Measurement
  • ✓Human baseline recorded
  • ✓Pass and stop lines in the project brief
All nine green and no red flags before the pilot starts; fix missing items in checklist order — never start with gaps.

Scenario selection: easy first

A pilot scenario should be frequent (happens daily), bounded (right and wrong are judgable) and contained (errors can be rolled back). Support Q&A, document processing and internal knowledge retrieval usually qualify; deciding for management does not — that is the destination, not the starting point.

All three tests must pass: frequent but unbounded work ("judge how interested this prospect is") can't be verified at scale; bounded but rare work saves less than the build cost; frequent and bounded but irreversible work (automatic dunning letters) turns one misjudgement into an external incident. See the safest first use cases.

Knowledge foundations: govern before connecting

An agent's answer quality is capped by its knowledge base. Before connecting: merge duplicates, retire stale versions, classify sensitive content, give every document an owner. Skip this and the agent will confidently quote a three-year-old policy.

Stale versions are the trap: a policy revised three times still has all three versions on the shared drive, and the agent may pull the old one by similarity and answer with it, confidently. Keep one current version per document; retire the rest from retrieval scope. If the agent also reads the public website, check its machine-readable foundations first: in Negency's flagship measurement of the global homepages of 30 Chinese exporter companies (a single-day sample on 30 October 2026, measuring technical website visibility only — not brand mention rates in AI answers), machine readability averaged only 69.2 (median 68.5) and 17 of 30 sites had no JSON-LD at all. Source: Flagship Report 2026, Issue 1.

Governance: rules before launch

Who may instruct the agent to do what, which actions require human approval, how long logs are kept — written into the pilot design. The approval list must name concrete actions ("send a customer email", "change a price list"), not vague phrases like "human review when necessary". In the EU, GDPR and AI Act classification come on top: classify first, deploy second — the risk grade decides which obligations apply (see why agents need governance and approval points).

Measurement: no baseline, no result

Record the manual baseline when the pilot is chartered: handling time, first-contact resolution, error rate. Compare on the same definitions after launch; scale only on evidence, stop cleanly otherwise — fair to the business and to the agent alike.

"Same definitions" is the operative phrase: measure after launch exactly as you measured before. Excluding cases handed back to humans flatters the error rate overnight — the number fools the report, not the business. Write pass and stop lines into the brief, with re-measurement dates.

The pre-launch readiness checklist, item by item

Nine checks in four groups: what to do, what breaks if skipped, rough effort.

  1. Scenario: the pilot is named, owned, and sized — and passes all three tests: frequent, bounded, reversible. Skip it and nobody is accountable for acceptance. Effort: usually days.
  2. Scenario: a negative list states what the agent must never do. Without one, the agent may cross a line nobody drew — such as sending a commitment to a customer. Effort: usually days.
  3. Knowledge: pilot documents deduplicated, stale versions retired, every document owned. Skip it and the agent quotes outdated policy at volume. Effort: usually weeks.
  4. Knowledge: sensitive content classified; agent read scope matches employee permissions. Skip it and the agent may disclose salary bands or price floors to the wrong people. Effort: usually weeks.
  5. Governance: approval list final, approvers named. An approval point that only says "review when necessary" is no approval point. Effort: usually days.
  6. Governance: log fields and retention set; any incident replayable end to end. Without logs you cannot tell which step failed or who approved it. Effort: usually weeks.
  7. Governance: for EU operations, AI classification and the GDPR assessment come first. Finding out after launch means rebuilding compliance at far higher cost. Effort: usually weeks.
  8. Measurement: human baseline recorded — handling time, first-contact resolution, error rate. Without a baseline, pilot results are unjudgeable. Effort: usually 1–2 weeks of sampling.
  9. Measurement: pass and stop lines in the brief, with re-measurement dates scheduled. Without a stop line, a failing pilot keeps running on sunk cost. Effort: usually days.

Red flags: do not start yet if you see these

  • The knowledge base holds three versions of the same policy and nobody can say which one is current;
  • Approval points say only "human review when necessary", with no action list and no named owner;
  • Nobody can state the current process's handling time or error rate;
  • The pilot scenario is "advise management on decisions" — a task with no objective right or wrong.

All nine green, no red flags: start the small, controlled pilot. Anything missing gets fixed first, in checklist order.

Bring the agent solution into your workflows

Read the answer — the next step is judging it against your scenario. Discuss an agent solution: tell us the business problem and your systems for a preliminary suggestion.

Related questions

How is GEO different from SEO?

SEO optimises a page's rank in a list of links, aiming for clicks. GEO (Generative Engine Optimization) optimises how discoverable, understandable, trustworthy and citable a company is inside AI-generated answers — the goal is to be in the answer itself. They share technical foundations (crawlability, structured data, content quality), but GEO additionally requires governed entity facts, a machine-readable surface (llms.txt, Markdown mirrors) and a third-party mention ecosystem. A site that ranks well is not automatically visible to AI: engines cite the companies whose facts they can fetch, parse and verify. The concrete differences sit in four dimensions — goal, object, content structure and evaluation — compared item by item in the body below.

How can Chinese companies going global build AI search visibility?

For Chinese companies going global, the visibility gap is rarely content volume — it is the machine-readable surface. Our audit of 30 Chinese outbound companies found machine-readability the weakest category (69.2/100 average): 17 had no JSON-LD on the homepage, 15 had a missing or thin sitemap, 13 had a missing or duplicated H1. The path has four steps: audit bot reachability and machine-readability first; govern entity facts so Chinese and English statements agree; publish question-shaped content built on real overseas buyer questions; then earn third-party mentions (media, communities, partners) and verify with periodic resampling against a fixed question set.

What should a corporate website change for the AI search era?

Five changes. (1) Bot reachability: robots.txt explicitly allows AI crawlers and live fetches are not stopped by firewalls or challenge pages. (2) A machine-readable surface: an llms.txt fact file (optional aid), a complete sitemap, Markdown versions of core pages (optional). (3) Entity structure: JSON-LD naming entity types such as Organization, clean title/H1 discipline, hreflang pairing on bilingual sites. (4) Question-shaped content: pages organised around buyer questions, short answers first, FAQ schema attached. (5) Measurability: analytics that separate human and bot traffic and attribute AI-referred inquiries. Negency's own site was rebuilt to exactly this standard, and the public audit tool scores against it.

What is llms.txt, and should every company website have one?

llms.txt is a plain-text brief at the site root written for AI systems: who the company is, what it does, where the core pages live, and the canonical facts and definitions. It does not by itself raise citation rates — in Ahrefs' May 2026 study of 137,210 domains, 97% of published llms.txt files received zero requests that month, so its direct effect is near zero — but it is the cheapest fact-governance move available: one file anchors a single version of the truth that crawlers can rely on. Verdict: worth adding, useless alone; it works as part of entity-fact governance, structured data and question-shaped content. Negency's llms.txt is a full fact bible: company definition, offering boundaries, sourced cases and citation rules.

Why do enterprise AI agents need governance and human approval points?

Because an agent differs from ordinary software in one decisive way: it chooses its own next actions, and its errors amplify at machine speed. Governance answers four questions — which data it may touch (permissions), which actions require a human (approval points), what it did (audit trail), and how it stops (kill switch). Approval points are not distrust of the technology; they keep accountability on the human side: external sends, money, deletions and commitments pass a human, everything else flows automatically. The EU AI Act likewise requires human oversight for higher-risk systems — governing early is the cheapest compliance path.