How FairMate Built a Niche Expense-Splitting SaaS by Targeting Relevant Communities

It started on a string of trips in early 2023 with family and friends, mostly to places with no internet and no signal for days at a time. After a week away, nobody could agree on who'd actually paid for what, and we'd end up going through credit card statements trying to reconstruct it. I was running the whole thing in a personal Excel spreadsheet, and it only worked if everyone trusted my math and nobody lost a receipt. The same problem showed up worse in my share house, where I was the admin for five of us. People moved in and out mid-month, and splitting rent, bills, and one-off costs like a new TV or fridge fairly got complicated fast. Arguments over cleaner’s fees and missing receipts actually damaged friendships, which is the part that really bothered me. I built FairMate to replace that spreadsheet, attach a receipt, FairMate reads it, splits it transparently, and settles it through PayID or UPI instead of guesswork.

The tactic that worked was posting directly in WhatsApp groups, share-house and flatmate groups, trip-planning groups, the places where the actual problem was already being talked about. People in those groups are already mid-argument about a bill or already organizing a trip, so the app is relevant the moment they see it, not something they have to be convinced they need. The one that flopped was paying for spots on influencer marketing platforms. I picked that channel because it's the obvious thing to try when you have no marketing background, but the audience was broad and lifestyle-focused, not people actively splitting costs with anyone. The clicks looked fine, the signups didn't convert into anyone actually creating a gathering or house. I learned the hard way that for a niche, problem-specific tool, going where the problem already exists beats paying to manufacture attention for it. Lesson learned, spend the time before you spend the money.

The complaint that came up most was the app being useless with no signal, which mattered a lot since most of our own trips were to places with no internet. People would try to log an expense while traveling and just get nothing. I built an offline queue so you can keep adding expenses with no connection, and it syncs automatically once you're back online, with idempotent backend writes so a half-finished sync never creates a duplicate. The same complaint kept surfacing in a different form too, people wanted to attach a proper invoice, not just a photo, since plenty of real bills land as a PDF in your inbox, not a paper receipt. After launch, I added PDF receipt support and then on-device scanning so FairMate reads the vendor and total off a photo automatically instead of you typing it in by hand. On top of that, FairMate now notifies everyone automatically when an expense is added, so nobody has to chase the group to find out what actually happened.

Most apps treat group expenses like a single dinner bill, divide it by how many people are in the group right now. That works for a one-off trip, but it breaks down for anything ongoing, like a share house. If someone moves in halfway through the month, splitting rent by headcount overcharges them for days they weren't living there. I built FairMate's split engine to allocate every dollar by the exact day someone was a member, not just who's on the list today. The same problem shows up with bonds. People move out, someone else moves in, and untangling who's owed what against the deposit pool becomes a mess fast. FairMate settles that automatically. The market treats splitting costs as solved because equal division is easy to code. Doing it fairly when people's time in the group isn't equal is the hard part, and most apps skip it because it's harder to build and harder to explain, even though it's what actually decides whether people trust the numbers.

The next 6-12 months are about taking the cost-splitting and settlement engine I built for FairMate and applying it to construction. Builds and renovations involve multiple parties, owners, contractors, family members co-funding a project, and the same problems show up, who paid what, who owes what, and proving it with receipts and invoices. I'm planning a few solutions for that space, reusing the day-weighted allocation and transparent settlement logic that works for trips and share houses. The goal is to take something that already works for splitting a holiday or a house and point it at a market where the money and the disputes are a lot bigger.

Free tier stays generous by design, earning trust before monetizing.

Before FairMate, I spent my career as a solution and enterprise architect, mostly across government and university IT environments where accuracy and security aren't optional because real people and real data are on the line. That experience shaped how carefully FairMate handles money, every calculation is precise, and edge cases like someone joining or leaving partway through a billing period are accounted for, not glossed over. I'm building FairMate solo, with no co-founder and no team, so the same discipline that once applied to one part of a large enterprise system now covers everything, product, engineering, infrastructure, and the business.

My biggest mistake was spending money on influencer marketing platforms before testing cheaper channels. I assumed paid promotion was the obvious way to get visibility, so I went there first instead of starting with WhatsApp groups, where the actual problem was already being discussed. The clicks looked fine, but almost none turned into someone creating a gathering or a house. What I learned is that for a niche tool solving a specific problem, distribution works best where people are already talking about that exact problem, not wherever attention happens to be for sale. I shifted effort to those communities instead.