Skip to content
Samprat Trivedi
SplitwiseTeardown

Splitwise put its paywall on the one action the product can’t work without

A shared ledger is only useful if it is complete. Splitwise's free plan limits how many expenses you can add in a day, so the limit damages the thing people came for.

What it's for

Splitwise keeps a running tally of who owes whom in a group: flatmates, a trip, a couple. The job is trust. Everyone can see the same ledger, so nobody has to remember or argue.

That only works if every expense goes in. A ledger that is missing three dinners is not 90% useful. It is wrong, and once it is wrong the group goes back to arguing.

The decision

Since late 2023, free accounts can add only a handful of new expenses a day. Splitwise's own reply on its App Store page puts the number at four; users report three to five depending on platform. Pro removes the cap and adds extras such as receipt scanning, currency conversion and search.

Hevy, free plan
  • Logging is unlimited
  • Limits sit on routines, custom exercises and history
Splitwise, free plan
  • Adding expenses is capped per day
  • The limit sits on the core action
Two free plans, two places to put the limit. Hevy caps what surrounds the log. Splitwise caps the log itself.

Why it's risky

The cap is daily, but the usage is bursty. A flat-share adds a few expenses a week and never notices. A trip adds ten in a day. Someone who saves receipts and enters them once a month adds twenty in one sitting. The cap is invisible to light users and hits hardest in exactly the moments the product is most needed.

One person's limit is the whole group's problem. The ledger is shared, so when one member hits the cap, everyone's balances are incomplete. Splitwise's own suggested workaround, on that same App Store page, is to ask a friend to add the expense for you. That works, and it shows the issue: the cost of the cap is paid by the group, not just the person who hit it.

The exit is easy. Unlike a workout history, a group's balances can be settled and restarted in another app in an evening. The moment of frustration and the moment of switching are close together.

In fairness, the decision has a logic. Heavy users get the most value and are the right people to charge, and a limit on usage is the simplest way to find them. My argument is with where the limit sits, not with charging.

What I'd test

Replace the daily cap with a monthly allowance of roughly the same size.

  • Why: light users are unaffected either way. Bursty users, trips and monthly batch entry, can finish what they started, so the ledger stays complete. Heavy users still hit the limit, later in the month, after the product has done its job for them.
  • The tradeoff: some people who upgrade today out of mid-trip frustration would no longer need to.
  • How I'd measure it: Pro conversion among users who reach the limit, with two guardrails: expenses logged per active group per week, and how many groups are still active 60 days later. If conversion holds and groups stay more complete, the daily cap was costing more than it earned.

The free-plan limit is from Splitwise's App Store page, checked on 15 November 2026; reported numbers vary by platform. The analysis is my own and I have no access to Splitwise's data.

All teardowns