Methodology
This page is the public rule book behind everything on atozaiaccounting.com. It explains what the scores mean, where the data comes from, what a vendor can change, what only the editor can change, and what's on the roadmap that isn't built yet.
It is a working document. The site is updated several times a day; this document is updated less often. When the two disagree, the site wins and the next revision of this document catches up.
1. What this is, and what it is not
The A to Z of AI Accounting Software is two things:
- A live, independent directory of vendors operating in the AI accounting and finance stack.
- An eight-chapter editorial report on where the category is going and who is positioned to win it.
The directory is structured, filterable, and updated continuously. The report is editorial. The report does not change every time a vendor adds a new feature. It evolves with the market, not the press cycle.
I am not a vendor and I am not an analyst firm. I am a former practitioner writing what I see, with the bias that comes from having been on the buy side and the build side. I do not take pay-to-play money from vendors for placement, ranking, or commentary. Vendors can claim their entry for free, which gives them edit rights on factual fields. Vendors cannot pay for a higher AI Maturity score, a place on the Map, or favourable copy in Our Perspective.
There are mistakes in this directory. Some of them are mine, some of them are out-of-date public information, some of them are the vendor's own copy. I publish the rules I use so you can spot the mistakes faster than I can.
1.1 Disclosures
The A to Z of AI Accounting Software is independently produced by Bundahsi Consulting Ltd, trading as Damon Anderson. It is not sponsored, commissioned or funded by any vendor covered in the report. Where I have relationships that could reasonably affect my independence, I list them here.
Media partnership: Sift. Since September 2026 I have worked with Sift, which owns AccountingWEB, the Festival of Accounting and Bookkeeping and the Accounting Excellence Awards. The arrangement runs for six months and covers a monthly column on AccountingWEB, contributions to its AI newsletter, a recurring slot on its podcast, and helping shape and present the AI content at FAB 2027. It is a commercial arrangement. It has no bearing on any vendor assessment, ranking or published criterion.
Advisory work. I advise companies in this market, and I hold interests in some of them. Advisory clients get no advantage in the Directory, the maturity scores, the World Ranking or the Map. Where a company I work with appears in the research, it is assessed against the same published method as everyone else.
What money cannot buy. No vendor can buy a rank, a badge, a place on the Map, an AI Maturity score or favourable copy. That holds through the Sift partnership, through advisory work, and through any other arrangement. Questions about editorial independence go to hello@atozaiaccounting.com.
2. How updates land
The Directory is updated continuously. When a vendor's claim is approved or an edit request goes through, anyone signed in sees the change within seconds. Signed-out pages are served from a pre-rendered copy and catch up on the next build, usually within the hour.
The Report is a different beast. Chapter content is editorial. It revisits material market shifts rather than tracking individual product launches. Expect material revisions every four to eight weeks, not daily.
Confidence scores (see §5.4) recompute every Monday morning. The Big 30 is rebuilt on every site build from the current data and the rules in §4. Directory rankings recompute on every page load.
3. The Stack: how vendors are categorised
Every vendor sits in a single Main category that describes where it does the work, plus a Sub-category that picks the specific job. Vendors that genuinely span two main categories (rare) get the one closest to their centre of gravity.
The ten main categories:
- Economic Event: where money moves or commits. Banks, payments, expense capture at source, anything upstream of the ledger.
- Ingestion: capture and extract source documents. OCR, document capture, supplier invoice ingestion.
- Normalisation: raw transactions into clean, reconciled, categorised data. Bank reconciliation, transaction coding, close.
- General Ledger: the authoritative ledger of record. Both AI-native ledgers and traditional ERPs sit here.
- Assurance: audit, internal audit, controls, SOX, risk and compliance.
- Tax: direct, indirect, personal, corporate compliance and filing.
- Decision & Action: FP&A, AP, AR, spend management. Anything that consumes the cleaned ledger to drive a decision or a payment.
- Orchestration: the control layer above the ledger. Practice management, agent management, workflow automation for firms.
- Productivity: horizontal tools repurposed for accounting (call transcription, document automation that isn't accounting-native).
- Data Layer: infrastructure under everything. APIs, identity, analytics pipes. Not user-facing.
Sub-categories are the working list. I add new ones when enough vendors arrive in the same place to justify a name; I rename them when the language settles. The current list is published in the Directory filter.
A vendor's category is editorial. Vendors can challenge it through the claim form. I read every challenge.
4. The Map: who's in and who's out
The Map shows the Big 30: the real players in each layer of the stack, for buyers in your market. A product earns its place three ways: businesses in the market actually buy it (footprint), its AI does real work (the World Ranking score), and there is a substantial business behind it (company strength). AI carries the most weight, but a product nobody in the market uses cannot win a slot on AI alone. For AI on its own, worldwide, see the World Ranking (§11.2).
4.1 Editions
There is a Global edition and a market edition for the United Kingdom and the United States. You land on the edition for the country you are browsing from, and can switch at the top of the Map. A market gets its own edition once I have rated enough products there (§4.3) to fill all 30 slots. Until then, viewers there see Global. Australia does not have one yet.
4.2 Who is eligible
Any vendor can be on the Big 30 if it is:
- In the report as software. Service firms that do the work with people (AI-run or human-run accounting firms) belong in the Directory. Payroll and HR platforms sit outside the accounting stack, so they are filed under Payroll & HR and never appear on the Map.
- Live or Beta. Alpha and Waitlist products are Directory-only.
- Rated as present in the market: a footprint above 0 there (§4.3). For Global, in the UK or the US.
There is no minimum AI maturity and no editorial pick or exclusion: I do not add or remove vendors by hand. AI is 65% of the score, so a product with little AI rarely makes it, but the score decides that, not a gate.
4.3 Market footprint
Every vendor in the running is rated 0 to 4 in the UK and in the US, from public evidence: named local customers, customer counts, a local office or team, local partners and accounting-firm channels, and support for local tax and reporting. Being headquartered in a market does not count on its own, and nor does a vendor simply listing the market.
- 0: not sold there.
- 1: available, but no evidence of local customers.
- 2: named local customers and modest traction.
- 3: established, with hundreds of customers, a local team or a channel.
- 4: a category leader in that market.
A product needs a 2 or more to count as a player in a market; on Global, 2 or more in both the UK and the US. Products below that bar only fill a layer that would otherwise be short. I keep the evidence behind every rating, and a vendor can send better evidence at any time.
4.4 The Big 30 score
Each eligible product gets a score out of 100:
- Market footprint, 25 points. Ratings of 1, 2, 3 and 4 earn 10%, 30%, 70% and 100% of these points. The steps get bigger on purpose: being on sale is not enough, and an established player pulls clearly ahead of a product with a few local customers. On Global, the UK counts 40%, the US 40% and reach into other market areas 20%: Australia, New Zealand, Canada, Ireland, Europe, Asia Pacific, Middle East & Africa and Latin America, with full credit at 5 areas.
- AI, 65 points: the product's World Ranking score (§11.2), from the latest monthly edition.
- Company strength, 10 points: the number of paying business customers the vendor states worldwide, in bands: 100,000+ earns 100%, 10,000+ earns 85%, 1,000+ earns 65%, 100+ earns 45%, 1+ earns 25%. Users and free accounts do not count. Where no figure is published, the ownership stage is used instead, from 85% for a public company down to 10% for pre-seed. Funding is worth less than customers on purpose.
The Map is written for most buyers, so among products above the footprint bar, those sold only to large enterprises rank after the rest.
4.5 Filling the 30
The top 3 in each of the nine layers, 6 in General Ledger (8 × 3 + 6 = 30), because the ledger is where the largest re-platforming bet sits. Decision & Action always includes one reporting or planning product (Reporting & Analysis, FP&A / Planning, Cash Flow Forecasting, AI CFO / Advisory Insights, Consolidation & Multi-entity) and one payables or receivables product (Accounts Payable, Accounts Receivable, Collections / Credit Control), so the layer reflects both halves of the work. Ties go to name.
4.6 Why some big names are not on the Map
- Their footprint in that market is below the bar, or, for Global, they are not established in both the UK and the US.
- They are sold only to large enterprises, and the layer has enough products for everyone else.
- The layer is full and other products outscore them, usually on AI.
- They are a service firm, a payroll or HR platform, or not yet rated. The Directory lists every vendor.
You can dispute any of these through the claim form or by emailing me directly.
5. The scores: what each one means
5.1 AI Maturity (0–4)
This is the most important score on the site. It is also the one most worth disputing if you think it's wrong.
The rubric:
- 0 — No AI. Traditional rule-based software. AI is not part of the product story.
- 1 — Tasks. A chatbot, basic extraction, or narrative summary layered onto an otherwise unchanged product. Marketing emphasis is on AI; product reality is mostly the same product with an AI add-on.
- 2 — Workflows. AI meaningfully speeds up or improves individual capabilities but humans remain the primary decision-makers across the product. Typically one or two capabilities affected.
- 3 — AI-first. AI is the primary decision-maker in at least three of: categorisation, reconciliation, anomaly detection, compliance checking, forecasting, narrative generation, workflow routing. Humans handle exceptions and review.
- 4 — Autonomous. The product delegates whole workflows to AI agents with human oversight rather than human execution. The product is recognisably built around agents, not around screens.
AI Maturity is editorial. Vendors cannot edit it directly. They can submit a challenge through the claim form, with evidence (product demo, public roadmap, customer reference). I review challenges within a few business days.
This score is harder than the others to keep current. It is the area I am putting most automation work behind: news-watching for product launches, evidence ingestion from public sources, and a structured re-review cadence. Expect this rubric to harden in v2.
5.2 AI Core to Value
A three-way: Yes / Partial / No.
- Yes: remove the AI and the product either doesn't work or loses its core differentiation.
- Partial: AI is a meaningful part of the value but the underlying product also works without it.
- No: AI is a marketing wrapper or a tiny feature.
A vendor can have AI Core to Value = Yes and a maturity score below 4. Plenty of agentic products are at maturity 2 today and will be at 4 in two years. The two scores answer different questions: "is AI structurally what this is" vs "how far along is the AI today".
5.3 Verified ✓
A vendor is Verified when their claim has been approved by me. Claiming is free. The vendor confirms or corrects every public-facing field on their record, and the Verified badge appears.
What Verified means:
- A real human at the vendor has reviewed the entry.
- The factual fields (category, launch status, ownership, funding, modules, use cases, regions, and so on) are accepted by the vendor as accurate.
- Editorial fields (Our Perspective, AI Maturity, Threat to Incumbents) remain editorial. Verified does not mean "the vendor approves of the perspective written about them".
Verified is a public signal. Vendors are welcome to call out their Verified status off-site through the share kit on their company page; the badge tells readers a human at the company stood behind the factual entry, nothing more.
What Verified is not:
- It is not a quality endorsement. A Verified vendor at AI Maturity 0 is just a verified vendor that doesn't ship AI.
- It does not expire automatically today. If a vendor goes stale (12+ months without contact), the Confidence score downgrades and the badge is paired with a Medium or Low confidence indicator. A future revision will retire badges for vendors that haven't responded for two cycles.
5.4 Confidence / Information Integrity
A three-way: High / Medium / Low. Recomputed every Monday morning.
- High: Confirmed with the vendor in the last 12 months.
- Medium: Cross-checked across multiple public sources within the last 18 months, or vendor-confirmed but ageing past 12 months.
- Low: Public sources only, or stale, or thin (three or more of the six key fields blank: public AI use cases, workflow stages, core modules, main category, ledger requirement, AI maturity).
Confidence is computed, not editorial. It is the honest answer to "how much should you trust this entry today". An unclaimed Low-confidence entry is a flag to me as much as to you.
5.5 Threat to Incumbents
A three-way: Low / Medium / High. Editorial only.
- Low: complements rather than competes; niche; enabling layer; or an incumbent holding ground with no disruptive pressure of its own.
- Medium: competes meaningfully with existing players; capturing share in a contested segment; credible but not dominant.
- High: dominant in category, actively displacing incumbents, or posing a clear existential threat.
Vendors can challenge this through the claim form.
5.6 Launch Status
- Live: generally available, customers can buy and use the product today without restriction.
- Beta: available to limited customers (invite, signup approval, capacity-limited rollout).
- Alpha: early access only. Design partners, hand-picked customers, pre-release testing.
- Waitlist: not yet shipping. Collecting signups for a future launch.
Live and Beta are eligible for the Map. Alpha and Waitlist are Directory-only (see §4.2). Vendors can challenge this through the claim form.
5.7 MCP Depth & Safety (0–5)
Model Context Protocol, or MCP, is an open standard that lets an AI assistant like Claude or ChatGPT connect directly to a software product and work with your data. A vendor builds one MCP server and any assistant that speaks the protocol can use it.
I score how good that server is, not whether one exists. I deliberately do not count tools. Tool counts are easy to inflate, impossible to verify from outside, and vendors' own published figures frequently do not reconcile with each other. What I look at instead is what an accountant would actually want to know before connecting an agent to a live ledger: can it change your data, how narrowly can you fence in what it touches, and is there a record of what it did.
- 5: reads and writes, with a log of every AI action.
- 4: reads and writes, with fine-grained permissions.
- 3: reads and writes, with account-wide permissions.
- 2: reads your data, cannot change anything.
- 1: announced, no public documentation.
- None found: I checked and found no MCP server.
- Could not check: the vendor's site blocks automated checks.
The line between 3 and 4 is the one that matters most in practice. Both can change your books. A tier 3 server hands an agent everything the account can reach, so an assistant connected for one client can act across all of them. A tier 4 server can be restricted to a single entity, client or action. Same capability, very different consequences if something goes wrong. Tier 5 adds the record: scoping limits what an agent can damage, a log lets you find out what it did. Very few vendors have both.
What I check, and what the scores do not tell you. I read what a vendor publishes: their site, their developer and documentation subdomains, their llms.txt, and whether an MCP endpoint responds. Everything is dated, because this moves quickly. That means I am scoring published documentation, not testing a live server against real data. A vendor with an excellent MCP behind a customer login will score lower here than one with tidy public docs. I think the trade is worth making because it can be applied consistently to every vendor and re-run every month, but it is a real limit and I would rather state it than imply more than I know.
“None found” does not mean “no MCP.” It means I checked that vendor's own site on that date and found nothing. The method has been wrong before: one vendor was checked three separate times and recorded as having nothing, and a better check later found around fifty tools documented on their own site. Treat a positive finding as solid and an absence as provisional.
“Could not check” means the vendor's site blocks automated requests. That is ordinary enterprise security and not a mark against anyone. It is more common among large vendors than small ones, so this state is disproportionately the household names.
How it counts toward the ranking. MCP Depth & Safety has been published on vendor profiles since September 2026 and counts toward the World Ranking from the November 2026 edition. It is a connectivity signal, not a measure of AI capability, so it is deliberately small: it can add a few points, scaled by how central AI is to the product (§5.2), and it never lowers a score. A vendor with no MCP, or one I could not check, scores exactly as it would if the signal did not exist. That includes products that are themselves the agent and have no reason to ship one. An MCP never earns an AI capability on its own (§5.1): only functionality built into the product does.
6. Editable vs editorial: who controls what
A vendor can claim their entry and edit the factual record. The editorial layer stays with the editor.
6.1 Vendor-editable after claim
Through the claim form and subsequent edit requests, a vendor can update:
- Identity: name, website, CEO, ownership, founded year, funding stage, year, total raised band.
- Footprint: UK presence, operating regions, target market.
- Product: core problem solved, core modules, workflow stages covered, public AI use cases, ledger integrations, ecosystem connectivity, AI Core to Value.
- Commercial: primary user, primary buyer, end user, sales motion, pricing model, partner dependency, growth scale, requires core ledger.
- Category: main category, sub-category (challenge only — admin reviews).
6.2 Challenge-only (admin reviews with reasoning)
- AI Maturity
- Launch Status
- Threat to Incumbents
A vendor submits proposed value plus evidence; admin reviews and either updates the record or rejects with reason.
6.3 Editor-only, never vendor-editable
Limited to fields the public can see on the site:
- Our Perspective: the editorial paragraph on the company page.
- Verified ✓ badge: set by the editor on claim approval.
- Confidence score: computed weekly (see §5.4); not editor-set.
- Market footprint: the UK and US ratings behind the Big 30 (see §4.3). A vendor can send evidence, the same way AI use-case evidence works, but the rating stays mine.
- MCP Depth & Safety: assessed from published documentation (see §5.7). A vendor can send the URL of their MCP server or its documentation and I re-run the check against it, the same way AI use-case evidence works. Vendors supply the link, the assessment stays mine.
A handful of further editorial signals are captured behind the scenes (working notes on threat rationale, internal categorisation, source trail, and so on). Those are not published today and don't sit on the public record.
7. The other classification fields
Brief descriptions; full enum lists live in the Directory filters.
- Workflow stages covered: the steps in an accounting workflow this product touches. Capture, categorisation, reconciliation, approvals, close, consolidation, reporting, variance & narrative, forecasting & planning, audit & assurance, plus adjacent stages like client onboarding, payroll, practice management, statutory & secretarial, tax.
- Core modules: the named features inside the product. A fifty-something-strong list ranging from Bank Feeds & Reconciliation to Agentic Workflow Builder.
- Public AI use cases: the AI capabilities the vendor publicly advertises. Used to validate AI Maturity claims and to power filtering. If the vendor lists capabilities but the product doesn't demonstrate them, the maturity score will not reflect the marketing.
- Requires core ledger: Yes / No / Partial / N/A. Whether the product needs a general ledger underneath it to function.
- Sales motion: Self-serve / Sales-led / PLG / Partner-led / Developer-led / Hybrid.
- Pricing model: Transparent / Tiered-public / Gated-demo / Enterprise-only.
- Ownership: Founder-led / VC-backed / PE-backed / Public / Acquired / Corporate subsidiary / Government.
- UK Presence: Yes / Limited / No / Coming soon. "Yes" means the vendor has real customers and named UK go-to-market motion. "Limited" means UK customers exist but the product is not localised or supported. "No" is no UK footprint today. "Coming soon" is a stated commitment.
8. Research methodology
Three inputs feed every entry:
- AI-assisted desk research from public sources. Initial drafts of every record are produced from web data, product sites, press releases, funding databases, and direct product documentation. AI is used to extract, normalise, and structure. AI does not make editorial calls.
- Primary research through interviews. I have detailed conversations with vendors covering product roadmap, demos, customer base, and AI architecture. Not all vendors respond. Where a vendor has responded, the entry is marked Verified and Confidence reflects recency.
- External views from customers, accountants, and investors I speak to. These rarely show up as a cited source but they materially inform Our Perspective. The Our Perspective paragraph is a composite read; it is not a quote from any single interview.
Where a vendor has not responded, the entry is built from public sources only. Confidence is set Low. Unclaimed entries are clearly marked as such on the site and in the Directory.
Sources are captured internally for every entry. They are not currently published per-vendor (which is a known gap; see §10).
9. Update cadence
- Vendor records: live for anyone signed in. Approved claims and edit requests land within seconds; signed-out pages follow on the next build.
- Confidence scores: recomputed every Monday morning.
- The Big 30: rebuilt on every site build from the current data and the rules in §4.
- Directory rankings: refreshed on every page load.
- Editorial test and market tests: I review them roughly weekly, and on any challenge.
- Report chapters: editorial. They change when the market changes, not when a vendor ships a feature. Expect material revisions every four to eight weeks.
- News ingestion: automated, every Monday morning, with quality gates before anything is published.
- MCP Depth & Safety: re-checked monthly (§5.7).
- The World Ranking: published monthly as a dated edition (§11.2).
- This methodology document: versioned with the date stamp at the top. v2 lands when the AI Maturity rubric hardens, news-watching is automated, and source citations go public.
10. What's wrong with this today, and what I'm doing about it
Things I know are wrong or weak today:
- The Maturity rubric is still calibrating. Edges between 2 and 3 are the hardest call. Disputes are encouraged.
- Sources are not public per-vendor. They will be. The plumbing exists, the surface doesn't.
- Some vendors are out of date. The Confidence score is the honest answer to "how much should you trust this today". A Low-confidence entry is a flag.
- Verified does not yet auto-decay. If a Verified vendor goes 18 months without contact, the badge should retire. In v1 it doesn't. Confidence downgrades instead.
- Threat to Incumbents notes are not public. The score is; the rationale is editor-only today. I want this to be public in v2 so the call is reviewable.
Things I am building toward:
- Structured re-review cadence: every Verified entry gets a touch every 12 months minimum, automated reminders to the vendor.
- Public source trail: per-entry list of where each fact came from, with last-checked date.
- Maturity v2: harder rubric with evidence requirements per level, made auditable.
- Editorial changelog: per-vendor changelog of when Our Perspective was last revised and why.
11. The World Ranking and the Big 30: how the lists are built
There are two different "who's leading" surfaces on the site, and they answer different questions.
11.1 The Big 30 (on the Map)
The Big 30 answers: "which AI accounting software matters most inthis layer of the stack, for buyers in my market?" It's capped at 3 vendors per layer (6 for General Ledger) so no single layer swamps the Map, and it weighs market footprint, AI and company strength, with the full scoring published in §4.4. It comes in Global, UK and US editions (§4.1).
11.2 The World Ranking
The World Ranking (published monthly, top 50) answers a different question: "who's furthest along on real AI capability, full stop, regardless of category?" Every vendor in the report gets a single 0–100 score and is ranked against every other vendor directly, not just within its own category.
The score is built from five ingredients. In the interest of keeping the list resistant to gaming, I publish what goes in, not the exact weighting of each part:
- How mature and central the AI actually is — the AI Maturity rating, plus whether AI is core, partial, or cosmetic to the product (see §5.1 and §5.2).
- How advanced the claimed capabilities are — foundational capabilities (document extraction, categorisation) count for meaningfully less than advanced ones (agentic workflows, autonomous close, tax intelligence). A claim that hasn't been through evidence review yet still counts, but at a discount versus one that has.
- How much of the workflow the product actually covers — breadth across modules and workflow stages (§7).
- How well-evidenced and how visible the listing is — claimed status, Confidence (§5.4), genuine press coverage, and how deeply the vendor is covered in the report itself.
- A structural discount for AI that isn't core to the product — a large, well-known incumbent with a bolted-on AI feature is discounted on the size/coverage-driven parts of the score, so it can't out-rank a smaller AI-native challenger purely by being bigger or better known.
MCP Depth & Safety counts, but only upward. The column appears beside every ranked vendor (§5.7). From the November 2026 edition a strong MCP can add a few points to the 0–100 score, less where AI is not core to the product. Not having one, or not having been checked, costs nothing.
The World Ranking is a general capability ranking. It is deliberately not personalised, and it is not a recommendation for your specific business — for that, see My Stack (§12) or use Ask. Movement (▲/▼) shows change since the previous published edition, once more than one edition exists to compare against.
12. My Stack (the Hub): personalised, not general
Everything above — the Directory, the Map, the Big 30, the World Ranking — is the same for everyone. My Stack is the opposite: it's personalised to you, free with an account, and it's where "what's right for me" actually gets answered rather than "who's leading overall".
My Stack has four views:
- Recommendation: a shortlist filtered to your own profile and the problem you're trying to solve, not a general leaderboard position.
- Saved: track the vendors you're actually using, evaluating, or keeping on the radar — your own working stack, not the site's.
- Watching: live signal (funding, launches, announcements) for vendors you've pinned, so you don't have to keep checking back.
- Compare: side-by-side comparison of your saved vendors, built for the shortlist you're actually deciding between.
The framing adapts to who you are (practitioner, analyst/investor, or other) but the underlying data is the same. If the World Ranking and Big 30 tell you who's leading in general, My Stack is where that gets narrowed down to who's leading for you.
13. How to dispute or correct an entry
Three routes:
- Claim the entry. Use the "Claim this entry" link on any unclaimed company page. Free. You get edit rights on factual fields and a chance to challenge editorial fields with evidence.
- Edit request. If you've already claimed, hit "Edit this entry" on your company page. Goes into the editorial queue.
- Email. hello@atozaiaccounting.com. For anything that doesn't fit the structured forms (a missing vendor, a wrong category, a perspective you think is materially off).
I read everything. I do not always agree.
Versions
- v1.7 · 11 November 2026: the Big 30 rebuilt around market footprint (§4). Each product is rated 0 to 4 in the UK and the US on evidence of real local customers, and the score is now footprint 25, AI 65 and company strength 10. Company strength comes from stated paying customers, not funding. Removed: the AI maturity gate, editorial interest, the hand-set include and exclude flags, and the home-market bonus. Products sold only to enterprises rank after the rest, and Decision & Action now also keeps a payables or receivables slot. Payroll and HR platforms moved to their own category, off the Map.
- v1.6 · 11 November 2026: MCP Depth & Safety now counts toward the World Ranking, as announced in v1.2 (§5.7). It is a small connectivity signal that can only lift a score, scaled by how central AI is to the product. A vendor with no MCP, or one not yet checked, scores as it would without it. Confidence (§5.4) now follows the rule as written: a listing built from public sources only is Low until the vendor claims it or an editor reviews it. AI Maturity 4 needs hands-on verification, such as a live demo. Every vendor new to this edition was reviewed against §5.1 and §5.2 before it was ranked. Earlier editions are not rescored.
- v1.5 · 10 November 2026: the Global Big 30 now requires a vendor to be sold in both the UK and the US, plus one bonus point for each further market area served, up to 5 (§4.3, §4.4). Before this, Global had no market test, so products sold in only one market could take a Global slot.
- v1.4 · 3 November 2026: the Big 30 rewritten (§4). Global, UK and US editions, with a market test for the market editions. A published score balances AI capability, scale and editorial interest, replacing the old sort on AI Maturity, Verified and UK presence. Decision & Action keeps a reporting or planning slot. The Alpha and Waitlist top-up is gone.
- v1.3 · 3 November 2026: AI Maturity levels renamed to match the rest of the site: No AI, Tasks, Workflows, AI-first, Autonomous (§5.1). The criteria for each level and every vendor's score are unchanged.
- v1.2 · 23 September 2026: MCP Depth & Safety added as a published signal (§5.7), shown on the World Ranking but not scored into it until the November edition. News ingestion moved from roadmap to shipped. Access wording corrected throughout: the site is free with an account, so the paid/free split described in v1.1 no longer exists.
- v1.1 · 10 July 2026: added §11 (World Ranking and Big 30 list-building) and §12 (My Stack). What's published is what goes into the World Ranking score, not the exact weighting — see §11.2.
- v1.0 · 17 May 2026: first published methodology. Covers everything above.