Explore the build library
consultance.ai
Deal Copilot
Build libraryControlsAboutCase studiesBlogBook an audit
consultance.ai

Systems

WorkflowsDeal CopilotPrivate knowledgeFinance automationBuild library

Company

About usCase studiesBlogContact

Start a conversation

Free AI auditfounder@consultance.ai

Teams

Investment bankingCFOs & financePrivate equityPrivate creditReal estateProperty managementProfessional servicesOther industriesAll industries

Legal

Privacy policyTerms of service

Our approach

Audit the workflow.Build in your environment.Hand over a system you own.
Build something useful © 2026 consultance.ai
Build library/Free Personal Finance App With Claude

Finance and data

Free Personal Finance App With Claude

For anyone paying for a budgeting app: install a free open source finance app a startup spent $1 million on, connect Claude, and tie every account, transfer and subscription.

Technical setup4 steps11 prompts
Open the setup guide Discuss an implementation
Finance and data

Start with the guided setup

Follow the setup below in your own workspace. For a demonstration of the prompt-copying process, open the optional walkthrough.

Watch the setup walkthrough
Step 1 · setup
Three minutes, four steps, nothing to install by hand

Claude sets it up for you. You just paste.

Never used Claude? It is free and takes 30 seconds to open. Copy the instruction below, paste it into Claude, and it reads this page and walks you through everything, one question at a time.

  1. Tell Claude how to talk to you

    One tap. It changes how much Claude explains, and how slowly it goes. You can change it any time.

  2. Copy your setup instruction

    A short instruction plus a link to this page lands on your clipboard. First copy asks for your email once. That unlocks every button across the whole library.

  3. Open Claude in a new tab

    Free account, no card, 30 seconds. This tab stays open so you can come back.

    Open claude.ai
  4. Paste, send, and answer one question

    Claude reads this page, asks one question about your work, then guides you step by step until your first output is right. If anything looks wrong, tell Claude what you see, and it fixes it with you.

▸Prefer the full prompt instead of the link? (optional)
Click to copy
I am comfortable copy-pasting and following instructions, but I am not a developer.
There is nothing to install for this one and no commands to type: it all happens inside Claude. If any instruction below implies a Terminal, translate it into the equivalent click path for me instead.
- Plain English. Define jargon the first time it appears.
- One step at a time, then wait for me to confirm before the next one.
- Tell me what success looks like at each step, and diagnose any error before moving on.

Follow the instructions below with those rules applied.

If you can browse the web, open and read this page in full first, it has the complete guide and every prompt you will run (the vault is under the-vault anchor): https://consultance.ai/library/free-finance-app-claude#the-vault . If you cannot open links, tell me and I will paste the page in, do not guess the prompts.

You are the setup concierge for the Free Personal Finance App With Claude pack from consultance.ai. Your job is to get one person from "I heard there is a free finance app" to their first month of money tied and reviewed, calmly, one step at a time.

House rules for you:
- Ask ONE question in your first message. Nothing else.
- Define a term the first time you use it. Docker is a free program that runs apps like this one in a box on your computer. MCP is the connection point that lets Claude read the app. A tied balance means the app's balance matches your bank statement to the cent.
- One step at a time. Wait for them to say it worked before the next step.
- Select Claude Opus 5.5 in the model picker for every unit.
- Never change anything in the app without the person saying yes.

First message, exactly this and nothing more:

"Do you want to install the free app on your own computer (it takes Docker and some typing in a terminal), or start with no install by pasting one month of bank statements into this chat?"

Then route on the answer:

If NO INSTALL:
1. Paste prompt 01, then prompt 02, the fake sample. Match the answer key. If it counts the credit card payment as spending, stop and find out why first.
2. Then paste one month of statements, one account at a time, and run units 05, 06, 08 and 11.

If INSTALL: this is a Terminal install, one command at a time.
1. Ask them to install Docker from its official guide (docs.docker.com/engine/install) and then run docker run hello-world . Success: it prints a hello message.
2. Run prompt 03 step by step, exactly as written. Success: the Sure login screen at http://localhost:3000, and signups set to Closed afterwards.
3. Run prompt 04 in Claude Code on the same computer. Success: claude mcp list shows sure as connected, and the account list matches the bank.
4. Paste prompt 01, run prompt 02, then units 05 to 11 for the first month.

Know these facts and say them when they matter:
- Sure is free and open source (AGPL), kept going by its community. We did not build it and do not run it.
- Claude can change data in the app, so every change is shown first and made only after a yes.
- If port 3000 is already in use, a different program is using it; stop and name it rather than changing files.
- Turn model training off before connecting real accounts. The data stays on the person's computer and their own Claude account.
Step 2 · run it on your data

Step 1 set it up. These 11 prompts do the work.

the vault

The 11 prompts

Grab the whole pack as one file, or tap any prompt below to copy it on its own. Placeholders that look like {{THIS}} get swapped for your own numbers — and if you ran Step 1, Claude fills them in for you.

One .md file · all 11 prompts, numbered, in order · nothing left out.
Click to copy
FREE FINANCE APP WITH CLAUDE: SHARED RULES
Every unit in this pack follows these rules. They are written here once.

1. WHERE TO RUN IT
- The app is Sure, a free open source personal finance app (github.com/we-promise/sure, AGPL licence). It is the community version of an app a startup spent nearly $1 million building before it open sourced it. It runs on your own computer with Docker.
- Claude connects to it through Sure's own MCP endpoint, the connection point Sure documents for AI assistants. Use Claude Code on the same computer: it signs in to Sure with OAuth.
- Before using the Claude app on the web, check Anthropic's own help pages for how its integrations reach a server on your own computer. If it cannot reach it, use Claude Code.
- One statement or a few transactions you can paste: the Claude app in a private Project, without the app. Prompt 02 runs this way.
Model: select Claude Opus 5.5 in the model picker.
Privacy: your money data stays in the app on your computer. What Claude reads goes only to your own Claude account, never to us. Turn model training off before you connect real accounts.

2. BEFORE THE FIRST RUN
First ask what the person wants from their money this year (pay off a card, save for a house, stop leaking on subscriptions), and record it. Then ask, one at a time:
{{NAME}} whose money this is. {{ACCOUNTS}} every account: bank, cards, savings, loans, investments. {{CURRENCY}} the home currency. {{MATERIALITY}} the amount worth a question (default 10.00). {{MONTH}} the month to review.
A missing item gets a plain default, labelled ASSUMED.

3. READ FIRST, CHANGE ONLY WITH A YES
Sure's tools can read and change data. Every unit reads first. A change (a category, a rule, a transfer match, a budget) is shown first as a preview or a dry run when the tool offers one, then made only after the person says yes. Never import, delete or move anything without a yes.

4. STOP RATHER THAN GUESS
- A balance needs a statement that is not imported: name the account and month, mark it OPEN.
- Two figures disagree and nothing in the normal list explains it: show both. Do not pick one.
A stop blocks only the outputs that need the missing input. Everything else still runs.

5. LABELS ON EVERY FIGURE
REPORTED (the statement or the app, with the account and date or page) · CALCULATED (show the arithmetic; a figure calculated from an assumed input says so) · ASSUMED (who set it: the person, or this pack's default) · MARKETING (a claim from a bank or app ad: it makes a question, never a number) · NOT IN SOURCE.

6. THREE FLAG TAGS
- CHANGES THE DECISION: a balance does not tie, or money left that should not have.
- WORTH A QUESTION: only if the answer could move a figure by more than {{MATERIALITY}}.
- EXPLAINED BY CONTEXT: one line under "Checked, normal". Once closed, it stays closed.

7. LOOKS WRONG, IS NORMAL
- A credit card payment from the bank account | it moves money to the card; the card purchases are the spending | not normal when the card's purchases are missing from the app.
- Money moved to savings | a transfer, not spending | not normal when the savings account shows no matching deposit.
- A refund | negative spending in the month it arrives | not normal when no original purchase exists.
- A yearly subscription | one large charge a year | not normal when it repeats inside the year.
- Pending transactions | not yet posted, they can change | not normal when pending for more than 10 days.
- Income lower one month | pay dates fall in different months | not normal when the yearly total drops too.
- Net worth falls with spending flat | an investment price move | not normal when no investment account changed.

8. STANCE
A calm money coach who has done this many times. Most months are normal. Do not shame spending. Find what is wrong, explain what is normal, and let the person decide.

9. HANDOFF (every unit ends with this)
Read (and not read) · Outputs · Checks: pass, fail or not run · Changes made, each with the yes that allowed it · Open items, with the statement needed · Next unit.
Click to copy
TRY THIS FIRST: A 5 MINUTE TEST ON FAKE DATA
Run units 05, 06, 08 and 11 on this sample in chat, as if the app had already imported it. Steps that need the app itself are NOT RUN in this test; say so and go on. Compare your result to the answer key. If one figure does not match, stop and find out why first. One statement is missing on purpose, so you see the pack stop instead of guess.

SAMPLE: October 2026, USD. MATERIALITY 10.00.

CHECKING (statement page 1): opening 4,200.00. 1 Oct salary +5,000.00. 3 Oct rent -1,800.00. 5 Oct transfer to savings -500.00. 10 Oct credit card payment -1,245.00. 12 Oct gym -49.00. 15 Oct 09:14 StreamCo -15.49. 15 Oct 09:14 StreamCo -15.49. Printed closing 5,575.02.

SAVINGS (statement page 1): opening 10,000.00. 5 Oct transfer from checking +500.00. Printed closing 10,500.00.

CREDIT CARD (statement page 1): previous balance owed 1,245.00. 10 Oct payment received 1,245.00. Purchases: groceries 620.00, restaurants 340.00, annual software plan 119.00 (charged every October), store 285.00. 22 Oct refund from the store 60.00. New balance owed 1,304.00.

The account list also shows BROKERAGE. No October statement for it has been imported.

ANSWER KEY
| Check | Expected | Working |
| Checking tie | TIES, 5,575.02 | 4,200.00 + 5,000.00 - 1,800.00 - 500.00 - 1,245.00 - 49.00 - 15.49 - 15.49 = 5,575.02 |
| Savings tie | TIES, 10,500.00 | 10,000.00 + 500.00 |
| Card tie | TIES, 1,304.00 owed | 1,245.00 - 1,245.00 + 620.00 + 340.00 + 119.00 + 285.00 - 60.00 = 1,304.00 |
| Savings transfer | EXPLAINED BY CONTEXT, a transfer | The -500.00 and +500.00 match. Not spending. |
| Card payment | Transfer, not spending | The 1,245.00 paid off last month's card purchases. The trap is counting it as spending, which gives 4,428.98 instead of 3,183.98. |
| October spending | 3,183.98 | Rent 1,800.00 + gym 49.00 + StreamCo 30.98 + card purchases 620.00 + 340.00 + 119.00 + 285.00 - refund 60.00 |
| Refund | EXPLAINED BY CONTEXT | Reduces spending in October. |
| Annual software 119.00 | EXPLAINED BY CONTEXT, yearly | Charged every October. |
| StreamCo twice | WORTH A QUESTION: likely duplicate, 15.49 (it becomes CHANGES THE DECISION if the person has one plan) | Same merchant, same amount, same minute. 15.49 is above the 10.00 materiality. Ask StreamCo for a refund. |
| Net worth, 3 accounts | Start 12,955.00, end 14,771.02, change +1,816.02 | Start 4,200.00 + 10,000.00 - 1,245.00. End 5,575.02 + 10,500.00 - 1,304.00. Proof: income 5,000.00 - spending 3,183.98 = 1,816.02. |
| Brokerage | OPEN: import the October brokerage statement | Net worth is shown for the 3 tied accounts only, and says so. Every check above still runs. |

A run that counts the card payment as spending, calls the refund or the yearly charge a problem, or guesses the brokerage balance, has failed.
Click to copy
<unit name="install-sure">
Follow the shared rules in prompt 01.
What it does: installs Sure with Docker on the person's own computer, step by step, using the project's own commands.
Use when: once, before anything else that needs the app.
Needs: a computer where the person can install software, and Docker. Install Docker from its official guide first (docs.docker.com/engine/install).
Method (one command at a time, wait for each to finish, copy them exactly):
1. Check Docker works: docker run hello-world . Pass: it prints a hello message.
2. Make a folder and go into it: mkdir -p ~/docker-apps/sure then cd ~/docker-apps/sure
3. Download the app's setup file: curl --fail --location --silent --show-error --output compose.yml https://raw.githubusercontent.com/we-promise/sure/main/compose.example.yml
4. Download the settings file: curl --fail --location --silent --show-error --output .env https://raw.githubusercontent.com/we-promise/sure/main/.env.example
5. Make a secret key: openssl rand -hex 64 . Open the file .env and set SECRET_KEY_BASE to that key, and POSTGRES_PASSWORD to a password the person chooses. Keep both safe; a new key later makes stored data unreadable.
6. Start it: docker compose up . Open http://localhost:3000 in the browser. Pass: the Sure login screen.
7. Create the account on the login page. Then in Settings > Self-Hosting > Onboarding, set signups to Closed.
8. Run it in the background: press Ctrl+C, then docker compose up -d , then docker compose ls to see it running.
<trap>Using an example or shared SECRET_KEY_BASE. Sure uses it to protect sessions and encrypt stored keys. Each install makes its own.</trap>
Stop: Docker not installed or not allowed on this computer: stop and say so; prompt 02 still works in chat. Port 3000 already in use: stop and name the program using it; do not change the app's files to work around it without a yes.
Output: the checks passed at each step, then the handoff. Next: connect-claude.
</unit>
Click to copy
<unit name="connect-claude">
Follow the shared rules in prompt 01.
What it does: connects Claude Code to Sure's MCP endpoint and proves the connection with one read-only call.
Use when: once, after install-sure passes.
Needs: Sure running at http://localhost:3000, and Claude Code on the same computer.
Method:
1. Add the connection: claude mcp add --transport http sure http://localhost:3000/mcp
2. Start Claude Code and let it sign in to Sure in the browser when it asks (Sure uses OAuth). Approve access in Sure.
3. Run claude mcp list . Pass: sure is listed and connected.
4. First call, read only: list the accounts with their balances (the get_accounts tool). Compare each balance to the bank's own app or statement.
5. Read the tool list Sure returns. It is the source of truth for what Claude can do; Sure's own docs say so.
<trap>Treating the connection as read only. Sure's tools can also change categories, rules, transfers and budgets. Rule 3 in prompt 01 applies to every one of them.</trap>
Stop: the sign-in fails or the tool list is empty: show the exact error and stop. No other unit uses the app until this passes.
Output: the connection status, the account list with balances, the tool list, then the handoff. Next: load-and-tie.
</unit>
Click to copy
<unit name="load-and-tie">
Follow the shared rules in prompt 01.
What it does: makes sure every account in the app matches its statement, to the cent.
Use when: after connect-claude, and at the start of every monthly review.
Needs: one statement per account for {{MONTH}} (bank, card, savings, loan, brokerage), and the accounts in the app.
Method:
1. List every account in {{ACCOUNTS}} and in the app. Name any account in one list but not the other.
2. For each account: opening + money in - money out = closing, against the printed statement closing.
3. If an account's opening balance in the app is wrong, show the fix with a dry run first (the app's opening balance tool supports one), then make it only after a yes.
4. Import missing statements only with a yes, and only the file the person names.
<trap>A card statement shows what is owed, not what is held. Count it as a minus in net worth.</trap>
Stop: no statement for an account: that account is OPEN for the month. The others still tie.
Output: one line per account (opening, in, out, closing, statement closing, TIES or BREAK), then the handoff. Next: transfers.
</unit>
Click to copy
<unit name="transfers">
Follow the shared rules in prompt 01.
What it does: finds money moved between the person's own accounts and marks it as a transfer, so it never counts as income or spending.
Use when: every month, after load-and-tie.
Needs: the month's transactions in every account.
Method:
1. Find pairs: the same amount out of one own account and into another within 5 days (savings moves, card payments, loan payments).
2. For each pair, show the app's own match candidates and any pending auto match.
3. Confirm a match only after a yes. Reject a wrong auto match the same way.
4. A card payment is a transfer to the card. The spending is the card's purchases.
<trap>Counting a credit card payment as spending. The purchases on the card were already counted, so the month's spending doubles.</trap>
Stop: one side of a transfer is in an account with no statement imported: mark the pair OPEN.
Output: matched pairs, open pairs, changes made with the yes for each, then the handoff. Next: categories-and-rules.
</unit>
Click to copy
<unit name="categories-and-rules">
Follow the shared rules in prompt 01.
What it does: puts every transaction in the right category and writes rules so next month sorts itself.
Use when: every month; rules once, then only for new merchants.
Needs: the month's transactions, the category list and the merchant list from the app.
Method:
1. List uncategorised transactions and transactions in a category that does not fit the merchant.
2. Propose a category for each, with the reason. Change them only after a yes.
3. For a merchant that repeats, propose a rule. Preview it first (how many transactions it would change, with a sample), then save and apply only after a yes.
4. Never let a rule change a transaction the person set by hand.
<trap>A rule that matches too broadly, like every merchant containing "AMZN" as Shopping, when some are a subscription or a refund. Preview before applying.</trap>
Stop: a transaction with no merchant name: leave it for the person, with the date and amount.
Output: changes proposed and made, rules previewed and saved, then the handoff. Next: subscriptions.
</unit>
Click to copy
<unit name="subscriptions">
Follow the shared rules in prompt 01.
What it does: lists every recurring charge, what it costs a year, and the ones to question.
Use when: every month, and before any budget change.
Needs: 12 months of transactions if the app has them, and the app's recurring transactions list.
Method:
1. List every recurring charge: merchant, amount, how often, next date, cost per year (CALCULATED: monthly x 12, weekly x 52).
2. Flag: the same merchant twice in a short time for the same amount, a price that went up, a charge with no use the person can name, and free trials that turned paid.
3. Total the yearly cost of everything flagged.
<trap>Calling a yearly charge a new expense or a price jump. Check last year's same month first.</trap>
Stop: fewer than 3 months of history: list what is there and say the yearly figures are ASSUMED from the months seen.
Output: the subscription table, the flagged list with the yearly saving if cancelled, then the handoff. The person cancels; Claude never does. Next: monthly-review.
</unit>
Click to copy
<unit name="monthly-review">
Follow the shared rules in prompt 01.
What it does: writes the month's review: income, spending by category, budget against actual, and what changed.
Use when: every month, after units 05 to 08.
Needs: the app's income statement and budget for {{MONTH}} and the month before.
Method:
1. Income and spending for the month, with transfers left out. Compare with the month before and the same month last year if the app has it.
2. Budget against actual by category. Show the 3 biggest overruns and the 3 biggest underspends.
3. Explain each big change in one line, testing it against the normal list first.
4. Propose next month's budget changes. Change the budget in the app only after a yes.
<trap>Comparing a 5 paycheck month with a 4 paycheck month and calling it a raise. Check the pay dates.</trap>
Stop: an account with no statement this month: its spending is OPEN and the review says so.
Output: a one page review in plain words, then the handoff. Next: net-worth-and-forecast.
</unit>
Click to copy
<unit name="net-worth-and-forecast">
Follow the shared rules in prompt 01.
What it does: shows net worth and its trend, and forecasts cash for the next 12 months from the recurring income and bills.
Use when: every month, after the review.
Needs: the app's balance sheet, the recurring transactions, and the person's goal from prompt 01.
Method:
1. Net worth: assets minus what is owed, each account listed, and the change since last month.
2. Forecast: starting cash = today's tied cash balances. Add recurring income, subtract recurring bills and the average of the last 3 months of other spending, month by month for 12 months.
3. Show the first month cash would fall below the amount the person wants to keep, if any.
4. Goal: months to the goal at the current saving rate. If the person wants a savings goal in the app, create it only after a yes.
<trap>Starting the forecast from the balance in the app before the accounts are tied. A wrong balance carries through all 12 months.</trap>
Stop: an investment account with no recent statement: its value is OPEN and net worth says so.
Output: the net worth table, the 12 month forecast, the goal line, then the handoff. Next: proof-check.
</unit>
Click to copy
<unit name="proof-check">
Follow the shared rules in prompt 01.
What it does: proves the month's numbers before the person relies on them, from the statements, without reading the earlier summaries first.
Use when: last, every month.
Needs: the statements and the app's figures for the month.
Method:
1. Recompute every account's closing balance from its statement. Difference must be 0.00.
2. Net worth change = income - spending + investment price changes. Money moved into or out of an investment account is a transfer, not a price change. Show the arithmetic. A gap means a missed transaction or a transfer counted as spending.
3. Every transfer pair nets to zero.
4. The forecast's starting cash equals today's tied cash (bank and savings balances that tied in unit 05), if unit 10 has run; if not, this check is NOT RUN.
Only then compare with the earlier units. Any difference is named, with the account and date, and the review is marked BLOCK: do not release it to the person as final until the difference is fixed.
<trap>Reading the review first and then "confirming" it. Recompute first, then compare.</trap>
Stop: a statement missing: that account's check is NOT RUN and the review says so.
Output: the four checks with the arithmetic, PASS or BLOCK with the named difference, then the handoff. PASS can stand beside a NOT RUN check, as long as the NOT RUN is named in the review.
</unit>

From a working build to an operating system.

For anyone paying for a budgeting app: install a free open source finance app a startup spent $1 million on, connect Claude, and tie every account, transfer and subscription.

Path A · free

Run the build independently

The setup rail and every prompt above are free and stay free. The cost is your time, and the risk of wiring it wrong on live data.

Back to the prompts
Path B · done with you

Connect it to your operation

The pack sets up one person's books. We set it up for a family office or a founder's household: every account connected, the monthly review run on a schedule, and the same proof checks used on company books. Reply "wire it" for a 30 minute slot.

Book a build call
data safety

Before you use live numbers

  • • Run last quarter's numbers first. Live data is not a test bed.
  • • Nothing here uploads to us. It runs in your own Claude account, on your own machine.
  • • A named human reviews and signs every output before it reaches a board, lender, or client.
  • • Mask account numbers and names to the minimum the task needs.
the fine print

Straight answers on ownership

Sure is open source under the AGPL licence, a community fork of the archived Maybe Finance app, not affiliated with consultance.ai. The prompt set is authored by consultance.ai. Your data stays on your own computer and in your own Claude tenant; we never see it. Not financial, tax or investment advice.

Bring this workflow into your operation.

Book a build callBack to the library

Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.

Newsletter

New builds, as they ship

One short note when a new build ships: what it does, who it is for, and how to run it in your own Claude.

Free. Three short welcome emails over your first three days, then at most one email a week. Unsubscribe in one click.

More like this

Related builds

All builds
Finance and data
Finance and data

Portfolio Company Reporting Kit

For PE firms to hand to every portfolio company: the monthly package for the sponsor, with management accounts, KPIs, covenants from the credit agreement and 13 week cash, tied before it is sent.

Setup guide
Finance and data
Finance and data

Accretion Dilution Merger Model

For deal teams and corp dev building the buy-side merger model: 12 prompts that run accretion or dilution, the funding mix, goodwill, synergies, and the breakeven price where the deal stops adding to EPS, in an afternoon instead of a two-week associate build.

Setup guide
Finance and data
Finance and data

AI Deal Diligence Prompt Pack

For PE deal teams and corp dev: read a data room and draft the IC memo in Claude with 11 prompts. Reads every contract, ties the financials to source, flags concentration and change of control, and reconciles before the memo. Replaces the associate grind and a chunk of the third party diligence engagement.

Setup guide
Get the free kitBook a call

Share with your workflow owner.

Bring the relevant team into the conversation with the build and setup guide.

Forward by email
in one line

What is Free Personal Finance App With Claude?

Free Personal Finance App With Claude is a finance and data build in the consultance.ai AI Build Library. For anyone paying for a budgeting app: install a free open source finance app a startup spent $1 million on, connect Claude, and tie every account, transfer and subscription. It fits People and families who pay for a budgeting app or rebuild a money spreadsheet every year, and finance professionals who want to run their own books with Claude before they trust it with anyone else's. Setup difficulty is Technical, with 4 plain-English steps.

What does Free Personal Finance App With Claude do?

For anyone paying for a budgeting app: install a free open source finance app a startup spent $1 million on, connect Claude, and tie every account, transfer and subscription.

Who is Free Personal Finance App With Claude for?

It fits People and families who pay for a budgeting app or rebuild a money spreadsheet every year, and finance professionals who want to run their own books with Claude before they trust it with anyone else's.

How hard is Free Personal Finance App With Claude to set up?

Technical to set up — one guided setup instruction covering 4 plain-English steps, plus 11 ready-to-run prompts on the resource page.

How would consultance.ai build this out?

The pack sets up one person's books. We set it up for a family office or a founder's household: every account connected, the monthly review run on a schedule, and the same proof checks used on company books. Reply "wire it" for a 30 minute slot.

What are the licensing terms?

Sure is open source under the AGPL licence, a community fork of the archived Maybe Finance app, not affiliated with consultance.ai. The prompt set is authored by consultance.ai. Your data stays on your own computer and in your own Claude tenant; we never see it. Not financial, tax or investment advice.

Connect this build to your workflow.

Discuss how Free Personal Finance App With Claude fits your systems, controls, and team. We define the integration, review process, and deployment requirements with you.

This build comes from our AI consulting and AI implementation practice — see the full AI in finance guide and how we work with CFO teams.

Book an audit