The money feature your users switched for
Your users left their bank because you promised better money tools.
<FreeCashflow /> · your UI
Free cashflow
Live£918
Finlo · your brand · our engine
01
The promise is insight. The build is brutal.
Your whole product promise is superior money insight: your users deliberately left their bank's app for yours.
Your roadmap · Q3
backlogEPIC · Live cashflow forecasting engine
02
How it works
You render, we calculate
Step 01
Push your categorised transactions
Your app already holds categorised transactions via its aggregator, which is the one prerequisite.
SALARY · GRANITE PARTNERS+£2,850.00
NETFLIX−£15.99
TFL TRAVEL−£42.10
POST /v1/transactions · 202
from your aggregator · already categorised
Step 02
The engine resolves one number
Pouch detects the frequency and classification of every recurring inflow and outflow, excludes internal transfers, and consolidates every account the user connects.
One number · resolved live
£918
COSTA · −£4.20 · just landedre-settles → £913.80
the number moves in front of the user
Step 03
Today, and any future day
The same number comes back for today and for any future date, across any forward period you define: daily, weekly, monthly, any window.
income minus chosen bills · over any window
£164
£402
£918
forecast to the day · any window you define
Step 04
Render it as your feature
Your UI, your brand, your credit.
Left to spend
£918
of £1,240 · resets 1 Nov
a fast integration · not a rebuild
03
The demo
What you will see in the demo
04
FAQ
The questions your team will ask.
- Couldn't we build this in-house?
- You could, in quarters, with your best engineers, and you would still be validating cycle-detection edge cases while a competitor ships. The engine underneath is years of iteration on real users' cash. Buy the engine, own the feature: the credit is entirely yours.
- Isn't another vendor just added cost?
- It is a fraction of the engineering cost of building the engine yourself, and it powers the feature that drives retention, the metric your next round is priced on. The pilot lets you weigh the value on your own data before any commitment.
- What data do we need to qualify?
- Categorised transactions, which your app already holds through its aggregator. A few months of history is enough to produce output, and a longer history sharpens the forecasts as longer cycles become visible. Pouch is always a layer on your categorisation, never a replacement for it.
- How accurate is the forecast?
- The number is calculated from detected cycles, not guessed, and the forward values come from the same engine. We claim the resolution, a value for any single day rather than a multi-month band, and the pilot exists so you can judge it on your own users' data.
See it on your own data.
Book a 15-minute demo, then test the live number on your own users' data.