M
Cabin groceries4 people · weighted split
kr 620
Offline-first expense sharing
Split expenses
while life is still
happening.
SplitFlow is built for trips, households, and group plans where the connection is patchy and the details are easy to lose. Add expenses immediately, keep the context attached, and let sync catch up when the internet does.
Save locally firstKeep receipts and notes attachedSync when the signal returns
Trips
Capture shared spending in the moment instead of reconstructing the weekend later.
Households
Keep groceries, utilities, and one-off spends in one shared timeline that still makes sense.
Groups
Run dinners, events, and cabin weekends without turning every payment into a separate chat thread.
Why SplitFlow
A cleaner way to keep shared spending understandable.
Local-first capture
Expenses save on-device immediately, so the core workflow stays reliable when the network does not.
Receipts, notes, and context
Keep the amount, people, note, place, and receipt trail attached to the same record.
Readable balances
See who owes what without manually recomputing the math after every shared purchase.
Groups and personal mode
Track solo spending and shared spending in one product without forcing everything into the same shape.
Designed for the hard part
The product is built around unreliable situations, not perfect ones.
A shared expense app fails the moment it assumes stable signal, immediate confirmation, and perfect memory. SplitFlow puts the write on the device first and treats network sync as reconciliation, not permission.
Local-firstNo forced round trip to save an expense.
Shared contextPeople, notes, and receipts stay attached.
Balance claritySee what changed after each spend.
Web supportLinks can recover gracefully outside the app.
Product flow
Three steps. No spreadsheet archaeology.
Add the expense instantly
The phone saves locally first and updates the interface from the same record.
Carry the full story
People, split logic, note, location, and receipt status move with the expense.
Sync when online
The server catches up later, which keeps weak connectivity from breaking the product.
Web bridge
Email and SMS links that still know where the app is.
SplitFlow Web handles auth, invite, and recovery links so they can land safely in the browser, then pass the user back to mobile when the app is installed. If the app is missing, the experience stays useful instead of collapsing into a dead end.
Link openedEmail or SMS becomes a stable web URL.
→
Safe landingThe browser keeps the payload and computes the app handoff.
→
App resumesMobile takes over if it is installed, with a fallback if it is not.
SplitFlow
Modern expense sharing for the moments that are easy to forget.
The mobile app stays local-first. The web app handles discovery and recovery. Together they make the product feel dependable instead of fragile.