The workflow, in plain English
Before: You log into your bank. A list of 100 transactions. You export CSV, import into YNAB, manually categorize the ones it missed, wait for reports.
After: Dassi reads every transaction row directly from the bank page. At the top of your statement, a panel materializes: “Food: $423, Transport: $187, Subscriptions: $89.” A pie chart appears. Your bank didn’t build this feature. Dassi did, using the data already on screen.
Why traditional tools can’t: Budgeting apps require CSV export or API access. Dassi reads the DOM directly — no export, no integration, no sharing your credentials with a third party.
Step-by-step
- Open your bank statement page (while logged in).
- Ask dassi to read the transaction table and categorize spending.
- Review category assignments and correct any ambiguous merchants.
- Export a summary or copy the categorized list into Sheets if needed.
Example prompts to try
- “Categorize these transactions and show a pie chart.”
- “Flag subscriptions and list them with monthly cost.”
- “Show total dining spend for the last 30 days.”
Tips for better results
- Be specific about what you want injected into the page (buttons, filters, a panel, a summary, etc.).
- If the page has multiple sections, tell dassi exactly what to focus on (e.g., “the transactions table” or “the diff for file X”).
- Prefer safe workflows first: draft, summarize, label, and prepare — then take actions (submit, purchase) only after review.