Read-only by design
Where an account is connected, it is read-only. There is no code path for initiating or moving money. This is a technical limit, not only a policy.
How it works
Paste a list of transactions, upload a CSV exported from your bank, or start with sample data to see how it works before adding anything of your own. Add your current balance and Tellwise builds a forecast in seconds.
Nothing is connected to your bank by default. You control what goes in. If you connect an account later, the connection is read-only: Tellwise can read transactions to keep the forecast current and can never initiate or move a payment. This is a firm technical limit of the product, not only a policy.
Tellwise reads the dozen ways banks export a CSV, including dollar signs, thousands separators, and parenthesised or trailing-DR debits. Dates in day-first and month-first order are both handled.
Transactions, sample data
Direct deposit
Jul 28
Rent payment
Jul 26
Whole Foods Market
Jul 25
Netflix
Jul 23
Client invoice
Jul 21
Paste, upload a CSV, or start with sample data like this.
A predictive model runs over your transaction history to find the patterns: which income arrives and when, which bills recur and on what schedule, and what your everyday spending looks like and how much it varies week to week.
From those patterns, Tellwise projects your balance forward day by day. The projection comes with a confidence range that widens the further out it looks. The more regular your income and bills, the tighter that range. The more variable they are, the wider it is. Both are the honest answer.
The numbers are computed in code. A language model only writes the plain-language read around them; it is never handed a figure to invent.
Patterns detected
Client retainer
Income · Monthly, 1st
Rent
Bill · Monthly, 28th
Netflix
Subscription · Monthly, 23rd
Groceries
Everyday spend · Weekly
Computed in code. No language model is involved in the numbers.
The weeks ahead come back as a forecast, with the tight weeks and overdrafts marked on the line. Each warning names the date, the expected low, and what is driving the pressure, days ahead while there is still time to move a payment or hold off on something large.
Subscriptions that have risen quietly are flagged with the old and new amounts and the annualised difference. Charges well outside your normal range for a merchant are surfaced so you can check whether they were intentional.
Everything is explained in plain language: one sentence per warning, grounded in the computed numbers, written so you can act on it without looking anything up.
What you get back
Aug 17 · dips to –$107 before invoice on Aug 19. Move a payment before then.
Spotify raised $9.99 to $11.99. That is +$24/yr if it stays.
Amazon · $387.40 · 9x your usual range. Worth checking.
The read
"Comfortable through Aug 14. Tight for 2 days before the Aug 19 invoice. August ends in the green."
Privacy
What you add
What Tellwise never needs
Where an account is connected, it is read-only. There is no code path for initiating or moving money. This is a technical limit, not only a policy.
You never give Tellwise a bank password. You paste exported data or upload a CSV. There is no login flow to a third-party bank.
Your transactions and forecasts are yours. Export them as CSV or delete your account entirely from Settings, at any time.
Start with sample data to see what the forecast looks like, then add your own. Free, and no card required.