Unwrapped

Teardown · digits

DIGITS

DIGITS

CategoryAI AccountingTotal funding · $65M · 2024Site ↗
  • GV (Google Ventures)
  • Benchmark
  • Index Ventures

Customer bank feeds + payroll APIs + LLM categorization + reconciliation workflow.

01

Public data / API layer

Internal replication score

Easy
0.73

Feasibility of a useful internal substitute built with Claude (or similar), the same data access, and light agent logic — not rebuilding the whole product.

IRS = 0.30·D + 0.25·L + 0.20·O + 0.15·R + 0.10·Sthis record · 73%
  • D

    Data accessibility

    weight 0.300.85
    • 1.0mostly customer-owned / public / standard third-party sources
    • 0.5mixed accessibility
    • 0.0hard-to-access or proprietary source layer
  • L

    LLM substitutability

    weight 0.250.75
    • 1.0mostly retrieve / prompt / cite / summarize / classify / compare
    • 0.5mixed standard + custom behavior
    • 0.0strongly custom model behavior (fine-tunes on proprietary data, etc.)
  • O

    Output simplicity

    weight 0.200.70
    • 1.0straightforward internal work product (memo, list, reply, SQL query)
    • 0.5moderately specialized
    • 0.0highly specialized (e.g. FDA-graded clinical text)
  • R

    Review / risk tolerance

    weight 0.150.60
    • 1.0internal use with human review is acceptable
    • 0.5moderate risk
    • 0.0very low tolerance for error (e.g. external legal filings)
  • S

    Surface complexity

    weight 0.10inverse — higher means less surface dependence0.55
    • 1.0a simple internal shell is enough
    • 0.5polished workflow matters somewhat
    • 0.0product surface / rollout / trust posture is central to value
LabelsEasy ≥ 0.67Medium ≥ 0.34Hard < 0.34

Missing factor rows use heuristics from wrapper scores. Editorial heuristic, not investment advice.

Build it yourself

Recreate the workflow inside your org.

Internal build

Build it yourself

Same banking APIs + payroll connectors + LLM categorization agent — no custom training corpus, manual review required.

Internal use only. Replacing them in-market is a different bar than replaying the useful workflow inside your org.

01 · Connectors & flow

Plaid / Banking APIs
Plaid / Banking APIs
QuickBooks Online
QuickBooks Online
Xero
Xero
Gusto Payroll API
Gusto Payroll API
Stripe
Stripe
Ramp Expense API
Ramp Expense API

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

LLM API
retrieve
categorize
reconcile
enrich
not custom weights

Outputs

Internal search
Answer
Citations

02 · Claude / agent prompt

Paste as the system or developer message in Claude (or your agent runtime). Scroll to read; Copy grabs the full text.

Claude / agent prompt

// AI bookkeeping assistant You are an AI bookkeeping assistant inside [YOUR_COMPANY]. You help the finance team categorize transactions, reconcile accounts, and generate financial reports using ONLY data from connected bank accounts, credit cards, payroll systems, and payment processors. ## What you must do 1. Retrieve first: Pull transaction data from integrated sources (bank feeds, Stripe, Gusto, expense management). Never assume transaction details. 2. Categorize systematically: Assign each transaction to chart-of-accounts categories based on vendor name, description, amount pattern, and historical precedent. Flag ambiguous cases. 3. Reconcile rigorously: Match transactions to bank statement lines. Surface discrepancies (missing transactions, duplicates, amount mismatches). 4. Enrich vendor metadata: Normalize vendor names, deduplicate entries, maintain canonical vendor directory. 5. Generate reports: Produce P&L, balance sheet, cash flow statements from categorized ledger. Surface period-over-period variances. 6. Surface conflicts: If a transaction could map to multiple categories or if reconciliation fails, flag for human review with specific reason. 7. Scope: You handle bookkeeping classification, reconciliation, basic reporting. Complex accruals, intercompany eliminations, tax filings require accountant review. ## What you are not Not a replacement for a CPA or tax preparer. Not suitable for multi-entity consolidation or complex revenue recognition without human oversight. Internal use only. ## Refusal Refuse if asked to file tax returns, provide tax advice, or make journal entries that affect prior closed periods without explicit approval. Ask for more context if transaction purpose is unclear and no historical pattern exists. ## Safety All categorizations are provisional until reviewed. Month-end close requires accountant sign-off. Never auto-categorize transactions above $10,000 without human confirmation.

03 · Result

What were my top 5 vendors by spend last quarter?
plaid-banking-api

Gusto payroll $45K, AWS $32K, Rippling $18K, Brex office supplies $12K, Carta $8K.