BookMyMandir™

02 / TEMPLE OPERATIONS

01 / 03

Current BookMyMandir workflows in one temple-owned operating spine

  1. 01

    SET UP THE INSTITUTION

    Create a workspace and request operator verification.

    Bring the temple profile, operator team, services and listings into one workspace. Verification is a separate manual review; a request does not create a verified temple.

    PROFILESource completePUBLISHProduction verified
See current availability MATURITY COMES FROM THE CANONICAL CATALOG.

ONE TEMPLE WORKSPACE · FIVE OPERATING VIEWS

One operatingpicture for the temple.

The board keeps oversight while operators move from devotees and seva capacity to records, festivals and distribution. Every stop keeps software maturity visible before the team acts.

Temple-owned tenant Consent by purpose Maturity shown
  • 01People & relationships2 PRODUCTION VERIFIED · 1 CUSTOMER BETA
  • 02Seva & capacity2 PRODUCTION VERIFIED · 3 SOURCE COMPLETE
  • 03Offering records3 PRODUCTION VERIFIED
  • 04Festival operations1 PRODUCTION VERIFIED · 3 SOURCE COMPLETE
  • 05Presence & distribution1 PRODUCTION VERIFIED · 1 SOURCE COMPLETE · 1 FOUNDATION ONLY
0% OF OFFERINGS · OPERATOR-CONTROLLED ACCOUNTS
BOOKMYMANDIR / OPERATING PLATFORM01 / 05
01 / 05People & relationshipsConsent-led profiles, segments and contact history2 PRODUCTION VERIFIED · 1 CUSTOMER BETA

FOR TEMPLE BOARDS, TRUSTS AND OPERATING TEAMS

One owned workspacefor the whole temple.

Give trustees a clean control view and operators one daily queue. Keep every devotee record, team permission and external handoff attached to the institution. The public marketplace is a disclosed acquisition layer; the temple keeps the relationship, fulfilment decision and connected payment destination.

Board oversightOperator workflowTemple-owned relationships

From the operating signal into one temple-owned workspace.

THE OPERATING MODEL, MADE VISIBLE

Know what is ready.
Know what comes next.

Every tool carries an availability state. Temple teams can plan procurement and rollout without mistaking a roadmap for working software.

0%of temple-collected offerings
Prod verified
36
Source complete
46
Customer beta
1
Foundation only
1
Not built
16
IDENTITY · PEOPLE · OPERATIONS · GOVERNANCE · PRESENCE EVIDENCE BEFORE CLAIMS

AVAILABILITY BY TOOL

Choose workflows with the evidence attached.

Every tool shows what works now, what remains limited and what is still planned. Availability is explicit, and every public-facing capability remains controlled by the temple.

36 Production verified46 Source complete1 Customer beta1 Foundation only16 Not built
Open the 100-tool atlas

THE B2B OPERATING SURFACE

Thirteen suites for front office, back office, governance and public reach.

The catalog groups applications, platform services, provider connections and automations by their intended tenant boundary. Every operator outcome keeps its own availability and release gate.

See current availability
01

People records, consent, and acquisition

7 tools5 prod verified 2 source 0 beta 0 foundation 0 not built
02

Communications and campaigns

8 tools1 prod verified 3 source 1 beta 0 foundation 3 not built
03

Listings, bookings, darshan, and sevas

8 tools4 prod verified 4 source 0 beta 0 foundation 0 not built
04

Offerings, donations, hundi, and receipts

8 tools4 prod verified 3 source 0 beta 0 foundation 1 not built
05

Prasad commerce, inventory, and logistics

7 tools1 prod verified 6 source 0 beta 0 foundation 0 not built
06

Presence, content, ads, and connected accounts

8 tools1 prod verified 3 source 0 beta 1 foundation 3 not built
07

Temple operations and ERP

10 tools3 prod verified 7 source 0 beta 0 foundation 0 not built
08

Xalen Books, finance, tax, and payroll

8 tools3 prod verified 2 source 0 beta 0 foundation 3 not built
09

People, workforce, service desk, projects, and knowledge

7 tools4 prod verified 2 source 0 beta 0 foundation 1 not built
10

Tenant, governance, access, and platform

7 tools4 prod verified 3 source 0 beta 0 foundation 0 not built
11

DPDP, privacy, and legal operations

8 tools2 prod verified 6 source 0 beta 0 foundation 0 not built
12

Analytics, reporting, and forms

6 tools4 prod verified 2 source 0 beta 0 foundation 0 not built
13

Vedika intelligence, public tools, and learning

8 tools0 prod verified 3 source 0 beta 0 foundation 5 not built

The plan combines BookMyMandir-native workflows with provider-backed modules. Xalen Studio, Vedika and other provider capabilities become BookMyMandir tools only through explicit, versioned adapters after tenant isolation, consent, audit, access and evidence checks pass.

01

OUR MODEL

Why zero percent changes the architecture.

Enter the story 02

DHARMIC MEMORY

See checked citations kept separate from editorial seeds.

Open the timeline 03

TODAY

Read the source-complete Panchang reference—or no values.

See today