The visitor never sees a page change. They move through a venue — arrival, lobby, halls, pavilion, stage, and a follow-up that keeps working after they log out.
A multi-tenant virtual experience platform for FranchiseWorld and EBG Realty. Two independently branded venues. One core that a third company can join without a line of new code.
Thirty-four sections, and the hard requirement is in three of them: one codebase, two unrelated industries, and a third company that must join later without a rebuild. Everything else follows from getting that right.
Two tenants, one core
FranchiseWorld and EBG Realty must feel like different products and share one codebase. That is an architecture decision, not a design decision.
Nothing may be hardcoded
No table, API or screen may assume franchise or real estate. Terminology, fields, halls, offerings and CTAs are data — not code.
Every move is measurable
Entry to hall to pavilion to offering to document to meeting, with dwell time at each step. The analytics are the product, not a report.
“I entered an exhibition, moved through halls, visited a brand booth, spoke to a representative, picked up the brochure, attended a presentation and booked a meeting” — not “I browsed a franchise listing website.”
A visitor knows they have entered somewhere before reading a word.
At every moment they know where they are and what is one step away.
A human conversation is one click from the moment of interest.
App-layer tenant checks fail the day someone forgets a WHERE clause.
Row-level security makes cross-tenant reads impossible at the engine, not the endpoint —
which is what acceptance scenario E actually demands.
Domain resolves the tenant before a single byte of content loads
Segment schema — terminology, fields, taxonomy, module toggles
Pavilion · offering · scheduling · leads · analytics
Postgres with row-level security — isolation the database enforces
Onboarded by tenant creation, domain mapping, schema configuration and content loading. No clone. No new codebase.
One pavilion component. Sixteen optional modules, each controlled from the CMS at tenant or entity level. Turn one off and it disappears — no empty card, no dead button, no orphaned nav. Try it.
Logo · statement · category · verified status
What is this opportunity — start/completion tracked
Leadership message — label configurable per tenant
Images · walkthroughs · case studies
Zero, one or many options — hides entirely at zero
Dynamic attributes bound to the selected offering
Territories or inventory — segment-appropriate model
Common or offering-specific · versioned · tracked
Outlets, project sites or experience centres
Online / busy / offline — gates instant contact
Prefilled with tenant + entity + selected offering
Queue-based 1:1 with transfer and transcript policy
Instant video — falls back to scheduling on timeout
Local-time slots · no double booking · .ics invite
Tenant-defined appointment type
Saved at offering level, persistent across devices
Every module is disabled. In production the pavilion would not publish — the CMS blocks it at the completeness check.
Same component. Same database. Same API. Flip the tenant and every label, field, unit, document and CTA is replaced from the segment schema — with no deployment and no branch in the code. This is acceptance scenario C and D, running.
- Investment
- 35–45 L
- Franchise Fee
- 6 L
- Outlet Area
- 850–1,200 SQ FT
- Royalty
- 5 %
- Payback
- 24–30 MONTHS
- Territory
- 14 states open
- Investment
- 22–28 L
- Franchise Fee
- 4 L
- Outlet Area
- 600–900 SQ FT
- Royalty
- 4 %
- Payback
- 18–24 MONTHS
- Territory
- 22 states open
- Investment
- 1.8–2.4 CR
- Franchise Fee
- 35 L
- Territory Size
- 1 state
- Royalty
- 7 %
- Payback
- 36–42 MONTHS
- Territory
- 6 states open
- Investment
- 12–18 L
- Security Deposit
- 3 L
- Warehouse Area
- 2,000+ SQ FT
- Margin
- 11–14 %
- Payback
- 12–18 MONTHS
- Territory
- 31 districts open
- Price
- 2.4–2.9 CR
- Booking Amount
- 5 L
- Built-up Area
- 3,150 SQ FT
- Plot Size
- 2,400 SQ FT
- Possession
- Q4 2027
- Inventory
- 18 of 64 available
- Price
- 78–96 L
- Booking Amount
- 2 L
- Plot Size
- 1,200–1,800 SQ FT
- Rate
- 5,400 /SQ FT
- Possession
- Immediate
- Inventory
- 41 of 120 available
- Price
- 1.35–1.62 CR
- Booking Amount
- 3 L
- Saleable Area
- 1,780 SQ FT
- Carpet Area
- 1,240 SQ FT
- Possession
- Q2 2027
- Inventory
- 96 of 240 available
- Price
- 92 L–1.4 CR
- Booking Amount
- 4 L
- Chargeable Area
- 640–980 SQ FT
- Expected Yield
- 6.5 %
- Possession
- Q1 2027
- Inventory
- 12 of 48 available
/ Nothing above is a separate page, template or code path. It is one renderer reading one schema.
Video and webinar infrastructure is a solved, metered commodity. Building it would add months to launch and put concurrency risk on the critical path. We buy it, wire it in, and you pay for it on event days — not every day.
- No WebRTC media-server engineering on the critical path to launch
- Video and streaming bill per minute — you pay on event days, not every day
- Vendor SLAs carry concurrency risk that a first release should not carry
- Every vendor above has a named alternate; none of them holds your data
A first-party event trail, not a pixel. Every movement, media play, document open and contact is captured with tenant, entity and selected offering attached — which is the only reason the sales queue can be trusted.
- SESSION
- login · expo entry · exit · device · source/campaign
- MOVEMENT
- lobby entered · hall entered/exited · booth entered/exited
- ATTENTION
- dwell time · offering selected · tab viewed · territory checked
- MEDIA
- video start · 25/50/75/100% · gallery opened · document viewed
- INTENT
- shortlisted · compared · WhatsApp · chat · Meet Now · scheduled
- STAGE
- session joined/left · watch duration · poll · related booth click
- CONVERSION
- lead created · qualified · meeting completed · closure
- Entered pavilion / viewed offering
- Watched explainer or founder video
- Downloaded brochure or deck
- Shortlisted or compared
- WhatsApp or live chat opened
- Requested Meet Now
- Scheduled meeting or site visit
A prioritisation aid, not a judgement about a person. Admin can always open the actions that produced a score.
You asked for no mandatory stack, and for what happens if a vendor is swapped. So every row carries an alternate. Nothing here holds your data hostage, and the four metered services are marked.
Phases 01–03 put both tenants live. Phase 04 is growth capital — a third company, AI, multilingual and the Signature 3D tier — and it is deliberately separable so Phase 1 stays cost-conscious, exactly as §32 asks.
Foundation
A signed-off experience and an architecture that cannot be argued with later.
- Discovery workshops · assumptions · risk register
- Information architecture and visitor journeys, both tenants
- International design system — grid, type, motion, components
- Two distinct tenant visual identities on one system
- 2.5D venue concept + one Signature 3D concept frame
- Clickable high-fidelity prototype: lobby → hall → pavilion → booking
- Technical architecture, multi-tenant data model, analytics event taxonomy
- Vendor selection with cost, limits and exit path per service
Core Platform
Both tenants live end-to-end, operated entirely from the CMS.
- Multi-tenant core with Postgres row-level security isolation
- Domain → tenant resolution with automated SSL provisioning
- Segment schema engine — terminology, fields, taxonomy, no deploys
- Pavilion engine (2.5D) with per-entity module toggles
- Offering engine + dynamic attributes: zero, one or many per entity
- Media and document layer — CDN, versioning, access policy, tracking
- Discovery: search, filters, guided match, compare, shortlist
- My Experience visitor workspace
- CMS / Experience Manager + exhibitor and representative portals
- Leads, intent model and sales pipeline views
- WhatsApp Business API + scheduling with slot locking and .ics
- Live chat and presence · first-party event pipeline · tenant analytics
Live Expo
The venue runs a real event day at target concurrency.
- Meet Now 1:1 video — integrated, not engineered
- Main Stage webinar, HLS delivery and chaptered recordings library
- Moderated Q&A, polls, reactions, related-pavilion conversion
- Queue management with wait estimates and callback fallback
- Real-time operations dashboard — live now, sales queue, stage
- Event management: campaigns, event-scoped overrides and reporting
- Notification automation across in-app, email and WhatsApp
- Load and concurrency hardening with documented test results
- Security testing, accessibility pass, UAT and dual-tenant launch
Scale & Intelligence
A third company onboards by configuration. The platform starts selling itself.
- Third-tenant onboarding proof — no clone, no new codebase
- AI Expo Concierge grounded strictly in approved tenant data
- AI Booth Assistant with human handoff when representative offline
- Multilingual experience for priority markets
- Smart itinerary and networking matchmaking
- Sponsor monetisation: placements, premium tiers, promoted sessions
- CRM and marketing automation integrations
- Signature real-time 3D pavilion tier — the premium upsell
- PWA with push notifications
One-time build below. Infrastructure and metered third-party services are recurring and scale with your concurrency — the bands are in the appendix, along with support.
Phase 01 starts with a two-day discovery workshop and ends with a prototype your stakeholders can walk through. Everything after that is execution.
Everything §20.1 and §29 ask for, kept out of the main scroll on purpose.
A — RECURRING COST BANDS
- AWS ap-south-1 compute · Postgres · Redis · R2 + CDN · VOD storage · WhatsApp Business API · email/SMS · monitoring
- Metered 1:1 video minutes · live stream egress · autoscale headroom — charged on event days only
Third-party services are billed at cost, in your own vendor accounts. We do not mark them up and we do not hold the contracts.
B — SUPPORT & AMC
- Uptime monitoring, alerting and incident response
- Security patching and dependency upgrades
- 20 engineering hours / month for minor enhancements
- Quarterly backup-restore and DR drill
- Tenant onboarding support and CMS training refreshers
C — WHAT WE NEED FROM YOU
Per tenant. Phase 01 cannot close without these.
- 01 Brand system: logo, palette, typography licence, tone of voice
- 02 Approved domain/subdomain and DNS access for mapping
- 03 Entity list: brands or projects, with hall/zone assignment
- 04 Offering data: plan or property types, values, sizes, availability
- 05 Documents: brochures, decks, floor plans, payment plans, disclosures
- 06 Video: explainer, founder/developer, walkthrough — final cuts
- 07 Representative roster with roles, routing rules and availability windows
- 08 WhatsApp Business number and Meta account access
- 09 Legal: privacy policy, terms, consent copy, regulated disclosures
- 10 Named decision-maker per tenant with sign-off authority
D — EXCLUSIONS & ASSUMPTIONS
- Content production — copywriting, photography, video shooting and editing
- Brand identity design; we apply the tenant brand, we do not create it
- Third-party licence and usage fees (video, webinar, WhatsApp, cloud) — billed at cost
- Native iOS/Android applications; the platform is a responsive web app (PWA in Phase 04)
- Data entry and bulk content loading beyond two seeded reference entities per tenant
- CRM licences and any customisation inside the client’s existing CRM
- Legal, RERA and regulatory compliance review — client counsel’s scope
- Paid media, campaign management and SEO content programmes
- Two tenants in Phase 1. A third tenant is Phase 04 or a separate order.
- Client provides consolidated feedback within 3 working days per review cycle.
- Two review cycles per design deliverable; further rounds are change requests.
- Concurrency contracted at 1,000 simultaneous visitors for launch.
- Third-party vendor accounts are opened in the client’s name — client owns the data.
- Content freeze 10 working days before any flagship event date.