Pilot vs Kick

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Kick
   Pilot~partialprobed4/10

   A probe confirms Pilot serves an llms.txt file at HTTP 200, so an agent can indeed be pointed at it — but the content shown is minimal (just entity/category metadata, no structured docs or API references), and other agent-doc formats (docs-md, openapi) return 404. Missing for 10: substantive llms.txt content beyond basic metadata, markdown docs mirror, and any first-party statement about agent-oriented documentation strategy.

   • [probe] “PROBE llms.txt: HTTP 200 at https://pilot.com/llms.txt # Pilot [Entity: Pilot] [Category: Professional Services] [Subcategory: Acco…”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   Kick✓fullprobed8/10

   A live llms.txt index exists at docs.kick.co/llms.txt (HTTP 200, confirmed by probe) with markdown mirrors and a documented ask-query interface, plus a real MCP JSON-RPC endpoint for docs search, giving agents multiple ways to consume agent-oriented documentation. missing for 10: this is a GitBook platform surface rather than a Kick-built capability, and there's no independent (non-vendor) corroboration of agents actually using it successfully.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.kick.co/llms.txt # Kick Docs ## Business Owners - [Kick Docs for Business Owners](https://docs.ki…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Pilot—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Kick—none0/10

   No evidence of an API, CLI, or headless automation surface for actual Kick operations: OpenAPI/swagger probes all 404, and the only live MCP endpoint found is a GitBook docs-search server, not a Kick account/ledger API. The single 'MCP/CLI' mention on the pricing page is a bare link with no supporting documentation of scriptable/CI-usable functionality.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [claimed-docs] “MCP/CLI”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round drawn
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with no evidence of any MCP server offering; docs mention integrations (Bill.com, Stripe, Gusto) but nothing about AI agent connectivity via MCP, and API/openapi probes returned 404s.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”

   proof ↗⚑ flag

   Kick—none0/10

   The only MCP endpoint found is a generic GitBook platform docs-search server (serverInfo "mcp-typescript server on vercel"), explicitly noted as serving documentation, not Kick account data or ledger actions — not an official Kick-built MCP server. Kick's documented AI workflow instead routes through Google Sheets exports for LLMs, with no first-party MCP server for agent access to financial data or actions.

   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”

   proof ↗⚑ flag

4. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Pilot—none0/10

   No evidence of a public API for Pilot; OpenAPI/swagger probes all returned 404 and no docs mention an API for driving the product programmatically. Pilot is a human-service accounting/bookkeeping product with integrations, not an API-driven platform.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   Kick—none0/10

   No documented public API for driving Kick itself was found: an OpenAPI/API probe returned 404s everywhere, and the only working MCP endpoint is explicitly a GitBook docs-search server that 'serves documentation, not Kick account data or ledger actions.' The AI integration path is one-way reporting into Google Sheets for LLMs to read, not a programmatic API to act on the product.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”

   proof ↗⚑ flag

5. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Pilot—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Kick—none0/10

   No evidence of any API credential system, scoped tokens, OAuth grants, or agent-specific permission levels for Kick's product/account data—only role-based access control for human team members and a documentation-search MCP endpoint unrelated to account access. No mention of issuing least-privilege API keys or credentials for AI agents to act on a user's financial data.

   • [claimed-docs] “Kick uses role-based access control so you decide exactly who can see and do what in your workspace.”
   • [claimed-docs] “"All data transmitted to and from Kick is encrypted in transit using TLS. Data at rest is encrypted using AES-256... Kick connects to your f…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”

   proof ↗⚑ flag

6. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with no evidence of any official SDKs; probes for API/OpenAPI specs returned 404s, and no docs mention developer SDKs.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   Kick—none0/10

   There is no evidence of an official Kick SDK: the OpenAPI/Swagger probe returned 404 on all candidate paths, and the only MCP endpoint found (kick-probe-3) is GitBook's generic docs-search MCP server, not a Kick-built API/SDK — it serves documentation, not account or ledger data. AI workflows are routed indirectly through Google Sheets exports rather than a programmable SDK.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”

   proof ↗⚑ flag

7. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Pilot—none0/10

   No evidence of any webhook subscription capability or event API; Pilot is an accounting/bookkeeping service and probes show no OpenAPI or developer API surface exists.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   Kick—none0/10

   No evidence anywhere in the pack of a webhooks feature or event subscription mechanism for Kick account/ledger data; the only outbound integrations mentioned are docs-search MCP (GitBook platform) and Google Sheets sync, neither of which is a webhook subscription API.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Pilot~partialclaimed4/10

   Pilot's marketing mentions 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead' (pilot-docs-7), which points to some AI-generated insight capability inside the product, and scenario/cash-flow modeling features (pilot-docs-8, pilot-docs-21) suggest similar analytical output, though these are framed as human CFO-delivered rather than explicitly AI-driven. There is no independent/hands-on corroboration of the AI feature actually working, and community reviews focus on bookkeeping accuracy/time savings rather than AI insights. Missing for 10: detailed documentation of the AI feature's scope/accuracy, independent user testimony specifically about the AI insights, and clarity on whether insights are AI-generated vs. human-analyst-generated.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”
   • [claimed-docs] “Model cash flow scenarios Know if you can afford new hires well before you make the offers.”
   • [claimed-docs] “Know if you can afford new hires well before you make the offers.”
   • [claimed-docs] “Track company expenses in real time Find the $2,000/month you didn't know you were wasting.”
   • [claimed-docs] “Find the $2,000/month you didn't know you were wasting.”

   proof ↗⚑ flag

   Kick~partialprobed4/10

   Kick documents AI categorization of transactions (auto-labeling ~97% on first pass, confidence-gated, learns from corrections) and real-time P&L updates from that AI action, which is a form of AI acting on user data. However, this is transactional automation, not explicit 'insights and suggestions' (e.g., anomaly flags, forecasts, recommendations) surfaced inside the product itself; the only place data is 'reasoned over' by AI (Gemini/Claude/ChatGPT) is via export to Google Sheets, which is outside the core product UI. Missing for 10: in-app AI-generated insights/recommendations dashboard, proactive suggestions beyond categorization, and evidence of AI reasoning happening natively within Kick rather than via Sheets/GitBook docs-search surfaces.

   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.kick.co/llms.txt # Kick Docs ## Business Owners - [Kick Docs for Business Owners](https://docs.ki…”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Kick
   Pilot—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Kick~partialprobed4/10

   Kick automates categorization, transfer matching, reconciliation checks, and rule-based overrides continuously in the background (kick-supp-categorization, kick-supp-reconciliation, kick-docs-7), which is a form of autonomous background automation for bookkeeping tasks. However, this is limited to Kick's own fixed bookkeeping pipeline, not a general-purpose, user-configurable automation/agent framework that an AI-native user could set up for arbitrary autonomous tasks. missing for 10: evidence of user-defined autonomous workflows/agents beyond built-in categorization rules, a scheduling/trigger system for custom automations, or an automation builder — none is documented; MCP surfaces found are docs-search only, not action-capable agents.

   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “Rules let you tell Kick exactly how to handle specific transactions - overriding AI categorization with your own logic.”
   • [claimed-docs] “"Reconciliation is the process of comparing your transactions in Kick against your actual bank or credit card statements to confirm everythi…”
   • [claimed-docs] “"The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, an…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Kick
   Pilot~partialclaimed3/10

   Pilot's pricing page mentions an AI feature offering 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead,' which is a thin, single-mention hint of an in-product AI assistant capable of some task-like actions (scenario modeling). There's no further documentation on scope, autonomy, or how tasks are delegated to it, and community evidence focuses on human bookkeepers/CFOs rather than the AI assistant. Missing for 10: detailed documentation of the AI assistant's task-delegation capabilities, independent/hands-on corroboration of it actually performing delegated tasks, and clarity on its scope beyond Q&A.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”

   proof ↗⚑ flag

   Kick~partialprobed4/10

   Kick documents AI automation for bookkeeping (auto-categorization with confidence gating, described as 'self-driving' per llms.txt) and logs AI actions in an audit trail, but this is background automation of a fixed task, not a conversational assistant a user delegates arbitrary tasks to. The actual 'ask an AI' workflow routes through external tools (Gemini/Claude/ChatGPT) reasoning over exported Sheets data, not a built-in assistant inside Kick's own UI. Missing for 10: a native in-product chat/assistant interface, evidence of delegating open-ended tasks (not just categorization) to it, and independent confirmation of this workflow beyond vendor docs.

   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “"The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, an…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.kick.co/llms.txt # Kick Docs ## Business Owners - [Kick Docs for Business Owners](https://docs.ki…”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Kick
   Pilot~partialclaimed3/10

   Pilot's marketing mentions 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead,' implying some natural-language Q&A interface, but there's no evidence of broader natural-language command execution (e.g., initiating actions, workflows) or any API/CLI to support it. missing for 10: evidence of NL commands beyond Q&A, independent/hands-on corroboration, technical documentation of the AI interface, API or programmatic access.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”

   proof ↗⚑ flag

   Kick~partialprobed4/10

   Kick supports AI-native interaction only indirectly: reports sync as live data to Google Sheets so Gemini/Claude/ChatGPT can read, reason over, and even write back to the sheet, and the docs are agent-legible via GitBook's MCP/llms.txt surfaces. But there's no evidence of a native chat/NL command interface inside Kick itself for issuing commands like 'recategorize this transaction' or 'send this invoice' — the MCP endpoint found only serves documentation search, not account actions, and AI categorization is automatic/rule-based rather than user-prompted NL commands. Missing for 10: a first-party NL command interface or agent that can execute ledger/invoicing/bill-pay actions directly from user prompts, and independent corroboration of the write-back capability actually altering Kick data (not just the sheet).

   • [claimed-docs] “Your Kick reports land as live spreadsheet data in your workbook, so Gemini, Claude, or ChatGPT can read and reason over them.”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Pilot—none0/10

   Pilot is an accounting/bookkeeping service with no evidence of any developer API reference or runnable examples; probes for OpenAPI/docs-md all returned 404, and no evidence pack items mention an API reference.

   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   Kick—none0/10

   There's no evidence of an interactive API reference or runnable code examples; probes explicitly show no OpenAPI/Swagger spec exists (all candidate paths 404), and the only 'API-like' surface is GitBook's generic docs-search MCP endpoint, which serves documentation text, not a runnable API reference.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Pilot—none0/10

   Probe explicitly checked common OpenAPI/swagger endpoints and all returned 404, and no documentation mentions a machine-readable API spec. Missing for 10: any published OpenAPI/Swagger spec, API documentation, or developer portal.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   Kick—none0/10

   A direct probe for an OpenAPI/Swagger spec returned 404 on all candidate paths, and no evidence pack item shows a downloadable machine-readable API spec for Kick's own product API; the only machine-readable surfaces found (llms.txt, GitBook MCP) serve documentation, not an API contract.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Pilot—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Kick—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with no evidence of any public API, versioning scheme, or deprecation policy; probes for OpenAPI specs all returned 404s. missing for 10: any public API documentation, versioning scheme, deprecation policy, or developer-facing API references.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   Kick—none0/10

   No evidence of a public, versioned Kick API exists — the openapi/swagger probe returned 404 on all candidate paths, and the only MCP/API-like surface found is GitBook's generic docs-search MCP endpoint, not a Kick-built account/ledger API. There is no mention anywhere in the docs of API versioning schemes or a deprecation policy.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Kick
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service; no evidence describes any bulk-operation or batch-processing capability across items (transactions, invoices, etc.) for AI-native automation. Missing for 10: any mention of bulk edit/import/export tools, batch API operations, or automation-scale item processing.

   ⚑ flag

   Kick~partialclaimed5/10

   Kick's AI categorizes ~97% of transactions automatically and rules apply logic across every matching transaction going forward, and multi-entity transaction splitting affects many items at once — all forms of bulk-scale automation. However there is no documented bulk-edit UI, batch API, or CLI/MCP action surface for an AI agent to programmatically trigger bulk operations across many items on demand. Missing for 10: explicit bulk-select/bulk-edit feature, a programmatic bulk-action API or CLI, and evidence of agent-triggered bulk operations beyond passive AI categorization.

   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “Rules let you tell Kick exactly how to handle specific transactions - overriding AI categorization with your own logic.”
   • [claimed-docs] “For expenses shared across businesses - like rent, software, or insurance - you can split a single transaction across multiple entities by a…”
   • [claimed-docs] “Upload PDF bank statements or CSVs for institutions not supported by Plaid, or to backfill historical data.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Kick
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with dedicated human experts and integrations, but there is no evidence of a rules engine or automation-trigger system letting users define event-based automated actions; features described are AI Q&A and integrations, not user-defined trigger/action rules.

   ⚑ flag

   Kick~partialclaimed6/10

   Kick's documented Rules feature lets users define logic that overrides AI categorization and 'run automatically whenever a matching transaction syncs' — a real event-triggered automation rule engine. However, this is scoped narrowly to transaction categorization events rather than a general-purpose trigger/action framework spanning arbitrary events (e.g., invoicing, bill pay, entity actions). Missing for 10: evidence of rules triggering on non-categorization events, multi-step or cross-feature actions, and any user-facing rule builder UI/API details beyond the single doc description.

   • [claimed-docs] “Rules let you tell Kick exactly how to handle specific transactions - overriding AI categorization with your own logic.”
   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Pilot—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Kick—none0/10

   Kick documents event-driven automation (AI categorization on sync, rules triggered by matching transactions) but no evidence of user-schedulable recurring jobs/workflows (e.g., recurring invoices, scheduled reports, cron-like automation) that an AI-native user could set up and manage.

   ⚑ flag

Ai reconciliation

1. ai-native userHave an agent reconcile a month end-to-end, matching transactions, flagging exceptions, and preparing the close for human review

   weight 3 · round to Kick
   Pilot~partialcommunity3/10

   Pilot's evidence shows human bookkeepers finalize monthly books with integration-driven transaction classification (pilot-comm-1, pilot-docs-18, pilot-docs-26), which is directionally toward automated reconciliation, but there is no evidence of an autonomous agent matching transactions, flagging exceptions, and preparing a close package end-to-end without human bookkeeper involvement. Missing for 10: explicit agentic exception-flagging workflow, evidence of AI (not human staff) doing the matching/reconciliation, and documentation of an automated close-prep output for review.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   Kick~partialprobed5/10

   Kick's AI auto-categorizes ~97% of transactions and gates low-confidence items for manual review, and the product includes month-end period locks and a full audit trail logging AI agent actions — echoing pieces of an end-to-end reconciliation workflow. However, the reconciliation docs themselves describe reconciliation as a process of comparing Kick's records to bank statements without documenting that Kick's AI actually performs the matching/flagging of reconciliation exceptions (as opposed to categorization); there's no evidence of a single agent command that walks through match, flag, and prepare-for-review end-to-end. Missing for 10: documented AI-driven bank-statement matching/exception flagging specific to reconciliation (not just categorization), and a described single-agent workflow that completes a full month-end close autonomously.

   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “"Reconciliation is the process of comparing your transactions in Kick against your actual bank or credit card statements to confirm everythi…”
   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”
   • [claimed-docs] “"The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, an…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.kick.co/llms.txt # Kick Docs ## Business Owners - [Kick Docs for Business Owners](https://docs.ki…”

   proof ↗⚑ flag

Bank feeds

1. founderConnect bank and credit-card accounts so transactions import automatically every day

   weight 3 · round drawn
   Pilot✓fullcommunity7/10

   Pilot's docs and a first-hand customer testimonial confirm bank/credit-card/expense integrations automatically feed transaction data for classification, with real-time account data in the portal, eliminating manual founder bookkeeping work. missing for 10: no explicit list of supported banks, no detail on daily-sync frequency or setup flow, and no independent technical documentation beyond marketing/community claims.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   Kick✓fullclaimed7/10

   Kick's docs confirm bank/credit-card connection via Plaid with automatic transaction sync ('every transaction in Kick comes from a bank feed or an import'), AI categorization triggered 'when transactions sync into Kick', and a PDF/CSV fallback for institutions Plaid doesn't cover. This clearly delivers the core capability, though the exact 'daily' cadence isn't explicitly stated and there's no independent/hands-on corroboration of sync reliability. Missing for 10: explicit statement of daily sync frequency, independent verification of import reliability.

   • [claimed-docs] “"All data transmitted to and from Kick is encrypted in transit using TLS. Data at rest is encrypted using AES-256... Kick connects to your f…”
   • [claimed-docs] “Upload PDF bank statements or CSVs for institutions not supported by Plaid, or to backfill historical data.”
   • [claimed-docs] “"Reconciliation is the process of comparing your transactions in Kick against your actual bank or credit card statements to confirm everythi…”
   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”

   proof ↗⚑ flag

Categorization

1. founderGet automatic categorization suggestions for imported transactions that learn from my corrections

   weight 2 · round to Kick
   Pilot—none0/10

   Evidence shows Pilot's transaction classification is handled by integrations plus human bookkeepers/accountants (pilot-comm-1, pilot-docs-17), not by an AI categorization engine that learns from founder corrections. No documentation describes a self-serve ML suggestion-and-correction loop. Missing for 10: any mention of an AI/ML categorization suggestion feature, evidence of a correction/feedback loop, or founder-facing UI for adjusting categorizations.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   Kick✓fullclaimed8/10

   Kick's docs explicitly state AI auto-categorizes ~97% of transactions on first pass, learns from user corrections, and lets users create Rules that override AI categorization permanently for future matching transactions — directly matching the story's requirement for learning-based categorization suggestions. Confidence gating (low-confidence transactions left uncategorized) further supports a learning/feedback loop. Missing for 10: no independent/hands-on verification of the learning accuracy or how quickly corrections propagate, and no detail on the mechanism (per-vendor vs. global learning).

   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “Rules let you tell Kick exactly how to handle specific transactions - overriding AI categorization with your own logic.”

   proof ↗⚑ flag

Reconciliation

1. accountantReconcile each bank account against the ledger with matched, unmatched, and duplicate transactions surfaced for review

   weight 3 · round to Kick
   Pilot—none0/10

   Pilot's evidence describes bank/tool integrations and automated transaction classification (pilot-comm-1, pilot-docs-17) but never describes a reconciliation workflow that surfaces matched, unmatched, and duplicate transactions for accountant review. Missing for 10: any documentation or user report of a reconciliation screen or matched/unmatched/duplicate transaction handling.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   Kick~partialclaimed6/10

   Kick's docs describe reconciliation as comparing ledger transactions against bank/credit statements to confirm amounts, dates, and flag missing or duplicate transactions, which aligns with the matched/unmatched/duplicate framing in the story. However, there's no detailed evidence of a dedicated UI that explicitly buckets transactions into 'matched,' 'unmatched,' and 'duplicate' categories for accountant review, nor screenshots or workflow steps showing how discrepancies are resolved. Missing for 10: explicit UI/workflow evidence of distinct matched/unmatched/duplicate views, reconciliation report exports, and independent/hands-on confirmation of the review process.

   • [claimed-docs] “Reconciliation is the process of comparing your transactions in Kick against your actual bank or credit card statements to confirm everythin…”
   • [claimed-docs] “"Reconciliation is the process of comparing your transactions in Kick against your actual bank or credit card statements to confirm everythi…”

   proof ↗⚑ flag

Bill management

1. accountantCapture vendor bills, route them for approval, and schedule payments from one workflow

   weight 2 · round drawn
   Pilot~partialclaimed3/10

   Pilot's pricing page lists 'Full accounts payable' as a service line item and mentions integration with Bill.com, implying vendor bill handling, but there is no documented detail on bill capture, approval routing, or payment scheduling mechanics within a single workflow — AP appears to be a done-for-you service rather than a described self-serve workflow. Missing for 10: bill capture/OCR details, approval routing configuration, payment scheduling functionality, and any hands-on/independent confirmation of the AP workflow.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”

   proof ↗⚑ flag

   Kick~partialclaimed3/10

   Kick can 'view and manage' bills synced in real time from Ramp or BILL, but the docs explicitly note Kick does not capture bills natively or execute vendor payments itself — it relies on synced data from external AP tools, and there is no documented approval-routing workflow within Kick. Missing for 10: native bill capture/OCR intake, an in-app approval-routing step, and evidence of Kick itself scheduling/executing payments (currently pass-through from Ramp/BILL).

   • [claimed-docs] “View and manage your bills in Kick, with real-time sync from Ramp or BILL.”
   • [claimed-docs] “AR and AP run through integrations plus native invoicing: "View invoices synced from Stripe, Mercury, and BILL, and create and send invoices…”

   proof ↗⚑ flag

Payables

1. accountantSee accounts payable aging and vendor balances at any point in time

   weight 2 · round drawn
   Pilot~partialclaimed4/10

   Pilot advertises 'Full accounts payable' as a service feature and real-time account data access via its portal, implying some visibility into AP status, but there is no specific mention of AP aging reports or vendor balance tracking at a point in time. missing for 10: explicit AP aging report feature, vendor balance detail/history, point-in-time reporting capability, screenshots or hands-on evidence of AP aging views.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   Kick~partialclaimed4/10

   Kick supports AP-adjacent features — viewing and managing bills with real-time sync from Ramp/BILL (kick-docs-13, kick-supp-invoicing-billpay), a real double-entry ledger (kick-supp-journal-entries), and locked periods that keep historical reports stable so numbers can be trusted 'at any point in time' (kick-supp-locks, kick-docs-14). However, there is no explicit documentation of an AP aging report (e.g., 30/60/90-day buckets) or a vendor-balance summary view — only bill list/sync visibility is evidenced. Missing for 10: dedicated AP aging report, vendor balance summary/report, and evidence of historical point-in-time AP snapshots beyond generic locked-period stability.

   • [claimed-docs] “View and manage your bills in Kick, with real-time sync from Ramp or BILL.”
   • [claimed-docs] “AR and AP run through integrations plus native invoicing: "View invoices synced from Stripe, Mercury, and BILL, and create and send invoices…”
   • [claimed-docs] “Kick is a real double-entry ledger: "Every transaction in Kick - whether it came from your bank, a payroll run, or a bill - generates a jour…”
   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”
   • [claimed-docs] “Reports for locked periods remain accurate and stable.”

   proof ↗⚑ flag

Close process

1. accountantLock closed periods so prior-period numbers cannot change without an explicit reopening

   weight 2 · round to Kick
   Pilot—none0/10

   No evidence in the pack mentions period locking, closing periods, or preventing retroactive changes to prior-period financials; the evidence only covers bookkeeping, tax, CFO, and integration features. Missing for 10: any mention of period-lock/close controls, reopening workflow, or audit trail preventing prior-period edits.

   ⚑ flag

   Kick✓fullclaimed9/10

   Kick documents explicit period locking: an accountant locks a period after review, which 'protects the finalized books for that period from being changed - by anyone, including you,' and locked-period reports 'remain accurate and stable,' implying reopening is required for changes. This directly matches the accountant story of preventing prior-period edits without explicit reopening. Missing for 10: explicit documentation of the reopening workflow/permissions and independent/hands-on confirmation beyond vendor docs.

   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”
   • [claimed-docs] “Reports for locked periods remain accurate and stable.”

   proof ↗⚑ flag

2. accountantRun a month-end close against a checklist that tracks reconciliations, accruals, and review sign-offs

   weight 3 · round to Kick
   Pilot~partialclaimed3/10

   Pilot's monthly bookkeeping service closes books and lets customers communicate on 'outstanding items needed to finalize your books every month' via a portal, implying some close-tracking process, but there is no evidence of an actual checklist artifact tracking reconciliations, accruals, and review sign-offs as distinct trackable steps. missing for 10: explicit reconciliation checklist UI, accrual tracking, and sign-off/approval workflow evidence.

   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   Kick~partialclaimed5/10

   Kick documents core close primitives — reconciliation against bank statements, period locks that finalize books, an audit trail of activity/AI actions, and rules/categorization workflows — which together support month-end close discipline. However, there is no evidence of a dedicated checklist feature tracking accruals as discrete tasks, formal review sign-off workflows, or a consolidated close-status dashboard for accountants. Missing for 10: a documented month-end checklist UI, explicit accrual task tracking, and formal sign-off/approval steps beyond simple period locking.

   • [claimed-docs] “"Reconciliation is the process of comparing your transactions in Kick against your actual bank or credit card statements to confirm everythi…”
   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”
   • [claimed-docs] “"The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, an…”
   • [claimed-docs] “Rules let you tell Kick exactly how to handle specific transactions - overriding AI categorization with your own logic.”
   • [claimed-docs] “"Kick sets up a standard Chart of Accounts when you create your workspace, and you or your accountant can adjust it from there: adding, rena…”

   proof ↗⚑ flag

Collaboration

1. founderInvite my external accountant or bookkeeper with role-scoped access to review and adjust the books

   weight 3 · round to Kick
   Pilot—none0/10

   Pilot's evidence describes its own bookkeeping team communicating with the founder via a portal (docs-18, docs-26) and lets customers keep QuickBooks data so any tax preparer can access it (docs-24), but there is no evidence of a feature to invite an external accountant/bookkeeper into Pilot's own system with role-scoped permissions to review or adjust books. missing for 10: any documentation of user/role invitation, permission scoping, or external collaborator access controls within Pilot's platform.

   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”
   • [claimed-docs] “Virtually every tax preparer in the US knows how to work with QuickBooks. You’ll have the freedom to choose any tax preparer you want.”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   Kick✓fullclaimed8/10

   Kick explicitly supports role-based access control ('you decide exactly who can see and do what'), lock periods where an accountant can finalize and lock books against changes, a full audit trail of workspace activity, and a dedicated Tax Package/accountant workflow with a marketed accountants page — together enabling a founder to invite an external accountant with scoped access to review/adjust books. Missing for 10: no explicit documentation of granular invite flow or specific role types (e.g., 'accountant' vs 'bookkeeper' role names) and no independent/hands-on confirmation of the invite UX.

   • [claimed-docs] “Kick uses role-based access control so you decide exactly who can see and do what in your workspace.”
   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”
   • [claimed-docs] “"The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, an…”
   • [claimed-docs] “The Tax Package generates a single Excel file with everything your accountant or tax preparer needs to file your taxes - no manual exports, …”
   • [claimed-docs] “We pivoted off QBO completely, and our team now outputs 10x what we used to without adding a single headcount.”
   • [claimed-docs] “Reports for locked periods remain accurate and stable.”

   proof ↗⚑ flag

Data access

1. developerPull the full general ledger and trial balance through a documented API in open formats

   weight 3 · round drawn
   Pilot—none0/10

   No evidence of a documented API for pulling general ledger or trial balance data; probes for OpenAPI/docs endpoints returned 404s and no API documentation is mentioned anywhere in the evidence pack.

   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   Kick—none0/10

   Kick documents a real double-entry ledger, chart of accounts, and journal entries, but there is no evidence of a documented API for exporting the general ledger or trial balance in open formats — the openapi probe returned 404s on all candidate endpoints, and the only 'API'-like surfaces found are a GitBook docs-search MCP server and Google Sheets AI integration, neither of which expose ledger/GL data programmatically.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [claimed-docs] “Kick is a real double-entry ledger: "Every transaction in Kick - whether it came from your bank, a payroll run, or a bill - generates a jour…”
   • [claimed-docs] “"Kick sets up a standard Chart of Accounts when you create your workspace, and you or your accountant can adjust it from there: adding, rena…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”

   proof ↗⚑ flag

Integrations

1. founderConnect my banking, payments, and payroll systems so their activity flows into the ledger automatically

   weight 2 · round drawn
   Pilot✓fullcommunity8/10

   Pilot explicitly integrates with banking, payments, and payroll systems (e.g. Bill.com, Stripe, Gusto, 10k+ integrations) to feed real-time transaction data into the ledger, and community testimonials confirm bank/card/payment integrations auto-handle transaction classification with minimal founder effort. missing for 10: no explicit first-party detail on the breadth/setup process of bank feed connections beyond named partners, no independent audit of integration reliability at scale.

   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “10k+ Integrations”
   • [claimed-docs] “If you use Gusto, we’ve partnered with Gusto to automatically apply the credit, saving you time.”
   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   Kick✓fullclaimed8/10

   Kick connects banking via Plaid (with manual PDF/CSV backfill for unsupported institutions), syncs payment/invoicing data from Stripe, Mercury, Ramp, and BILL, and posts payroll runs directly as journal entries into a real double-entry ledger with automated AI categorization. missing for 10: explicit named payroll provider integrations (e.g., Gusto/Rippling) beyond the generic 'payroll run' mention, and independent third-party corroboration beyond Kick's own docs.

   • [claimed-docs] “Upload PDF bank statements or CSVs for institutions not supported by Plaid, or to backfill historical data.”
   • [claimed-docs] “View invoices synced from Stripe, Mercury, and BILL, and create and send invoices directly from Kick.”
   • [claimed-docs] “View and manage your bills in Kick, with real-time sync from Ramp or BILL.”
   • [claimed-docs] “Kick is a real double-entry ledger: "Every transaction in Kick - whether it came from your bank, a payroll run, or a bill - generates a jour…”
   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “AR and AP run through integrations plus native invoicing: "View invoices synced from Stripe, Mercury, and BILL, and create and send invoices…”

   proof ↗⚑ flag

Migration

1. founderMigrate historical books from another accounting system without losing transaction detail

   weight 1 · round drawn
   Pilot~partialclaimed5/10

   Pilot markets that switching providers is supported and mentions keeping existing QuickBooks account and historical data, implying migration support, but there's no detail on how historical transaction-level detail is preserved or migrated from other systems (e.g., Xero, Wave, spreadsheets) beyond QuickBooks. missing for 10: documented migration process, evidence of no data/detail loss, support for non-QuickBooks source systems, independent confirmation of successful migrations.

   • [claimed-docs] “Whether you’re starting fresh or switching providers, your dedicated accounting expert is with you from day one handling onboarding, underst…”
   • [claimed-docs] “Keep your existing QuickBooks account and historical data”
   • [claimed-docs] “Whether you're starting fresh or switching providers, your dedicated accounting expert is with you from day one handling onboarding, underst…”
   • [claimed-docs] “Whether you’re starting fresh or switching providers, your dedicated accounting expert is with you from day one handling onboarding”

   proof ↗⚑ flag

   Kick~partialclaimed5/10

   Kick documents CSV/PDF backfill for historical data and offers a paid 'Advanced' tier with dedicated 'migration support,' plus a customer testimonial about switching off QBO — suggesting migration is a supported workflow. However, there's no documentation of how transaction-level detail, historical journal entries, or opening balances are preserved during a full accounting-system migration. Missing for 10: detailed migration/import methodology, evidence of transaction-level fidelity (e.g., historical journal entries, categorization history) surviving migration, and independent corroboration beyond one testimonial.

   • [claimed-docs] “Upload PDF bank statements or CSVs for institutions not supported by Plaid, or to backfill historical data.”
   • [claimed-docs] “We pivoted off QBO completely, and our team now outputs 10x what we used to without adding a single headcount.”
   • [claimed-docs] “Published plan table: "Free — $0/mo — 1 entity, up to 250 transactions/year, core features; Basic — $40/mo — 1 entity, unlimited transaction…”

   proof ↗⚑ flag

Invoicing

1. founderCreate and send invoices with online payment options and see when they are viewed and paid

   weight 3 · round to Kick
   Pilot—none0/10

   Evidence only shows Pilot offers 'full accounts receivable' as a bookkeeping service item, but there is no mention of self-serve invoice creation, online payment collection, or view/paid tracking features for founders—Pilot is a done-for-you bookkeeping service, not an invoicing tool. Missing for 10: invoice creation UI, online payment processing, read-receipt/paid-status tracking evidence.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”

   proof ↗⚑ flag

   Kick~partialclaimed5/10

   Kick lets founders create and send invoices directly and also view invoices synced from Stripe, Mercury, and BILL, giving AR visibility; but the docs describe invoicing as largely a sync/view layer for AR (no native online payment collection is documented, and there's no mention of payment-status tracking like 'viewed' or 'paid' timestamps within Kick itself — that likely happens on the connected platform, not in Kick). missing for 10: documented online payment collection built into Kick-issued invoices, and explicit view/paid status tracking or notifications within Kick's own invoicing UI.

   • [claimed-docs] “View invoices synced from Stripe, Mercury, and BILL, and create and send invoices directly from Kick.”
   • [claimed-docs] “AR and AP run through integrations plus native invoicing: "View invoices synced from Stripe, Mercury, and BILL, and create and send invoices…”

   proof ↗⚑ flag

2. founderSet up recurring invoices and automatic payment reminders for overdue customers

   weight 2 · round drawn
   Pilot—none0/10

   Evidence mentions 'Full accounts receivable' as a service but nothing about recurring invoicing or automated overdue payment reminders specifically. Pilot is positioned as a bookkeeping/accounting service, not an invoicing tool with these automation features documented anywhere in the pack.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”

   proof ↗⚑ flag

   Kick—none0/10

   Kick's docs confirm basic invoicing (viewing synced invoices from Stripe/Mercury/BILL, and creating/sending invoices directly from Kick) but there is no mention anywhere in the evidence of recurring/repeating invoice schedules or automated overdue-payment reminders. missing for 10: recurring invoice scheduling, automatic overdue payment reminder/dunning workflow.

   • [claimed-docs] “View invoices synced from Stripe, Mercury, and BILL, and create and send invoices directly from Kick.”
   • [claimed-docs] “AR and AP run through integrations plus native invoicing: "View invoices synced from Stripe, Mercury, and BILL, and create and send invoices…”

   proof ↗⚑ flag

Receivables

1. accountantTrack accounts receivable with aging reports and per-customer balances

   weight 2 · round to Kick
   Pilot~partialclaimed4/10

   Pilot's pricing page lists 'Full accounts receivable' as a service offering, confirming AR management is part of the product, but there is no evidence of specific features like aging reports or per-customer balance tracking/reporting in the evidence pack. missing for 10: documentation of aging reports, per-customer balance views, AR-specific dashboards or reports, and independent/hands-on confirmation of these features.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”

   proof ↗⚑ flag

   Kick~partialclaimed5/10

   Kick supports AR via invoices synced from Stripe/Mercury/BILL and native invoice creation (kick-docs-12, kick-supp-invoicing-billpay), and the Plus plan advertises 'AR & AP' as a feature (kick-supp-pricing), implying some balance tracking exists. However, there is no documented aging report, no explicit per-customer balance/statement view, and AR appears to depend on synced platforms rather than a dedicated native AR module. Missing for 10: documented aging reports (30/60/90-day buckets), per-customer balance ledger or statement view, and any hands-on/independent confirmation of AR reporting depth.

   • [claimed-docs] “View invoices synced from Stripe, Mercury, and BILL, and create and send invoices directly from Kick.”
   • [claimed-docs] “AR and AP run through integrations plus native invoicing: "View invoices synced from Stripe, Mercury, and BILL, and create and send invoices…”
   • [claimed-docs] “Published plan table: "Free — $0/mo — 1 entity, up to 250 transactions/year, core features; Basic — $40/mo — 1 entity, unlimited transaction…”

   proof ↗⚑ flag

Ai ledger

1. ai-native userHave an agent draft and post journal entries via the API and leave them in a review queue for my accountant

   weight 3 · round drawn
   Pilot—none0/10

   No evidence of any API, agent integration, or journal entry review queue functionality; Pilot is a human-service bookkeeping/accounting company with no documented API (openapi probes 404). Missing for 10: any API existence, journal entry draft/post capability, review queue workflow, agent-facing endpoints.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE llms.txt: HTTP 200 at https://pilot.com/llms.txt # Pilot [Entity: Pilot] [Category: Professional Services] [Subcategory: Acco…”

   proof ↗⚑ flag

   Kick—none0/10

   Kick documents journal entries, categorization confidence-gating, rules, and period locks, but there is no evidence of a public API/SDK for agents to draft or post journal entries programmatically, nor any 'review queue' workflow exposed via API. The only discovered API-like surface is a GitBook docs-search MCP endpoint (docs only, not ledger actions), and explicit probes for an OpenAPI spec returned 404s.

   • [claimed-docs] “Kick is a real double-entry ledger: "Every transaction in Kick - whether it came from your bank, a payroll run, or a bill - generates a jour…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”

   proof ↗⚑ flag

Chart of accounts

1. accountantCustomize the chart of accounts with account types, sub-accounts, and class or tag dimensions

   weight 3 · round to Kick
   Pilot—none0/10

   Pilot is a done-for-you bookkeeping/accounting service, so ledger customization is a fair question, but the evidence pack only mentions generic 'custom workflows and reporting' with no mention of chart of accounts structure, account types, sub-accounts, or class/tag dimensions. Missing for 10: any documentation of COA setup, account type hierarchy, sub-account creation, or class/tag dimension tagging controlled by the accountant.

   • [claimed-docs] “Custom workflows and reporting”

   proof ↗⚑ flag

   Kick~partialclaimed6/10

   Docs confirm a standard Chart of Accounts that accountants can add/rename/restructure, and pricing explicitly lists 'classes' as a Plus-tier dimension feature, supporting class-based tagging. However there is no explicit documentation of sub-account/parent-child hierarchies or generic 'tag' dimensions beyond classes, and account-type customization is only implied by 'restructuring' rather than detailed. Missing for 10: explicit sub-account nesting support, explicit account-type editing controls, and tag (non-class) dimension documentation.

   • [claimed-docs] “"Kick sets up a standard Chart of Accounts when you create your workspace, and you or your accountant can adjust it from there: adding, rena…”
   • [claimed-docs] “Published plan table: "Free — $0/mo — 1 entity, up to 250 transactions/year, core features; Basic — $40/mo — 1 entity, unlimited transaction…”

   proof ↗⚑ flag

Journal entries

1. accountantPost manual journal entries with balanced debits, credits, and supporting memos

   weight 3 · round to Kick
   Pilot—none0/10

   Pilot's evidence describes a done-for-you bookkeeping/CFO service built on QuickBooks with dedicated experts handling books, but there is no mention of any interface for accountants to post manual journal entries with debits/credits and memos. Missing for 10: any UI or workflow for manual JE creation, debit/credit balancing, or memo attachment.

   • [claimed-docs] “Keep your existing QuickBooks account and historical data”
   • [claimed-docs] “Virtually every tax preparer in the US knows how to work with QuickBooks. You’ll have the freedom to choose any tax preparer you want.”
   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”

   proof ↗⚑ flag

   Kick~partialclaimed5/10

   Kick documents a genuine double-entry ledger where every transaction generates a journal entry with debit/credit sides, plus a chart of accounts accountants can adjust, supporting the underlying ledger mechanics. However, the evidence describes journal entries as system-generated from transactions/payroll/bills, not explicit manual entry creation by an accountant with supporting memos. Missing for 10: explicit documentation of manually creating/posting a journal entry, memo/description fields on manual entries, and confirmation entries must balance before posting.

   • [claimed-docs] “Kick is a real double-entry ledger: "Every transaction in Kick - whether it came from your bank, a payroll run, or a bill - generates a jour…”
   • [claimed-docs] “"Kick sets up a standard Chart of Accounts when you create your workspace, and you or your accountant can adjust it from there: adding, rena…”
   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”

   proof ↗⚑ flag

Ai audit

1. ai-native userHave an agent monitor the ledger and flag anomalies in spend or duplicate transactions before the close

   weight 3 · round to Kick
   Pilot—none0/10

   Pilot's evidence covers bookkeeping, tax, CFO services, and AI Q&A on transactions, but there is no mention of an autonomous agent that monitors the ledger, flags spend anomalies, or detects duplicate transactions before close. missing for 10: anomaly-detection feature, duplicate-transaction flagging, any agentic monitoring capability, pre-close audit workflow evidence.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”
   • [claimed-docs] “Track company expenses in real time Find the $2,000/month you didn't know you were wasting.”
   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”

   proof ↗⚑ flag

   Kick~partialclaimed5/10

   Kick's reconciliation workflow explicitly checks for missing/duplicate transactions before close, and AI categorization has confidence-gating that flags low-confidence transactions for manual review, with all actions logged in a full audit trail — covering pieces of anomaly detection. However, there's no documented feature where an agent proactively/continuously monitors the ledger and surfaces anomaly or duplicate alerts ahead of close; the AI-agent angle is limited to external LLMs reasoning over exported Sheets report data, not a native monitoring agent. Missing for 10: a dedicated automated agent/alerting workflow for anomaly and duplicate detection tied to close, and evidence of proactive (vs. manual/scheduled) flagging.

   • [claimed-docs] “"Reconciliation is the process of comparing your transactions in Kick against your actual bank or credit card statements to confirm everythi…”
   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “"The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, an…”
   • [claimed-docs] “Your Kick reports land as live spreadsheet data in your workbook, so Gemini, Claude, or ChatGPT can read and reason over them.”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”

   proof ↗⚑ flag

Audit trail

1. accountantSee a complete audit trail of who changed what and when across the entire ledger

   weight 3 · round to Kick
   Pilot—none0/10

   No evidence in the pack describes any audit trail, change history, or user-activity logging feature within Pilot's platform; the material focuses on bookkeeping services, integrations, CFO advisory, and tax credits. Missing for 10: any mention of audit logs, change tracking, user attribution, or timestamped edit history across the ledger.

   ⚑ flag

   Kick✓fullclaimed8/10

   Kick documents a full Activity tab audit trail logging every transaction change, categorization update, and sync event with timestamp and actor (including AI agent actions), plus period locks that prevent retroactive changes to closed periods and RBAC to control who can act. This directly covers who-changed-what-when across the ledger, including multi-entity workspaces. Missing for 10: no independent/hands-on corroboration of the audit trail in practice, no detail on exporting/filtering audit logs for compliance review, and no explicit confirmation the trail spans across all entities in a multi-entity workspace simultaneously.

   • [claimed-docs] “"The Activity tab is a full audit trail of everything that's happened in your workspace. Every transaction change, categorization update, an…”
   • [claimed-docs] “The Activity tab is a full audit trail of everything that's happened in your workspace.”
   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”
   • [claimed-docs] “Reports for locked periods remain accurate and stable.”
   • [claimed-docs] “Kick uses role-based access control so you decide exactly who can see and do what in your workspace.”
   • [claimed-docs] “If you own more than one business, or have a holding company structure, Kick lets you manage all your entities from a single workspace.”

   proof ↗⚑ flag

Multi entity

1. accountantManage multiple legal entities and produce consolidated financials across them

   weight 2 · round to Kick
   Pilot~partialclaimed4/10

   Pilot's FAQ mentions it can provide consolidated reporting for US entities with foreign subsidiaries, but there is no evidence of multi-entity management for domestic entities, no detail on consolidation methodology, and no independent/hands-on corroboration of this feature. missing for 10: multi-entity dashboard/management capability, domestic multi-entity consolidation support, detailed consolidation workflow, independent verification.

   • [claimed-docs] “We can also provide US entities with foreign subsidiaries with consolidated reporting.”

   proof ↗⚑ flag

   Kick~partialclaimed5/10

   Kick documents multi-entity management from a single workspace, including cross-entity expense splitting (kick-docs-5, kick-docs-6), and pricing tiers explicitly support 'unlimited entities' (kick-supp-pricing). However, there is no explicit documentation of consolidated financial statements or roll-up reporting across entities—only per-entity management and transaction splitting are described. Missing for 10: explicit consolidated P&L/Balance Sheet reporting across entities, evidence of a consolidation feature or combined financial statement output.

   • [claimed-docs] “If you own more than one business, or have a holding company structure, Kick lets you manage all your entities from a single workspace.”
   • [claimed-docs] “For expenses shared across businesses - like rent, software, or insurance - you can split a single transaction across multiple entities by a…”
   • [claimed-docs] “Published plan table: "Free — $0/mo — 1 entity, up to 250 transactions/year, core features; Basic — $40/mo — 1 entity, unlimited transaction…”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round drawn
   Pilot—none0/10

   No evidence of any public API for Pilot; probes for OpenAPI/swagger endpoints all returned 404, and all documentation describes only the human portal/UI and service offerings. missing for 10: any documented API, API parity claims, or developer endpoints.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   Kick—none0/10

   Evidence shows no general Kick API: OpenAPI/swagger probes all 404'd, the only MCP endpoint found is a GitBook docs-search server explicitly noted to serve documentation, not Kick account data or ledger actions, and the AI workflow route is one-directional Google Sheets report export (with limited spreadsheet write-back, not writing into Kick). There is no evidence of programmatic access to core UI actions like categorization, reconciliation, invoicing, or entity management.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”
   • [claimed-docs] “AR and AP run through integrations plus native invoicing: "View invoices synced from Stripe, Mercury, and BILL, and create and send invoices…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Kick
   Pilot—none0/10

   While Pilot mentions QuickBooks compatibility and tax-preparer portability, there is no evidence of a dedicated data export feature, open-format export (CSV/JSON/API), or a documented process to fully extract and leave with all financial data; probes even show no public API/OpenAPI spec.

   • [claimed-docs] “Keep your existing QuickBooks account and historical data”
   • [claimed-docs] “Virtually every tax preparer in the US knows how to work with QuickBooks. You’ll have the freedom to choose any tax preparer you want.”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   Kick~partialclaimed3/10

   Kick offers some export surfaces — a Tax Package that bundles reports into a single Excel file and live Google Sheets sync of reports for AI tools to read — but there is no documented capability to export the full ledger/transactions/journal entries in bulk open formats (CSV/JSON) or a documented account-closure/migration export process; 'migration support' is only mentioned as a paid Advanced-tier perk with no detail. missing for 10: full-data export (transactions, journal entries, chart of accounts) in open formats, documented account closure/migration workflow, evidence of independent/hands-on export testing.

   • [claimed-docs] “The Tax Package generates a single Excel file with everything your accountant or tax preparer needs to file your taxes - no manual exports, …”
   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”
   • [claimed-docs] “Published plan table: "Free — $0/mo — 1 entity, up to 250 transactions/year, core features; Basic — $40/mo — 1 entity, unlimited transaction…”
   • [claimed-docs] “Upload PDF bank statements or CSVs for institutions not supported by Plaid, or to backfill historical data.”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Pilot—none0/10

   No evidence in the pack addresses data residency, region selection, or storage location controls; Pilot is an accounting/bookkeeping service with no mention of infrastructure or data-residency options. Missing for 10: any documentation of data storage regions, residency guarantees, or configurable data location.

   ⚑ flag

   Kick—none0/10

   Kick's evidence pack (security, pricing, integrations, multi-entity docs) never mentions data residency options, regional storage selection, or geographic data controls; only generic encryption-in-transit/at-rest claims are documented.

   • [claimed-docs] “"All data transmitted to and from Kick is encrypted in transit using TLS. Data at rest is encrypted using AES-256... Kick connects to your f…”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Pilot—none0/10

   Pilot is an accounting/bookkeeping service; the evidence pack contains no privacy policy statements, opt-out controls, or AI-training data usage terms addressing whether customer financial data is used to train AI models. This is a fair question given Pilot advertises 'AI answers' features, but no evidence confirms any data-training opt-out or exclusion mechanism. Missing for 10: privacy policy/ToS language on AI training data usage, an opt-out mechanism, or any statement on data handling for AI features.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”

   proof ↗⚑ flag

   Kick—none0/10

   Kick's evidence covers security (encryption, RBAC, audit trail) and AI-based categorization, but there is no documentation of an opt-out for AI/model training on user data, no privacy policy excerpt, and no data-usage/training statement of any kind.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Pilot—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or privacy settings for Pilot's AI features or data; the pack only covers accounting, bookkeeping, and tax service offerings. Missing for 10: any documentation of data retention/deletion controls, privacy settings, or data handling policies for AI or customer data.

   ⚑ flag

   Kick—none0/10

   The evidence covers encryption, RBAC, and audit trails but contains no mention of data retention policies, data export, or account/data deletion controls that a user could invoke. Nothing addresses this axis at all, so it applies but is unaddressed.

   ⚑ flag

Ai insights

1. ai-native userAsk an agent "can we afford X?" and get an answer grounded in live ledger data pulled through the API

   weight 3 · round drawn
   Pilot~partialprobed4/10

   Pilot advertises an in-app AI feature offering 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead,' which aligns with the 'can we afford X' query use case, but there is no evidence this is exposed via an API for external agents to query — the openapi probe returned 404s and no API/agent-integration docs exist. missing for 10: evidence of a public API/endpoint an external AI agent could call, documentation of grounding in live ledger data via API, and any independent confirmation the AI answer feature works as described.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”
   • [claimed-docs] “Model cash flow scenarios Know if you can afford new hires well before you make the offers.”
   • [claimed-docs] “Know if you can afford new hires well before you make the offers.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   Kick~partialprobed4/10

   Kick documents an AI workflow where live report data lands in Google Sheets so Gemini/Claude/ChatGPT can read and reason over it, which could support a question like "can we afford X?", but this runs through a spreadsheet bridge, not a genuine public ledger API — probes show openapi/swagger endpoints all 404, and the only live MCP endpoint found serves GitBook documentation search, not ledger data or account actions. Missing for 10: a documented public API or account-scoped MCP server exposing live ledger data directly to agents, and any evidence of natural-language affordability Q&A being answered from it.

   • [claimed-docs] “The documented AI workflow routes through Google Sheets: "Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets... Your K…”
   • [claimed-docs] “Your Kick reports land as live spreadsheet data in your workbook, so Gemini, Claude, or ChatGPT can read and reason over them.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.kick.co/openapi.json, https://docs.kick.co/swagger.json, https://docs.kick.co/api/opena…”
   • [probe] “PROBE mcp-docs (2026-09-16): keyless JSON-RPC initialize to https://docs.kick.co/~gitbook/mcp completes a real MCP handshake (HTTP 200, prot…”
   • [claimed-docs] “The docs are agent-legible via GitBook: a full llms.txt index, .md markdown mirrors on every page, and a documented dynamic query interface …”

   proof ↗⚑ flag

Custom reports

1. accountantBuild custom reports filtered and grouped by class, location, or tag dimensions

   weight 2 · round drawn
   Pilot—none0/10

   Evidence only mentions generic 'custom workflows and reporting' (pilot-docs-10) with no mention of class, location, or tag dimension filtering/grouping capabilities typical of QuickBooks-style reports; missing for 10: any documentation of dimension-based (class/location/tag) filtering or grouping in reports.

   • [claimed-docs] “Custom workflows and reporting”

   proof ↗⚑ flag

   Kick—none0/10

   Evidence only shows that the Plus plan includes 'classes' as a feature label in pricing (kick-supp-pricing), but there is no documentation of a report builder that lets users filter/group by class, location, or tag dimensions, nor any mention of 'location' or 'tag' dimensions at all. Missing for 10: documented custom report builder UI, filter/group-by controls, evidence of location dimension, evidence of tag dimension.

   • [claimed-docs] “Published plan table: "Free — $0/mo — 1 entity, up to 250 transactions/year, core features; Basic — $40/mo — 1 entity, unlimited transaction…”

   proof ↗⚑ flag

Statements

1. founderGenerate an accurate P&L, balance sheet, and cash-flow statement for any period on demand

   weight 3 · round to Kick
   Pilot~partialcommunity5/10

   Pilot's bookkeeping and CFO service pages reference real-time account data, custom workflows/reporting, and budget-vs-actuals/scenario planning, implying standard financial statements are produced as part of monthly bookkeeping, and community reviews confirm books are kept accurate and up to date. However, no evidence explicitly confirms generation of a P&L, balance sheet, and cash-flow statement for any arbitrary period on demand. Missing for 10: explicit documentation of the three core statements, confirmation of on-demand/any-period generation (vs. standard monthly close), and independent verification of statement accuracy/timeliness.

   • [claimed-docs] “Custom workflows and reporting”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Custom financial model with strategic insights Budget vs actuals variance analysis Scenario planning model”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”
   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [community] “Pilot customer here; they are amazing. It's pretty different from a regular bookkeeper largely in that Pilot is super accurate and timely. M…”

   proof ↗⚑ flag

   Kick~partialclaimed6/10

   Kick's docs show a real double-entry ledger with live P&L and Balance Sheet organized by Chart of Accounts, updating in real time as transactions are categorized, plus period locking that keeps historical reports accurate for any locked period (kick-supp-coa, kick-supp-categorization, kick-supp-journal-entries, kick-supp-locks). However, no evidence explicitly confirms a cash-flow statement report or an 'any period on demand' report generator UI — missing for 10: explicit cash-flow statement documentation, evidence of arbitrary custom date-range reporting on demand, and independent/hands-on verification of statement accuracy.

   • [claimed-docs] “"Kick sets up a standard Chart of Accounts when you create your workspace, and you or your accountant can adjust it from there: adding, rena…”
   • [claimed-docs] “"Kick automatically categorizes your transactions and learns from your changes. When transactions sync into Kick, the AI categorizes approxi…”
   • [claimed-docs] “Kick is a real double-entry ledger: "Every transaction in Kick - whether it came from your bank, a payroll run, or a bill - generates a jour…”
   • [claimed-docs] “Period locking is documented: "When your accountant finishes reviewing and closing a period, they lock it. A lock protects the finalized boo…”
   • [claimed-docs] “The Tax Package generates a single Excel file with everything your accountant or tax preparer needs to file your taxes - no manual exports, …”

   proof ↗⚑ flag