Who Owes What
Scan · Split · Settle
-
3
Just tried it, worked flawlessly on an old receipt of mine! Nice.
What I'd like to see improved is the format of the shareable summary (e.g. headings by person, bullet points, etc). To make it easier to scan and find a specific person in the group.
On payment. I like the idea of pay as you go, tho in the moment I need to scan, I want it to be quick. A prepayment would be good. 50¢ looks alright, but would love to get it down to 3 for 1€ maybe.
What happens if the scan fails, will I get refunded or credit issued to my account?
-
2
Receipt-first might be solving the wrong moment of awkwardness. Identifying who ordered which dish is usually the easy part. People remember what they had. The real awkward moment is shared items: appetizers everyone picked at, or pitchers split unevenly across people who barely drank and people who finished it. OCR can read each line, but it can't tell you that one person ate 80% of the shared appetizer. Item-level assignment adds steps without resolving the underlying ambiguity for shared items. Splitwise's lazy equal split works because it gives up granularity to keep things peaceful.
Worth asking: is receipt-first solving the cognitive split (who had what) or the social split (was this fair)? They're different products. The bigger market is the social one, and that one doesn't get solved by better OCR.
-
1
Thanks! This is a really good framing.
Agree that shared items (appetizer, pitcher) are often the awkward part, and OCR can’t know who ate 80%. Assignment doesn’t remove that judgment — it only helps once the group agrees how to treat the line (e.g. tap multiple people → split that line evenly).
Receipt-first here means itemized bill → assign (including shared lines) → share a clear total, not “OCR solves fairness.” The win is often long receipts + shareable summary, not memory of your own dish.
The share step with a clear per-person summary (WhatsApp/PDF), shifts the awkward part from “what’s the number?” to “do we agree this is fair?” That’s closer to the social moment you describe.
Equal split is the peaceful default when granularity isn’t worth it and the app still shows ≈ what each person would pay if you split the total evenly, so the group has a simple baseline even when you’re assigning lines. This is for when you want itemized clarity without a forever ledger.
Curious if you’ve tried it for shared items. Does multi-tap on one line feel useful or too much hassle?
-
-
2
the WhatsApp drop in one tap is the feature that converts skeptics. the awkward part of splitting a bill isn't the math, it's the social proof that the split is fair. a shareable summary everyone can see is doing social work not just financial work
-
1
Agreed. For many people the awkward part isn’t the math, it’s whether everyone trusts the split. A shareable summary (WhatsApp/PDF in one tap) is meant as social proof, same numbers for the whole group, not just a private total.
So the flow is:
build the breakdown (scan or type, assign lines, including shared ones)
share so the chat sees one clear story.
That’s the feature we’re trying to make obvious. If you try it, does the WhatsApp drop feel like “fair enough, move on” or still missing something?
-
1
the 'same numbers for the whole group' framing is exactly it. the trust problem isn't about accuracy, it's about everyone seeing the same thing at the same time. one shared view kills the 'wait what did you include' back-and-forth before it starts
-
-
2
This is good. My pain point when splitting expenses is that people often overlook things once the bill is paid. I would appreciate it if you could add an option to invite the group before the event so that everyone knows upfront and is ready to pay. It kind of removes the awkward silence when the bill arrives.
-
1
Thanks! Great note.
Pre-event “we’re splitting tonight” is a real gap. A core goal is no accounts: data stays on your device, and you share the summary on WhatsApp, PDF, or whatever you already use, not a platform we lock you into.
Right now we focus at the bill: assign → share → mark paid. Pre-invites likely need a light link or optional sync later, without turning into “another app with a group ledger.”
Would a no-signup pre-meal link help, or do you need named invites before the event?
-
-
2
This is a great idea......
-
1
Thank you for the feedback
-
-
2
Really like this idea, as it's a pain-point for everyone, and your concept seems different enough from other existing bill-splitting apps to carve out a nice niche. The only sticking point I could see is the manual entry of all the names of the people that you dined with. Have you explored mechanisms of getting the names to auto-populate, i.e., pulling them from group text threads, emails, etc.? Regardless, nice job and wish you all the best.
-
1
Thanks for the feedback, I really appreciate it.
That’s a good point. Typing in everyone’s names manually definitely adds extra steps, so I’m exploring ways to pull names in automatically on mobile and make the whole process faster. Hopefully I’ll have an update there soon.
Apart from that, I hope everything else felt pretty seamless — that’s really what I’m aiming for.
-
-
2
The receipt-first angle is the actual wedge, but it's buried. Your hero reads generic ("tired of group ledgers") which puts you against Splitwise — and you won't win that fight. 10+ years of data, network effects, habit lock-in.
The differentiation underneath: Splitwise assumes you already know what each person ordered. Receipt OCR + line-item assignment removes the "who got the calamari" moment at the table. That's a different use case — one-off restaurant meals, not ongoing ledgers. Different buyer. Lead with it.
On pricing: per-receipt creates a negotiation moment when user wants zero friction. Splitwise Pro is $36/year unlimited and they barely monetize. Category economics are brutal.
Harder question: is this even a paid product? Bill-splitting is occasional. Might be a free tool that monetizes adjacently — restaurant referrals, payment app partnerships. Worth thinking through before optimizing pricing.
-
1
Thanks for taking the time to write this — really helpful.
Receipt-first is the core wedge: scan (or type) line items, assign people per line, share a clear summary so the “who had what?” moment at the table is settled without mental math or a group chat argument. That’s the job Who Owes What is optimized for.
Fair point on positioning: leading with “not another group ledger” can sound like a direct Splitwise competitor. Splitwise has years of habit and network effects; Who Owes What isn’t trying to win that fight head-on — it’s trying to win the itemized receipt → fair split → share moment first, with splits saved on your device by default, not as a growing cloud ledger.
I completely agree about the pricing. Still gathering ballpark feedback, but “free tool, monetize elsewhere” is on the table.
If you try it, would love one note: does the assign-lines flow feel like the main win, or does anything still feel like “lite Splitwise”?
-
1
The question you're asking is the right diagnostic, but "does it feel like the main win" is hard to answer well in DMs — people tell you nice things because they like you. Polite-positive feedback is noise.
The signals that actually tell you which one it is:
Repeat usage in first 2 weeks. Receipt-first product is occasional by design. Used once and never returned = lite Splitwise. 3+ uses unprompted in 2 weeks = the assign-lines mechanic is solving a real moment.
Willingness to pay anchored to specific scenario. "Would you pay $X" generates polite numbers. "When you split that calamari moment last Friday, would $0.50 have been worth not arguing for 5 minutes" anchors to memory of actual pain.
Side-by-side observation, not self-report. Don't ask "how is this different from Splitwise" — show both, watch which they reach for in a real scenario. Behavior beats self-report.
Once you have signal on which one it is, HiveMind is built for pressure-testing how you position around it — code HivemindIH123 at myosin.xyz/hivemind. AI strategy copilot, contrarian by design.
-
-
-
1
This comment was deleted 3 months ago
Comment