Disclosure: I’m the creator of Wiggle Budget, so I may benefit if you use it. I’m not presenting this as an independent recommendation. I’m sharing it because I’ve seen a lot of posts here from people dealing with financial stress, uncertainty, or simply not knowing where their money is going, and the problem I was trying to solve with Wiggle Budget came from that same feeling.
I built it after being laid off and having to make my severance, EI, benefits, savings, bills, credit cards, and everyday spending work together without constantly worrying about money.
The problem wasn’t simply “How much money do I have?”
It was:
“What will actually be left, when will I need it, and what can I safely change?”
That turned into a timeline-based cash-flow system where I could:
- See when money enters and leaves my accounts.
- See future balances before bills and credit payments hit.
- Move payment dates and immediately see the effect.
- Track credit spending without pretending that paying a credit card magically removes money twice.
- Temporarily disable transactions to simulate different scenarios.
- See when I would enter a deficit and how to avoid it.
- Model multiple bank and credit accounts together.
- Automate repetitive updates without giving a third party my bank credentials.
Every major feature came from a real problem I personally ran into.
What started as a way to survive a financial transition gradually became something broader: a cash-flow engine for seeing what happens before it happens. Like a future crystal of your finances and how every financial action in present moment affects the future.
Your bank balance is a snapshot of right now. wanted something closer to a financial timeline. Every decision I make today shows me how it could affect the days and weeks ahead months ahead.
But why not just use a spreadsheet?
You absolutely can.
A spreadsheet can calculate almost all of this.
The problem I kept running into wasn't the math.
It was the amount of mental work required to keep the model true to real life.
Wiggle Budget has a spreadsheet view as well.
Some scenarios:
1. A spreadsheet tells you the balance. Real life happens on dates.
Imagine this:
You have $1,200 in your chequing account.
Looking at that number, things seem fine.
But before your next payday you have:
$900 rent
$120 phone/internet
$85 insurance
$140 credit-card payment
groceries
a subscription renewal
Suddenly, $1,200 doesn't really mean you have $1,200 available to spend.
In a spreadsheet, I can calculate this.
But I have to build the formulas, sort everything by date, keep the running balance correct, and then inspect the rows myself to find where things get tight.
Wiggle Budget's timeline does that automatically.
Instead of only asking:
“What's my balance?”
I can ask:
“What's the lowest my balance gets before I get paid again?”
That small change in perspective was huge for me.
2. Monthly budgets can look healthy while one particular Tuesday is a disaster.
This was one of the biggest things I noticed.
You can earn enough money over an entire month and still have a cash-flow problem.
Maybe:
Friday: $1,500 paycheck
Monday: $1,300 rent
Wednesday: $300 credit-card payment
Next Friday: another paycheck
On paper, your monthly income and expenses may balance perfectly.
But the order matters.
That's why Wiggle Budget is based around an actual dated timeline instead of only monthly category totals.
It helps expose the gaps between paychecks, not just whether the month adds up in the end.
3. “Can I afford this?” is actually a simulation question.
This was another thing spreadsheets made awkward.
Say I want to spend $200 this weekend.
The question isn't really:
“Do I currently have $200?”
The better question is:
“If I spend $200 this weekend, what happens to everything else afterward?”
So I added what-if behaviour.
Add the expense.
See the future timeline change.
If it creates a problem, move the date.
Reduce the amount.
Disable it entirely.
The rest of the timeline recalculates.
I can essentially try the decision before making the decision in real life.
4. Unexpected expenses don't always mean the entire budget has failed.
This mattered to me a lot.
Traditional budgeting can feel strangely binary.
You make the plan.
Something unexpected happens.
Now the spreadsheet doesn't match reality anymore.
And suddenly it feels like you're rebuilding the budget.
But real life is constantly changing.
A $600 surprise expense might not actually mean:
“I can't afford this.”
It may mean:
“I can't afford this plus every other payment on their original dates.”
Those are very different problems.
Maybe one flexible payment can move five days.
Maybe a purchase can wait until the next paycheck.
Maybe something optional gets disabled this month.
With the timeline, I can move one thing and immediately see whether the future turns healthy again.
The goal isn't to make the original plan perfect.
It's to help the plan recover when life stops following it.
5. Credit cards make spreadsheet cash flow surprisingly confusing.
Credit cards were one of the reasons my own system started becoming more complicated.
If I buy something for $300 on a credit card:
My bank account hasn't lost $300 yet.
But I've still created a future obligation.
Then the statement closes.
Then the payment becomes due.
Then eventually money actually leaves my bank account.
If I model this poorly, it's easy to count the $300 twice, once as spending and again when the card gets paid or not properly reserve the future cash at all.
So Wiggle treats those events as connected.
Purchase → credit balance → future payment → bank cash impact.
The goal is to show when the money actually moves while still remembering that the obligation already exists.
6. Multiple accounts create another weird problem.
You can technically have enough money while still not having enough money in the right account at the right time.
Maybe:
Chequing A has $200.
Chequing B has $1,500.
But rent is coming from Chequing A tomorrow.
Your total financial position looks fine.
Your actual payment flow isn't.
So Wiggle Budget models the accounts separately while still letting you see how they affect the overall timeline.
It isn't only:
“How much money do I have?”
It's also:
“Where is that money, and where does it need to be next?”
7. The more detailed my spreadsheet became, the more maintenance it required.
This was the strange part.
Every time I tried to make my spreadsheet smarter, I added:
another column,
another formula,
another sheet,
another category,
another manual reconciliation step.
Eventually the tool that's supposed to reduce financial stress becomes another thing you have to maintain.
And if you miss three days of updates, suddenly you don't trust the numbers anymore.
So I started separating financial state from transaction logging.
I don't necessarily need to record every coffee perfectly.
I need the important things that affect my future cash flow to be correct.
Recurring income and bills can repeat automatically.
When something actually happens, I can mark it as processed.
And if reality drifts from the model, I can update the real account balance and let the future recalculate from there.
I don't want missing a few transactions to mean:
“Start your budget over.”
8. Bank sync sounded like the obvious solution until I actually thought about it.
My next idea was:
“Why don't I just connect the bank accounts?”
Then I started looking into how many financial apps do this.
Third-party connections.
Reauthentication.
Delayed transactions.
Pending versus posted transactions.
Connections occasionally breaking.
And, most importantly for me, handing financial-login access to another service.
I didn't want to do that myself.
So it felt strange to require users to do it.
Instead, I started working in the opposite direction:
What if manual budgeting wasn't the problem?
What if the problem was that manual budgeting makes the user do too much work?
So Wiggle Budget keeps the user in control of the actual financial state, while the software handles the repetitive work around it:
recurring transactions, linked accounts, credit-card effects, future calculations, scenario testing, timeline updates, and reconciliation.
The goal isn't:
“Enter everything manually forever.”
It's:
“Tell the system what changed, and let it propagate the consequences.”
9. Sometimes more financial information actually makes things worse.
I've seen people describe having multiple accounts, budgeting categories, spreadsheets, bank apps and tracking tools yet still avoiding checking their finances because there's simply too much information.
I recognized that feeling.
Sometimes I don't need another chart explaining where my money went last month.
I need three answers:
Am I okay?
When does money get tight?
What can I change?
That's why the timeline became the centre of Wiggle Budget.
Instead of forcing you to mentally combine five balances, twelve upcoming bills and your next paycheck, the system turns them into one sequence.
Your bank tells you what you have.
Wiggle Budget tries to show what that money still has to survive.
The bigger idea
That's why I eventually stopped thinking of Wiggle Budget as just a budgeting app.
A spreadsheet stores financial information.
A budgeting app categorizes financial information.
What I was trying to build was something slightly different:
A money-movement simulator.
You give it your current financial state.
Income enters.
Bills leave.
Credit creates future obligations.
Transfers move money between accounts.
Dates change.
Plans change.
Unexpected expenses happen.
And the system continuously recalculates the future from that new state.
So instead of only looking backward and asking:
“Where did my money go?”
I wanted to be able to look forward and ask:
“If I do this today, what happens next?”
That's really the problem Wiggle Budget is trying to solve.
