SplitMate — split expenses with a link - Split group expenses with a link. No accounts, no fuss

by•
Split group expenses without the signup. Share a link, add expenses, settle up.

Add a comment

Replies

Best
Maker
📌
I built SplitMate because every time I split a bill with friends, someone had to get everyone to download an app and create an account just to log a $12 lunch. That friction meant the "settling up" step just… never happened. The idea: what if the group was just a link? No signup, no password. You open the link, pick your name (or make one up), and start adding expenses. SplitMate handles: - Equal splits across the group - Running balances — who owes who, at a glance - Debt simplification — collapses everything down to the minimum number of payments needed to settle up It started as a weekend project for a trip with friends, and the biggest design constraint became: would my least technical friend use this without complaining? That ruled out accounts, multi-step onboarding, and anything that felt like a finance app. It should feel as light as sending a text. Would love feedback on the balance/settle-up flow especially — that's the part I iterated on most.

 The no-signup approach makes a lot of sense for something as simple as splitting lunch. I upvoted SplitMate, and I especially like the debt simplification feature since it removes another decision from settling up. Curious how you’re measuring whether the flow feels intuitive to less technical users.

Maker

 Thanks, I’m really glad the debt simplification landed and you liked the no-signup approach. That was the one feature I didn’t want to compromise on.

Honestly, my assessment of usability is still more gut-feel than rigorous. The in-app feedback button goes directly to me, and I track a few signals like groups created, whether a first expense gets logged, and whether people return to add more. But those tell me what users do, not where the experience feels intuitive or confusing.

I don’t yet have proper funnel tracking or structured usability testing with non-technical users, so I’m often inferring friction from silence rather than measuring it directly. My most useful test so far has been handing the app to a few non-technical friends and watching where they hesitate, insightful, but hardly scalable.

Instrumenting the create → first-expense journey is next on my list. If you’ve found a lightweight way to validate “intuitive” with non-technical users without over-engineering the process, I’d genuinely love to hear it!