About SaudaFlow — built for Indian real estate, in Mumbai

Four people from software, and the one thing they had in common

The first version of SaudaFlow was built by four people, all of whom had spent their working lives in software. That is the whole of the origin story, and we are not going to inflate it into something with more scenes in it.

What mattered was not where any of the four had worked before. It was the thing they had in common, which is unglamorous and specific: each of them had shipped a system that was technically correct and went unused anyway, and each of them had sat through the meeting afterwards where somebody explains that the users are the problem. That leaves a mark. It makes you permanently suspicious of a decision that only looks good on a whiteboard.

Four is not a garage story and it is not false modesty about the number. It is the size at which every person can hold the entire product in their head at once, which is exactly what you need while you are still finding out whether the thing is right at all. Nobody had a lane. Whoever wrote the sync layer also answered the support calls about it, which is a fast and unpleasant way to learn what you got wrong.

What the gap actually looked like

It looked like Sunday night. A buyer named on a WhatsApp forward, retyped into a spreadsheet — name, number, budget, which tower they asked about — for the third time that month, because the sheet on the laptop and the thread on the phone were two different accounts of the same person and neither was complete.

It looked like a lead going quiet for eleven days because the call that mattered was made from a personal handset, nobody logged it, and by the time anyone noticed the gap the buyer had booked somewhere else. Nothing dramatic happened. That is the point: nothing happened, and a sale disappeared.

They tried the software that exists for this. Several of them, over a couple of years, the ones every Indian property firm evaluates. They are real products built by real teams and none of them are bad at what they set out to do. But every one of them wanted the work to move to where the software was — open the laptop, open the record, retype what already happened. None of them went the other way and moved the software to where the work already was, which is a phone, a WhatsApp thread, and a rate card that changes by tower and by floor.

So the thing being described here is not a company doing it wrong. It is a category that had not been built for this market yet. Once you have seen a gap that specific from both sides, it is genuinely hard to go back to your day job and forget about it.

How the team grew after that

The first public build shipped in May 2026 and most of it was rebuilt within three months. That is not a confession, it is the method. You cannot learn what an agent needs from a requirements document, and every one of those rebuilds started with an engineer sitting in a builder’s sales office watching our own software fail in front of the person using it.

Hiring followed that pattern rather than a headcount plan — people were added where the product kept breaking, not where an org chart said there should be a box. AB Corp is sixty people today across the company. We publish that number because it is true and someone reasonably wants to know it. We do not publish funding, valuation, revenue or a customer count, because those get quoted for effect and this one does not have to be.

What sixty buys you, and the reason it is worth stating: engineers who have sat in a builder's sales office and watched the software fail in real time, support answered by people who can change the thing you are complaining about, and enough hands to fix a floor-rise calculation for one firm in Thane without the roadmap stopping.

Why the category needed another attempt

Indian real estate is sold on a phone. A lead arrives from a portal at six in the morning, lands in a WhatsApp group, gets called by whoever is awake, and the actual negotiation — the price the buyer pushed back on, the floor they wanted, the month their loan clears — happens in a personal chat on one agent's handset.

Most CRMs sold into this market were designed for businesses that run on email, then localised. They ask an agent to open a laptop, retype what already happened on WhatsApp, and maintain a second version of the truth. Predictably, the second version is always worse than the first. So the software gets bought in January, half-adopted by March, and quietly abandoned by June, while the pipeline stays where it always was.

That is not a discipline problem you can train away. It is an architecture problem: the CRM is not in the place where the work happens. Fixing it meant starting from the phone and the WhatsApp thread rather than from a lead table with a mobile view.

What we decided to do differently

Four things, and none of them are especially clever. They are just choices most of the category declined to make.

• The price is published, in rupees, per seat, with GST stated — no quote gate, no seat-band maths, no price that depends on how eager you sounded on the call
• The WhatsApp conversation lives in the lead record, so the firm owns the relationship rather than the individual holding the handset
• Caller ID names the lead before you say hello on Android, with the app closed — and we say plainly that iOS cannot do this rather than implying it can
• Your data stays in the Mumbai region, and the DPDP Act 2023 workflows are in the product rather than in a policy page nobody reads

What we are not

A short list, because being specific about the gaps is the only way the rest of this site earns any credibility.

Sixty people is not an enterprise vendor. There is no funding announcement here, and we are not a platform with a professional-services arm — if your evaluation requires a six-week implementation and a named delivery manager, we are the wrong shape and you will find that out faster from this paragraph than from a pilot.

We have not won awards, we do not publish customer counts we have not earned, and we do not hold certifications we have not been through. Where a page on this site would normally carry that kind of proof, it says what is actually true instead. The awards page is a single honest paragraph rather than a badge wall.

The company, and the other product

AB Corp is the company. It is based in Mumbai, it is the entity named in the Terms of Service, the Privacy Policy and the Data Processing Agreement, and it is the GSTIN that appears on your invoice. SaudaFlow is founded and led by Ankit Bhadauria.

AB Corp also runs Cusina, a multi-tenant point-of-sale system for restaurants, at cusina.tech. It is a separate product with separate customers and separate data — mentioned here only because a company that pretends to have one product when it has two is starting the relationship with a small lie.

The reason we stay close to the Indian market rather than chasing a global one first is unromantic: it is the market we can call. When a builder in Thane says the cost sheet is wrong for their floor-rise structure, we can be on a call about it that afternoon, and the fix ships in a version they will actually receive.

How we work with the people who use it

There is no self-serve signup, deliberately. Every workspace is provisioned by an operator after a demo call, at the tier and seat count that were agreed on it, with real project names already in place.

Support is email and in-product chat, 10am to 10pm IST, answered by the people who build the product rather than a first-line queue whose job is to deflect. That does not scale forever and we know it. While it does, it is the fastest feedback loop this company has.

A note from the founder

I have kept my life story off this page. You did not come here for it, and a CV tells you nothing useful about whether a piece of software will still be answering the phone in two years.

The part that affects you is this. I read the support queue. I take demo calls myself. My name is on the company that holds your data and on the invoice you pay. If SaudaFlow stops being worth paying for, there is no account-management layer between you and the person responsible — you can put it to me directly on a call, and people do.

— Ankit Bhadauria, Founder, AB Corp