How couples actually share a budget: what worked for us, twelve years apart

Twelve years ago, my wife Angela and I shared a budget. The method was a spreadsheet. Every purchase, typed in by hand, in the order it happened, with a category in the next column. We did it for a few months. While we did it, it worked. We could see where the money was going, we made better decisions about the next purchase, and the end-of-month surprises stopped.

Then we stopped doing it. Not because it didn't work — because it took too long. Pulling out a laptop, opening the file, typing in three receipts you'd forgotten about from the past four days. Eventually you fall behind by a week. Then the data is no good. Then you stop opening the file.

For the next twelve years we didn't run a structured shared budget at all. We tried a couple of apps, never stuck with them, drifted along with whatever the bank balance suggested. Looking at our spending honestly was something we did in retrospect, in difficult conversations after the credit card statement came in.

I built Tallyo so we could do what we did twelve years ago — capture every expense, between the two of us — without the friction that killed it the first time. The proof, nine months in: we've cut our monthly spending by about 30% and we've held that for nine months straight. Not a six-week novelty. A real, sustained, end-of-month-different number. The same method that worked in our late twenties, modernised enough to survive the rest of life.

This is what I've learned, twelve years apart, about what a shared budget for couples actually needs.

The method has not changed; the friction has

The first thing to say is the underlying method has not gotten cleverer. The basic technology of a shared budget — write down what you spend, look at it before you spend more — has been the same forever. Envelope budgeting, the Quicken-era spreadsheet, YNAB, and yes Tallyo, are all variations of the same idea. The thing that differs between them, and the thing that decides which ones survive past month two, is friction.

In 2014 the friction was finding the laptop and remembering the receipts. In 2026 it's something else — bank-sync apps make logging effortless but make the data 24 to 72 hours stale; app-by-app, the friction has moved from data entry to data trust. But it's always there, and it's always what kills the method.

Our 2014 spreadsheet died because logging a transaction took too long. Tallyo lives because logging a transaction takes about three seconds — under the threshold where either of us would think "I'll do it later." That single number is the thing that did or did not make the system survive. Everything else is downstream.

What a couples budget actually has to do

Strip away the apps and the methods and a couples budget has three jobs. If your setup does all three, it will work. If it misses one, it will quietly fall apart and you will not be able to articulate why.

1. Both of you see the same number, in real time

The most common couples-money fight is not really about money. It is about information. One person looks at the bank balance and feels a small jolt of panic. The other person doesn't think it's that bad. The conversation that follows is defensive on both sides because neither of you had the full picture during the month — by the time the picture assembles, it's already a month old and emotionally loaded.

A shared budget closes that gap. If both of you can open something on your own phone and see the same running number, the gap disappears, and so does the fight. Not because you agreed to budget harder, but because there's nothing to discover at the end of the month. Everything is already shared.

This was true with the 2014 spreadsheet too, except the spreadsheet's "real time" was "whenever one of us next opened the laptop." Tallyo's "real time" is "two seconds after the purchase." That difference is most of why one of them survived past three months and the other didn't.

2. Logging has to be effortless or one of you will stop

The single biggest failure mode of couples budgets is that one partner becomes the budget person. They enter the data, they keep the records, they tell the other person what they can spend. This works for a while and then it ends badly. The non-budget partner feels infantilised. The budget partner feels like an unpaid accountant. Resentment accumulates. The budget breaks.

The fix is structural, not behavioural. The act of logging a purchase needs to be light enough that whichever of you is closer to a phone does it without thinking about it. If you have to designate someone as "the one who tracks", the system has already failed — you just don't know it yet.

In our 2014 version, the friction was on me. Angela couldn't type into a shared spreadsheet from her phone in a useful way, so I did most of it. That asymmetry is what tipped the system over. The current version works partly because neither of us is the budget person. Whichever of us bought the thing logs the thing, in seconds, from the phone we have on us. There is no role.

3. The signal has to be glanceable

The third job is the one most apps get wrong. Whatever you're tracking, the answer to "are we on track?" has to be readable in about a second. Not a chart you have to interpret. Not a number that requires mental arithmetic. A signal you can scan, on the lock screen or in two taps, and instantly know whether you can or can't make a discretionary purchase right now.

Most budget apps give you a dashboard with seven categories, three time horizons, and a chart. To know if you're on track you have to read all of it and do some maths. The maths gets skipped. The dashboard goes unread. The budget becomes a thing you set up rather than a thing you use.

Tallyo's version: each category has a bar, and each bar carries a small pace marker positioned at the period's pro-rata point. Day 10 of a 30-day budget puts the marker at one third of the way across the bar. If the spent portion is behind the marker, that category is fine. If it's past the marker, it's bleeding. You glance at the row of bars and immediately see which colours are over the line. That's the whole interaction. We probably look at it for under five seconds a day, each.

How we actually use Tallyo, nine months in

Now the practical bit. What our setup actually looks like:

Eight categories. Groceries, eating out, transport, household, kids, personal, gifts, miscellaneous. We agreed them once. We haven't changed them. More categories means more decisions per purchase, which means more friction, which means a non-zero risk of one of us giving up.

Monthly period. Tallyo lets you pick — weekly, monthly, custom — and we run monthly because it matches paydays. We have considered running shorter periods. If our overspending ever starts sneaking up on us, we will. The choice is yours; the marker calibrates to whatever you set.

Both of us log. Whichever of us bought the thing taps three buttons. Currency is automatic, category is suggested from previous merchants, amount is the only thing typed. We're at the point where this happens reflexively, mid-walk-out-of-a-shop. That reflexiveness is the whole game.

No bank sync. Deliberately. Bank sync introduces lag (24 to 72 hours of staleness) and a maintenance burden (credentials break, banks rotate APIs). For couples, the lag is fatal — it puts you back in postmortem territory, which is exactly what we're trying to escape. Manual entry, kept fast, beats sync for our use case. Your mileage may vary if your bank sync is genuinely instant and stable, but in our experience it never is.

We look at the bars, not the dashboards. The pace marker is what we check. Are the colours behind the line or past it? If they're all behind, the day is fine. If one is past, we have a quick conversation about whether to pull back or to move money over from another category.

What changed between 2014 and now

The system is the same. The difference, end to end, is that the friction of logging is gone. In 2014, capturing one transaction was a minute of work. In 2026 it's three seconds. That's the whole story. Compound those seconds over twelve years of household spending and you get either "we have a budget" or "we used to have a budget."

The thing I didn't know in 2014 — and that I'm trying to say without making it sound like a slogan — is that friction is the budget. Not discipline. Not categorisation theory. Not envelope graphics or AI categorisers. Just: how many seconds does it take to record what you just spent, and how confident are you that both of you will keep doing it in eight months. That's the whole product question.

If you want to try this with your partner

You don't need Tallyo specifically. The principles work in any tool, even on paper if you can hold the discipline. What you need:

• Both partners able to see the same number, on their own phone, updated within seconds — not hours, not at end-of-day. The gap-closing is the whole point.
• Logging fast enough that neither of you skips it. If it takes more than about five seconds per entry, you will stop. Find a tool that's faster or accept that this method isn't for you yet.
• A small number of categories. Under ten. Granularity costs you in friction far more than it gives you in insight.
• A glanceable signal — pace marker, daily allowance, traffic-light category status, whatever — so checking the budget is a one-second action, not a screen you have to interpret.

Tallyo is what Angela and I built because nothing on the market did all four. If you want the longer version of how it works, the About page has the household setup. If you want how we compared it to YNAB and Mint, that comparison is here. If you'd like a heads-up when Tallyo opens up beyond our household, email us — that goes to the same inbox Angela and I check.

Nine months in is a small dataset. Twelve years between attempts is a long gap. But the spreadsheet worked when we did it, and Tallyo is working now, and the lesson is the same both times: the budget that survives is the one that's cheap enough to use every day. That's it. The rest is window dressing.