Why Indian proptech has not yet found its scale.
Bhavadeep Reddy — Bobby to the family — has watched the largest asset class on the planet run on the smallest amount of software for a quarter of a century. He moved from electrical engineering into low-end housing colonies for Infosys staff, into an IT services company that wanted to list in 2001 and ran straight into the crash, and back into property when the early-2000s margins were generous enough that no developer needed to be efficient. From that vantage point he became one of the country’s few proptech angels, watched real-estate accelerators fail to convert, watched KEF’s modular-construction beauty go under, and watched fractional ownership stall against the Indian mindset that wants the whole piece, not the strata. The conversation that follows is his account of why the trillion-dollar Indian real-estate market has not yet produced a category-defining proptech company — and the specific subcategories he now thinks will.
In sixty seconds.
Bhavadeep’s thesis arrives in pieces but rests on a single observation. Real estate is the largest asset class on the planet and the slowest to absorb technology in India, because between 2000 and the early 2010s the margins were thick enough that no developer needed to be efficient. The pressure to digitise — procurement, design-to-execution handover, drone-based site inspection, transparent broker flows, blockchain-backed land titles — arrived only when those margins compressed. The proptech accelerators that opened in the 2010s mostly failed because there were no anchor builders ready to onboard the pilots; the drone companies and the inventory-tracking startups withered on the periphery without an industry buying-pattern to land in.
The second beat of the conversation is the angel filter. Bhavadeep names the founder first, the idea second, and the willingness of the industry to participate third — and argues that any proptech idea sold as a product-market-fit experiment, the way a SaaS founder would, will fail in real estate because the acceptance has to come from the industry itself. The corollary is concrete: the top ten Indian developers have decades of accumulated procurement data sitting in closed systems; if even a handful of them opened their APIs the way UPI opened payments, an entire layer of proptech becomes investible overnight. That, in Bhavadeep’s reading, is the wedge.
The third beat is the future shape. Bhavadeep is now building toward fractional and tokenised ownership of real estate on chain, not because the technology is mature but because the Indian saver understands real estate better than equities and wants a piece of every project they pass. He extends the thesis outward — agritech is proptech because the warehouse and the land sit underneath it; smart cities are proptech because Wi-Fi was the cheap sale and the real product is information transit; UPI’s sibling for property is a stack the industry has not yet asked the government to back. The companion episode with Rohan Shenoy (Ep 44) sits adjacent to this argument; the two pages together describe the same blocked category from the operator and the angel sides.
Where to land in the conversation.
Each chapter opens the YouTube video at that timestamp in a new tab.
Six ideas to carry into your own work.
Mental models lifted from the conversation that travel beyond Indian real estate. Each one is the kind of thing you could quote in a developer meeting on a Tuesday or repurpose in any industry where the largest incumbent is also the slowest to digitise.
The margin shield.
From the early 2000s through 2005 the property margins were tremendous, costs were low, and the developer did not need to be efficient. Efficiency, Bhavadeep argues, is a derivative of margin compression — not of available technology. The category that does not adopt is usually the category whose unit economics still allow the waste. The question for any proptech founder is which builders have already crossed the compression threshold; the others are still wearing the shield.
The industry-first sequence.
Bhavadeep refuses the SaaS-style product-market-fit script for real estate. The acceptance has to come from the industry itself. The right order is to take the idea to a handful of developers, secure their participation, and only then build the product. The reverse order — build the product, find a buyer — is the failure pattern he has watched repeatedly. A category that lives on relationship and scale needs its first ten customers in the room before the first line of code.
The open-procurement wedge.
The top ten Indian developers each carry millions of unstructured procurement data points. If even three of them opened the APIs, the way UPI opened payments, an entire proptech layer becomes investible — price discovery, supplier benchmarks, predictive material costs, scaffolding the procurement of the next thousand mid-size developers. The closed-loop is the moat the incumbents think they are protecting; in fact it is the moat that keeps the category undersized.
The mid-level resistance map.
Bhavadeep names the resistance precisely. It is not the top of the construction firm; it is the mid- and lower-tier managers who fear that the new system removes the side income or the discretion that makes their role survivable. The technology does not lose to a strategic objection; it loses to a thousand small refusals at the point of operation. Any proptech founder who sells only to the chairman has misread the org chart. The implementation buy-in lives lower.
The property-as-platform claim.
Proptech, for Bhavadeep, is not a vertical SaaS — it is the platform layer underneath an Indian’s entire life. Home, office, retail floor, warehouse, agricultural land. E-commerce is a real-estate business. Agritech is a real-estate business. EV charging is a real-estate business. The framing is operationally useful: a founder who treats access, identity, and transit as the work product, not the building itself, ends up with a category-spanning company instead of a single-vertical app.
The let-them-figure-it-out rule.
Bhavadeep’s advice to a Japanese fund that has spent thirty-five years trying to understand India: don’t. Find the Indians who are figuring out India, get on their backs, and let them service the world from there. The rule generalises to any market where the cultural specificity is the unit of differentiation. The foreign investor’s job is not to model the country; it is to identify the operator who already has the country in their bones and finance the version of them that can scale.
Fifteen things to walk away with.
Each one carries the timestamps where the moment lives and a transferable note for work that isn’t real estate. The order follows the arc of the conversation — from the three-generations frame down to the specific subcategories Bhavadeep would still back in 2023.
The three-generations frame: the rule about watching what was done.
Bhavadeep has watched three generations of Indian real-estate operators — the listing-era IT services entrepreneurs of the late nineties, the early-2000s property princelings whose margins paid for the early proptech accelerators, and the post-RERA developers who now actually need software to survive. His rule for reading a founder is borrowed from that arc: do not weight what is said in the interview, weight what has actually been done. The first two generations talked about technology and built brochures; the third one started by collecting data and only then built the dashboards.
The transferable shape is that founder evaluation gets more honest when the evaluator has watched at least two prior cycles in the same category. A pattern visible only across a decade is invisible inside a single deal memo. The angel investor who has been around for three cycles also makes fewer of the price-and-valuation mistakes that defined the 2014-2022 era; the muscle memory is calibrated for the right kind of bet, not the loudest one.
The margin-shield diagnosis: efficiency follows compression, not technology.
The single explanation Bhavadeep returns to for why proptech under-performed in India is unfashionable but specific. Between 2000 and 2005, property margins were tremendous; costs were low; demand-supply was tilted toward the developer; migration was filling every new apartment. Software was not adopted because the spreadsheet did not need it. The category started taking efficiency seriously only when RERA, capital discipline and end-buyer scrutiny compressed the per-project margin to a point where waste became visible. The lag is not cultural; it is arithmetic.
The framing matters because it predicts which builders will absorb proptech first. The ones whose backlog is profitable enough to ignore tooling will keep ignoring it. The ones whose mid-sized projects now run at single-digit margins will buy — not because they understand the technology better, but because they have run out of slack to absorb the alternative. The founder who profiles the buyer pool by margin profile, not by stated digital strategy, wastes less time pitching.
The Narayana Murthy footnote: sustainable is one shade, not the rule.
Bhavadeep and Vishal had both attended a recent press conference where Narayana Murthy named the founder’s job as building a sustainable, profitable company. Bhavadeep’s footnote is careful: Murthy is right in the right way, but the rule is not black and white. The right shade depends on the business. Growth without profitability can be the right shade for a particular phase; sheer-valuation growth without a path to either is what the 2014-2022 era confused for a shade and treated as the rule. The maturity question is which shade fits the company.
The corollary is what Bhavadeep means when he says India tried to jump the phase. The country went from a services economy to a venture economy without serving the intermediate apprenticeship in price discipline. The investors pushed money into product-market-fit experiments built on copies of Western ideas; the founders accepted the capital and the valuation arithmetic that came with it; the maturity that Indian venture now needs is the one that picks the right shade for its specific business, not the loudest one.
The 80 percent statement, said calmly.
Eighty percent of the startups will not be around next year. Bhavadeep delivers the number without theatre. The reasoning is not a cycle-call; it is a fundamentals call. The companies in question never reached sustainability, never matched a Western valuation grade to an Indian unit-economics grade, and never had a path to cash they did not already need. The capital that financed them is now scarce, the willingness to bridge has thinned, and the survivors will be the ones who built business shapes that can survive on their own working capital.
The statement is interesting less as a prediction and more as a frame for founder behaviour. The 80 percent who will disappear are the ones who did not internalise the price-discipline shade of the previous takeaway. The 20 percent who survive will be the ones who treated capital as scarce even when it was not, and built their hiring, marketing and physical footprint against the lean year, not the abundant one. The investor’s job is to underwrite the 20 percent without paying the price of the 80.
KEF and the krishnagiri factory: timing as the unforgiving variable.
KEF Holdings built a beautiful modular-construction factory in Krishnagiri to ship pre-fabricated panels to Indian construction sites. The technology was real; the architecture-grade execution was visible; the buyer who picked up the company afterwards also went under. Bhavadeep’s framing is that the industry was not yet ready for the product, and a category that needs scale on day one cannot survive its first three years without an anchor adoption commitment. The factory was right; the year was wrong.
The transferable lesson is that the proptech failures in India have rarely been technology failures. They have been timing failures dressed as technology failures. The drone-inspection startups, the modular-construction houses, the brokerage-tech firms each had a working prototype and a missing industry sponsor. The founder who reads the failure as “we built the wrong thing” rebuilds in the next cycle and dies the same way; the founder who reads it as “we built it before the industry could absorb it” spends the next cycle securing the sponsor before the next factory goes up.
The accelerators that did not accelerate.
India had real-estate-themed accelerators in the early-to-mid 2010s — drone companies, procurement-tracking firms, the brokerage-tech middleware around the broker network. Bhavadeep’s blunt read is that they did not look complete, did not converge on a stack, and did not produce a single category-defining company. The accelerator format presumed a startup-first pattern; the industry, organised around scale and relationship, could not actually pick up the demos coming out of the demo days. The accelerators ran; the adoption did not.
The lesson is not that accelerators are wrong but that the founder mix has to match the industry shape. A real-estate accelerator that runs without anchor builders signing onboarding commitments is a software accelerator wearing a hard hat. The right shape, in Bhavadeep’s reading, is industry-led: the senior developers identify the gaps they actually have, the accelerator selects against those gaps, and the demo day is a procurement event, not a pitch event. Nothing else converts.
The procurement-API wedge: a UPI-shaped opening for property.
The most operational idea in the conversation. The top ten Indian developers each hold millions of procurement data points — vendor histories, price curves, lead-time variances, scaffolding-grade specifications, material wastage patterns. The data is closed; each developer treats it as gold. Bhavadeep’s proposal is that if even three of them opened the APIs, the way UPI opened the payments rail, an aggregator could pool the best practices, layer AI on top, and serve the next two thousand mid-size developers off the same scaffolding. The category does not need a hero startup; it needs an open data layer.
The same logic recurs across the conversation. Land titles on blockchain would surface the under-table transactions and let private equity flow into residential the way it has flowed into commercial. A common building-society API would let access, e-commerce delivery, EV charging and visitor management share one identity layer instead of five. Each opening produces a fresh proptech sub-category. The technology is not novel. The political act of opening the closed loop is what is missing.
Resistance lives at the mid-level, not the top.
Bhavadeep names a pattern that survives across every construction firm he has worked with. The senior leadership is broadly willing to adopt technology — the boardroom understands the efficiency case. The resistance is concentrated at the mid- and lower-tier managers, where the new procurement system threatens both the visible discretion and the invisible side income that has made the role bearable. He says it carefully but does not soften it: the underlying friction is that the technology removes the off-book economics that the role quietly depends on.
The implication for the founder is that selling to the chairman is not the same as deploying with the team. The pilot stalls between sign-off and roll-out because the team that has to operate the system was not bought in. The remediation is procedural: design the implementation so that the mid-level role survives the upgrade with status intact, train the team on the system as a productivity tool before it becomes a transparency tool, and accept that the political work is more expensive than the engineering.
The property-as-platform claim and the e-commerce intersection.
Bhavadeep extends proptech outward until it becomes an operating-system claim. Every Indian’s entire life happens against a real-estate substrate — home, office, retail floor, gated community, warehouse. He uses the delivery-rider queue outside the gated society as an example: the rider waits because the building’s access layer is not addressed, the e-commerce company eats the time cost, the resident receives the order late, and three different stakeholders pay for one missing API. The proptech wedge sits at the integration point, not inside the building.
The same framing makes the Shetty-store-versus-app comparison concrete. Single-digit e-commerce penetration in India is not just a consumer story; it is a real-estate story about the durability of the local provision store as a node. If 95 percent of the transaction volume still happens within walking distance of the home, the proptech question is how to make the local store more efficient, not how to disintermediate it. The biggest dollars in the next decade may not be on the e-commerce side at all — they may be on the offline-efficiency side that the e-commerce category has not yet noticed.
The case for a property stack alongside UPI.
The government has built UPI for payments, an agri-stack for farming, and the early scaffolding of a health stack for insurance and care. Bhavadeep argues that the property stack — or the “real India stack” in his framing — is the missing piece. India has 1.4 billion people who need to be housed, employed, transported, and productively located; almost every infrastructure problem the country faces ultimately reduces to a property problem. The case for a public rail is not theoretical; it is the only way to make the residential layer transparent enough to bring private equity in at scale.
The political shape Bhavadeep proposes is industry-first, government-backed. The developers form the initiative; the platform comes from the private side; the government endorses it the way it endorsed RERA. He believes a credible figure inside the policy network would back it if it were presented properly. The cost of not doing it is concrete: government real estate alone is estimated at 500 billion dollars of under-utilised assets, and a transparent rail could surface a meaningful share of that without new legislation.
Agritech is proptech: the warehouse sits underneath the supply chain.
Bhavadeep’s expansion of the proptech boundary lands on agritech with a specific number. Roughly six percent of India’s annual grain output is lost in transit and storage, because the warehouse network is fragmented and unaccountable. The corporate-farming-and-direct-sourcing reforms are real but downstream of the bottleneck. The actual lever is the warehouse and the land it sits on — both real-estate assets. If a property stack made warehouse capacity addressable, the grain-loss number drops, food-supply predictability rises, and Bhavadeep estimates a trillion-rupee addition to the economy follows.
The wider lesson is to look beneath each consumer-facing category for the property substrate it actually rests on. Warehouses for grocery delivery. Cold-storage for pharma. Charging-grid land for EVs. Co-working square footage for the gig economy. The category that calls itself by its consumer outcome is almost always supported by a property layer that does not have an owner-operator yet. The right entry point for a founder is often the layer below the layer the headlines describe.
Fractional and tokenised ownership: the strata-mindset Indian saver.
Bhavadeep is now building toward tokenised real estate on chain, after a decade of watching fractional and strata ownership stall at the same wall. The Indian saver understands real estate better than equities and wants a piece of every project. The product-market fit, in that sense, is structural. The blocker is the mindset: the Indian buyer wants to own the whole piece, not a 10-square-foot strata slice. The fractional companies have brought openness and transparency; what they have not yet broken is the cultural definition of ownership.
The tokenisation move is granularity downward and transparency upward. The chain handles the granularity — a token per square foot or per rental cash-flow stream, depending on the asset. The on-chain settlement handles the transparency — every transaction visible, every cap-table change auditable, the investor able to see the asset state in real time. Bhavadeep is honest that he is early; the regulator has not yet caught up; the model is still being shaped. But the structural argument — Indians understand real estate, want a piece, and need a non-leveraged way in — is the most defensible piece of the new thesis.
Don’t try to figure out India; figure out the Indians figuring it out.
The line lands on a conversation about a Japanese fund that has spent thirty-five years studying India. Maruti Suzuki landed, the appetite is real, the firm has tried every framework, and the country still resists abstraction. Bhavadeep’s instruction is unsentimental: stop trying to figure out India. Identify the Indians who have already figured out India — the founder who has rebuilt the procurement chain three times, the operator who understands every Indian state as a different country — and get on their backs. They will service the world from the local complexity outward.
The framing reads as a foreign-capital instruction but applies just as well to any acquirer or incumbent looking sideways into a category. A national bank trying to break into rural lending. A pharma company trying to address tier-three distribution. The constraint is not the model; the constraint is the operator’s adjacency to the constraint itself. Capital can be deployed against many places; the scarce thing is the founder with the right shoulders.
Founders who will not dilute, and egos larger than the companies.
Bhavadeep names the most common founder pathology he sees in the proptech and adjacent categories. The founder wants an American valuation and an Indian retention pattern. They will not dilute. They will not let others run the company even when their own gift is the idea and not the operation. They will fight among themselves before they will fight the market. The ego, he says, is larger than the company; the company is what suffers for it.
The Flipkart contrast is deliberate. The Indian startup era was defined by Flipkart, and Flipkart was defined by founders who eventually let go. Bhavadeep does not romanticise the exit — not every startup gets the Flipkart exit, not every founder should expect the Flipkart exit — but the absence of the willingness to even consider letting go is what produces the broken cap-tables and the unhappy founder-investor relationships of the post-2022 collapse. The angel filter follows from this: he writes cheques for founders who will let other people kind of participate. The willingness to share is the prerequisite, not a luxury.
What India still owes itself in new cities.
Bhavadeep’s final structural argument is about geography. Singapore is one city. Dubai is one city. India has talented operators clustered in Bangalore, Mumbai, Hyderabad and Pune and is asking them to move to a new financial hub like GIFT City on policy alone. The Indian operator does not move easily; the family unit, the schooling, the food preference, the climate adjacency all count. The government’s mistake, Bhavadeep argues, is to build the new city far from the existing talent cluster rather than next to it. The fix is to seed the next financial hub adjacent to Bangalore or Mumbai with similar weather and a comparable living standard, and let the migration cost stay low.
The deeper claim under the geography argument is about how the country reaches a five-to-ten-trillion-dollar economy. The math requires construction at a pace that is unreachable without private participation and proptech. Capital is not the constraint — international investors want to put money into India today. The constraint is the operational scaffolding to deploy it. The new cities, when they come, will be the test of whether the property stack and the proptech category can support the migration. Until then, the country builds infrastructure faster than the construction industry can absorb the demand.
Lines worth keeping near your desk.
The jargon, unpacked.
Some terms are India-specific proptech vocabulary; some are pan-real-estate. Skim, mark the unfamiliar, return later.
Check what you actually retained.
Try to answer before you click. The point is to notice where the conversation is fuzzy in your memory, then return to the transcript.
Five prompts. Notes save in your browser.
Use these to convert the reading into your own decisions. Nothing is uploaded; storage is local to this device.
Bhavadeep’s margin-shield diagnosis says efficiency follows compression, not technology. In your own category, which incumbents have crossed the compression threshold and which are still wearing the shield
If you had to negotiate an open-API moment for your own category — the equivalent of three top developers opening procurement — which three players would you choose and what would you ask them to open
Where in your operational rollout has the resistance lived at the mid-level rather than the top, and what did the senior sponsor not see about the team’s informal economics
Bhavadeep treats agritech as proptech because the warehouse sits underneath it. What category in your work is one substrate down from the layer the press release describes, and what would you build there
Bhavadeep’s angel filter weights the founder before the idea, and the founder’s willingness to dilute above their conviction. Audit one founder you have backed or considered — what did their cap-table behaviour tell you that the pitch deck did not
The strongest version of the disagreement.
Four counter-arguments an honest sceptic would press on this conversation. Each is written to be persuasive, not to win.
The margin-shield story is too clean — Indian proptech under-performed because the underlying property data is broken, not because incumbents were comfortable.
Bhavadeep’s account treats developer comfort as the binding constraint, but the deeper failure may be in the substrate the software has to read. Indian land titles remain contested across revenue, registration and survey records; legal title is layered with succession, agricultural-versus-residential conversion history and litigation. A procurement-API opening assumes that the underlying data is machine-readable; in practice large parts of it are unreconciled or contradictory. The honest read is that even with margin pressure pushing developers toward adoption, the data layer below cannot yet support a category-defining proptech without a substantial public clean-up first. The accelerators did not fail only because the industry was not ready; they failed because the inputs they were asked to operate on did not actually exist in clean form.
Tokenised real estate is regulatory roulette, not a product thesis.
Bhavadeep’s tokenisation move is operationally elegant but regulator-vulnerable in a way the framing under-weighs. India’s securities regulator treats most token issuance models as either an investment scheme or a collective investment scheme, both of which carry registration and disclosure burdens that are not yet adapted to fractional real-estate tokens. The fractional-ownership operators have built compliance bridges through SEBI-registered intermediaries; pure on-chain tokens have no such bridge in 2023. Building toward tokenisation now, on the bet that the regulator catches up, is a defensible founder choice — but it is more honest to call it a regulatory bet than a market bet. The mindset-fit and the cultural argument are real; the path-to-volume is gated by a Delhi conversation that has not happened.
The mid-level resistance frame under-reads the actual incentive structure.
Bhavadeep names mid-level resistance as the binding adoption constraint and points at the side-income economics that the new system threatens. The stronger version of the argument is that mid-level managers in construction firms are also the people whose technical judgement holds the project together — they catch site issues that the procurement dashboard cannot, they manage the contractor relationships that no API replaces, and they absorb the discretionary calls that the senior leadership does not have time for. The proptech wave that treats them as the obstacle, rather than as the operator whose judgement the software needs to encode, will keep producing pilots that pass the sign-off and stall in the field. The reframing matters because it changes the product. Software that reduces mid-level discretion has a different ceiling from software that augments it.
The Indian-saver-understands-property thesis is selection-biased to the urban middle.
Bhavadeep argues that every Indian understands real estate better than equities, and that this cultural fit is the structural argument for fractional and tokenised products. The sceptical version is that the Indian who understands real estate as a saver is largely an urban, salaried, tier-one or tier-two participant — the population for whom property is the appreciating asset they aspire to. For the rest, property is land that may or may not be theirs, that may or may not be litigated, that does not yet behave like an asset class. Tokenisation may scale beautifully to the first cohort and stall against the second. A retail product addressing only the urban middle is not the trillion-dollar bet the framing implies; it is a fintech segment with a property wrapper. The thesis is correct in direction and over-sized in articulation.
Three readers, three different jobs to do.
Each card is a checklist for one role this conversation is most useful to. Pick the one that fits your week.
If you are a proptech founder
- Profile the buyer pool by gross-margin trend, not by stated digital strategy. The developers running single-digit margins are the buyers; the others are still wearing the shield.
- Secure two named developer-anchor commitments before the first sprint. The user-test that converts is the deal sheet, not the click-through.
- Map the mid-level role you are about to disrupt and design the implementation so the role survives the upgrade with status intact. Train the team on it as a productivity tool first.
- Bake the dubbing-equivalent into the product — a cross-developer module the next ten buyers can adopt with one configuration change. Single-developer custom builds collapse the unit economics.
- If you are pitching the procurement layer, sell the API opening as the wedge, not the SaaS. The category you are competing for is the rail, not the dashboard.
If you are an angel or early-stage investor
- Weight founder behaviour against the last downturn more than founder thesis about the next one. The pattern that survived a previous cycle is the predictive signal.
- Underwrite for the 20 percent that survives the next year, not the 80 percent that excites. The diligence question is least-likely-to-fail, not most-likely-to-grow.
- Read the cap-table as a personality test. The founder who refuses to dilute early will refuse to share decision-making later. Both behaviours compound.
- For proptech specifically, require evidence of industry participation before subscription — a developer letter of intent, a procurement pilot, a paid trial with a tier-one builder. Pure PMF data is the wrong signal here.
- Diversify away from category-funnel duplication. If three of your portfolio companies are racing to the same proptech sub-category, you are paying for the duplication twice.
If you are a developer or industry operator
- Audit one procurement category for the data-opening cost. If the cost of sharing aggregated supplier benchmarks is bounded, the benchmark you receive in return is worth more than the data you give up.
- Form an industry working group with three other developers around one shared pain — resident-access, EV-charging, construction-waste reporting. The proptech founders chase working groups; isolated pilots they ignore.
- Sequence the mid-level training before the system roll-out. The pilot survives the boardroom and dies in the field; pre-empt the second outcome.
- For redevelopment projects, bring the resident-coordination software in earlier than feels necessary. The contract friction at month nine is what kills the project, and the software has to be load-bearing by then.
- Petition the relevant regulator for a tokenised-real-estate sandbox window. The first developer to ship under a sandbox carve-out sets the regulatory shape for everyone behind them.
The whole conversation, searchable and timestamped.
Search the text, highlight what matters, and export your highlights and notes together. Click any timestamp to jump in the video.