FAQ

How does Negency differ from large consulting firms?

Different unit economics. Large consultancies sell senior time and process: broad scope, long cycles, deliverables that lean to reports, and a minimum engagement size mid-market companies rarely fit. A specialist team like Negency sells one narrow capability delivered as running systems and published pages (the audit tool on this site is itself the product demo), with fixed-price diagnostics and regular measurement loops. The choice is not who is smarter; it is whether the job is enterprise-wide transformation (buy the scale player) or making one capability real, fast and provable (buy the specialist).

Figure 01 · Negency vs large consultancies: six dimensions

Pricing

Negency

Fixed-price diagnostics, stop at any step; diagnostic package RMB 19,800 (published on this site)

Large consultancy

Typically priced by day rates and senior staffing, usually with an effective minimum ticket size (check each firm's published rates)

Deliverables

Negency

Running code and published pages; this website is itself the working sample

Large consultancy

Typically diagnosis reports and transformation blueprints

How results are verified

Negency

Every conclusion traces to raw samples and page evidence, re-measurable next quarter on the same basis; our own website scored 97/100 (11 Nov 2026)

Large consultancy

Typically report delivery and milestone reviews

Who does the work

Negency

The team that signs is the team that executes, hands-on with the crawl surface

Large consultancy

Selling and delivery teams commonly differ; day-to-day contacts vary in seniority

Entry threshold

Negency

Free audit entry; fixed-price diagnostic; no minimum ticket threshold

Large consultancy

Usually an effective minimum ticket size; mid-sized clients often out of range

Right problem

Negency

Narrow, deep execution problems — one capability working and provable with data

Large consultancy

Multi-country restructuring, organisation-wide change, board-level governance and endorsement

The consultancy column describes common practice in that category; check each firm's published rates and actual delivery. Every claim in the Negency column is verifiable on this site (diagnostic page, audit, the live site itself).

The structural difference: selling time, or selling a working result

Large consultancies typically sell by seniority and staffing: diagnosis-heavy, deck-heavy, long cycles, and usually a minimum ticket size that quietly filters out mid-sized clients (check each firm's published rates for specifics). Their GEO / AI-visibility offering is often one recently assembled line inside a big transformation practice — strong on research and argument, weak on the daily publish-measure-iterate loop that decides citation outcomes. A specialist team is the reverse: one link of the chain, done in a way that is verifiable, re-testable and hand-over-able.

The incentives differ. A consultancy bills by input, so longer projects with more senior staff earn more; a specialist team bills by deliverable at fixed prices, so dragging things out gains it nothing. Neither incentive is inherently nobler — but a buyer should be clear what the money is buying: judgement, or a working result.

What a specialist team does differently

  • Scope: one link of the chain (AI visibility, website machine-readability, agent governance) instead of the whole transformation;
  • Delivery form: running code and published pages instead of decks — this website itself is Negency's working sample (audit engine, bilingual FAQ matrix, machine-readable mirrors), not a portfolio screenshot. Negency's own website scored 97/100 in an audit on 11 November 2026: the technical surface is proven on ourselves first;
  • Pricing form: fixed-price diagnostics with stop points, instead of day rates that meter your decision time. Negency's diagnostic package is a fixed RMB 19,800, published on the diagnostic package page.

Why the difference matters more in GEO

Most GEO work is hands-on, not argumentative. The Negency Flagship Report 2026 (Issue 1) — a sample of 30 Chinese exporters' global website home domains, measured with the Negency AI visibility audit engine (around 30 signals, five categories) in a single-day sample on 30 October 2026; the report measures website technical visibility only (whether AI can crawl and read the site), not brand mention rates in AI answers — found 17 of 30 sites with no JSON-LD at all, 15 of 30 with sitemap problems, and 13 of 30 with a missing or non-unique H1. The fix for those is changing code, pages and configuration — not another analysis report. A team that changes the crawl surface itself and a team that only recommends changes are two different kinds of supply in GEO.

An honest boundary

If you need multi-country, multi-vendor transformation programmes, organisation-wide change management, or a board brand that insulates internal sponsors, a large consultancy is the right buy — do not hire a specialist for that. If what you need is a specific capability that works and measurably proves it, the specialist's ratio of delivery to meetings wins. The two are not substitutes; pretending otherwise in either direction is a category error.

Sometimes the answer is both: a consultancy for the organisation-wide AI plan and governance frame, a specialist team for visibility execution itself — buy planning and execution separately, each for its strength. Write the handover into the contract: which of the planner's outputs are acceptance criteria the execution team can use directly, and which are directional advice only.

Three questions that separate them on the spot

Who actually does the work? Is the team that sells the same team that executes, and is your day-to-day contact a partner or a first-year analyst? A good answer: the delivery team can name your website's specific problems on the spot. A bad one: another meeting, always.

Do deliverables contain re-testable data? A thick report, or conclusions that trace back to raw samples and page-level evidence and can be re-measured next quarter on the same basis? A good answer: deliverable samples published for anyone to read. A bad one: "our methodology is proprietary and cannot be shown."

What language is the quote written in? Priced by named work items with acceptance points, or wrapped in framework vocabulary nobody can price against? A good answer: every price line maps to one verifiable deliverable. A bad one: a single total.

In fairness: for multi-country, multi-business restructuring or board-level governance and endorsement, a large consultancy's brand and organisational reach genuinely fit better. A specialist firm's home ground is the narrow, deep execution problem — getting one concrete thing done in a way that is verifiable, re-testable and hand-over-able. Decide which kind of problem you are holding before deciding whom to call. Once the kind is settled, run the firm through the 12 due-diligence questions.

See where your brand stands in AI search

Start with the free AI visibility audit: your scores for crawler reachability, machine readability and entity structure in minutes. For the full competitor comparison and fix list, see the AI search visibility diagnostic package.

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.

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.