Product teardowns

The moodboard establishes the visual register. This document is the operating layer: how the products in this category actually behave, product by product, with a specific extraction from each.

Two cohorts, and Lopifi has to serve both:

• The spend/banking layer — Ramp, Mercury, Brex, Slash, Rho, Navan, Bill. Where money moves. Consumer-grade polish, high-frequency use, strong opinions about the primary action.
• The accounting layer — Puzzle, Digits, Numeric, FloQast, Campfire, Rillet, Xero, QBO, NetSuite. Where money is recorded. Dense, workflow-heavy, historically ugly, and where the biggest design opportunity sits.

The pattern that recurs across every good product here: make the core action obvious for one specific role, show the numbers competitors hide (fees, rates, limits), and treat deliberate friction in high-stakes flows as a feature. That sentence is close to a summary of this entire design system.

Cohort 1 — Spend & banking

Ramp

The category leader on product design, and the clearest model for how a finance UI should think.

What it does that matters:

• Leads with the exception, not the aggregate. The dashboard's job isn't "here's your spend", it's "here are the four things that are wrong". Anomalies, policy violations, duplicate vendors, unused subscriptions.
• The table is the hero surface. Ramp invests the same craft in row density, column hierarchy, and bulk selection that most products spend on a marketing hero. Transaction review is the product.
• Bulk operations are first-class. Select 40 transactions, categorize them, create a rule from the pattern. Not a power-user escape hatch — the main path.
• Savings framed as a product outcome. Every screen quantifies what it saved you.
• AI suggestions with a visible basis — "coded to Software because the last 6 charges from this vendor were", not an opaque confidence score.

Lopifi takes:

• AnomalyCard in the core catalog, and no generic "welcome back" hero anywhere.
• BulkActionBar and CategoryPicker, with rule creation inline from a single transaction and a match-count preview.
• Suggestions always show their basis. Encoded as a rule in icons & microcopy and in ReconciliationView's match suggestions.
• The transaction table gets the same design budget as the balance card.

Lopifi refuses:

• Marketing-grade motion inside the product. Spend review is a hundreds-of-times-a-day task; the frequency law makes it near-motionless.
• Framing every number as a saving. Accounting has to present neutral facts, including bad ones.

Mercury

The design benchmark. Recognizable without a logo — which is the highest compliment a design system gets.

What it does that matters:

• Accent scarcity as a discipline. 16 structural tokens, 2 brand tokens. One cobalt, spent only on the primary action.
• Decorative blues that never touch a button. Scenery and affordance are strictly separated.
• A custom typeface at an unusual weight (480) — confident without shouting.
• Leads with one trusted number. The balance is the page.
• Onboarding that finishes. Account opening completes in one sitting, and the product doesn't nag afterwards.

Lopifi takes: the one-accent law · the 16:2 structural-to-brand token ratio · the decoration/affordance separation · one trusted number per surface. All of it is in color.

Lopifi refuses: dark-first. Our users read dense numeric tables for eight hours next to a spreadsheet, and often print. Light-first, dark as a full peer.

Also refused: depending on a proprietary display face. The taste has to survive on Inter + Geist Mono, which is a harder constraint and a better one.

Brex

What it does that matters:

• A brand color so committed it's recognizable without a logo. The orange is the product.
• Policy encoded into the card itself — limits, categories, and vendor restrictions enforced at the point of spend rather than caught at review. Prevention over detection.
• Travel, expense, and card unified in one flow instead of three products.

Lopifi takes:

• Prevention over detection, as a general rule. BillForm runs duplicate detection before save. ExpenseCapture shows policy violations at entry, not at approval. A control that fires at the point of action costs a second; the same control at review costs a week.
• The willingness to commit hard to one accent. Ours is ink blue rather than orange, but the commitment is the same idea.

Lopifi refuses: brand color as a functional color. Brex's orange appears in states as well as branding; we keep semantic and brand strictly separate, so "green" always means "favourable" and never means "us".

Slash

The vertical-specific take: purpose-built accounts and cards for particular business models, with working capital and credit lines layered in.

What it does that matters:

• Purpose-scoped accounts. Money is organized by what it's for — a campaign, a client, a product line — rather than one pooled balance. This is closer to how businesses actually think than a single account is.
• Credit and cash presented in one position view. Available-to-spend includes the line, and it says so.

Lopifi takes:

• The dimension model is the generalization of this. Purpose-scoped accounts are just a dimension on the ledger — see the accounting model. Lopifi supports scoping every balance, statement, and chart by dimension, with the scope always stated in the header.
• Available-to-spend must state its composition when it includes credit: cash and available credit as separate lines that sum, never as one blended figure. Blending them is how a company thinks it has runway it doesn't.

Lopifi refuses: presenting a credit line inside a cash balance. It's a liability, and the balance sheet is unambiguous about that.

Rho

What it does that matters: banking, cards, AP, and expense in one platform with the accounting integration treated as a first-class surface rather than a settings page — sync status, mapping, and errors are visible product, not configuration.

Lopifi takes: bank-connection status (AccountCard) and integration health are product surfaces, not settings. A stale or broken sync silently showing old numbers is the most dangerous state in a finance product, and it gets a prominent component (StaleIndicator) rather than a grey dot in an admin panel.

Bill.com / Navan

What they do that matters:

• Bill — approval workflows as the entire product. The approval inbox, the mobile approve, the audit trail. Unglamorous and correct.
• Navan — policy at the point of booking, so the violation never happens.

Lopifi takes: ApprovalInbox is mobile-first, with the source document rendered inline. Approvals happen on phones between meetings, and an approver who has to click through to see what they're approving stops clicking through. See payables.

Stripe & Wise (restated)

• Stripe owns financial tables and documentation. The currency symbol lighter than the value; consistent decimal places; the docs site is the product.
• Wise owns FX honesty. Every fee itemized, the rate timestamped, "recipient gets" stated. That shape is ConversionBreakdown more or less verbatim.

Cohort 2 — The accounting layer

This is where Lopifi's real opportunity is. The spend layer is beautifully designed and crowded. The accounting layer is where the workflows are hard, the incumbents are twenty years old, and the AI-native entrants are still figuring out what the UI should be.

Puzzle

AI-native GL for startups and the firms serving them. Founder-friendly setup, partner model.

Takes: accountant and operator are two different users of the same data, and the UI should say which it's addressing. Lopifi handles this with density modes and role-scoped surfaces rather than two products — the same ProfitAndLoss is comfortable for a founder and compact for a controller closing books.

Digits

Positions as an "autonomous general ledger" — AI agents in place of bookkeeping labor.

Takes: the ambition to make the ledger self-maintaining is right, and the UI consequence is that every automated action must be inspectable and reversible. Lopifi's rule: an auto-matched item is reviewable and reversible, and auto-categorization rules default to autoPost: false. An automation you cannot inspect is one you cannot defend at audit.

Refuses: full autonomy as the default posture. The accountant is accountable for the numbers; the UI's job is to make their review fast, not to remove them from it. Every suggestion in Lopifi shows its basis and requires a human disposition on anything material.

Numeric, FloQast, BlackLine

The close-management lane: task checklists, account reconciliations, flux review, sign-offs, team status.

Takes — and this is the largest structural borrow in the document:

• The close is a first-class object with a pipeline, owners, gates, and sign-off. CloseStatus, CloseChecklist, AccountTieOut, FluxAnalysis are core catalog, not add-ons. See periods & close.
• Flux review with required explanations on material variances, and unexplained material variances as the reviewer's worklist.
• Sign-off is irreversible, audited, and bound to a version of the numbers.
• Every balance sheet account needs supporting evidence, and an account without any is itself a finding.

Refuses: living beside the ledger as a separate system. In Lopifi the close operates on the same components that render the statements, so a tie-out failure is visible on the balance sheet itself rather than in a parallel checklist tool.

Campfire / Rillet

AI-native ERP for mid-market: multi-entity consolidation, complex close, revenue recognition at scale.

Takes: multi-entity is not an enterprise upsell, it's table stakes, and retrofitting it is brutal. Lopifi makes entityId a required dimension on every transaction from day one, and EntitySelector, ConsolidationView, and IntercompanyMatrix are core — see multi-entity & FX.

Xero & QuickBooks

The incumbents. Enormous installed base, and the products every user is comparing you against whether you like it or not.

Takes:

• Bank reconciliation as the daily habit loop. Xero's rec screen is the most-used screen in small-business accounting, and its "suggest a match, one click to accept" loop is genuinely good. ReconciliationView inherits it.
• The chart of accounts is a user-facing object, not schema. People customize it constantly.
• Integration breadth is a moat, so components must tolerate imported data being messy, partial, and read-only. Hence source: "integration" entries being read-only with a link back.

Refuses:

• Twenty years of accumulated modal-inside-modal navigation.
• Treating mobile as a cut-down viewer. Approvals, receipt capture, and balance checks are genuinely mobile-primary tasks — see responsive & input.
• The single-signed-amount column. Both incumbents blur debit/credit in places, and it costs users the ability to verify.

NetSuite

Takes: the depth of the data model — dimensions, subsidiaries, revenue arrangements, allocation schedules — is genuinely what mid-market needs, and it's why the domain layer in these docs is as detailed as it is.

Refuses: everything about the interface. NetSuite is the standing proof that a correct data model with a hostile UI is a business opportunity, and it is the single biggest reason to build this.

Synthesis

The gap nobody has filled

Every product above is either beautifully designed and shallow on accounting (the spend layer) or deep on accounting and visually neglected (the accounting layer). Numeric and FloQast manage the close but don't own the ledger. Ramp and Mercury own the experience but stop at the bank feed.

Lopifi's position is the intersection: Mercury's restraint and Ramp's table craft, applied to Numeric's close and NetSuite's data model, distributed as components you own.

That's the whole thesis, and it's why the domain layer in these docs is as long as the design layer.