/* /builders — onlyWA for builders and developers. * * Why this page exists: builders are the second vertical the app is built for * (projects, units, site visits, bookings, progress updates — all shipped on * 10 Sep 2026, see docs/REAL-ESTATE-ROADMAP.md), but until now the site had * nowhere to send one. The /demo/realty link existed and no page pointed at * it; a builder who clicked an ad landed on a page about service reminders * for cars. * * What it says, in this order: the four moments of a builder's day that the * app puts on WhatsApp (roadmap §2.1, §2.2, §2.4 and the channel-partner desk * W5), then broadcasts and the owner's evening summary, then what it * deliberately does not do. The "does not" block is part of the pitch, not a * disclaimer: a builder's fear is a bot that quotes the wrong price or asks * for money on WhatsApp, and saying plainly that it never does is what makes * the rest believable. * * Rules this file keeps (docs/MARKETING.md §1): * - Say the job, not the category. No "platform", "CRM", "engagement". * - No invented numbers. Every figure in an illustration belongs to * Aarambh Developers, the FICTIONAL builder from the app's demo * (src/app/mock.jsx), and the illustration says so. No real client's * name appears here, ever — this page is shared with prospects. * - No prices. Our fee lives in pricing.jsx and Meta's rates on /pricing; * a figure typed here would be a third copy that drifts. * * Same design system as dealersaarthi.jsx (pp-* classes from styles.css, * tokens only so html.dark keeps working); page-scoped CSS below is prefixed * .bl-. Mounted by builders.html with Nav + Footer. Lives at /builders * (cleanUrls in vercel.json serves builders.html there). */ // The platform's own number, as in contact.jsx. The `DEMO BUILDERS` prefix is // the entry code: the onlyWA demo journey files it as entry:BUILDERS, so the // Journeys funnel shows how many builders came from this page // (docs/DEMO-NUMBER.md → Entry codes). const BL_WA_HREF = 'https://wa.me/919288416463?text=' + encodeURIComponent('DEMO BUILDERS'); // A redirect in vercel.json to the app running on the fictional builder's // fixtures (/app?mock=1&industry=real_estate). Nothing a visitor does there // reaches a server, which is why it is safe to hand to anyone. const BL_DEMO_HREF = '/demo/realty'; /* The hero illustration: an enquiry answered, and the availability chart the * app draws from the units table. Both are pictures of real screens with the * demo builder's data — aria-hidden because the copy beside it already says * everything they show. */ function BLStage() { // Tower B, floors 6 → 1, four flats a floor. a = available, h = on hold, // b = booked. Illustrative only; the real chart is rendered per project. const floors = [ ['6', 'aabh'], ['5', 'abba'], ['4', 'bbab'], ['3', 'bhbb'], ['2', 'bbbb'], ['1', 'babb'], ]; return ( ); } function BLHero() { return (
Home
onlyWA · for builders and developers

Answer every enquiry and every buyer on WhatsApp — from your own number.

The brochure and price band in seconds, even at 11 pm. Site visits booked and reminded. Construction updates in every buyer's chat until possession. Every lead a channel partner sends, registered with the time. One app your whole sales team replies from.

{/* Said up front because the demo is the fixture, not a login: a builder should know before clicking that nothing they try there sends a real message. */}

The demo opens the real app on a fictional builder's projects. Click anything; nothing is sent.

); } /* The four moments, in the order a buyer lives them. Each "points" line names * something that is shipped today — if a line here stops being true, the line * goes, not the caveat. Where each one lives (checked 18 Sep 2026): * 01 journeys/presets.js realty_lead_intake (brochure, dated price lines, * RERA line, the three buttons, sets interested_project_id) * 02 vertical/real_estate.js site_visit_reminder [1, 0] — sent by the * morning reminders run (09:00–12:00 IST), so "the day before", not * "the evening before" as the roadmap first had it; automations * post_visit_nudge and site_visit_no_show; the #/site-visits board * 03 bookings/upsert.js (the "Your home" card), projects/progress.js, * agreement_due / registry_due / possession_soon * 04 _lib/cp.js (contact card → registration, 60-day window, refusal * without naming the other partner), cron/cp-digest.js (Monday board); * availability on request is the AI assistant's send_availability_chart * tool, so that line says it needs the assistant. */ function BLMoments() { const moments = [ { n: '01', t: 'An enquiry gets its answer in seconds', b: 'Whether they tapped a Facebook ad, scanned the QR code on a hoarding or typed the project\'s name, the reply arrives while they are still looking.', points: [ 'Brochure, price band on carpet area, location and RERA number', 'Three buttons: book a site visit, send the price list, call me', 'Every price is dated "as of", so nobody is quoted last month\'s rate', 'The lead lands in your list, filed under the project they asked about', ], }, { n: '02', t: 'Site visits booked, reminded and followed up', b: 'Weekend slots offered first, because that is when families visit. Your team sees today\'s visits on one board.', points: [ 'A confirmation with the location and who will meet them', 'A reminder the day before, and again on the morning of the visit', 'Visited but not booked: a thank-you and the price list the next day', 'No-show: two new slots the same day, one more nudge three days on', ], }, { n: '03', t: 'Buyers hear from you until possession', b: 'Delay and silence are what buyers complain about between booking and possession. You cannot always fix the first; one photo and one line a month fixes the second.', points: [ 'A "Your home" card at booking: project, unit, possession date', 'Post a progress photo once; every buyer of that project gets it', 'Reminders for agreement, registry and possession dates', 'No demand notes and no payment requests, ever', ], }, { n: '04', t: 'A channel-partner desk on WhatsApp', b: '"Who brought this client?" ends when every lead a partner sends carries a time stamp.', points: [ 'A partner forwards a contact card and gets it registered to them, with the time', 'Another partner is told the lead is taken, without being told by whom', 'With the AI assistant on, partners ask what is left and get the dated chart', 'Every Monday, each partner\'s rank by bookings — no commission figures', ], }, ]; return (

Four moments of a builder's day, on WhatsApp.

Each one used to be a phone call someone forgot to make. Now it goes out from your number on its own, and your team steps in when a buyer wants a person.

{moments.map(m => (
{m.n}

{m.t}

{m.b}

    {m.points.map(pt => (
  • {pt}
    • ))}
))}
); } /* Broadcasts and the owner's summary sit apart from the four moments: they * are not a step in a buyer's journey, they are how the owner reaches * everyone at once and how he hears what happened. The summary illustration * uses the demo builder's names and is labelled as such. */ function BLOwner() { return (

Reach everyone at once. Hear how the day went.

Broadcasts without getting blocked
A new launch, a Dhanteras booking offer, a price revision, "4 flats left in Tower B" — to your whole list from your own number, on Meta's official platform, paced to your number's daily limit. Only people who agreed to hear from you, and STOP is honoured in English and Hindi.
The owner's summary on WhatsApp
At 9 pm, or the hour you pick: enquiries by source, visits booked and done, bookings, what each site visit cost from your real Facebook ad spend (once your ad account is connected), and which leads nobody has touched for two days. No dashboard to open.
Evening summary · example
Aarambh Developers — today
Enquiries: 14 (Facebook 8, portal 4, hoarding 2)
Site visits: 6 booked, 2 visited, 1 no-show
Bookings: 1 — Shanti Crest B-704
Ravi has 3 leads untouched for 48 h

Figures from the fictional demo builder, not a client.

); } /* What it will not do. Each line is a decision in REAL-ESTATE-ROADMAP.md §0 / * §7, and each is something a builder has been burned by or fears. */ function BLLimits() { const limits = [ { t: 'No payments on WhatsApp', b: 'No demand notes, payment links, EMI or receipts. Money stays with your accounts team.' }, { t: 'No exact prices or discounts from the assistant', b: 'It quotes the dated price band you set and hands the exact unit price, discounts, loans and legal questions to your team.' }, { t: 'No "assured returns" talk', b: 'Anything shaped like guaranteed returns or buyback is refused and handed to a person.' }, { t: 'Your sheet stays the record', b: 'Holds and allotments stay in your sheet or your CRM. The app mirrors the unit status you mark and counts "flats left" from it, never from a typed number.' }, ]; return (

What it will never do.

What a builder worries about most, answered before you ask.

{limits.map(l => (
{l.t}
{l.b}
))}
); } /* Going live, in the order docs/CLIENT-ONBOARDING.md insists on: projects * before leads, because every lead, visit and price hangs off a project. */ function BLHowItWorks() { const steps = [ { n: '01', t: 'Your projects first.', b: 'Configurations, carpet areas, price bands, RERA number, possession date — and the unit list if you keep one.' }, { n: '02', t: 'Your leads come in.', b: 'Upload your telecalling sheet or a portal export. Each lead is matched to its project.' }, { n: '03', t: 'Your number goes live.', b: 'Your own WhatsApp number on Meta\'s official platform, the messages approved by Meta, set up with you.' }, { n: '04', t: 'Your team replies from one app.', b: 'One shared inbox for every executive, a login each, and the evening summary for you.' }, ]; return (

From your spreadsheet to live, done with you.

Meta's business verification is the longest step. We start it on day one and set up everything else alongside.

{steps.map(s => (
{s.n}

{s.t}

{s.b}

))}
); } function BLCTA() { return (
Try it before you talk to us

See a builder's day in the app.

Projects, site visits, bookings and the availability chart, on a fictional builder's data. Then ask us anything on WhatsApp.

{/* Prices are linked, not restated: pricing.jsx owns our fee and /pricing owns Meta's rates, and a third copy here would drift. /pricing#features has a row for each builder message (the booking card, progress updates, the partner board, replies to a partner's card) before and after Meta's 1 Oct 2026 change — which is also why nothing on this page calls a reply free. */}

What it costs — our monthly fee, and what Meta charges for each builder message before and after 1 October 2026 — is on the pricing page.

); } function Builders() { return ( <> ); } window.Builders = Builders;