HELM vs Copilot Money. Different operators, different tools.

Copilot Money is one of the best-designed personal-finance apps shipped in the last decade. It won an Apple Design Award. It's gorgeous, fast, and the categorization is genuinely better than Mint's was. We're going to spend most of this comparison saying so. Copilot is the right answer for most operators in most life stages. HELM is the right answer for a small subset of operators in a specific life stage — multi-account, equity-comp-heavy, $1M+ net worth, tax-decision oriented. The honest comparison is about which subset you're in.

What Copilot does brilliantly

Copilot Money is an iOS-first (now also macOS, Android in beta) personal finance app focused on day-to-day spend tracking, budgeting, and net-worth visualization. It connects to your accounts via Plaid, auto-categorizes transactions with a model that outperforms most competitors, and presents the result in a UI that's genuinely beautiful. The pricing is around $13/month or $95/year — meaningful but not painful for the audience it serves.

The audience Copilot serves well: operators who want their daily money picture in one app, who do most of their spend on cards (so transaction categorization is the dominant signal), and who don't have multi-decade tax planning as the dominant decision driving their financial life. That's most people. Copilot is right for most people, and the team behind it deserves credit for shipping a product that earns its category-leading position.

Things Copilot does that HELM doesn't and won't:

• Auto-categorized transactions, daily. Plaid-pulled, ML-categorized, manually correctable. The ongoing visibility into spend by merchant + category is the core feature, and it's excellent.
• Cashflow forecasting. "You'll have $X at the end of the month at current burn rate" is the kind of question Copilot is built for. HELM doesn't track transaction-level data and so has no view into burn rate.
• Subscription tracking. Identifies recurring charges, surfaces price increases, helps cancel. Specific feature, well-executed.
• iOS-native experience. Genuinely beautiful interactions, strong widget support, designed for thumb-driven daily check-ins. HELM is a PWA — works everywhere, but doesn't aim for "best iOS app" status.

Where the architectures split

Copilot uses Plaid (or, for some institutions, Yodlee or MX) to authenticate to your bank and brokerage accounts. The aggregator stores a long-lived credential equivalent. The pros and cons of that architecture are a whole pillar by themselves — see the aggregator problem for the full version. Short version: aggregator integration is what gives Copilot its real-time auto-sync, and it's also what creates the credential surface that some operators specifically want to avoid.

HELM is manual-first. No Plaid, no Yodlee, no MX. You enter your holdings yourself; we never ask for any brokerage credential. The architectural choice is described in the aggregator problem pillar, the database side is published in our complete data inventory, and the cost (no real-time auto-sync) is named explicitly in the trade.

What HELM does that Copilot doesn't

The features below aren't on Copilot's roadmap because Copilot serves a different audience well. We're not arguing Copilot should add them. We're arguing that the operator who needs them is already on the wrong tool if they're trying to make Copilot do this work:

• Tax Brain. Wash-sale detection across every brokerage in one view (cross-account §1091). Tax-loss harvest opportunities pre-computed. RMD calendar. IRA contribution tracking. QSBS §1202 clock with five-year-mark countdown. AMT/ISO modeling for equity-comp households. None of this is in Copilot, by design — Copilot is a budgeting app.
• Monte Carlo cash-flow simulator. 10,000 sequence-of-returns runs, P10/P50/P90 paths, Box-Muller normal sampling, FI probability surface. The full math is in pillar #6. Operators planning multi-decade horizons need this; daily-spend operators don't.
• Scenario builder. Saved what-if scenarios with named inputs (ISO exercise dates, asset sales, contribution changes) and the resulting projection. Versioned for comparison.
• Document Vault. Encrypted-at-rest storage for tax letters, estate documents, account-opening confirmations. Per-account encryption key. Indexed in the quarterly PDF. Optional — most operators upload nothing — but useful for the surviving-spouse use case.
• Banker-grade quarterly PDF. The artifact you forward to your CPA, CFP, estate attorney, or family. Page-by-page spec is in pillar #9.
• Ask HELM. AI specialist trained on tax code and FI math, with persistent saved threads. Always ends in a CPA-disclaimer because we are software, not advisors.

Direct comparison — feature by feature

Who should pick which — said directly

Pick Copilot if: Your dominant financial question is "where is my money going week to week, and am I on track for my month/quarter spend goal." You want a beautiful daily app. You're comfortable with the Plaid aggregator model. Your portfolio doesn't have multi-decade tax planning as the dominant variable. This describes most operators in their 20s–40s in W-2 careers without significant equity comp.

Pick HELM if: Your dominant financial question is "what's the right tax-aware decision this quarter on my multi-account portfolio with [vesting equity / QSBS clock / inherited IRA / multi-state exposure / business-sale planning]." You don't want any aggregator vendor between you and your accounts. You'd rather re-enter holdings quarterly than have transaction streams pulled daily. Your CPA bill is north of $3K/year and the marginal value of a tax-aware decision tool exceeds the price gap.

Pick both if: You're an HNW operator who also wants daily-spend visibility — Copilot for the daily layer (budgeting + cashflow + categorization), HELM for the quarterly layer (tax + portfolio + scenarios + PDF). Some of our operators do this and it works well; the two tools occupy genuinely non-overlapping jobs-to-be-done. The cost of running both is around $1,050/year combined, which is less than the difference between a $400/hour CPA finding one wash-sale early and not.

Where Copilot wins flat-out

We'll be specific about where Copilot is straightforwardly the better tool, because we don't want operators on HELM who'd be better served by Copilot:

• If you're under $250K net worth and most of your assets are in a single 401(k) plus a checking account. The marginal value of HELM's tax + Monte Carlo + scenario depth is small at this scale; Copilot's daily-spend visibility is high-value. Stay on Copilot. Come back to HELM when your portfolio compounds into the seven figures with multiple accounts.
• If you find yourself opening your finance app daily. HELM's quarterly cadence will frustrate you. Copilot is built for the daily check-in habit, and that habit can itself be financially healthy if it keeps you connected to your spend.
• If beautiful iOS-native experience is genuinely important to you. HELM is a PWA. It works on every platform; it doesn't aim for "this is a beautifully-crafted iOS app" status. Copilot does, and it's earned that status.
• If you don't have meaningful equity-comp complexity. The Tax Brain features in HELM are most valuable when you have ISOs, NSOs, ESPPs, RSUs, QSBS-eligible founder stock, or multi-account positions where wash-sales actually trigger. Without those, HELM is over-tooled for your use case.

The honest pricing argument

HELM Founding is roughly 10× the price of Copilot Money. That's a real gap and we're not going to dress it up. The pricing math is the same as the Tiller comparison: at NW levels under $1M without significant equity comp, the gap is not justified. At $2M+ with multi-account complexity and a CPA you pay $400+/hour, a single avoided wash-sale or a single QSBS clock that you actually track instead of forgetting pays for HELM for a decade. The pricing is set so that a single substantive Tax Brain insight covers the cost. Operators below the relevant complexity threshold should not be on HELM. We mean that — the founding-25 cohort is sized for fit, not for filling.