Pay-Per-Consented-Intro vs Pay-Per-Lead for Builders

The invoice that doesn't add up

Every month, a mid-sized developer's marketing head opens the portal invoice and does the same silent arithmetic: 340 leads purchased, 41 actually answered the phone, 9 booked a site visit, 1 converted. The cost per lead looked reasonable on the rate card. The cost per sale, once you divide the real invoice by the one signed booking, tells a very different story — and it's the number that should have been on the rate card in the first place.

This is the structural problem with pay-per-lead pricing: it charges for contact, not for intent. A portal that sells the same "lead" to four competing builders in the same micro-market has no incentive to filter for genuine interest — volume is the product. The builder pays per name, then pays again in sales-team hours chasing numbers that never planned to answer a builder's cold call. An alternative has been gaining traction as data-privacy rules tighten and buyer patience with resold contacts wears thin: pay-per-consented-intro, where the fee attaches to a buyer who explicitly opted in to be reached by your project specifically, not to a name pulled from a shared database. This article walks through both models with real Rupee math, so you can decide which one your budget should actually be funding — not which one the portal salesperson prefers.

Two very different things being called "a lead"

The word "lead" hides a real difference in what you're buying.

Pay-per-lead (volume model). A portal aggregates contact details — sometimes from a form fill, sometimes from a phone number captured against multiple listings at once — and sells access to that contact to some number of builders paying to be in front of the same person. The builder pays a fixed cost per lead (CPL) regardless of whether that person ever intended to talk to them specifically, or whether they've already committed to a rival project down the road. Exclusivity, when it exists, usually costs extra.

Pay-per-consented-intro (intent model). The buyer goes through a defined discovery flow — describing their requirement, budget, and locality preference — and only after that do they choose to release their contact to a specific matched project. The fee attaches to that release event, not to a database row. Crucially, this is a mechanism DPDP-era platforms are built around by design: consent is captured at the point the buyer's data moves to a third party, which is exactly what India's privacy rules now require as standard practice, not a nice-to-have.

According to Deloitte India's coverage of the DPDP Rules 2025, the DPDP Act 2023 combined with the 2025 Rules requires consent before personal data is shared with a third party, with penalties running up to Rs 250 crore for non-compliance (source: Deloitte India, "India's DPDP Rules 2025," 2025). A resold lead — captured for one purpose and distributed to several builders without the buyer choosing each recipient — sits closer to the compliance risk zone this framework was written to close. A consented intro, by construction, already has that consent event on record.

Where the market is headed, and why unit economics start to matter more

India's real estate sector isn't shrinking into a market where volume-based lead buying gets easier to sustain — it's scaling into one where competition for the same qualified buyer intensifies. IBEF's real estate industry report puts the sector on a trajectory from roughly US$200 billion in 2021 to US$1 trillion by 2030, and potentially US$5-7 trillion by 2047 (source: IBEF, "Real Estate Industry in India," Feb 2026). Institutional investment into Indian real estate reached US$10.5 billion across 78 deals in 2025 per the same report — capital that is funding more supply, more listings, and more builders bidding for the same pool of ready buyers.

When more builders chase the same demand, the cost of a shared, resold contact tends to rise while its usefulness per builder falls — you're one of several callers a buyer hears from within hours of filling one form. A model priced around a buyer's one-time, specific opt-in doesn't face the same dilution: the intro is already directed at you.

Step-by-step: how to actually evaluate the two models before committing budget

1. Pull your last 90 days of portal lead data. Total leads purchased, total spend, and — this is the number portals rarely surface for you — how many of those leads ever answered a call or replied to a message.
2. Calculate your true CPL. Total spend divided by leads that made real contact, not leads purchased. This is usually 3-6x the "headline" CPL quoted on the rate card.
3. Track your leads-to-sale ratio for the same period. How many contacted leads did it take to close one unit.
4. Visit /builders and review the consented-intro structure DrawMagic uses, where the fee is tied to a buyer completing a requirement flow and choosing to release contact to your project.
5. Check the intro-to-sale ratio you'd expect based on how targeted the intro is — a buyer who specified your locality, budget band, and configuration before opting in should convert at a materially higher rate than a shared contact.
6. Model both costs per sale (see the worked table below) using your own historical conversion numbers, not industry averages.
7. Pilot in parallel for one quarter rather than switching outright — run a subscription tier via /builder/subscription alongside your existing portal spend, and compare the two cost-per-sale numbers with real data before reallocating budget.
8. Review your /builder/leads dashboard to see how each intro records the buyer's stated requirement — the data that would have taken your sales team a full qualifying call to extract from a cold portal contact.

Cost comparison: what each model actually charges for

A Mumbai MMR scenario

Take a mid-scale project in Thane, competing in one of India's highest-CPL markets. The developer buys 500 portal leads a month at an advertised Rs 250 per lead — Rs 1,25,000 in headline spend. Of those 500, roughly 60 ever pick up a follow-up call (a familiar attrition pattern in resold-lead markets), 12 convert to a site visit, and 1.5 close per month. True cost per sale: Rs 1,25,000 ÷ 1.5 ≈ Rs 83,000 — and that's before counting the sales team hours spent dialling 440 numbers that never intended to engage a builder directly.

Now run the same project on a consented-intro model at, say, Rs 1,200 per intro — a materially higher unit price. If 40 intros come through in a month because they're generated from buyers who've already specified Thane, a 2BHK, and a Rs 60-90 lakh budget before opting in, and the tighter targeting lifts conversion to 1 in 8 rather than 1 in 8-plus-heavy-attrition, that's 5 closes from Rs 48,000 in spend — a cost per sale near Rs 9,600. The unit price per contact went up; the cost per sale went down, because the model charges for intent, not volume. High-CPL markets like Mumbai MMR and NCR are exactly where this gap tends to be widest, since portal bidding wars inflate the resold-lead price without improving its qualification depth.

Two pricing models, side by side: the worked cost-per-sale math

Use your own historical conversion numbers to rerun this table — the ratios above are illustrative of the mechanism, not a promise of results for any specific project.

Pro tips for builders switching models

1. Don't cancel your portal spend on day one. Run both in parallel for a full sales cycle before reallocating budget; real conversion data beats a spreadsheet estimate.
2. Ask what "consent" actually means on any platform claiming it. A checkbox buried in generic terms is not the same as a buyer choosing your specific project.
3. Track cost per sale, not cost per lead, in every marketing review. CPL is the metric portals want you watching; cost per sale is the one that pays your team's salaries.
4. Weight your intro budget toward your highest-CPL micro-markets first — that's where the gap between the two models is largest.
5. Review the /how-it-works buyer-consent flow so your sales team understands what a buyer has already disclosed before the call, and can skip re-asking basic qualifying questions.

Common mistakes to avoid

1. Comparing headline CPL to headline intro price without adjusting for real contact and conversion rates. A cheaper unit price on paper can be a more expensive channel in practice.
2. Treating DPDP consent as a legal checkbox rather than a lead-quality signal. A buyer who consented to be contacted specifically is, on average, a warmer prospect than one whose number was captured incidentally.
3. Switching 100% of budget on a single month's data. Real estate sales cycles run months, not weeks — validate across at least one full cycle.
4. Ignoring sales-team time cost. The hours spent dialling unqualified numbers are a real cost that rarely appears on the marketing line item but shows up in lower team productivity.
5. Assuming every "verified lead" claim from a portal means consented and exclusive. Ask the platform directly how the contact was captured and how many builders it was sold to.

Where this fits with the rest of your DrawMagic setup

The consented-intro model isn't a standalone feature — it's the pricing logic behind the builder subscription tiers at /builder/subscription, and it's what shows up as structured buyer requirements inside your /builder/leads dashboard rather than a bare name and number. If your team hasn't walked through the underlying buyer flow yet, /how-it-works covers how a buyer's requirement brief turns into a specific, opted-in introduction rather than a resold contact. A capability like /buyer/intelligence — richer buyer readiness and affordability signals attached to each intro — is still evolving on the roadmap, but the core consent-based intro mechanism is live today.

This is general market and pricing information, not financial or legal advice — DrawMagic is a software and information platform, not a broker, lead reseller, or compliance advisor. For DPDP compliance obligations specific to your business, consult a licensed legal or data-privacy professional.

Key takeaways

• Pay-per-lead charges for contact regardless of intent; pay-per-consented-intro charges for a buyer who opted in to reach your specific project.
• The metric that matters for budget decisions is cost per sale, not cost per lead — a higher unit price with better conversion can be far cheaper per closed sale.
• DPDP Rules 2025 require consent before third-party data sharing, with penalties up to Rs 250 crore, making consent-first models a structural compliance advantage, not just a marketing angle (per Deloitte India, 2025).
• IBEF projects the real estate market scaling toward US$1 trillion by 2030, meaning competition for the same buyer pool — and the cost of shared, resold leads — is likely to intensify, not ease.
• High-CPL markets such as Mumbai MMR and NCR tend to show the widest gap between the two models' true cost per sale.
• Always calculate true CPL using leads that made real contact, not leads purchased, before comparing models.
• Pilot a consented-intro subscription via /builder/subscription in parallel with existing portal spend for a full sales cycle before reallocating budget.
• Review structured buyer requirements on /builder/leads to see what a consented intro discloses that a cold portal contact does not.
• Never assume a portal's "verified lead" claim means consented and exclusive — ask directly how the contact was captured and distributed.

FAQ

Is a consented intro always cheaper than a portal lead? Not on a per-unit basis — the intro price is often higher. It tends to be cheaper on a cost-per-sale basis because of higher real contact and conversion rates, but you should validate this with your own data using the worked-example method above, not assume it applies to every project.

Does DPDP compliance apply to lead-buying specifically? DPDP Rules 2025 govern how personal data is collected, shared, and consented to generally, which includes third-party lead sharing. This article summarizes general information only; consult a licensed legal professional for how DPDP obligations apply to your specific lead-sourcing arrangements.

Where do I see the consented-intro pricing structure? Visit /builder/subscription to review current tiers, or start at /builders to explore the full developer landing page and sign up if you're ready to pilot.