Not “find a Pandit.”
Right ritual × right specialist × right location × right muhurat.
“Har Puja ke liye wahi Pandit Ji, jo us Puja mein visheshagya hain.”
The relationship belongs to JiPanditJi — Aapke Ghar Ke Pandit Ji. The ritual is performed by whichever verified specialist is actually right for it. The family never has to search, compare or judge a Pandit profile themselves; JiPanditJi takes that responsibility. This is the single idea every zone, ritual, message and channel decision below must reinforce.
FRLV (Family Ritual Lifetime Value) is a management metric for this dashboard. It is never customer-facing language — nor are RAH, MPC or Competency Passport. The customer only ever hears the promise above in plain Hindi/English.
What we are NOT
A Pandit directory. A lead marketplace. A discount platform. An astrology fear-selling app. A “1000+ Pandits” numbers game.
What we ARE
A managed ritual expertise network. We know which verified specialist should serve which family, for which ritual, in which geography and muhurat — and we deliver that consistently.
The moat
Not Pandit count. The accumulated operating knowledge connecting RAH → Ritual Matrix → MPC → Certification → Allocation → Satvik Quality → Family ID → FRLV.
Public Introduction — Pehchaan Banao, Pitch Mat Karo
JiPanditJi ek naya business nahi, ek naya category hai — market ko abhi pata hi nahi ki aisi koi entity exist karti hai. Is section ka kaam sirf ek cheez hai: naam ko public consciousness mein naturally discoverable banana — bina kisi individual ko pitch kiye, bina paid advertising ko default answer banaye. Enquiry, conversion, CAC, Google Ads — sab Section 02 se aage ki baat hai; wo tab kaam karega jab yeh phase pehle chal chuka ho.
Sell JiPanditJi.
Pitch individual families. Lead with an offer. Make paid advertising the first and default touchpoint. Ask for a booking before anyone knows what the name means.
Make JiPanditJi discoverable.
Let people encounter the name passively, hear it socially, then see it demonstrated as real — in that order — so that by the time they have a genuine ritual need, the name is already familiar, not a cold pitch.
The Exposure Sequence — Dekhna → Sunna → Mehsoos Karna → Khojna
A name has to be encountered multiple times, in different registers, before it feels ‘real’. This sequence is the actual mechanism — each step is deliberately not an ask.
Online Existence Signals
Owned and earned, before paid. Each builds ‘this is a real, established thing’ — not ‘someone is trying to sell me something’.
Not a sales site. A genuinely useful public reference: ‘Griha Pravesh muhurat kaise nikalein’, ‘Rudrabhishek kya hota hai, kab karayein’, ‘Satyanarayan Katha ki vidhi’. People search the QUESTION, not ‘book a pandit’ — they find JiPanditJi answering it respectfully, with the name attached.
A real, verifiable local presence per P0 zone — photos, service area, genuine reviews as they accumulate. Makes JiPanditJi look like an established local entity, not a website that appeared yesterday.
JustDial, Sulekha, local community app listings, WhatsApp Business catalog — unglamorous but this is where an ‘is this a real business’ check happens for a cautious Indian household.
Short, respectful explainers — same visual identity every time (maroon/gold, same logo mark) so repeated exposure reinforces one consistent memory, not scattered content.
Chander speaking (LinkedIn, local business forums, podcasts) about the specialist-Pandit insight — press finds ‘category creator founder’ stories genuinely interesting; this earns coverage paid ads cannot buy.
Dainik Jagran / Amar Ujala / local editions and Delhi-NCR hyperlocal digital publications run human-interest ‘naya concept’ stories for free — ‘Aapke Ghar Ke Pandit Ji: NCR mein ek naya concept’ is a real story, not an ad.
Genuinely answering questions in society/local groups (with disclosure, not spam) — people remember who actually helped, not who pitched.
A clear, neutral, well-sourced public profile (company registry info, founding story, what the category is) — signals permanence and legitimacy when someone checks.
Ground Existence Signals
Physical, ambient, repeated — where Delhi NCR households actually spend attention, without a hard sell attached.
The single highest-leverage ground tactic in Indian households. A genuinely useful wall calendar (muhurat dates, festival calendar, Ekadashi/Purnima list) with the JiPanditJi mark — stays on the kitchen/pooja-room wall for 12 months of passive, repeated, zero-cost exposure. Distributed free via societies, not sold.
Every empanelled Acharya arriving in a visible JiPanditJi ID/badge (and where feasible, a simple branded bag/kit for samagri) turns every single booking into ambient visibility for the whole building — neighbours see it happen, not just the booking family.
Where a genuine temple/Acharya-network relationship exists, a small respectful signage — ‘Empanelled specialists available via JiPanditJi’ — borrows the temple's existing trust, in a location people already associate with ritual authenticity.
Not a discount poster — a genuinely useful one: this month's shubh muhurat dates, an upcoming festival's correct vidhi summary, with the name quietly present. People read useful noticeboard content; they skip sales posters.
Small standees at 2–3 high-dwell-time neighbourhood shops per zone (kirana, chemist, chai shop) — classic hyperlocal Indian ambient advertising, extremely cheap, extremely repeated exposure for local residents.
Low-cost, hyper-local, culturally familiar formats — an auto panel or a local cable TV crawler line in the P0 zones builds the ‘this is a known local name’ feeling faster than any digital format for an older/family-decision-maker audience.
Sponsoring (not overtly branding) a small local Navratri pandal, a society Diwali mela stall, or a Ganesh Chaturthi community event — presence without a hard sell, in exactly the moment ritual is on people's minds.
A small, real event in the first Tier A zone — e.g. a respectfully organised Griha Pravesh or community Puja that local press/RWA can point to as ‘JiPanditJi's first ceremony here’ — gives the brand an origin story people can retell.
Phase 0 Timeline — Before the 13-Week Performance Calendar
This precedes and overlaps with Section 14's 13-Week Execution Plan. Ground/content signals start immediately (Week 1); performance marketing (Search/Meta/ Society desks/Budget — Sections 07–13) switches on only once recognition exists, around Week 10, so it is answering a half-known name rather than introducing a stranger.
- Panchang calendar design finalised + printed for Tier A zones
- First 8–10 kirana/chai-shop standees placed
- Society noticeboard content (muhurat calendar) placed, non-sales
- Acharya ID/badge + visible kit rolled out for every live booking
- Google Business Profile + directory listings live for Tier A
- Ritual knowledge hub: first 6–8 genuinely useful guides published
- 3–4 explainer reels/shorts — consistent visual identity
- Organic participation in 5–10 local WhatsApp/Facebook groups
- Pitch 2–3 hyperlocal press outlets with the ‘category creation’ story
- Temple/Acharya-network plaque conversations begin
- Track branded search volume for ‘JiPanditJi’ specifically (not generic ‘pandit near me’)
- Informal ‘have you heard of JiPanditJi’ pulse-check in 2–3 Tier A societies
- First press piece runs (if secured)
- Symbolic local launch moment executed in strongest Tier A zone
- Direct/type-in website traffic and WhatsApp mentions-by-name tracked
- Google Search/Meta campaigns launch into a market that already half-recognises the name
- Society desks convert faster because the noticeboard/calendar primed the residents
- CAC should trend better than a cold-market baseline — track this explicitly as validation
- Public-introduction assets continue running alongside performance marketing, not replaced by it
What NOT to do in Phase 0
- Do not cold-pitch individual families — Phase 0 is recognition, not conversion
- Do not make paid advertising the first or default touchpoint
- Do not lead with discounts or offers — it signals ‘unknown business trying too hard’, not ‘established category’
- Do not scatter visual identity across formats — same mark, same palette, every single touchpoint
- Do not skip straight to Section 07–13 performance marketing before some Phase 0 recognition exists — CAC will be materially worse in a genuinely cold market
Measuring Recognition (not conversion)
Searches for “JiPanditJi” by name, not generic “pandit near me” LIVE
People typing the URL/name directly LIVE
Enquiries that name JiPanditJi before being told about it LIVE
“Have you heard of…” spot-checks in Tier A societies ASSUMPTION
90-Day North Star
Bookings and GMV alone reward low-quality one-time growth. The number the Founder should watch every Monday is families whose ritual was actually completed by a matched specialist — not clicks, not impressions, not followers.
Completed Specialist-Matched Ritual Bookings
A booking only counts once the ritual is completed by a Pandit certified for that exact ritual. This is the single number that proves the specialist-matching promise is real, not just a marketing line. ASSUMPTION exact qualifying definition to be locked with Ops in Week 1.
Raw bookings can be hit by discounting or mismatched allocation. GMV can rise while specialist match rate quietly falls. The North Star must fail loudly if we win volume by breaking the specialist promise.
Vanity reach metrics do not tell the Founder whether a real family trusted us enough to invite a Pandit into their home. They are diagnostic for channels, not a business-level North Star.
Leading Indicators (this week's actions move these)
| Qualified enquiries | Growth/CRM |
| Booking conversion % | Growth |
| Specialist match rate | Ops ≥ 98% |
| On-time arrival % | Ops ≥ 95% |
| Society activations live | Society |
Lagging Indicators (prove whether it worked)
| Completed rituals | Ops |
| New families acquired | CRM |
| Repeat bookings (90D) | CRM |
| Referral bookings | CRM |
| CAC / Contribution per booking | Finance |
| Ritual-specific rating | Quality ≥ 4.7/5 |
P0 Geographic Battlefield
30-zone Delhi-NCR structure and RAH model per the attached Excel SOURCE. We are not making all of NCR aware of JiPanditJi in 90 days — we are dominating four contiguous Tier A zones before expanding to the rest of the P0 Eastern NCR corridor.
Schematic cluster map of the 11 P0 Eastern-NCR zones (not GIS-accurate) — arranged by the Ghaziabad → East Delhi → Noida → Greater Noida contiguous corridor described in the strategy master. Block size is illustrative, not proportional.
Tier A — Attack First
Selected on RAH, monthly booking potential, pandit pool depth and corridor contiguity (highest-demand zones that also sit next to each other, so specialists can be shared per the strategy master's Level-2 zone-sharing logic).
Greater Noida West
Noida North
Indirapuram
Siddharth Vihar-Crossings
Tier B — Expand After Proof
Remaining P0 Eastern-NCR zones. Opens only after the Day-45 gate (Specialist Match ≥ 98%, On-time ≥ 95%, first repeat cohort visible in Tier A).
Noida Expressway
Mayur Vihar
Preet Vihar-IP Ext.
Vasundhara
Noida Central Premium
Noida Central
Vaishali-Kaushambi
Full 30-Zone Model — Live Recalculation
| Zone | Cluster | Tier | HH Est. | RAH | Addressable Occasions/Yr | Capture | Bookings/Mo | Annualised GMV | Pandit Pool | Density |
|---|
| Zone | Why it matters | Primary channels | Operational risk | Pandit supply need |
|---|---|---|---|---|
| GN-01 Greater Noida West | Largest single RAH in P0 (115,500) and biggest pandit pool (13) — anchors the whole Greater Noida West flank and de-risks Griha Pravesh MPC. | Society RWA tie-ups in Gaur City/Techzone, Google Search (Griha Pravesh + Vastu keywords), Meta retargeting on new-possession societies. | Largest new-apartment base means concentrated possession dates → severe Griha Pravesh muhurat clustering; requires the deepest floating backup bench. | Recruit/certify 3–4 additional Griha Pravesh/Vastu specialists before Week 6; this zone alone can exhaust core bench on one strong muhurat date. |
| NO-03 Noida North | Very high density, established professional households, strong Rudra/Sanskar mix — good for both acquisition and repeat. | Google Search (Rudrabhishek, Satyanarayan), Society Puja desks, WhatsApp group activation in resident communities. | Only 6 pandits in pool against 21.8 bookings/month base demand — tightest ratio in Tier A. | Priority recruitment target; cross-certify 2 existing Family/Regular Puja pandits into Griha Pravesh/Rudra where evidence supports it. |
| GZ-01 Indirapuram | Strategy master's explicit ‘ideal pilot guild’ — very dense apartments, high local repeat potential, easy specialist sharing with GZ-02/03/04. | Elevator/lift branding, RWA festival activity, Google Search geo-fenced to Indirapuram, referral seeding from first completed families. | Adjacent zones (GZ-02/03) will lean on this guild's specialists — protect travel buffers so Indirapuram bookings are never starved to serve neighbours. | Build the first fully-certified guild here: target 8–10 core + backup across Family, Griha Pravesh and Rudra competencies by Day 30. |
| GZ-04 Siddharth Vihar-Crossings | Rapid new-home formation — ‘exceptional Griha Pravesh’ signal in source data; young upper-mid households are the highest-intent new-customer segment. | Griha Pravesh landing page + Google Search, new-possession-society partnerships, standee/QR at sales/possession offices where permitted. | Young-family demand is muhurat-concentrated around possession waves; travel radius should flex 5–7 km per the ritual-radius table. | Pre-lock Griha Pravesh specialist availability around known possession dates; this is the zone most exposed to MPC-driven stockouts. |
Hero Ritual Strategy
Seven rituals carry the first 90 days, selected against search intent, frequency, AOV, muhurat sensitivity, specialist differentiation and cross-sell potential from the Ritual Taxonomy SOURCE. We do not market 300+ rituals equally.
| Primary search keywords | griha pravesh pandit, housewarming puja pandit near me, vastu shanti pandit |
| Specialist proposition | Griha Pravesh Specialist — not a generalist — matched to your muhurat window |
| Landing-page message | “Naya ghar, sahi shuruaat. Aapke Griha Pravesh ke liye visheshagya Pandit Ji.” |
| Likely objection | “Any Pandit can do Griha Pravesh” |
| Trust proof required | Verified Griha Pravesh ceremony count + ritual-specific rating on Pandit card |
| Suggested CTA | Check muhurat & book specialist |
| Cross-sell / next family opportunity | Vastu Shanti bundle → Satyanarayan Katha (first festival) → Family ID created |
| Primary search keywords | satyanarayan puja pandit, satyanarayan katha at home |
| Specialist proposition | High-frequency family ritual — reliable, on-time, familiar specialist where possible |
| Landing-page message | “Ghar ki khushi, bina chinta ke. Aapka trusted Satyanarayan Pandit Ji, samay par.” |
| Likely objection | “Why pay platform when local Pandit is cheaper” |
| Trust proof required | On-time arrival %, ritual-specific rating, transparent dakshina policy |
| Suggested CTA | Book this month's Puja |
| Cross-sell / next family opportunity | Festival Puja reminders (opt-in) → Dhoopana/samagri subscription |
| Primary search keywords | rudrabhishek pandit, rudrabhishek puja at home, shiv puja pandit |
| Specialist proposition | Rudra/Shiv Specialist — correct mantra and sequence, not a generic Puja Pandit |
| Landing-page message | “Rudrabhishek sirf mantra nahi, parampara hai. Isliye hai visheshagya Pandit Ji.” |
| Likely objection | “How is this different from any temple Pandit” |
| Trust proof required | Rudra-specific certification badge + verified ceremony count |
| Suggested CTA | Talk to a Rudra specialist |
| Cross-sell / next family opportunity | Mahamrityunjaya Anushthan (if genuine need) → Graha Shanti |
| Primary search keywords | mahamrityunjaya puja pandit, mahamrityunjaya anushthan at home |
| Specialist proposition | Senior Specialist Acharya — advanced mantra competence, protected duration |
| Landing-page message | “Gambhir avsar ke liye, gambhir visheshagya. Senior Acharya, poori nishtha ke saath.” |
| Likely objection | “This feels expensive for a home Puja” |
| Trust proof required | Senior Specialist status, advanced mantra assessment evidence, supervised-ceremony history |
| Suggested CTA | Request senior specialist consultation |
| Cross-sell / next family opportunity | Family ID continuity → future Pitru Karma / annual Anushthan |
| Primary search keywords | naamkaran sanskar pandit, baby naming ceremony pandit |
| Specialist proposition | Lifecycle Sanskar Specialist — gentle, family-language matched |
| Landing-page message | “Naye sadasya ka shubhaarambh, sahi Sanskar Visheshagya ke saath.” |
| Likely objection | “We already know a family Pandit for this” |
| Trust proof required | Language/tradition match shown upfront on Pandit card |
| Suggested CTA | Plan your Naamkaran date |
| Cross-sell / next family opportunity | Annaprashan → Mundan (only when family reaches that stage) |
| Primary search keywords | vivah pandit, shaadi pandit booking, wedding puja pandit NCR |
| Specialist proposition | Senior Vivah Acharya — tradition and language fit outranks proximity |
| Landing-page message | “Vivah sirf ek din nahi, ek parampara hai. Isliye Senior Vivah Acharya, sahi bhasha aur riti ke saath.” |
| Likely objection | “Family priest tradition is hard to replace” |
| Trust proof required | Tradition/regional competency tags (e.g. Marwari Vivah) verified on profile |
| Suggested CTA | Reserve your wedding date early |
| Cross-sell / next family opportunity | Full family lifecycle — highest FRLV entry point, seasonal pre-lock required |
Message Architecture
One proposition, four levels of depth, respectful of Pandits and tradition throughout.
Campaign Message Territories
“Kya har Pandit Ji har Puja ke expert hote hain?” — “Nahi. Isliye hai JiPanditJi.” Then demonstrate: Griha Pravesh → Griha Pravesh Specialist, Rudrabhishek → Rudra Specialist, Vivah → Vivah Acharya.
“Har Puja ke liye wahi Pandit Ji, jo us Puja mein visheshagya hain.” Primary line across all paid channels.
“JiPanditJi — Aapke Ghar Ke Pandit Ji.” Brand-level emotional anchor; used in retention and post-service communication.
Each hero ritual gets its own specialist-framed line (see Section 04 scorecard) rather than one generic message across all rituals.
Copy Examples by Surface
| Surface | Copy |
|---|---|
| Google Search Ad | Griha Pravesh Pandit, Certified Specialist | JiPanditJi — Har Puja ke liye visheshagya Pandit Ji. Muhurat ke anusaar booking. Verified & Satvik. |
| Meta Reel Hook | “Kya aapka Pandit Rudrabhishek aur Griha Pravesh dono mein expert hai?” (3-sec pattern interrupt, then reveal specialist system) |
| WhatsApp (booking confirm) | Aapki Griha Pravesh Puja confirm ho gayi hai — Acharya [Name], Griha Pravesh Specialist, [X] verified ceremonies. Muhurat: [date/time]. |
| Society Poster | Naye ghar ki shubh shuruaat. Griha Pravesh Visheshagya Pandit Ji, aapki society mein, aapke muhurat par. [QR] |
| Elevator Poster | Har Puja ke liye wahi Pandit Ji, jo us Puja mein visheshagya hain. JiPanditJi — Aapke Ghar Ke Pandit Ji. |
| Standee (Society Desk) | Aaj hi milen: apni agli Puja ke liye sahi Visheshagya Pandit Ji chunein. |
| Website Hero | Aapke Ghar Ke Pandit Ji. Har Puja ke liye, wahi Pandit Ji jo us Puja mein visheshagya hain. |
| Ritual Landing Page (Griha Pravesh) | Griha Pravesh ek baar hota hai — sahi Visheshagya Pandit Ji ke saath karein. Verified specialists, muhurat-matched. |
| Booking Confirmation | Dhanyawaad. Aapke liye [Ritual] Specialist Acharya [Name] allocate kiye gaye hain — [X] verified ceremonies, rating [X.X]/5. |
| Pandit Specialist Card | See Trust Architecture (Section 06) for the full card layout. |
Trust Architecture
The specialist promise only works if the family can see the proof. One consistent “JiPanditJi Verified Ritual Specialist” system, shown everywhere. VALIDATE no Pandit counts or ratings are fabricated below — all numeric fields are placeholders pending real data.
Specialist Card (reference layout)
Verified Griha Pravesh ceremonies: [LIVE DATA]
Ritual-specific rating: [LIVE DATA]/5
JiPanditJi Satvik Service Standard: ✓ Compliant
[LIVE DATA PLACEHOLDER] fields populate from the Competency Passport once bookings accumulate — never estimated or invented.
Where this trust system appears
| Website | Specialist card on every ritual landing page and search result |
| Pandit profile | Full competency passport view (customer-visible fields only) |
| Booking confirmation | Allocated specialist card + certification badge |
| Compact card in confirmation + “Pandit en route” message | |
| Pandit ID/badge | Physical ID shown on arrival, matches app profile photo |
| Physical collateral | QR on society posters/standees links to specialist directory for that zone |
| Post-service | “Rate your [Ritual] specialist” — ritual-specific, not generic star rating |
Google Search Capture Engine
High-intent engine. Campaign → Ritual → Zone → Intent, never one PMax catch-all. Budget migrates toward the Ritual × Zone combinations that actually produce qualified bookings.
Campaign Architecture
| Layer | Structure | Example |
|---|---|---|
| Campaign | One per Hero Ritual (Search, manual bidding early) | Griha Pravesh — Search — Tier A |
| Ad Group | One per Zone cluster within the campaign | Griha Pravesh — Indirapuram |
| Keyword Theme | Intent tiers: exact ritual, “near me”, comparison, generic | “griha pravesh pandit indirapuram” / “pandit for griha pravesh near me” |
| Landing Page | Maps 1:1 to ritual, not to a generic homepage | /griha-pravesh (zone-aware content block) |
Sample Keyword Themes
- Griha Pravesh Pandit / Pandit for Griha Pravesh near me
- Rudrabhishek Pandit / Rudrabhishek Puja at home
- Pandit for Puja at home [zone]
- Vivah Pandit / Shaadi Pandit booking NCR
- Satyanarayan Katha Pandit near me
- Graha Shanti Pandit / Navagraha Puja at home
Negative Keyword Logic
- Free / job / salary / course / training (non-buyer intent)
- Astrologer-only / kundli matching (different intent than ritual booking) — route to Graha Shanti ad group only if ritual-specific
- Competitor brand terms excluded from Hero Ritual campaigns; handled in a separate, capped conquesting campaign
- Out-of-zone city names outside current P0/Tier A geo-targeting
Radius/polygon targeting per Tier A zone cluster (see Section 03 map), not a blanket “Delhi NCR” radius — avoids paying for East/West Delhi clicks we can't yet fulfil.
Call tracking number per zone, WhatsApp click-to-chat event, and form-fill — all three feed one “Qualified Enquiry” conversion action so Search can optimise toward it.
Landing-page visitors (no enquiry), enquiry-no-booking, booked-no-repeat-yet — each gets a distinct Meta/Search retargeting message, not one generic remarketing list.
Weekly: rank every live Ritual × Zone ad group by Qualified-Enquiry-to-Booking rate and CAC. Combinations beating target CAC (see Section 20 Kill/Scale Rules) get incremental budget first; combinations missing CAC for 2 consecutive weeks get paused, not silently left running. New Ritual × Zone combinations only launch inside Tier A until the Day-45 gate opens Tier B. This is the mechanism referenced in Section 18's Zone × Ritual Matrix.
Meta Demand Creation Engine
Meta does not duplicate Google Search. Its job is education, trust and retargeting — building the specialist-matching insight in people's minds before they ever search.
Creative Pillars
“Kya har Pandit Ji har Puja ke expert hote hain?” pattern-interrupt hook
Griha Pravesh Specialist vs Rudra Specialist — visual side-by-side
Respectful profile of an Acharya's training/certification journey
Real family experience (consented) — what specialist matching felt like
Glimpse of the practical assessment / Satvik SOP training
Dress, punctuality, samagri checklist — what “managed” actually means
Why Griha Pravesh timing/sequence matters — respectful, not fear-based
Why JiPanditJi exists — institutional trust framing
Only for genuine upcoming muhurat windows — never manufactured urgency
Sample Creative Concepts
| Format | Concept |
|---|---|
| Reel Hook (3s) | “Aapka Pandit Griha Pravesh AUR Rudrabhishek dono mein expert hai?” → cut to specialist card reveal |
| Reel Hook (3s) | “Ek Pandit, saari Pujaein?” (text on screen) → “Nahi. Har Puja ka apna visheshagya hota hai.” |
| Carousel | Card 1: “Griha Pravesh” → specialist photo+badge. Card 2: “Rudrabhishek” → different specialist. Card 3: CTA “Aapki Puja, sahi Visheshagya” |
| Static | Split-frame: generic “any Pandit” (greyed out) vs JiPanditJi verified specialist card (in colour) |
| 15s Video Script | 0-3s: hook question. 4-9s: show 3 different specialists for 3 different rituals. 10-13s: “JiPanditJi — Aapke Ghar Ke Pandit Ji.” 14-15s: CTA card. |
| Retargeting Static | “Aapne Griha Pravesh dekha tha — apna muhurat abhi confirm karein” + specialist availability nudge (genuine, not countdown-timer pressure) |
Hyperlocal Society (RWA) Domination
The highest-leverage channel in Tier A. Density means a small number of well-run society activations can dominate a zone faster than any paid channel alone.
Target Society Archetypes
| Archetype | Primary Tactic |
|---|---|
| Premium high-rise | Concierge desk tie-up, festival activation, higher-AOV specialist rituals (Rudrabhishek, Vastu) |
| Large middle/upper-mid society | RWA festival calendar tie-up, weekend consultation desk, standee at gate |
| New-possession society | Griha Pravesh desk at possession office, builder/facility-management partnership |
| Senior-citizen-heavy community | Recurring/family Puja focus, phone + WhatsApp booking (lower digital-first assumption) |
| Young-family community | Naamkaran/Mundan lifecycle messaging, referral-led, Meta-heavy over Search |
The One-Society Launch Kit (repeatable)
| # | Item | Detail |
|---|---|---|
| 01 | RWA tie-up letter | One-page respectful introduction + Satvik standard summary; no discount language |
| 02 | Society Puja desk kit | Table signage, specialist card printouts, QR to zone landing page, sign-up sheet |
| 03 | Elevator/lift poster | Core promise line + QR, sized to standard lift panel |
| 04 | Notice-board poster | Slightly longer format — education hook + specialist examples |
| 05 | Society-specific landing page/QR | Pre-filled zone field so bookings tag back to that society for attribution |
| 06 | Resident WhatsApp group message | One respectful intro message + desk date, not repeated spam |
| 07 | Weekend consultation slot | 2-hour desk booking, staffed by Zone Lead or trained rep, log every conversation |
| 08 | Referral card | Handed to every completed-Puja family on-site, see Section 11 |
Target: 2 new societies launched per Tier A zone per fortnight in Weeks 1–6 (ASSUMPTION — adjust once first activations show real desk-to-booking conversion).
WhatsApp Family Relationship Engine
Lifecycle communication, not spam. Every message has a stated purpose and timing — no message goes out just because a template exists.
| Trigger | Condition | Timing | Message Purpose |
|---|---|---|---|
| New enquiry | Enquiry submitted (any channel) | Immediate | Confirm receipt + set expectation for specialist match |
| Abandoned enquiry | No booking within 24h | T+24h | Gentle follow-up, offer to answer questions — not a discount push |
| Booking confirmation | Booking confirmed | Immediate | Specialist card + date/time + what to prepare |
| Pre-Puja preparation | 48h before ritual | T-48h | Samagri checklist, address confirmation, any prep guidance |
| Pandit assignment | Specialist finalised | T-24h | Introduce allocated Acharya by name and specialisation |
| Pandit en route | Travel started | Day-of | ETA + specialist card, builds trust before arrival |
| Completion | Ritual completed | Immediate after | Thank-you + what happens next (feedback link) |
| Feedback | Post-service | T+2h | Ritual-specific rating request, not generic star rating |
| Thank-you / relationship | After positive feedback | T+1 day | Warm relationship message, Family ID context stored |
| Referral prompt | After positive feedback only | T+3 days | Natural referral ask (see Section 11), never before service quality confirmed |
| Relevant future ritual reminder | Lifecycle signal / opt-in festival calendar | Context-dependent | Only genuinely relevant reminders — no manufactured anxiety |
| Festival communication | Opt-in festival calendar | Seasonal | Respectful, optional, easy to mute |
Representative flows only, per the brief — not a full 30-message library. Consent controls (reminder preferences) per the Family Profile schema SOURCE govern every non-transactional message.
Referral Engine
“If someone in my family/society needs a Pandit, I know whom to call.” Culturally appropriate — never a discount-coupon scheme for a spiritual service.
Asked only after a genuinely positive completed ritual; simple “who else in your family might need this” prompt.
Referral card left with every completed family at society activations; tagged to the society for attribution.
Highest-trust moment in the lifecycle — natural point to ask for an introduction to a neighbour also moving in.
Specialists who consistently deliver strong ritual-specific ratings can be the trusted face of a referral ask, with Ops oversight.
CRM-prompted: when a Family ID's contact mentions a friend/relative's need during support conversation.
Where appropriate — framed as a gesture of thanks, never as a coupon-code growth hack.
Referral KPIs
Family Acquisition Loop
A first ritual becomes a long-term relationship — only where the need is genuine. We do not imply every family needs every ritual.
This loop is descriptive of possible genuine paths, not a forced sales sequence. The Next Family Requirement (NFR) logic in the strategy master governs when — if ever — the next step is actually relevant to a specific family.
Budget Architecture
Three scenarios, editable assumptions. Every figure below is a PLANNING ASSUMPTION — there is no JiPanditJi historical CAC/conversion data yet, so treat these as starting hypotheses to replace with real numbers after Week 2–4.
| Channel | Split | Monthly | 90-Day |
|---|
Editable Assumptions
| Monthly budget override (₹) | |
| Lead → booking conversion (%) | |
| Average order value (₹) | |
| Contribution margin (%) |
Blended cost-per-qualified-enquiry is fixed at ₹220 for this illustration ASSUMPTION — replace with real blended CPL once Google/Meta campaigns have run for 2+ weeks.
Target CAC range referenced from SOURCE 01_Assumptions Family acquisition CAC: Base ₹900, Conservative ₹1,300, Upside ₹650.
13-Week Execution Plan
Concrete week-by-week actions across nine workstreams. Day-45 gate sits inside Week 6/7; formal 90-day review closes Week 13.
Expand any week for full detail
| Growth | Lock Tier A zones (GZ-01,GZ-04,NO-03,GN-01); finalise hero ritual list |
| Content | Write 7 ritual landing pages; record 3 specialist-explainer reels |
| Perf. Marketing | Build Google Search campaigns for Griha Pravesh + Satyanarayan in Tier A; set up conversion tracking |
| Society Activation | Map 15 target societies across Tier A; send first 5 RWA intro letters |
| Pandit Supply | Audit current empanelled Pandits against Competency Passport; identify Griha Pravesh/Rudra gaps |
| Product/Tech | Ship specialist-card component on website + booking confirmation |
| CRM/WhatsApp | Set up WhatsApp Business templates: confirmation, pre-Puja, en route |
| Analytics | Instrument qualified-enquiry conversion action (call+WhatsApp+form) |
| Founder/CEO Review | Approve Tier A zone list, hero ritual list, budget scenario |
| Growth | Launch Meta education-hook creative in Tier A geo |
| Content | Publish first 4 ritual landing pages live; 3 more reels |
| Perf. Marketing | Launch Search campaigns; Meta awareness set live; retargeting audiences created |
| Society Activation | Run first 2 society desk activations (GZ-01, GN-01) |
| Pandit Supply | Begin certifying 3 Griha Pravesh trainee-stage Pandits (supervised ceremonies) |
| Product/Tech | Zone-aware landing page routing; call-tracking numbers per zone |
| CRM/WhatsApp | Activate booking-confirmation + pre-Puja WhatsApp flow |
| Analytics | First CAC/CPL read (directional only, low volume) |
| Founder/CEO Review | Review Week 1-2 spend vs first qualified enquiries |
| Growth | First paid-to-booking cohort closes; identify best-performing zone/ritual pair |
| Content | Publish 2 customer-story assets (consented) from earliest bookings |
| Perf. Marketing | Reallocate Search budget toward best CAC ad groups; pause weak keywords |
| Society Activation | 2 more society activations (GZ-04, NO-03); referral cards seeded |
| Pandit Supply | Close first Griha Pravesh/Rudra certification cohort; update accessible bench |
| Product/Tech | Ship ritual-specific rating capture (not generic stars) |
| CRM/WhatsApp | Activate feedback + thank-you flow |
| Analytics | Zone × Ritual matrix goes live with first real data points |
| Founder/CEO Review | First specialist-match-rate and on-time-arrival read |
| Growth | Launch referral prompts for completed families |
| Content | Add Rudrabhishek + Mahamrityunjaya landing pages |
| Perf. Marketing | Test specialist-vs-generic messaging (Experiment 1) |
| Society Activation | 2 more activations; first society-specific landing pages live |
| Pandit Supply | MPC check ahead of next major muhurat window; pre-lock Griha Pravesh backup |
| Product/Tech | WhatsApp deep-link from ad creative to zone landing page |
| CRM/WhatsApp | Referral-prompt template live (post-positive-feedback only) |
| Analytics | Weekly Founder Review panel format finalised |
| Founder/CEO Review | Review Experiment 1 result; decide scale/kill |
| Growth | Push into remaining Tier A demand (GZ-01/04 secondary societies) |
| Content | Publish Naamkaran + Graha Shanti landing pages |
| Perf. Marketing | Test call vs WhatsApp CTA (Experiment 2) |
| Society Activation | Weekend consultation desks begin in 2 top societies |
| Pandit Supply | Recruit against Week 3-4 MPC gaps; sourcing channel yield review |
| Product/Tech | Add family-ID linkage on repeat booking flow |
| CRM/WhatsApp | Festival/lifecycle opt-in reminder capture added to CRM |
| Analytics | First 90-day-cohort tracking scaffolding (too early for results) |
| Founder/CEO Review | Review CAC trend by zone; flag any zone above target |
| Growth | Consolidate Tier A learnings into a one-page playbook |
| Content | Refresh underperforming landing pages based on 5 weeks of data |
| Perf. Marketing | Test ritual-specific landing page vs generic page (Experiment 3) |
| Society Activation | 4th activation wave; referral-rate check-in per society |
| Pandit Supply | Certify second cohort (Sanskar + Graha specialists) |
| Product/Tech | Ship Pandit Competency Passport view (customer-visible fields) |
| CRM/WhatsApp | Review WhatsApp opt-out/complaint rate; adjust cadence if needed |
| Analytics | Compile Day-45 gate readiness report |
| Founder/CEO Review | DAY-45 GATE REVIEW: Specialist Match, On-time, repeat cohort |
| Growth | Gate decision: open Tier B zones (NO-04, ED-01, ED-02, GZ-03, NO-02, NO-01, GZ-02) or extend Tier A |
| Content | If gate passed: draft Tier B zone-specific landing content |
| Perf. Marketing | Scale budget toward proven Ritual × Zone combinations per Kill/Scale rules |
| Society Activation | Begin Tier B RWA outreach if gate passed; else deepen Tier A |
| Pandit Supply | Recruitment requisitions raised for Tier B competency gaps |
| Product/Tech | Zone expansion config in booking/allocation system |
| CRM/WhatsApp | Segment CRM by Tier A cohort vs new Tier B cohort |
| Analytics | Publish Day-45 gate outcome to whole team |
| Founder/CEO Review | Approve Tier B go/no-go and revised budget scenario |
| Growth | Tier B soft-launch (if approved) with same playbook, lighter spend first 2 weeks |
| Content | Tier B landing pages live |
| Perf. Marketing | Search + Meta live in Tier B at 50% of Tier A per-zone spend initially |
| Society Activation | First Tier B society activations |
| Pandit Supply | Onboard Tier B recruits; supervised ceremonies begin |
| Product/Tech | Monitor system load/allocation latency as zone count grows |
| CRM/WhatsApp | Ensure WhatsApp flows scale cleanly to new zones |
| Analytics | Track Tier A vs Tier B CAC side by side |
| Founder/CEO Review | Review Tier B early signal vs Tier A Week-1 baseline |
| Growth | Run Experiment 4-6 (see backlog) across combined Tier A+B |
| Content | Add Vivah-related content ahead of seasonal window if relevant |
| Perf. Marketing | First full budget reallocation across all live zones by CAC ranking |
| Society Activation | Referral-engine push: target 15% of completed families referring |
| Pandit Supply | Vivah specialist bench review ahead of season |
| Product/Tech | Ship referral tracking/attribution in CRM |
| CRM/WhatsApp | 365-day repeat tracking scaffold (too early for real numbers, structure only) |
| Analytics | Zone × Ritual matrix fully populated for Tier A+B |
| Founder/CEO Review | Mid-point (Day ≈63) review of North Star trend |
| Growth | Identify first zones eligible for early Tier C (P1) scouting |
| Content | Publish first FRLV-informed content: ‘life of a family with JiPanditJi’ story |
| Perf. Marketing | Run Experiment 7-9 |
| Society Activation | Second-wave activations in highest-referral Tier A societies |
| Pandit Supply | Re-certification review for earliest-certified Week-1 Pandits |
| Product/Tech | Dashboard: expose live specialist-match and MPC-gap views to Ops |
| CRM/WhatsApp | Audit opt-in reminder performance; trim low-engagement sends |
| Analytics | First real (if early) 90-day repeat cohort read for Week-1-2 bookings |
| Founder/CEO Review | Review referral engine traction and CAC:FRLV early signal |
| Growth | Freeze new-zone expansion; focus on deepening existing zones |
| Content | Consolidate top-performing creative into always-on set |
| Perf. Marketing | Run Experiment 10-12; cut anything below minimum decision threshold |
| Society Activation | Push toward density target in weakest-performing Tier A/B zone |
| Pandit Supply | Full MPC recompute ahead of upcoming festival/muhurat season |
| Product/Tech | Harden booking/allocation system for festival-season load |
| CRM/WhatsApp | Prepare festival-season WhatsApp calendar (opt-in only) |
| Analytics | Draft 90-day results summary structure |
| Founder/CEO Review | Review supply readiness for festival season |
| Growth | Run Experiment 13-15; finalise which messages/channels graduate to always-on |
| Content | Publish 90-day learnings recap (internal) |
| Perf. Marketing | Lock Month-4 budget scenario recommendation (Lean/Base/Aggressive) from evidence |
| Society Activation | Document society-playbook v2 with real conversion data |
| Pandit Supply | Confirm certified bench sufficient for Month-4 planned zones |
| Product/Tech | Ship any P1-readiness features identified as blockers |
| CRM/WhatsApp | Finalise 90-day family-relationship report per Family ID |
| Analytics | Compile full 13-week KPI trend pack |
| Founder/CEO Review | Pre-review of 90-day results ahead of Week 13 formal review |
| Growth | Present 90-day outcome vs North Star + all supporting metrics |
| Content | Archive/refresh content plan for Month 4+ |
| Perf. Marketing | Finalise Month-4 channel budget split by evidence, not assumption |
| Society Activation | Lock Month-4 society activation target list |
| Pandit Supply | Lock Month-4 recruitment plan by MPC gap |
| Product/Tech | Roadmap Month-4 product priorities from 90-day learnings |
| CRM/WhatsApp | Publish FRLV cohort read (Tier A Week-1–6 families) |
| Analytics | Final 90-day dashboard snapshot archived |
| Founder/CEO Review | FORMAL 90-DAY REVIEW: expand P0→P1 decision per Section 20 rules |
First 30 Days — What Happens Tomorrow
The first 30 days answer one question only: can we prove the specialist-matching promise works, end-to-end, in four zones — before spending a rupee wider?
Pages that must be ready before Day 1 spend
- Griha Pravesh landing page (Tier A zone variants)
- Satyanarayan Katha landing page
- Rudrabhishek landing page
- Website hero + specialist-card component
- Booking confirmation page with allocated-specialist card
Campaigns live by end of Week 1
- Google Search: Griha Pravesh — Tier A (4 ad groups, one per zone)
- Google Search: Satyanarayan Katha — Tier A
- Meta: Education-hook awareness set, Tier A geo
- Meta: Warm retargeting list creation (no spend yet, list-building)
Creatives ready Week 1
- 3 reels: education hook, specialist explainer, Satvik service glimpse
- 1 carousel: 3-ritual specialist showcase
- 2 statics: split-frame generic-vs-specialist, specialist card hero
Societies targeted Week 1–2
- GZ-01 Indirapuram: 2 large societies (Ahinsa/Niti Khand)
- GZ-04 Siddharth Vihar-Crossings: 2 new-possession societies
- NO-03 Noida North: 2 established societies
- GN-01 Greater Noida West: 2 large new-possession societies
Pandit specialist profiles required Week 1
- Minimum 2 certified Griha Pravesh specialists per Tier A zone
- Minimum 1 certified Rudra specialist covering Tier A cluster (shared across zones initially)
- Minimum 2 Family/Regular Puja generalists per zone as immediate bench
Tracking that must work before spend
- Call-tracking numbers per zone
- WhatsApp click-to-chat conversion event
- Form-fill conversion event, unified into one “Qualified Enquiry” action
- Zone tag on every booking record
What the Founder must see by Day 7
by zone, by ritual
by channel
with specialist match confirmed
count + quality note
GTM Experiment Backlog
15 experiments, each with a hypothesis, both variants, one primary metric, a minimum decision rule fixed in advance, and the action to take after the result — no post-hoc rationalisation.
| # | Experiment | Hypothesis | Variant A / B | Primary Metric | Minimum Decision Rule | Action After Result |
|---|---|---|---|---|---|---|
| 01 | Specialist vs generic messaging | “Visheshagya Pandit” framing outperforms generic “book a Pandit” framing | A: Specialist-framed ad copy B: Generic “book a pandit” copy |
Qualified-enquiry rate | ≥ 20% relative lift, min 200 impressions/arm | Scale winner as default; retire loser |
| 02 | Pandit photo vs ritual visual | A named specialist's photo builds more trust than a generic ritual scene | A: Specialist photo + name B: Ritual ceremony photo |
CTR + enquiry rate | ≥ 15% relative lift | Adopt winner across Tier A creative |
| 03 | Call vs WhatsApp CTA | WhatsApp CTA converts higher for this demographic than phone call | A: “WhatsApp now” CTA B: “Call now” CTA |
Qualified-enquiry rate | ≥ 10% relative lift, min 150 clicks/arm | Set winning CTA as primary, keep other as secondary |
| 04 | Society QR vs direct WhatsApp number | A QR to a landing page converts better than a printed WhatsApp number | A: QR code to zone landing page B: Printed WhatsApp number |
Desk-to-enquiry rate | ≥ 15% relative lift, min 3 society activations/arm | Standardise winner in Launch Kit |
| 05 | Ritual-specific landing page vs generic page | A dedicated Griha Pravesh page outconverts a generic “book a puja” page | A: /griha-pravesh page B: Generic /book page |
Enquiry conversion rate | ≥ 20% relative lift, min 500 sessions/arm | Build dedicated pages for all Hero Rituals |
| 06 | Price visible vs enquiry-first | Showing indicative price upfront changes enquiry quality/volume | A: AOV range shown on landing page B: No price, “enquire for details” |
Enquiry volume AND booking conversion (both) | Directional read, min 300 sessions/arm, 2-week min | Adopt whichever wins on booking conversion, not just volume |
| 07 | Certification proof placement | Certification badge above the fold lifts trust more than below the fold | A: Badge in hero section B: Badge lower on page |
Scroll-to-enquiry rate | ≥ 10% relative lift | Standardise placement sitewide |
| 08 | Customer testimonial placement | Testimonial near CTA lifts conversion more than testimonial in a separate section | A: Testimonial adjacent to CTA B: Testimonial in dedicated section |
Enquiry conversion rate | ≥ 10% relative lift | Adopt winning layout |
| 09 | Education hook vs direct offer (Meta) | “Kya har Pandit expert hai?” hook outperforms a direct “book now” ad | A: Education-hook creative B: Direct-offer creative |
CPL (cost per qualified enquiry) | ≥ 15% lower CPL | Shift Meta budget toward winning creative pillar |
| 10 | Reel vs static (Meta) | Video reels outperform static images for this audience/message | A: 15s reel B: Static image, same message |
CPL + watch-through/enquiry | ≥ 15% lower CPL | Rebalance creative mix toward winner |
| 11 | RWA formal tie-up vs informal desk | A signed RWA tie-up produces materially more bookings than an informal desk-only activation | A: Formal RWA letter + tie-up B: Desk-only, no formal tie-up |
Bookings per society, 30-day window | ≥ 25% relative lift | Prioritise formal tie-ups if winner, else save Ops time by skipping paperwork |
| 12 | Referral timing: immediate vs delayed | Asking for referral 3 days after positive feedback outperforms asking immediately | A: T+3 day referral ask B: Immediate post-feedback ask |
Referral rate | ≥ 15% relative lift | Lock winning timing in CRM flow |
| 13 | Senior vs standard specialist framing (premium rituals) | Explicit ‘Senior Acharya’ framing lifts conversion for Mahamrityunjaya/Vivah | A: “Senior Specialist Acharya” label B: Standard “Specialist” label |
Enquiry-to-booking rate on premium rituals | ≥ 10% relative lift, min 60 enquiries/arm | Apply to all premium-tier rituals if winner |
| 14 | Muhurat urgency vs evergreen messaging | Genuine upcoming-muhurat urgency lifts conversion without feeling manufactured (tracked via complaint/opt-out rate too) | A: Muhurat-window creative B: Evergreen specialist creative |
Enquiry rate AND opt-out/complaint rate (both tracked) | ≥ 15% lift with no increase in opt-out rate | Use only if trust metric holds; discard if opt-outs rise |
| 15 | Zone-exclusive vs cross-zone specialist messaging | “Specialist based in your zone” messaging outperforms generic “specialist available” | A: “Aapke Indirapuram mein…” local framing B: Generic availability framing |
Qualified-enquiry rate | ≥ 10% relative lift | Localise messaging per zone if winner |
War Room Dashboard
All cells are LIVE DATA PLACEHOLDER — wire to the CRM/Ads APIs when ready. Traffic-light status is illustrative logic (green/amber/red thresholds), not real data.
Zone × Ritual Matrix
SCALE / HOLD / FIX / STOP at a glance across Tier A + top Tier B zones and the six highest-priority hero rituals. LIVE DATA PLACEHOLDER — status logic shown here is illustrative until real demand/CAC/conversion/specialist-availability data feeds it (see Section 20 for the actual decision rules that should drive these statuses).
| Zone | Griha Pravesh | Rudrabhishek | Satyanarayan Katha | Mahamrityunjaya | Graha Shanti | Naamkaran |
|---|---|---|---|---|---|---|
| GZ-01 | ||||||
| GZ-04 | ||||||
| NO-03 | ||||||
| GN-01 | ||||||
| NO-04 | ||||||
| ED-01 | ||||||
| ED-02 |
Weekly Founder Review — Monday Panel
Ten questions, maximum. Answering all ten should take under 20 minutes once the dashboard is wired to real data.
[Founder / CMO notes — fill in during Monday review]
[Founder / CMO notes — fill in during Monday review]
[Founder / CMO notes — fill in during Monday review]
[Founder / CMO notes — fill in during Monday review]
[Founder / CMO notes — fill in during Monday review]
[Founder / CMO notes — fill in during Monday review]
[Founder / CMO notes — fill in during Monday review]
[Founder / CMO notes — fill in during Monday review]
[Founder / CMO notes — fill in during Monday review]
[Founder / CMO notes — fill in during Monday review]
Kill / Scale Rules
Explicit thresholds so decisions are not made on gut feel mid-week. All thresholds are initial test thresholds — edit them once 4–6 weeks of real data exist, but do not remove the discipline of having a written rule.
| Decision | Rule | Note |
|---|---|---|
| Increase zone budget | 3 consecutive weeks at/below target CAC (≤₹900 base) AND specialist match ≥ 98% | Initial test threshold — editable once real CAC baseline exists |
| Reduce zone budget | 2 consecutive weeks above ₹1,300 CAC with no improving trend | Initial test threshold |
| Pause a keyword/ad group | ≥ 50 clicks with zero qualified enquiries | Standard paid-search hygiene rule |
| Stop a zone (Tier A/B) | 4 consecutive weeks below 50% of forecast bookings with no structural fix identified (e.g. specialist shortage unresolved) | Initial test threshold — requires Founder sign-off, not automatic |
| Add a society | Zone density below target AND ≥ 2 existing societies show ≥ 15% referral rate (proof the playbook works locally) | Initial test threshold |
| Recruit another specialist | MPC alert: booked-slots / core-bench ratio ≥ 80% for 2 consecutive weeks in a category | Directly from 19_MPC_P0_Calculator logic — SOURCE |
| Expand P0 → P1 (Tier B → Tier C) | Day-45 gate passed AND Week-13 formal review confirms North Star + specialist-match + CAC targets held at scale | Matches strategy master's phased-rollout gate logic — SOURCE |
| Do NOT expand | Any of: specialist match < 95%, on-time < 90%, CAC trending up 2+ weeks without a fix, or MPC gaps unresolved in current zones | Guardrail — protects the specialist-quality promise over growth |
Non-negotiable guardrails (never overridden for growth)
- Never allocate a Pandit to a ritual they are not certified for, regardless of demand pressure
- Never use fear-based or urgency-manufactured messaging for remedial/astrology-linked rituals
- Never present “Pandit count” as the core marketing claim
- Never expand geography faster than certified specialist bench supports it
Founder Validation Required
The source workbook's 20_Recruitment_Gaps sheet (and the dependent
21_MPC_Dashboard “Recruitment Gaps Identified” cell) contains formulas using a
non-standard function (_xludf.MAXIFS, a Google-Sheets-export artefact) that returns
#NAME? errors when opened in Excel. This dashboard does not invent a replacement number for
recruitment gaps — recompute that sheet natively (standard MAXIFS/SUMIFS) before
relying on it for Week-1 recruitment requisitions.