100-tool plan · availability shown

See what your temple can use now.

Every planned workflow shows its current availability and limits. Today, zero tools have authenticated production proof; source complete and customer beta do not mean generally available.

0

Production verified

8

Source complete

24

Customer beta

2

Foundation only

66

Not built

One temple workspace

Connect people, operations, governance and public reach.

BookMyMandir is B2B software for temple operators, trusts and boards. The plan connects temple identity, consent, staff access, records and daily work while the institution owns every devotee relationship.

Your institution controls its money, devotee relationships, connected accounts, brand and data. BookMyMandir takes 0% of offerings and labels unavailable tools clearly.

The atlas includes BookMyMandir-native workflows and planned provider-backed modules. Xalen Studio, Vedika or another provider counts only when a versioned adapter delivers the named BookMyMandir operator outcome; access to a neighbouring product is not release evidence.

Availability by tool

Choose a workflow. Check its limits.

Search by workflow, team, availability, package or delivery phase. Open any row to see what exists and what is still limited.

Showing 100 of 100

01

People records, consent, and acquisition

7 shown
001Devotee registerTemple baseP0Temple admin, relationship staffSource complete

What exists

src/lib/devotees.ts; /api/devotees; /dashboard/devotees

Current limit

None for the current add, list, and dedupe scope.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Add, deduplicate and retrieve devotee records for follow-up without maintaining parallel spreadsheets.

Temple outcome to test

A single governed register reduces duplicate entry and staff time spent locating the current contact record.

Measure: duplicate rate · median record lookup time · weekly active operators · record correction count

Adoption path

Start with one office team and a bounded clean import, then expand only after consent and duplicate review.

Direct cost drivers

Fixed: workflow maintenance and tenant isolation; security, privacy and backup controls; baseline operator documentation.

Variable: database reads, writes and storage; audit and log volume; exports and support time.

Requires onboarding guidance and exception support; no support allowance is set until pilot time is observed.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Pause expansion if duplicate corrections or support minutes remain above the pilot baseline for two review periods.

Core recurring relationship-management job with a bounded existing source slice.

002Channel consent record ledgerTemple baseP0Owner, data steward, comms staffSource complete

What exists

recordConsent and canSend in src/lib/devotees.ts; /api/consent

Current limit

Notice policy and legal review remain operational responsibilities.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Include with the core

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Record purpose- and channel-specific consent before staff communicates with a devotee.

Temple outcome to test

A traceable ledger reduces unauthorised outreach and time spent proving why a message was permitted.

Measure: messages blocked for missing consent · consent retrieval time · withdrawal processing time · consent dispute count

Adoption path

Make consent capture mandatory in one campaign workflow, audit exceptions, then extend channel by channel.

Direct cost drivers

Fixed: privacy-policy and legal-control maintenance; secure workflow and evidence design; staff training and response playbooks.

Variable: request, export and evidence storage; notifications, processing and audit events; privacy review and response labour.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Stop affected sends if consent checks fail, evidence is incomplete or governing policy changes.

Required control for communication workflows, not a stand-alone growth promise.

003CSV/XLSX Devotee ImportTemple baseP0Temple admin, data operatorCustomer beta

What exists

src/lib/devoteeImport.ts; src/lib/devoteeXlsx.ts; src/lib/devoteeImportCommit.ts; /api/devotees/import; Devotees dashboard importer

Current limit

Bounded CSV and one-sheet XLSX preview plus tenant-scoped idempotent commit work up to 1 MB / 2,000 rows. Large/background jobs, user mapping, and authenticated production persistence proof remain.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Preview, map and commit bounded devotee CSV or XLSX files with row-level error handling.

Temple outcome to test

A controlled importer shortens migration time while reducing silent corruption and duplicate creation.

Measure: valid rows committed · rejected-row rate · duplicate rate after import · operator minutes per 1,000 rows

Adoption path

Run a small preview with an owner-approved mapping, reconcile the result, then repeat in capped batches.

Direct cost drivers

Fixed: parser and schema maintenance; malicious-file and formula-injection controls; mapping and recovery documentation.

Variable: file processing compute and temporary storage; database writes and duplicate checks; operator support for failed rows.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Stop a batch on schema drift, abnormal reject rates, file limits or unreconciled duplicate growth.

Concrete migration job that unlocks adoption of the core register.

004Devotee SegmentsTemple baseP1Comms staff, relationship staffCustomer beta

What exists

src/lib/devoteeSegments.ts; /api/devotees/segments; /dashboard/devotees/segments provide tenant-scoped saved allowlisted definitions with OWNER/ADMIN mutation, STAFF preview, idempotent create, optimistic versions, atomic audit events, and current consent-aware bounded member previews.

Current limit

No send or journey automation; membership is recomputed, never grants consent, and is not a point-in-time snapshot. Summaries become lower bounds after 5,000 scanned records, member pages scan at most 1,000, create replay lasts 30 days, and authenticated production proof remains.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Save consent-safe devotee segments for recurring festival, donor and service follow-up.

Temple outcome to test

Reusable eligibility rules reduce repeated list work and lower accidental outreach to ineligible contacts.

Measure: segment reuse count · list-preparation minutes · ineligible contacts excluded · segment correction rate

Adoption path

Create one reviewed festival segment from existing consent records, compare its result manually, then reuse it.

Direct cost drivers

Fixed: workflow maintenance and tenant isolation; security, privacy and backup controls; baseline operator documentation.

Variable: database reads, writes and storage; audit and log volume; exports and support time.

Requires onboarding guidance and exception support; no support allowance is set until pilot time is observed.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Disable a segment when consent logic, membership freshness or query cost cannot be reconciled.

Recurring CRM job with measurable preparation and compliance outcomes.

005Donor / Relationship PipelinePer seatP2Trustee, fundraiserCustomer beta

What exists

src/lib/relationshipPipeline.ts; /api/relationships; /dashboard/relationships provide verified-workspace, tenant-scoped opportunities linked to existing devotees, bounded stage and owner changes, append-only activities, actor-bound idempotency, optimistic versions and atomic audit events. OWNER/ADMIN manage the pipeline; assigned active STAFF can operate their records.

Current limit

No outreach, automation, forecast, donation attribution, bulk actions, custom stages, deletion or authenticated AWS production proof. This is a private relationship-workflow beta, not evidence that money was raised or contact occurred.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Track a donor or institutional relationship through owned stages, next actions and notes.

Temple outcome to test

A shared pipeline reduces missed follow-ups and unclear ownership without claiming fundraising revenue.

Measure: overdue next actions · median time between stages · records without an owner · completed follow-ups

Adoption path

Use for one approved relationship programme, import no speculative contacts, and review stage hygiene weekly.

Direct cost drivers

Fixed: workflow maintenance and tenant isolation; security, privacy and backup controls; baseline operator documentation.

Variable: database reads, writes and storage; audit and log volume; exports and support time.

Requires onboarding guidance and exception support; no support allowance is set until pilot time is observed.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Consolidate or stop if teams do not update next actions or support effort exceeds observed operator use.

Proven recurring relationship-operations pattern, bounded to temple-owned contacts.

006Opt-in Pandit Professional ProfilesFreeP3Pandit, faith professional, verified employerNot built

What exists

No professional-profile, publication/visibility consent, credential-review, cross-tenant discovery, contact-routing, or employer-search model.

Current limit

Separate professional identity; explicit publish and contact consent; privacy and retention controls; credential provenance; moderation; abuse reporting; and a fair-search policy.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Let a pandit voluntarily publish and maintain a professional profile with explicit visibility and contact consent.

Temple outcome to test

Verified opt-in profiles may reduce the time a temple spends finding relevant candidates without promising placement.

Measure: active consented profiles · profile completion rate · verified search-to-contact events · moderation SLA

Adoption path

Pilot with a small invited cohort, manual credential provenance and revocable visibility before any open discovery.

Direct cost drivers

Fixed: trust-and-safety policy and moderation tooling; employer and credential-review operations; search and anti-scrape controls.

Variable: profile indexing and search traffic; notifications and review minutes; abuse investigations and appeals.

Requires ongoing moderation, verification, abuse response and appeals; backlog and SLA are commercial gates.

Contribution gate

Keep free only within a funded public-good or acquisition budget and a measured per-user cost ceiling; otherwise cap, sponsor, consolidate or retire it.

Stop or reprice: Pause publication on consent failures, scraping, unsafe contact patterns or an unmanageable moderation backlog.

Explicit workforce vision; supply-side basic profile remains free and currently unbuilt.

007Temple Lead & Claim IntakeFreeP0Temple claimant, BMM opsSource complete

What exists

src/app/claim; /api/lead; /admin/leads

Current limit

Manual verification remains a BMM operations process.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Include with the core

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Review a temple institution's request to claim or establish an authorised workspace.

Temple outcome to test

Structured evidence intake reduces unsafe access grants and manual back-and-forth during onboarding.

Measure: median review time · requests needing more evidence · incorrect grants · abuse rejection count

Adoption path

Use owner-reviewed intake for invited institutions first, document evidence gaps, then formalise review SLAs.

Direct cost drivers

Fixed: public-form security and abuse controls; verification workflow maintenance; operator triage playbooks.

Variable: web requests, WAF checks and record writes; notifications and evidence storage; manual verification or abuse-review time.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Suspend approvals when reviewer capacity, evidence standards or revocation controls are inadequate.

Necessary institutional onboarding control rather than a stand-alone paid tool.

02

Communications and campaigns

8 shown
008Consent-Gated Email CampaignsUsageP0Comms staffCustomer beta

What exists

src/lib/campaigns.ts; src/lib/mailer.ts; /api/campaigns; dashboard UI provide a bounded, sender-dependent workflow.

Current limit

Delivery requires a configured verified sender; synchronous sends are capped at 25 recipients, a durable worker is absent, and provider acceptance is not inbox delivery.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Prepare and submit consent-eligible email announcements to a bounded temple audience.

Temple outcome to test

One governed send workflow may reduce manual mailing work and missed announcements.

Measure: eligible recipients · provider-accepted and delivered outcomes · bounce and complaint rate · operator minutes per campaign

Adoption path

Pilot with a verified sender, one small opted-in segment and reconciled provider events before broader use.

Direct cost drivers

Fixed: sender and compliance onboarding; template and consent policy maintenance; provider adapter certification and monitoring.

Variable: provider message or media charges; queue, retry and outcome-event usage; delivery support and complaint handling.

Software may be self-serve, but any execution by BMM is a separately scoped, approved and time-tracked managed service.

Contribution gate

Each metered unit must cover reconciled provider, cloud, retry and support cost using a current rate card; included units and margin remain unset until pilots.

Stop or reprice: Stop on consent failure, sender loss, complaint threshold, unreconciled delivery or provider rate change.

Recurring temple communications job; provider acceptance is not delivery proof.

009WhatsApp BroadcastUsageP0Comms staffNot built

What exists

src/lib/communications.ts and /api/communications provide an internal consent preview and provider-held job foundation, but no comms-staff UI or delivery path.

Current limit

Meta verification, Cloud API or BSP onboarding, approved templates, a worker, send-time consent recheck, and outcomes remain.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Send approved WhatsApp templates to an opted-in temple audience through a temple-authorised provider account.

Temple outcome to test

A governed channel may improve timely festival communication while reducing manual phone work.

Measure: consent-eligible recipients · delivered outcomes · opt-outs and complaints · response or enquiry events

Adoption path

Obtain provider approval and rate card, connect one temple-owned sender, then run a capped reconciliation pilot.

Direct cost drivers

Fixed: sender and compliance onboarding; template and consent policy maintenance; provider adapter certification and monitoring.

Variable: provider message or media charges; queue, retry and outcome-event usage; delivery support and complaint handling.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

Temple-owned provider spend must stay itemised or paid directly; BMM charges may cover software and separately approved labour only after both show positive contribution.

Stop or reprice: Remain unavailable or stop on missing approval, consent mismatch, quality downgrade, rate change or unreconciled spend.

High-demand proven channel workflow, but no send adapter exists today.

010SMS BroadcastUsageP0Comms staffNot built

What exists

src/lib/communications.ts and /api/communications provide an internal consent preview and provider-held job foundation, but no comms-staff UI or delivery path.

Current limit

Indian DLT principal, sender and templates, a provider contract, worker, send-time consent recheck, and outcomes remain.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Send consented operational or festival SMS through a temple-authorised and compliant sender.

Temple outcome to test

A governed SMS path may reduce missed time-sensitive notices for contacts without app access.

Measure: consent-eligible recipients · delivered outcomes · DLT rejection rate · opt-outs and complaints

Adoption path

Complete DLT/provider onboarding and rate-card review, then pilot one transactional or approved campaign template.

Direct cost drivers

Fixed: sender and compliance onboarding; template and consent policy maintenance; provider adapter certification and monitoring.

Variable: provider message or media charges; queue, retry and outcome-event usage; delivery support and complaint handling.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

Temple-owned provider spend must stay itemised or paid directly; BMM charges may cover software and separately approved labour only after both show positive contribution.

Stop or reprice: Remain unavailable or stop on DLT, consent, sender, delivery-reconciliation or provider-cost failure.

Concrete communications channel; no delivery outcome exists in current source.

011Campaign Journeys & AutomationsUsageP1Comms staffNot built

What exists

No journey state machine, trigger model, queue, or worker.

Current limit

Internal workflow rail using durable queues and idempotent workers.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Define a bounded sequence of consent checks, waits, approvals and follow-up actions for a recurring campaign.

Temple outcome to test

A controlled journey may reduce repetitive staff steps without increasing unauthorised outreach.

Measure: approved runs completed · manual steps removed · failed or retried steps · suppressed contacts

Adoption path

Start with one non-provider internal reminder flow, require dry-run and approval, then add a single verified action.

Direct cost drivers

Fixed: sender and compliance onboarding; template and consent policy maintenance; provider adapter certification and monitoring.

Variable: provider message or media charges; queue, retry and outcome-event usage; delivery support and complaint handling.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

Each metered unit must cover reconciled provider, cloud, retry and support cost using a current rate card; included units and margin remain unset until pilots.

Stop or reprice: Kill a workflow on budget breach, runaway retries, stale consent, missing approval or negative per-run contribution.

Recurring automation outcome, gated on the execution control plane and real adapters.

012Voice / IVR AnnouncementsUsageP3Temple office, elderly-devotee outreachNot built

What exists

No voice provider or route.

Current limit

Voice provider contract, consent, and recording policy.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Schedule approved voice or IVR announcements for consented recipients who benefit from spoken outreach.

Temple outcome to test

Voice may improve access for some audiences while reducing repetitive manual calls.

Measure: connected call outcomes · listening completion · opt-outs and complaints · cost per completed call

Adoption path

Approve recording and consent policy, connect one temple-owned provider account, and pilot a capped local-language message.

Direct cost drivers

Fixed: sender and compliance onboarding; template and consent policy maintenance; provider adapter certification and monitoring.

Variable: provider message or media charges; queue, retry and outcome-event usage; delivery support and complaint handling.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

Temple-owned provider spend must stay itemised or paid directly; BMM charges may cover software and separately approved labour only after both show positive contribution.

Stop or reprice: Stop on recording-policy, consent, spam-complaint, provider-rate or call-outcome reconciliation failure.

Specific accessibility and announcement workflow; provider and recording controls are unbuilt.

013PWA / Push NotificationsUsageP2Comms staff, devoteeNot built

What exists

No push subscription store, service worker send path, or adapter.

Current limit

Web-push or FCM, browser opt-in, and consent model.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Publish opted-in browser push notices for time-sensitive temple updates.

Temple outcome to test

A low-friction owned channel may reduce missed updates without provider messaging spend.

Measure: active opt-ins · successful push outcomes · unsubscribe rate · return visits after notice

Adoption path

Pilot installation and permission prompts on the temple microsite, then send only essential notices with frequency caps.

Direct cost drivers

Fixed: sender and compliance onboarding; template and consent policy maintenance; provider adapter certification and monitoring.

Variable: provider message or media charges; queue, retry and outcome-event usage; delivery support and complaint handling.

Requires onboarding guidance and exception support; no support allowance is set until pilot time is observed.

Contribution gate

Each metered unit must cover reconciled provider, cloud, retry and support cost using a current rate card; included units and margin remain unset until pilots.

Stop or reprice: Pause on permission dark-pattern risk, high unsubscribe rate, delivery drift or support cost above measured use.

Recognisable recurring owned-channel job, currently unbuilt.

014Social content schedule registerUsageP1Content staffCustomer beta

What exists

src/lib/posts.ts; /api/posts; /dashboard/posts; drafts and schedules persist.

Current limit

No publish worker. EventBridge plus approved Meta or YouTube adapters remain.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Draft and schedule a temple-owned social content calendar before staff publishes through approved channels.

Temple outcome to test

A shared schedule may reduce missed festival posts and duplicated content work.

Measure: scheduled items completed · late or missed items · approval turnaround · operator minutes per post

Adoption path

Use the register for one month with manual publishing and approvals before connecting a provider adapter.

Direct cost drivers

Fixed: publishing templates and editorial governance; accessibility, SEO and reliability monitoring; content and domain support playbooks.

Variable: CDN, build, storage and egress usage; research or generation credits; human review, publishing and support time.

Software may be self-serve, but any execution by BMM is a separately scoped, approved and time-tracked managed service.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Do not claim publishing; consolidate if teams only use an external calendar or managed labour dominates contribution.

Bounded editorial operations job with an existing source register.

015Multilingual Message Template LibraryTemple baseP1Comms staff, language editorNot built

What exists

No TPL# model or template UI.

Current limit

Translation and editorial QA plus provider template approvals.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Store approved reusable message templates by language, channel and purpose.

Temple outcome to test

Reviewed templates may shorten preparation time and reduce inconsistent or non-compliant wording.

Measure: template reuse count · drafting minutes · review rejection rate · translation corrections

Adoption path

Create a small approved festival set in one language pair, record ownership and review dates, then expand by demand.

Direct cost drivers

Fixed: publishing templates and editorial governance; accessibility, SEO and reliability monitoring; content and domain support playbooks.

Variable: CDN, build, storage and egress usage; research or generation credits; human review, publishing and support time.

Software may be self-serve, but any execution by BMM is a separately scoped, approved and time-tracked managed service.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Retire a template on stale facts, policy change, low reuse or translation-review burden beyond the plan.

Recurring content-governance job, distinct from delivery and AI generation.

03

Listings, bookings, darshan, and sevas

8 shown
016Unified Offerings & Listings CatalogTemple baseP0Temple admin, seva officeSource complete

What exists

src/lib/listings.ts; /api/listings; /dashboard/listings

Current limit

None for the current CRUD scope.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Maintain one operator-owned catalogue of sevas, darshan enquiries, events and other temple offerings.

Temple outcome to test

A single maintained catalogue may reduce inconsistent public information and staff re-entry.

Measure: active listings · stale-listing rate · update turnaround · duplicate catalogue entries

Adoption path

Publish a small verified set with named owners and review dates, then add categories only as fulfilment is operationally ready.

Direct cost drivers

Fixed: workflow maintenance and tenant isolation; security, privacy and backup controls; baseline operator documentation.

Variable: database reads, writes and storage; audit and log volume; exports and support time.

Requires onboarding guidance and exception support; no support allowance is set until pilot time is observed.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Unpublish stale, unverified or unfulfillable listings; reprice if review and setup labour exceeds observed use.

Core temple-operated presence and booking dependency with bounded source support.

017Darshan enquiry captureTemple baseP0Seva office, devoteeCustomer beta

What exists

Ticket listings, BookingWidget, and /api/booking create enquiries with an optional server-revalidated slot-preference snapshot.

Current limit

Public reservation, confirmation, token, expiry, and payment reconciliation are absent from the source path.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Capture and assign darshan enquiries for temple staff follow-up without presenting an instant booking.

Temple outcome to test

Structured intake may reduce missed enquiries and clarify response ownership.

Measure: enquiries assigned · first-response time · unresolved enquiries · temple-reported confirmations

Adoption path

Route one listing's enquiries to a named staff queue and compare against the prior phone or form process.

Direct cost drivers

Fixed: public-form security and abuse controls; verification workflow maintenance; operator triage playbooks.

Variable: web requests, WAF checks and record writes; notifications and evidence storage; manual verification or abuse-review time.

Requires onboarding guidance and exception support; no support allowance is set until pilot time is observed.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Pause public intake when staff capacity, response SLA, listing accuracy or abuse controls fail.

Concrete enquiry workflow; it must not be sold as confirmed ticketing.

018Seva / puja enquiry captureTemple baseP0Priest, seva office, devoteeCustomer beta

What exists

Service and pandit listings plus enquiry capture exist.

Current limit

Public scheduling, fulfilment state, token, expiry, and optional Vedika integration remain.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Capture seva or puja enquiries with the context staff needs to respond and fulfil manually.

Temple outcome to test

Structured requests may reduce incomplete details and repeated clarification calls.

Measure: complete enquiries · clarification contacts per enquiry · first-response time · temple-reported fulfilments

Adoption path

Use one verified seva listing with a minimal form and named responder before expanding the catalogue.

Direct cost drivers

Fixed: public-form security and abuse controls; verification workflow maintenance; operator triage playbooks.

Variable: web requests, WAF checks and record writes; notifications and evidence storage; manual verification or abuse-review time.

Requires onboarding guidance and exception support; no support allowance is set until pilot time is observed.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Stop intake when fulfilment ownership, privacy notice, listing facts or response capacity are not current.

Recurring operator intake job, explicitly separate from payment and fulfilment proof.

019Slot and capacity deskTemple baseP1Gate staff, operationsCustomer beta

What exists

src/lib/slots.ts, /api/slots, /dashboard/slots, and verified-public availability plus server-revalidated slot preferences on enquiries provide operator capacity controls and a non-reserving public reference.

Current limit

This bounded operator beta is not a public reservation, automated queue, digital or QR token, automatic hold expiry, notification path, payment tracker, or authenticated production integration proof.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Create capacity-bounded slots, place staff holds and confirm or cancel reservations with controlled restore.

Temple outcome to test

An atomic staff desk may reduce over-capacity errors and manual availability reconciliation.

Measure: capacity conflicts prevented · hold-to-confirm time · cancellations restored correctly · manual corrections

Adoption path

Pilot one listing and staff-only reservation flow, reconcile every slot manually, then expose no public picker until proven.

Direct cost drivers

Fixed: capacity and idempotency workflow maintenance; operator and fulfilment playbooks; booking-state monitoring.

Variable: transactional reads and writes; notification and reminder usage; exception handling and support time.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Stop confirmations on capacity ambiguity, reconciliation variance, excessive manual corrections or notification gaps.

Core capacity workflow with a bounded customer-beta source slice.

020Accommodation / Dharamshala BookingTemple baseP2Guest-house manager, devoteeNot built

What exists

No room, inventory, or reservation entity.

Current limit

Availability and deposit policy plus temple-owned payment handoff.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Manage room inventory, availability requests, guest details and staff-confirmed dharamshala stays.

Temple outcome to test

A shared room desk may reduce double allocation and time spent reconciling phone requests.

Measure: allocation conflicts · request-to-confirm time · occupancy record completeness · manual correction count

Adoption path

Model one property and room type, run staff-only beside the current register, then reconcile before any public availability.

Direct cost drivers

Fixed: capacity and idempotency workflow maintenance; operator and fulfilment playbooks; booking-state monitoring.

Variable: transactional reads and writes; notification and reminder usage; exception handling and support time.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop on inventory mismatch, guest-data control gaps, unsupported tax requirements or high setup labour.

Common temple accommodation operation, but the workflow is unbuilt.

021Kalyana Mandapam / Hall BookingTemple baseP2Events manager, devoteeNot built

What exists

No hall calendar, hold, deposit, or contract workflow.

Current limit

Calendar conflict control and temple payment handoff.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Maintain hall availability, requirements, enquiries and staff-approved event reservations.

Temple outcome to test

A governed calendar may reduce double-booking and repeated requirement collection.

Measure: calendar conflicts · complete requirement records · approval time · staff reconciliation minutes

Adoption path

Pilot a single hall with internal holds and approvals while money and contracts stay in temple-owned systems.

Direct cost drivers

Fixed: capacity and idempotency workflow maintenance; operator and fulfilment playbooks; booking-state monitoring.

Variable: transactional reads and writes; notification and reminder usage; exception handling and support time.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop if contract, deposit, tax, capacity or facility rules cannot be represented without unsafe workarounds.

Specific bookable-facility job with measurable conflict reduction.

022Remote Sankalp / Puja FulfilmentUsageP2Priest, seva office, devoteeNot built

What exists

No remote-puja order, proof, stream, or fulfilment workflow.

Current limit

Operational SOP, media and privacy policy, and fulfilment states.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Record a remote sankalp request, assignment, fulfilment evidence and temple-owned follow-up.

Temple outcome to test

A visible queue may reduce missed requests and unclear fulfilment ownership without claiming ritual outcomes.

Measure: requests assigned · fulfilment evidence completed · overdue requests · support disputes

Adoption path

Pilot one clearly scoped seva with temple-approved evidence and privacy rules; payment remains a separate temple handoff.

Direct cost drivers

Fixed: capacity and idempotency workflow maintenance; operator and fulfilment playbooks; booking-state monitoring.

Variable: transactional reads and writes; notification and reminder usage; exception handling and support time.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Stop intake on fulfilment backlog, unverifiable evidence, sensitive-data concerns or temple-policy mismatch.

Temple-operated fulfilment workflow; no spiritual, settlement or delivery claim is implied.

023Group / Yatra BookingTemple baseP3Yatra coordinator, devotee groupNot built

What exists

Content routes exist; no group inventory or itinerary workflow.

Current limit

Capacity, itinerary, and temple-owned payment arrangements.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Coordinate group or yatra enquiries, participant counts, requirements and temple-confirmed allocations.

Temple outcome to test

Structured group intake may reduce repeated calls and capacity surprises.

Measure: complete group requests · capacity exceptions · response time · participant-count corrections

Adoption path

Pilot with invited group organisers and staff-only allocation for one event before public intake.

Direct cost drivers

Fixed: capacity and idempotency workflow maintenance; operator and fulfilment playbooks; booking-state monitoring.

Variable: transactional reads and writes; notification and reminder usage; exception handling and support time.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop when participant privacy, capacity, transport responsibility or support load cannot be bounded.

Recurring group coordination job, distinct from travel-package commerce.

04

Offerings, donations, hundi, and receipts

8 shown
024Temple-Owned Payment-Link HandoffTemple baseP0Trustee, devoteeCustomer beta

What exists

src/lib/paymentHandoff.ts; /api/tenant/payment-destination; /api/payment-handoff; the OWNER profile and public enquiry widget provide strict HTTPS/exact-UPI normalization, optimistic actor-bound mutation, stale-review invalidation, reviewed-version approval, and a post-enquiry destination preview.

Current limit

This is an external handoff only: no order, payment ownership, collection, settlement, reconciliation, refund, statutory receipt, gateway verification, or authenticated AWS production proof. Changing a reviewed destination closes public output until the workspace and exact new version are reviewed again.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Include with the core

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Maintain an owner-approved temple payment destination and reveal only a reviewed handoff after an enquiry.

Temple outcome to test

A controlled handoff may reduce wrong-destination incidents while keeping all funds with the temple.

Measure: approved destinations · stale requests invalidated · wrong-destination reports · review turnaround

Adoption path

Verify one owner-controlled destination with dual review and a manual end-to-end enquiry check; create no BMM order.

Direct cost drivers

Fixed: money-record control design; audit, correction and reconciliation policy; high-assurance operator support.

Variable: transactional writes and evidence storage; exports, acknowledgements and reconciliation compute; review and correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Close public output on destination change, ownership doubt, review expiry, dispute or security incident.

Safety control for temple-owned payments; never a payment, settlement or percentage-revenue product.

025Temple-recorded donation ledgerTemple baseP0Trustee, cashier, accountantCustomer beta

What exists

src/lib/donations.ts; /api/donations; /dashboard/donations provide immutable originals, idempotent correction/reversal/reconciliation entries, conditional effective-state projection, private plain-text internal-record acknowledgements, and formula-safe operational CSV export.

Current limit

No payment settlement verification/import, statutory receipt sequence/PDF, 80G eligibility, Form 10BD/10BE output, legal acceptance, or authenticated production integration proof. The acknowledgement is not a payment, tax, settlement, or statutory document.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Record temple-reported offerings and corrections in an immutable operational donation ledger.

Temple outcome to test

A correction-safe ledger may reduce spreadsheet ambiguity and shorten internal reconciliation.

Measure: records reconciled · correction and reversal rate · missing-reference count · close preparation time

Adoption path

Run beside the temple's books for one controlled period, reconcile every entry, and keep BMM outside funds flow.

Direct cost drivers

Fixed: money-record control design; audit, correction and reconciliation policy; high-assurance operator support.

Variable: transactional writes and evidence storage; exports, acknowledgements and reconciliation compute; review and correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Stop or constrain entry when reconciliation variance, statutory confusion, support load or data quality is unresolved.

Core record-only temple job with a bounded customer-beta source slice.

02680G Acknowledgement + 10BD/10BE ExportTemple baseP0Accountant, trustee, donorNot built

What exists

No eligibility engine, receipt sequence, PDF, or statutory export.

Current limit

Counsel-approved fields and eligibility, sequence controls, PDF and filing formats.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Issue counsel-approved donation acknowledgements and prepare reviewed 10BD or 10BE data for an eligible temple trust.

Temple outcome to test

Controlled numbering and exports may reduce year-end preparation time and statutory correction work.

Measure: eligible records reviewed · sequence exceptions · export corrections · year-end preparation hours

Adoption path

Begin only with a legally reviewed eligibility policy, one registered trust and parallel professional reconciliation.

Direct cost drivers

Fixed: accounting, payroll or statutory domain design; migration, disaster-recovery and access controls; legal and professional review.

Variable: relational or transactional database usage; statements, exports and document generation; high-touch close, filing or correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Keep unavailable or shut statutory output when law, registration, sequence, reconciliation or professional review is not current.

High-value statutory workflow, but it cannot be inferred from a donation record or generic PDF.

027Recurring Donation / Nithya SevaTemple baseP1Fundraiser, donorNot built

What exists

No recurrence or scheduler.

Current limit

Temple gateway subscription support plus the donation ledger.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Track temple-approved recurring donation or nithya-seva intentions and the fulfilment records staff must review.

Temple outcome to test

A governed schedule may reduce missed follow-ups without BMM collecting or auto-debiting offerings.

Measure: active schedules reviewed · missed follow-ups · temple-reported fulfilments · cancellations processed

Adoption path

Pilot reminder-only schedules for existing temple relationships before any provider or payment automation.

Direct cost drivers

Fixed: money-record control design; audit, correction and reconciliation policy; high-assurance operator support.

Variable: transactional writes and evidence storage; exports, acknowledgements and reconciliation compute; review and correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Stop on ambiguous consent, payment ownership, fulfilment evidence, cancellation handling or reconciliation variance.

Recurring temple relationship job; no collection or settlement may be implied.

028Goal-Based Kainkaryam FundraisersTemple baseP1Fundraiser, devoteeNot built

What exists

Donation listings exist; no verified totals or progress ledger.

Current limit

Donation ledger, reconciled totals, and public progress component.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Publish and maintain a temple-approved kainkaryam goal with progress based only on reconciled temple records.

Temple outcome to test

Clear goals and updates may improve qualified supporter understanding without promising donation volume.

Measure: verified goal updates · stale-progress incidents · qualified enquiries · reconciliation lag

Adoption path

Pilot one time-bounded project with named approvers, source evidence and manual reconciliation before publication.

Direct cost drivers

Fixed: money-record control design; audit, correction and reconciliation policy; high-assurance operator support.

Variable: transactional writes and evidence storage; exports, acknowledgements and reconciliation compute; review and correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Unpublish on stale evidence, purpose change, reconciliation mismatch, legal concern or fulfilment dispute.

Specific temple fundraising-operations job; BMM remains outside funds flow and takes 0%.

029Physical Hundi ReconciliationPer seatP1Cashier, accountant, trusteeCustomer beta

What exists

src/lib/hundiReconciliation.ts; /api/hundi-reconciliation; /dashboard/donations/hundi provide verified-workspace integer-paise denomination batches, immutable maker counts, a blinded different-owner/admin denomination recount, optimistic versions, actor-bound replay, atomic event/audit writes, and a manual temple-reported bank-deposit comparison.

Current limit

Record-only beta: no donation-ledger entry, bank verification, custody proof, settlement, money movement, statutory receipt, Books/accounting sync, or authenticated production-AWS proof. The bank reference and deposit amount are operator-entered and not verified by BMM.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Record a denomination batch, independent blinded recount and manual comparison to a temple-reported deposit.

Temple outcome to test

A two-person evidence trail may reduce counting disputes and surface variance earlier.

Measure: batches independently recounted · variance rate · time to resolve variance · same-actor attempts blocked

Adoption path

Pilot beside the existing physical custody process with two authorised staff and manual bank reconciliation.

Direct cost drivers

Fixed: money-record control design; audit, correction and reconciliation policy; high-assurance operator support.

Variable: transactional writes and evidence storage; exports, acknowledgements and reconciliation compute; review and correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop on custody ambiguity, same-actor control failure, unresolved variance or confusion with bank verification.

Concrete dual-control record workflow with a bounded customer-beta source slice.

030Gold / Kind Donation RegisterPer seatP2Trustee, accountantNot built

What exists

No asset-linked in-kind donation model.

Current limit

Valuation policy, maker-checker, and asset register.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Register gold, material or other in-kind donations with valuation source, custody and disposition evidence.

Temple outcome to test

A controlled register may reduce missing provenance and speed internal or statutory review.

Measure: records with complete provenance · custody exceptions · valuation corrections · audit retrieval time

Adoption path

Define approved item classes and custody roles, then pilot a read-only migration beside the legal register.

Direct cost drivers

Fixed: high-assurance registry and access design; retention, evidence and audit controls; migration and verification playbooks.

Variable: record and attachment storage; audit events, exports and backups; verification, correction and support time.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Do not replace the legal register; stop on valuation, custody, ownership, insurance or retention uncertainty.

Temple-specific high-assurance register, currently unbuilt.

031Donor Statements & Opt-In Recognition WallTemple baseP2Fundraiser, donorNot built

What exists

CRM has contacts; no donation history or recognition consent.

Current limit

Donation ledger, statement renderer, and explicit public-display consent.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Prepare a donor's temple-recorded statement and manage explicit consent for any public recognition.

Temple outcome to test

Self-consistent statements may reduce manual enquiries while consent controls prevent unwanted publicity.

Measure: statement requests fulfilled · reconciliation corrections · recognition opt-ins withdrawn · support contacts per statement

Adoption path

Pilot private statements for reconciled records first; add public recognition only with granular revocable consent.

Direct cost drivers

Fixed: money-record control design; audit, correction and reconciliation policy; high-assurance operator support.

Variable: transactional writes and evidence storage; exports, acknowledgements and reconciliation compute; review and correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Disable output on ledger mismatch, identity uncertainty, consent withdrawal or unresolved privacy complaint.

Recurring donor-service job tied to a trusted ledger, not a public donor leaderboard.

05

Prasad commerce, inventory, and logistics

7 shown
032Prasad StorefrontTemple baseP2Store manager, devoteeNot built

What exists

No product, cart, or order routes.

Current limit

Internal commerce build and temple-owned payment arrangement.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Maintain temple-owned prasad items, availability and order requests for fulfilment by the temple or its approved vendor.

Temple outcome to test

A current catalogue may reduce phone ordering and incomplete fulfilment details.

Measure: complete order requests · out-of-stock requests · fulfilment turnaround · catalogue corrections

Adoption path

Pilot a small local catalogue with manual fulfilment and temple-owned payment before adding shipping providers.

Direct cost drivers

Fixed: catalogue, order and fulfilment workflow maintenance; provider and tax-boundary review; operator setup and exception playbooks.

Variable: order, inventory and shipment records; provider calls, notifications and labels; returns, reconciliation and support time.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Stop public ordering on inventory mismatch, tax ambiguity, unsafe food information or fulfilment backlog.

Recognisable temple commerce workflow; BMM does not own inventory, fulfilment or offering funds.

033Prasad Shipping & TrackingUsageP2Fulfilment staff, devoteeNot built

What exists

No shipment model or carrier adapter.

Current limit

Carrier contract and keys, pickup operations, and data-processing terms.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Create shipment requests and reconcile tracking outcomes for temple-fulfilled prasad orders.

Temple outcome to test

Integrated tracking may reduce status calls and unassigned shipment exceptions.

Measure: orders with tracking · dispatch time · delivery exceptions · status enquiries

Adoption path

Connect one approved shipping provider under temple credentials and reconcile a capped set of domestic shipments.

Direct cost drivers

Fixed: catalogue, order and fulfilment workflow maintenance; provider and tax-boundary review; operator setup and exception playbooks.

Variable: order, inventory and shipment records; provider calls, notifications and labels; returns, reconciliation and support time.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

Temple-owned provider spend must stay itemised or paid directly; BMM charges may cover software and separately approved labour only after both show positive contribution.

Stop or reprice: Stop on provider access loss, unreconciled shipping charges, unsafe address handling or exception backlog.

Concrete fulfilment job with provider pass-through economics.

034Inventory & Low-Stock AlertsPer seatP2Store or kitchen managerNot built

What exists

Xalen ERP is marketing-only; no stock ledger.

Current limit

SKU ledger, atomic movements, and alerts.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Record stock movements and review low-stock exceptions for prasad, supplies or approved store items.

Temple outcome to test

A maintained stock ledger may reduce stockouts and unexplained inventory variance.

Measure: stockout incidents · inventory variance · low-stock alerts resolved · manual adjustments

Adoption path

Pilot a single storeroom and limited SKU set with cycle counts before expanding locations or automation.

Direct cost drivers

Fixed: catalogue, order and fulfilment workflow maintenance; provider and tax-boundary review; operator setup and exception playbooks.

Variable: order, inventory and shipment records; provider calls, notifications and labels; returns, reconciliation and support time.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop automated availability on unresolved variance, missing movement discipline or excessive migration/support burden.

Proven inventory-control job adapted to temple operations.

035Temple Counter POSPer seatP3Counter staffNot built

What exists

No POS, receipt, tender, or offline sync path.

Current limit

Hardware and browser design, offline conflict rules, and temple payment terminal.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Record counter selections and hand off payment to the temple's own approved collection arrangement.

Temple outcome to test

A controlled counter register may shorten queues and reduce manual order transcription.

Measure: counter transactions recorded · void and correction rate · queue handling time · end-of-shift variance

Adoption path

Run one supervised counter in record-only mode and reconcile every shift before any hardware or payment integration.

Direct cost drivers

Fixed: catalogue, order and fulfilment workflow maintenance; provider and tax-boundary review; operator setup and exception playbooks.

Variable: order, inventory and shipment records; provider calls, notifications and labels; returns, reconciliation and support time.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop on offline conflict, shift variance, tax or payment ambiguity, device failure or support intensity beyond the pilot.

Recurring temple counter job; no payment-terminal or settlement capability exists today.

036Vendor Directory & RFQsTemple baseP3Procurement staff, vendorCustomer beta

What exists

src/lib/vendorRfqs.ts; /api/vendor-rfqs; /dashboard/vendor-rfqs provide a verified-workspace private vendor directory, RFQ drafts and manually recorded quotes with transaction-time role and tenant guards, optimistic versions, actor-bound idempotency and atomic audits.

Current limit

No vendor outreach or portal, claim verification, award, purchase order, inventory, contract, payment, comparison export or authenticated AWS production proof. Quotes are operator-entered records only and never imply a vendor was contacted.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Invite approved vendors to submit comparable quotations for a defined temple requirement.

Temple outcome to test

A structured RFQ record may reduce comparison time and missing quotation evidence.

Measure: complete quotations · comparison preparation time · late responses · conflict or correction events

Adoption path

Pilot one low-risk requirement with invited vendors, named reviewers and an off-platform award decision.

Direct cost drivers

Fixed: domain workflow and role-policy maintenance; audit and notification controls; operator onboarding material.

Variable: record, attachment and event storage; notifications and workflow execution; exception and training support.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop on vendor-verification gaps, procurement-policy conflict, collusion concerns or support-heavy custom comparisons.

Bounded sourcing job with an existing customer-beta RFQ slice; no procurement award is automated.

037Subscription Prasad BoxUsageP3Store manager, diaspora devoteeNot built

What exists

No commerce or recurring fulfilment engine.

Current limit

Prasad commerce and shipping plus temple gateway recurring payment.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Maintain recurring prasad preferences and staff fulfilment schedules with revocable customer instructions.

Temple outcome to test

A schedule may reduce missed repeat fulfilments and manual re-entry.

Measure: active schedules fulfilled · missed dispatches · preference changes processed · cancellations completed

Adoption path

Pilot a reminder-only schedule for a local cohort; keep payment and shipment confirmation in temple-owned flows.

Direct cost drivers

Fixed: catalogue, order and fulfilment workflow maintenance; provider and tax-boundary review; operator setup and exception playbooks.

Variable: order, inventory and shipment records; provider calls, notifications and labels; returns, reconciliation and support time.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Stop on payment ambiguity, stock instability, cancellation failure, shipment backlog or negative fulfilment economics.

Recurring fulfilment job; it depends on working inventory, orders and shipping.

038Returns / RTO / Refund Case ManagerUsageP3Fulfilment staffNot built

What exists

No order, shipment, return, or refund model.

Current limit

Commerce, carrier webhooks, and temple-owned refund rail.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Track return-to-origin, damage, refund-request and resolution cases for temple-fulfilled prasad orders.

Temple outcome to test

A shared exception queue may reduce unresolved cases and repeated status enquiries.

Measure: open exception age · cases with evidence · resolution time · repeat contacts per case

Adoption path

Use with one shipping provider and a written temple refund policy before automating any provider action.

Direct cost drivers

Fixed: catalogue, order and fulfilment workflow maintenance; provider and tax-boundary review; operator setup and exception playbooks.

Variable: order, inventory and shipment records; provider calls, notifications and labels; returns, reconciliation and support time.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop automated actions on policy mismatch, payment ownership ambiguity, provider dispute or excessive manual case labour.

Practical post-fulfilment operations job, currently unbuilt.

06

Presence, content, ads, and connected accounts

8 shown
039Public Temple MicrositeTemple baseP0Temple admin, devoteeSource complete

What exists

src/app/temple/[slug]; getTenantBySlug; listing rendering and verified-only payment-link handoff in source

Current limit

No authenticated production proof; the source-complete boundary is the current BMM subpath scope.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Publish and maintain an institution-controlled temple site with verified listings, notices and contact paths.

Temple outcome to test

An owned, current public presence may increase qualified enquiries and reduce misinformation.

Measure: valid pages indexed · qualified enquiries · stale-content incidents · site uptime

Adoption path

Launch a verified minimum site on the BMM path, assign content owners and measure enquiries before custom-domain work.

Direct cost drivers

Fixed: publishing templates and editorial governance; accessibility, SEO and reliability monitoring; content and domain support playbooks.

Variable: CDN, build, storage and egress usage; research or generation credits; human review, publishing and support time.

Software may be self-serve, but any execution by BMM is a separately scoped, approved and time-tracked managed service.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Noindex or unpublish unverified pages; reprice when custom content, support or traffic exceeds measured plan limits.

Core B2B public-presence workflow with measurable discovery and reliability outcomes.

040Domain availability checkerUsageP1Temple adminCustomer beta

What exists

/api/domains; src/lib/domains.ts; /dashboard/domain check availability only.

Current limit

Registration is human-gated; ACM, CloudFront binding, and DNS ownership remain.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Include with the core

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Check whether a requested domain may be available before an operator starts a separate purchase and binding process.

Temple outcome to test

A bounded check may reduce setup back-and-forth without implying registration or ownership.

Measure: checks completed · provider errors · checks leading to approved setup · support contacts

Adoption path

Offer during guided site setup with explicit availability and registrar disclaimers; require human approval for purchase.

Direct cost drivers

Fixed: publishing templates and editorial governance; accessibility, SEO and reliability monitoring; content and domain support playbooks.

Variable: CDN, build, storage and egress usage; research or generation credits; human review, publishing and support time.

Expected to be self-serve after setup; pilot must still measure support minutes and documentation gaps.

Contribution gate

Keep free only within a funded public-good or acquisition budget and a measured per-user cost ceiling; otherwise cap, sponsor, consolidate or retire it.

Stop or reprice: Rate-limit or stop on abuse, stale provider data, material query cost or confusion with domain registration.

Useful setup utility but not a complete domain product or stand-alone paid tool.

041Connected Accounts Vault FoundationTemple baseP0Owner, digital adminFoundation only

What exists

src/lib/connections.ts and src/lib/crypto.ts provide KMS-sealed credential primitives; /api/connections and the dashboard can list or revoke existing metadata.

Current limit

Every provider is unavailable, and there is no connect route, OAuth callback, or live adapter. The current UI is a gated foundation, not a usable connection flow.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Foundation · not sellable

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Store and revoke a tenant-scoped encrypted provider credential for a future approved adapter.

Temple outcome to test

A governed vault may reduce credential sprawl once real adapters exist; it has no operator outcome by itself.

Measure: credentials with owner and purpose · revocations completed · unauthorised access attempts · adapter activations using the vault

Adoption path

Use only behind one reviewed adapter with least privilege, expiry and revocation; never expose it as a separate product.

Direct cost drivers

Fixed: identity, authorization and security maintenance; audit, reliability and incident controls; platform documentation.

Variable: authentication, KMS and database operations; event, log and webhook volume; security and integration support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Disable activation on missing adapter contract, excessive scope, failed rotation, audit gap or security incident.

Security primitive #41 is explicitly foundation-only and must not count as a sellable operator workflow.

042Live Darshan StreamingUsageP2Media staff, devoteeNot built

What exists

No stream ingest, player, or provider source.

Current limit

Provider decision, rights and privacy policy, and bandwidth model.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Schedule and operate a temple-authorised live darshan stream with clear availability and moderation controls.

Temple outcome to test

Reliable live access may serve remote devotees while reducing repeated stream-status enquiries.

Measure: successful live minutes · viewer start failures · moderation incidents · cost per viewer minute

Adoption path

Pilot one event using temple-owned rights, a capped audience and an approved streaming provider.

Direct cost drivers

Fixed: media-rights and safety policy; player, ingest and delivery maintenance; stream reliability monitoring.

Variable: ingest, transcoding and stored media; viewer minutes and egress; moderation and live-event support.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

Temple-owned provider spend must stay itemised or paid directly; BMM charges may cover software and separately approved labour only after both show positive contribution.

Stop or reprice: Stop on rights uncertainty, unsafe content, reliability breach, unbounded egress or after-hours support overload.

Concrete media operation with material provider and live-support economics.

043Devotional Media Library / VODUsageP2Media staff, priestNot built

What exists

Static public assets are not a tenant media library.

Current limit

Tenant uploads, transcoding, retention, and permissions.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Upload, review, organise and publish temple-owned devotional recordings with rights and retention metadata.

Temple outcome to test

A governed library may reduce repeated uploads and help devotees find approved media.

Measure: approved assets · rights metadata completeness · successful plays · storage and egress per active asset

Adoption path

Begin with a small rights-cleared archive and defined retention policy before accepting large or user-submitted media.

Direct cost drivers

Fixed: media-rights and safety policy; player, ingest and delivery maintenance; stream reliability monitoring.

Variable: ingest, transcoding and stored media; viewer minutes and egress; moderation and live-event support.

Software may be self-serve, but any execution by BMM is a separately scoped, approved and time-tracked managed service.

Contribution gate

Each metered unit must cover reconciled provider, cloud, retry and support cost using a current rate card; included units and margin remain unset until pilots.

Stop or reprice: Archive or reject media on rights, moderation, low-use storage, egress or review-cost thresholds.

Practical temple media-management job, currently unbuilt.

044AI Content StudioUsageP1Content staff, priestNot built

What exists

No production AI generation route, evaluation, or approval UI.

Current limit

Approved model contract, safety and evaluation, cost meter, and human approval flow.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Draft temple-specific content from approved facts for a staff member to review, edit and publish.

Temple outcome to test

Assisted drafting may reduce first-draft time without reducing factual or cultural review.

Measure: drafts approved · editing minutes · factual corrections · model cost per approved draft

Adoption path

Pilot one constrained template with approved source facts, mandatory human review and a per-tenant model budget.

Direct cost drivers

Fixed: model adapter, evaluation and safety maintenance; prompt and provenance controls; operator review workflow.

Variable: model-native tokens, images or media units; workflow compute, storage and retries; mandatory human review and correction time.

Software may be self-serve, but any execution by BMM is a separately scoped, approved and time-tracked managed service.

Contribution gate

Each metered unit must cover reconciled provider, cloud, retry and support cost using a current rate card; included units and margin remain unset until pilots.

Stop or reprice: Stop on provenance failure, unsafe output, high correction rate, budget breach or negative cost per approved draft.

Concrete reviewed drafting workflow; generic generation without sources or review is not the product.

045Ad Campaign Brief BuilderTemple baseP1Marketing staffCustomer beta

What exists

src/lib/adBriefs.ts; /api/ad-briefs; /dashboard/ads export a brief.

Current limit

No live launch. Provider approvals remain and the temple must own spend and card.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Prepare an approved ad campaign brief and export it for manual launch in the temple's own ad account.

Temple outcome to test

A complete brief may reduce launch rework and missing approvals without claiming live ad delivery.

Measure: briefs approved · missing-field rate · approval turnaround · manual launch corrections

Adoption path

Use for one managed campaign with named approvers and temple-owned spend; compare exported brief to actual setup.

Direct cost drivers

Fixed: provider app review and adapter maintenance; approval, spend and policy controls; campaign support playbooks.

Variable: provider API or data-credit usage; media processing, retries and reporting; managed campaign labour; ad spend remains temple-owned.

Software may be self-serve, but any execution by BMM is a separately scoped, approved and time-tracked managed service.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Keep export-only; change-order managed work when review cycles or account setup exceed the written scope.

Bounded preparation job with source support; it is not automated ad launch.

046Per-Temple SEO / Discovery ConsoleUsageP2Digital adminNot built

What exists

BMM has global SEO surfaces; no tenant GSC or GBP dashboard.

Current limit

Provider OAuth and property verification.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Review verified search visibility, page health and qualified enquiry signals for one temple presence.

Temple outcome to test

An evidence-led console may focus staff on valid pages and discovery work rather than rank promises.

Measure: valid indexed pages · non-brand impressions and clicks · qualified enquiries · stale or invalid pages retired

Adoption path

Connect read-only first-party search data, establish a baseline and assign a monthly action review.

Direct cost drivers

Fixed: publishing templates and editorial governance; accessibility, SEO and reliability monitoring; content and domain support playbooks.

Variable: CDN, build, storage and egress usage; research or generation credits; human review, publishing and support time.

Software may be self-serve, but any execution by BMM is a separately scoped, approved and time-tracked managed service.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop generation or publishing on thin data, unverifiable facts, review backlog, research-budget breach or attribution drift.

Measurable owned-discovery job; no ranking or traffic guarantee is permitted.

07

Temple operations and ERP

10 shown
047Festival / Utsav Operations BoardPer seatP1Festival managerCustomer beta

What exists

src/lib/festivalOps.ts; /api/festival-ops; /dashboard/festival-ops provide verified-workspace private operations boards and dated checklists with OWNER/ADMIN board scope, STAFF task operations, active-member assignment, vendor/contact and crowd/capacity notes, durable replay, optimistic versions, transaction-time board/member invariants, atomic audit events, and bounded operator UI.

Current limit

Tenant-entered manual planning only. Vendor support is notes rather than a vendor workflow; no public festival facts, volunteer roster, notifications, automation, crowd telemetry, payments, pagination beyond 100 items, or authenticated production proof.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Coordinate festival tasks, owners, vendors, volunteers, dependencies and operational status in one board.

Temple outcome to test

A shared runbook may reduce missed dependencies and unclear ownership before an utsav.

Measure: overdue critical tasks · tasks without owners · blocked dependencies · post-event rework items

Adoption path

Run one festival from a reviewed template, hold weekly owner reviews and capture the post-event retrospective.

Direct cost drivers

Fixed: domain workflow and role-policy maintenance; audit and notification controls; operator onboarding material.

Variable: record, attachment and event storage; notifications and workflow execution; exception and training support.

Requires onboarding guidance and exception support; no support allowance is set until pilot time is observed.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Consolidate if teams only duplicate an external task tool; reprice when custom setup or support dominates use.

Recurring temple-specific operations job with a bounded customer-beta source slice.

048Pandit Opportunities & Temple HiringPer seatP2Pandit, temple HR, verified faith-sector employerNot built

What exists

No employer verification, role or engagement post, application, introduction, matching, recruiter seat, or hiring workflow.

Current limit

Tool 6; verified employer and recruiter; role moderation; consent-safe contact; anti-discrimination, retention, and audit controls; and a private-HR handoff. No job, interview, placement, response, endorsement, or external-employer partnership is promised.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Let a verified temple or faith-sector employer publish a role and review consented, relevant pandit applications.

Temple outcome to test

A governed hiring workflow may shorten time to a qualified applicant without promising interviews or placement.

Measure: verified employers · qualified applications · time to first qualified applicant · abuse and discrimination reports

Adoption path

Pilot invited verified employers, manually reviewed jobs and opt-in applicants with fair-ranking and contact controls.

Direct cost drivers

Fixed: trust-and-safety policy and moderation tooling; employer and credential-review operations; search and anti-scrape controls.

Variable: profile indexing and search traffic; notifications and review minutes; abuse investigations and appeals.

Requires ongoing moderation, verification, abuse response and appeals; backlog and SLA are commercial gates.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Pause employer access on verification failure, scraping, discrimination, unsafe contact or moderation-SLA breach.

Explicit workforce vision; employer workflow is unbuilt and no placement or partner claim is allowed.

049Crowd & Footfall ManagementUsageP3Operations, securityNot built

What exists

No gate count, occupancy, sensor, or manual counter path.

Current limit

Counter or sensor input, thresholds, and privacy-safe aggregation.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Plan crowd zones, staffing, incidents and capacity signals for a temple-controlled event.

Temple outcome to test

A shared operational view may reduce delayed escalation and capacity surprises; it does not guarantee safety.

Measure: incidents acknowledged · response time · capacity exceptions · post-event corrective actions

Adoption path

Pilot offline planning and staff reporting for one event with the temple's existing safety authority and procedures.

Direct cost drivers

Fixed: domain workflow and role-policy maintenance; audit and notification controls; operator onboarding material.

Variable: record, attachment and event storage; notifications and workflow execution; exception and training support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

Each metered unit must cover reconciled provider, cloud, retry and support cost using a current rate card; included units and margin remain unset until pilots.

Stop or reprice: Do not automate safety decisions; stop on sensor uncertainty, privacy risk, stale capacity data or false assurance.

Real high-stakes operations job, but requires domain inputs and safety governance.

050Annadanam / Kitchen ManagerPer seatP2Kitchen manager, volunteerNot built

What exists

No meal plan, ingredient, batch, or kitchen route.

Current limit

Recipes, procurement, and meal-count model.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Plan annadanam menus, meal counts, ingredients, preparation tasks and service records.

Temple outcome to test

A shared kitchen plan may reduce shortages, waste and last-minute procurement.

Measure: planned versus served meals · ingredient variance · stockout incidents · waste or leftover record

Adoption path

Pilot one recurring meal service with manual counts and food-safety owners before inventory automation.

Direct cost drivers

Fixed: domain workflow and role-policy maintenance; audit and notification controls; operator onboarding material.

Variable: record, attachment and event storage; notifications and workflow execution; exception and training support.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop automation when food-safety, count quality, procurement or support requirements cannot be bounded.

Temple-specific recurring kitchen operation with measurable variance outcomes.

051Asset & Jewel RegisterPer seatP2Trustee, custodian, auditorNot built

What exists

No asset data model; Xalen ERP is marketing-only.

Current limit

Strong RBAC, dual approval, immutable audit, and encrypted media.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Maintain a controlled register of temple assets and jewels with custody, condition, evidence and review history.

Temple outcome to test

A high-assurance register may reduce missing evidence and shorten authorised audit retrieval.

Measure: assets with complete custody evidence · unresolved custody exceptions · verification turnaround · audit retrieval time

Adoption path

Begin with a read-only verified subset, strict least-privilege roles and dual review beside the legal register.

Direct cost drivers

Fixed: high-assurance registry and access design; retention, evidence and audit controls; migration and verification playbooks.

Variable: record and attachment storage; audit events, exports and backups; verification, correction and support time.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop on access-control, custody, valuation, insurance, evidence or physical-verification uncertainty.

High-value temple governance job; digital records do not prove physical custody.

052Maintenance / Facilities DeskPer seatP2Facility manager, assigned staffCustomer beta

What exists

src/lib/facilities.ts; /api/facilities; /dashboard/facilities provide verified-workspace internal work orders with OWNER/ADMIN create and assignment, STAFF read/operate access, same-tenant active assignees, bounded status transitions, optimistic versions, actor-bound idempotency, append-only events, atomic audit, and bounded operator UI.

Current limit

Record-only internal desk: no public or devotee intake, BMM product support, attachments, vendor outreach/portal, procurement or purchase orders, inventory, IoT telemetry, notifications, SLA, costing, billing, deletion, or authenticated production-AWS proof.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Create, assign and progress internal temple maintenance work orders with controlled status history.

Temple outcome to test

A shared desk may reduce forgotten repairs and unclear assignment.

Measure: open work-order age · unassigned orders · reopened work · completion cycle time

Adoption path

Pilot one facilities team and a limited issue taxonomy without vendor outreach, procurement or SLA promises.

Direct cost drivers

Fixed: domain workflow and role-policy maintenance; audit and notification controls; operator onboarding material.

Variable: record, attachment and event storage; notifications and workflow execution; exception and training support.

Requires onboarding guidance and exception support; no support allowance is set until pilot time is observed.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Consolidate if staff do not maintain status; reprice when attachments, notifications or support exceed pilot bounds.

Concrete recurring facilities job with a bounded customer-beta source slice.

053Gaushala ManagerPer seatP3Gaushala managerNot built

What exists

No cattle, feed, or health data path.

Current limit

Domain workflow and optional veterinary-record policy.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Maintain gaushala animal, feed, health-task and care records for authorised staff.

Temple outcome to test

A shared care register may reduce missed scheduled tasks and incomplete animal histories.

Measure: scheduled care tasks completed · records missing required fields · feed variance · overdue health follow-ups

Adoption path

Co-design one bounded workflow with gaushala operators and veterinary policy before importing live records.

Direct cost drivers

Fixed: domain workflow and role-policy maintenance; audit and notification controls; operator onboarding material.

Variable: record, attachment and event storage; notifications and workflow execution; exception and training support.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Keep unavailable or stop when veterinary scope, record quality, welfare escalation or setup labour is not governed.

Temple-adjacent domain workflow with a real operator, but requirements are not yet evidenced.

054Land, Lease & Property RegisterPer seatP3Trustee, estate managerNot built

What exists

No property, lease, or rent records.

Current limit

Legal data model, document vault, and access controls.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Maintain temple land, lease, property documents, obligations and renewal dates under restricted access.

Temple outcome to test

A governed register may reduce missed renewals and time spent locating current property evidence.

Measure: properties with complete evidence · renewals due or missed · document retrieval time · unresolved ownership exceptions

Adoption path

Pilot a verified read-only register with legal review and document-level permissions; do not infer title validity.

Direct cost drivers

Fixed: high-assurance registry and access design; retention, evidence and audit controls; migration and verification playbooks.

Variable: record and attachment storage; audit events, exports and backups; verification, correction and support time.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop on title dispute, legal-policy mismatch, access-control gap, stale evidence or excessive migration review.

Recurring high-assurance property administration job, not a title or legal-opinion service.

055Ritual Calendar / Nitya-NaimittikaTemple baseP2Head priest, schedulerNot built

What exists

Panchang exists; no tenant ritual SOP, calendar, or reminders.

Current limit

Internal recurrence plus verified Vedika dates.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Maintain an approved nitya-naimittika ritual calendar with owners, preparation tasks and change history.

Temple outcome to test

A shared ritual operations calendar may reduce missed preparation steps and schedule conflicts.

Measure: scheduled duties completed · calendar conflicts · late changes · unassigned preparation tasks

Adoption path

Model one temple's current priest-approved calendar and validate a full cycle before notifications or public display.

Direct cost drivers

Fixed: domain workflow and role-policy maintenance; audit and notification controls; operator onboarding material.

Variable: record, attachment and event storage; notifications and workflow execution; exception and training support.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop public or automated output on calendar-authority disagreement, stale rules or high correction burden.

Temple-native scheduling job distinct from generic calendar software.

056Procurement & Vendor RecordsPer seatP2Procurement staff, accountantNot built

What exists

No purchase order or vendor ledger.

Current limit

Vendor master, approvals, inventory, and Books linkage.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Maintain approved vendors, procurement requests, decisions and supporting records after an RFQ.

Temple outcome to test

A traceable procurement record may reduce missing approvals and invoice-matching exceptions.

Measure: requests with complete approvals · decision cycle time · invoice match exceptions · vendor-record corrections

Adoption path

Pilot one low-risk category with written authority limits and manual award; integrate no payment or bank action.

Direct cost drivers

Fixed: domain workflow and role-policy maintenance; audit and notification controls; operator onboarding material.

Variable: record, attachment and event storage; notifications and workflow execution; exception and training support.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop on policy conflict, vendor-verification gap, collusion concern, budget ambiguity or high custom approval burden.

Concrete procurement record workflow that follows, but does not duplicate, the RFQ slice.

08

Xalen Books, finance, tax, and payroll

8 shown
057Xalen Books — Double-Entry AccountingPer seatP2Accountant, trusteeNot built

What exists

Marketing only; no journal, ledger, or chart of accounts.

Current limit

Accounting design, opening balances, and audit-grade invariants.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Post balanced accounting entries, close periods and produce controlled temple trust books.

Temple outcome to test

Purpose-built books may shorten monthly close and reduce spreadsheet reconciliation errors.

Measure: days to close · unbalanced or suspense items · post-close corrections · reconciliation exceptions

Adoption path

Start with accountant-approved chart-of-accounts design and parallel books for one entity and period.

Direct cost drivers

Fixed: accounting, payroll or statutory domain design; migration, disaster-recovery and access controls; legal and professional review.

Variable: relational or transactional database usage; statements, exports and document generation; high-touch close, filing or correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Keep unavailable or stop if accounting review, migration, close support, DR or reconciliation cannot meet pilot controls.

Proven back-office category with temple-specific needs; current source has no double-entry engine.

058GST & Tax Filing HelperPer seatP3AccountantNot built

What exists

No GST or tax entity and export path.

Current limit

CA or counsel-approved rules and versioned filing formats.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Prepare reviewed GST and tax working papers or filing handoffs from reconciled temple records.

Temple outcome to test

Controlled data preparation may reduce filing rework and missing-document follow-up.

Measure: records needing correction · working-paper preparation time · professional review findings · filing handoff exceptions

Adoption path

Design with current professional advice, generate draft-only working papers and compare to an approved filing cycle.

Direct cost drivers

Fixed: accounting, payroll or statutory domain design; migration, disaster-recovery and access controls; legal and professional review.

Variable: relational or transactional database usage; statements, exports and document generation; high-touch close, filing or correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Never auto-file until authorised; stop output on law, schema, registration, source-data or professional-review failure.

Recurring finance job; product must not present generic tax text as legal or filing capability.

059Payroll / VetanamPer seatP3HR admin, accountantNot built

What exists

Xalen HRMS is marketing-only.

Current limit

Payroll compliance, PF and ESI rules, and bank payout decision.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Prepare and review temple staff or priest payroll inputs, calculations and controlled pay-run outputs.

Temple outcome to test

A governed pay run may reduce calculation errors and correction cycles.

Measure: payroll corrections · run completion time · missing attendance inputs · unresolved pay exceptions

Adoption path

Pilot a small employee cohort in parallel with the current payroll professional and reconcile every line.

Direct cost drivers

Fixed: employment and payroll policy maintenance; role, privacy and migration controls; operator onboarding and close playbooks.

Variable: employee records, attendance and documents; pay-run or export compute; correction, compliance and support time.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop on labour-law, tax, attendance, bank, privacy or reconciliation uncertainty; never infer wage compliance.

Proven recurring HR-finance job with high correctness and support burden.

060Expenses & ReimbursementsPer seatP2Staff, approver, accountantNot built

What exists

No claim or approval entity.

Current limit

RBAC, approval workflow, and document storage.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Submit, review and reconcile staff expenses and reimbursements against temple policy.

Temple outcome to test

A structured approval trail may shorten reimbursement cycles and reduce missing evidence.

Measure: submission-to-decision time · claims missing evidence · policy exceptions · reconciliation corrections

Adoption path

Pilot one expense category and approval chain with manual payout remaining in the temple's bank process.

Direct cost drivers

Fixed: accounting, payroll or statutory domain design; migration, disaster-recovery and access controls; legal and professional review.

Variable: relational or transactional database usage; statements, exports and document generation; high-touch close, filing or correction support.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop automation on policy ambiguity, duplicate claims, receipt-verification gaps or support-heavy custom rules.

Common controlled back-office workflow, currently unbuilt.

061Vendor Bills & Accounts PayablePer seatP3Accountant, procurementNot built

What exists

No bill, accounts-payable, or payout route.

Current limit

Books, procurement, and temple-owned bank or payment rail.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Record vendor bills, approvals, due dates and temple-executed payment status.

Temple outcome to test

A governed payable queue may reduce late bills and missing approval evidence.

Measure: overdue approved bills · duplicate bills detected · approval cycle time · payment-status reconciliation exceptions

Adoption path

Pilot one vendor category with three-way evidence where available; keep payment execution in the temple's bank.

Direct cost drivers

Fixed: accounting, payroll or statutory domain design; migration, disaster-recovery and access controls; legal and professional review.

Variable: relational or transactional database usage; statements, exports and document generation; high-touch close, filing or correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop on duplicate risk, approval-policy conflict, tax ambiguity, bank-status mismatch or excessive exception support.

Proven payable operation with explicit temple-owned money movement.

062Budgets, Corpus & Fund AllocationPer seatP2Trustee, accountantNot built

What exists

No fund-restriction or budget model.

Current limit

Books, donation classifications, and trustee policy.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Set and review approved budgets, corpus restrictions and fund allocations against recorded actuals.

Temple outcome to test

Visible allocations may reduce overspend and late discovery of restricted-fund exceptions.

Measure: budget exceptions · restricted-fund mismatches · forecast revisions · review preparation time

Adoption path

Pilot one approved fund and period after the books model is reconciled; run board review from read-only reports.

Direct cost drivers

Fixed: accounting, payroll or statutory domain design; migration, disaster-recovery and access controls; legal and professional review.

Variable: relational or transactional database usage; statements, exports and document generation; high-touch close, filing or correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop decision support when source books, restrictions, approvals or allocation rules are not current.

Recurring board-finance workflow dependent on reliable accounting data.

063Bank / Gateway ReconciliationUsageP2AccountantNot built

What exists

Payment handoff stores no settlements; no bank import.

Current limit

Temple-authorized statement import or gateway adapter.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Match temple bank or gateway statements to internally recorded transactions and resolve exceptions.

Temple outcome to test

A structured match queue may shorten close and surface missing or duplicate records earlier.

Measure: automatic and reviewed match rate · unmatched items · days to reconcile · post-close corrections

Adoption path

Start with read-only statement import for one temple-owned account and manually approve every match.

Direct cost drivers

Fixed: accounting, payroll or statutory domain design; migration, disaster-recovery and access controls; legal and professional review.

Variable: relational or transactional database usage; statements, exports and document generation; high-touch close, filing or correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

Each metered unit must cover reconciled provider, cloud, retry and support cost using a current rate card; included units and margin remain unset until pilots.

Stop or reprice: Stop matching on schema drift, ambiguous references, provider access loss, unreconciled variance or excessive review labour.

High-value close workflow; it proves neither settlement nor account ownership by itself.

064Statutory Audit PackPer seatP3Trustee, auditorNot built

What exists

No audit binder or export; statutory donation chain is absent.

Current limit

Donation and finance tools plus CA or counsel acceptance.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Assemble a controlled audit pack of reconciled records, approvals, evidence and exception reports.

Temple outcome to test

A consistent pack may reduce evidence collection time and repeated auditor requests.

Measure: pack completeness · auditor follow-up requests · preparation hours · post-pack corrections

Adoption path

Define one accountant- or auditor-reviewed checklist and compare the generated draft to the prior period's accepted pack.

Direct cost drivers

Fixed: accounting, payroll or statutory domain design; migration, disaster-recovery and access controls; legal and professional review.

Variable: relational or transactional database usage; statements, exports and document generation; high-touch close, filing or correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Label draft-only or stop when source records, retention, professional requirements or completeness cannot be proven.

Practical evidence-assembly job dependent on finance modules and professional review.

09

People, workforce, service desk, projects, and knowledge

7 shown
065Xalen HRMS Staff RecordsPer seatP2HR admin, trusteeNot built

What exists

No staff or member management UI.

Current limit

RBAC and invites plus employment-data policy.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Maintain private temple staff records, roles, documents and lifecycle status.

Temple outcome to test

A governed employee record may reduce fragmented files and outdated access information.

Measure: active records with required fields · offboarding completion time · access mismatches · record correction requests

Adoption path

Pilot minimum necessary fields for one team, define retention and offboarding, and keep public pandit profiles separate.

Direct cost drivers

Fixed: employment and payroll policy maintenance; role, privacy and migration controls; operator onboarding and close playbooks.

Variable: employee records, attendance and documents; pay-run or export compute; correction, compliance and support time.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop collection on unclear purpose, excessive sensitive fields, retention gaps, access-control failure or high migration burden.

Core private HR job; it must never auto-create a public workforce profile.

066Attendance, Leave & ShiftsPer seatP2Staff, HR adminNot built

What exists

No attendance, leave, or shift model.

Current limit

HRMS, offline or mobile capture, and approval rules.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Plan staff or priest shifts, capture attendance and process leave against approved policy.

Temple outcome to test

A shared roster may reduce uncovered duties and payroll-input corrections.

Measure: uncovered shifts · attendance corrections · leave approval time · payroll exceptions from roster data

Adoption path

Pilot one team and roster cycle, allow manual correction with audit, then reconcile to payroll inputs.

Direct cost drivers

Fixed: employment and payroll policy maintenance; role, privacy and migration controls; operator onboarding and close playbooks.

Variable: employee records, attendance and documents; pay-run or export compute; correction, compliance and support time.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop automation on policy, biometric/privacy, offline-sync, correction or labour-law uncertainty.

Proven workforce operation with temple-specific scheduling needs.

067Volunteer / Sevadar ManagementPer seatP2Volunteer coordinatorNot built

What exists

No volunteer profile, availability, or assignment workflow.

Current limit

Consent, scheduling, and safeguarding policy.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Register, schedule and communicate with consented volunteers or sevadars for approved temple duties.

Temple outcome to test

A governed roster may reduce unfilled duties and repeated coordination calls.

Measure: duties filled · no-show rate · coordination contacts per shift · withdrawals processed

Adoption path

Pilot one event with explicit volunteer consent, safeguarding checks and named supervisors.

Direct cost drivers

Fixed: employment and payroll policy maintenance; role, privacy and migration controls; operator onboarding and close playbooks.

Variable: employee records, attendance and documents; pay-run or export compute; correction, compliance and support time.

Requires ongoing moderation, verification, abuse response and appeals; backlog and SLA are commercial gates.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop on safeguarding, consent, background-check, contact-abuse or coordinator-capacity failure.

Recurring temple volunteer coordination job, distinct from employment or public pandit hiring.

068Per-Temple Devotee HelpdeskPer seatP1Seva desk, devoteeCustomer beta

What exists

src/lib/helpdesk.ts; /api/helpdesk; /dashboard/helpdesk; /temple/[slug]/help provide verified-temple public contact intake and tenant-scoped operator tickets with status, priority, active-member assignment, internal notes, optimistic versions, append-only events, idempotent intake, atomic abuse counters, retention TTLs, and bounded operator UI.

Current limit

Manual record only: no outbound reply, provider notification, SLA, automation, attachments, or pagination beyond the latest 100 tickets and 200 events. Public abuse still needs WAF/challenge controls; authenticated production proof remains.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Receive, assign and resolve devotee-facing questions or service issues within a temple's own queue.

Temple outcome to test

A shared queue may reduce lost enquiries and make response ownership visible.

Measure: first-response time · open ticket age · reopen rate · tickets without an owner

Adoption path

Pilot one temple contact channel with a small taxonomy, named responders and no SLA promise until measured.

Direct cost drivers

Fixed: domain workflow and role-policy maintenance; audit and notification controls; operator onboarding material.

Variable: record, attachment and event storage; notifications and workflow execution; exception and training support.

Requires onboarding guidance and exception support; no support allowance is set until pilot time is observed.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Reprice or limit when attachment, message, after-hours or configuration burden exceeds observed seat use.

Concrete tenant helpdesk job with a bounded customer-beta source slice.

069BMM Product Support InboxFreeP0Temple user, BMM opsSource complete

What exists

/api/support; SupportWidget; lead storage and admin path

Current limit

BMM operations staffing and response policy.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Include with the core

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Submit a BookMyMandir product-support request and track BMM's response.

Temple outcome to test

A clear support path may reduce unresolved platform issues and repeated contacts.

Measure: first-response time · resolution time · reopen rate · support minutes by issue type

Adoption path

Route existing customer support through one queue, publish scope and hours, then staff against observed demand.

Direct cost drivers

Fixed: support tooling, knowledge base and staffing readiness; routing and escalation policy; service-quality reporting.

Variable: support minutes and after-hours coverage; attachments, email and log storage; specialist escalation and rework.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Set plan limits or separate services when custom implementation, after-hours work or specialist time exceeds support scope.

Necessary BMM service operation, but not a stand-alone temple business tool.

070e-Sign / MudraUsageP3Trustee, vendor, staffNot built

What exists

No document or signature flow.

Current limit

Valid e-sign provider and counsel-approved signature classes.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Route an approved temple document for identity-aware electronic signature and retain completion evidence.

Temple outcome to test

A governed signing path may shorten approval cycles and reduce missing signature evidence.

Measure: documents completed · completion time · failed identity checks · signature disputes

Adoption path

Select one low-risk document type, verify applicable signature standard and connect an approved provider under contract.

Direct cost drivers

Fixed: identity, authorization and security maintenance; audit, reliability and incident controls; platform documentation.

Variable: authentication, KMS and database operations; event, log and webhook volume; security and integration support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

Temple-owned provider spend must stay itemised or paid directly; BMM charges may cover software and separately approved labour only after both show positive contribution.

Stop or reprice: Keep unavailable or stop on legal-suitability, identity, provider, evidence-retention or rate-card failure.

Common approval workflow; provider and legal validity must be document-specific.

071Projects, Tasks & SOP Knowledge BasePer seatP2Manager, staff, volunteerCustomer beta

What exists

src/lib/projectsKnowledge.ts; /api/projects; /dashboard/projects provide verified-workspace projects, bounded tasks and immutable SOP revisions. OWNER/ADMIN manage scope; assigned active STAFF update their tasks. Writes enforce transaction-time verification, role, assignment, version and cap guards with durable idempotency and atomic audit events.

Current limit

Tenant-wide read visibility remains coarse. No per-project ACL, attachments, dependencies, notifications, automation, approvals, search, export, delete/unarchive, audit viewer or authenticated AWS concurrency proof.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Plan temple projects, assign tasks and maintain approved SOP knowledge with version history.

Temple outcome to test

A shared work and SOP surface may reduce missed tasks and repeated process questions.

Measure: overdue tasks · tasks without owners · SOP reuse · stale SOP review count

Adoption path

Pilot one recurring project and three operational SOPs, assign owners and review usefulness monthly.

Direct cost drivers

Fixed: domain workflow and role-policy maintenance; audit and notification controls; operator onboarding material.

Variable: record, attachment and event storage; notifications and workflow execution; exception and training support.

Requires onboarding guidance and exception support; no support allowance is set until pilot time is observed.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Consolidate if it duplicates an adopted external system; reprice when migration or custom workflow support dominates.

Proven recurring operations pattern with a bounded customer-beta source slice.

10

Tenant, governance, access, and platform

7 shown
072Tenant Profile + Verification IntakeTemple baseP0Owner, temple adminCustomer beta

What exists

src/lib/verification.ts; /api/tenant/verification; /api/admin/verifications; /dashboard/profile and /admin/verifications provide an OWNER request, pending operations queue, SUPER_ADMIN decision, transaction-time identity and destination snapshot guards, and atomic audit events.

Current limit

This remains customer-beta source evidence: no authenticated production-AWS review proof, reviewer assignment/SLA, document ingestion, expiry, periodic re-verification, revocation console, or automated authority verification.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Include with the core

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Maintain an institution profile and submit ownership or authority evidence for BMM review.

Temple outcome to test

A structured profile and decision trail may reduce unsafe activation and repeated onboarding requests.

Measure: complete submissions · review turnaround · reverification or revocation events · evidence correction count

Adoption path

Use for invited institutions with owner submission and independent admin review before exposing verified-only actions.

Direct cost drivers

Fixed: identity, authorization and security maintenance; audit, reliability and incident controls; platform documentation.

Variable: authentication, KMS and database operations; event, log and webhook volume; security and integration support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Suspend verified-only actions on stale authority, disputed ownership, reviewer backlog or revocation-control failure.

Required institutional trust control, not a paid verification endorsement.

073Staff Invites & Role-Based AccessPer seatP0Owner, all staffCustomer beta

What exists

src/lib/team.ts, seatEntitlements.ts, authorization.ts; /api/team; /dashboard/team; /invite/accept provide an owner-operated, audited invite/member lifecycle with atomic active and pending seat limits.

Current limit

Authenticated production proof remains. Invite mail is best-effort and requires a verified workspace plus configured Resend; owner transfer, service accounts, durable mail outbox, and Google OAuth remain unavailable.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Include with the core

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Invite temple staff, assign bounded roles and revoke access when responsibilities change.

Temple outcome to test

Role-scoped team access may reduce shared credentials and speed safe onboarding or offboarding.

Measure: active and pending seats · invite acceptance time · revocation time · role-change audit events

Adoption path

Pilot owner-led invites for a small verified workspace, review every role, then set paid seat packaging only after usage.

Direct cost drivers

Fixed: identity, authorization and security maintenance; audit, reliability and incident controls; platform documentation.

Variable: authentication, KMS and database operations; event, log and webhook volume; security and integration support.

Requires onboarding guidance and exception support; no support allowance is set until pilot time is observed.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop invites on capacity, identity, audit or authorisation failure; reprice only from observed active-seat support and cost.

Core access control with a bounded customer-beta source slice; seat limits are not billing proof.

074Audit Event Writer FoundationPer seatP0OwnerFoundation only

What exists

src/lib/audit.ts provides bounded append-only general events and a tenant-scoped recent-event reader; /api/audit and /dashboard/audit expose the latest owner-only events without request IDs or storage keys beyond the opaque event id.

Current limit

This is not WORM storage or a complete audit-trail product. No export, retention policy, update/delete prevention, full sensitive-route coverage, specialized-event migration, or authenticated production proof exists.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Foundation · not sellable

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Append a tenant-scoped audit event from another reviewed workflow.

Temple outcome to test

A common writer may improve evidence consistency, but it has no complete operator job by itself.

Measure: reviewed workflows emitting events · write failures · events missing required context · retention exceptions

Adoption path

Adopt internally one workflow at a time with schema, retention and access review; never market it separately.

Direct cost drivers

Fixed: identity, authorization and security maintenance; audit, reliability and incident controls; platform documentation.

Variable: authentication, KMS and database operations; event, log and webhook volume; security and integration support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Disable a caller on schema drift, missing actor or tenant context, retention failure or unaffordable log volume.

Platform primitive #74 is explicitly foundation-only and must not count as an immutable audit product.

075Multi-Temple / Board OrganizationPer seatP3Board admin, samsthanaNot built

What exists

No hierarchy above TENANT#.

Current limit

Organization tenancy, delegated admin, and consolidated policy.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Let an authorised board oversee multiple temple workspaces without collapsing their data, roles or accounts.

Temple outcome to test

A governed organisation layer may reduce duplicate administration and improve board-level exception review.

Measure: workspaces governed · cross-tenant access exceptions · board report preparation time · delegation changes

Adoption path

Pilot one legally related group with explicit membership, delegated roles and isolated records before aggregate reporting.

Direct cost drivers

Fixed: identity, authorization and security maintenance; audit, reliability and incident controls; platform documentation.

Variable: authentication, KMS and database operations; event, log and webhook volume; security and integration support.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop on legal-entity ambiguity, cross-tenant leakage, unsupported delegation or high-touch organisational setup.

Real enterprise governance job requiring a tenancy model beyond the current one-subject workspace.

076Configurable Approval WorkflowsPer seatP2Trustee, managersNot built

What exists

No maker-checker or workflow engine.

Current limit

RBAC, workflow rules, notifications, and audit.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Consolidate or remove

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Route a specific high-risk record through named approvers, thresholds and a recorded decision.

Temple outcome to test

Module-specific approvals may reduce unauthorised changes and missing decision evidence.

Measure: decisions completed · approval cycle time · bypassed or stale approvals · workflow-specific exceptions

Adoption path

Implement inside one proven module and policy first; extract shared primitives only after a second workflow validates reuse.

Direct cost drivers

Fixed: identity, authorization and security maintenance; audit, reliability and incident controls; platform documentation.

Variable: authentication, KMS and database operations; event, log and webhook volume; security and integration support.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Do not build a generic engine when module rules are unknown; consolidate on policy drift or custom-rule support overload.

Generic platform-shaped row; approval value must be sold inside concrete finance, procurement or governance workflows.

077Public API & WebhooksUsageP2Enterprise IT, integratorNot built

What exists

Current API routes are app-internal bearer-auth surfaces.

Current limit

Versioned API, service credentials, scopes, rate limits, and webhook signing.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Consolidate or remove

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Let an approved temple system read or receive a narrowly scoped BMM workflow event under revocable credentials.

Temple outcome to test

A versioned integration may reduce duplicate entry for a proven customer workflow.

Measure: successful authorised calls · duplicate steps removed · delivery failures · support incidents per integration

Adoption path

Build one customer-backed endpoint and webhook event with versioning, quotas and replay controls before any public platform claim.

Direct cost drivers

Fixed: identity, authorization and security maintenance; audit, reliability and incident controls; platform documentation.

Variable: authentication, KMS and database operations; event, log and webhook volume; security and integration support.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

Each metered unit must cover reconciled provider, cloud, retry and support cost using a current rate card; included units and margin remain unset until pilots.

Stop or reprice: Disable on abuse, scope creep, unreconciled usage, breaking-version cost or integration support above contribution.

Platform capability, not a stand-alone tool; retain only when a named customer workflow justifies it.

078Offline-First Temple Counter ModePer seatP3Counter staffNot built

What exists

Dashboard is online-only; no offline queue or sync.

Current limit

PWA storage, conflict and idempotency design, and printer support.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Continue bounded temple counter recording during a network outage and reconcile conflicts when connectivity returns.

Temple outcome to test

A controlled offline queue may reduce service interruption without creating duplicate or lost records.

Measure: offline records reconciled · conflict rate · duplicate prevention · recovery time

Adoption path

Pilot one device and one low-risk record type with short offline windows, signed local state and supervised reconciliation.

Direct cost drivers

Fixed: identity, authorization and security maintenance; audit, reliability and incident controls; platform documentation.

Variable: authentication, KMS and database operations; event, log and webhook volume; security and integration support.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop on unresolved conflicts, insecure device state, long offline windows, money ambiguity or high field-support burden.

Concrete temple-counter resilience job with significant device and conflict complexity.

11

DPDP, privacy, and legal operations

8 shown
079Data Fiduciary Dashboard / RoPAPer seatP2Data steward, trusteeNot built

What exists

Consent ledger exists; no obligations or processing-register UI.

Current limit

Counsel-reviewed control set and ownership workflow.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Maintain a reviewed record of processing activities, purposes, data classes, recipients and controls.

Temple outcome to test

A current RoPA may reduce compliance evidence collection time and expose unmanaged processing.

Measure: activities reviewed on schedule · activities missing owners or bases · stale records · audit preparation time

Adoption path

Begin with counsel-approved inventory workshops for one institution and quarterly named-owner reviews.

Direct cost drivers

Fixed: privacy-policy and legal-control maintenance; secure workflow and evidence design; staff training and response playbooks.

Variable: request, export and evidence storage; notifications, processing and audit events; privacy review and response labour.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Do not imply legal compliance; stop automation on law change, incomplete inventory or unavailable professional review.

Concrete data-governance job, but it requires legal review and current operational evidence.

080DSAR / Grievance PortalTemple baseP2Grievance officer, devoteeNot built

What exists

No data-request entity, identity verification, or SLA timer.

Current limit

Legal workflow, requester verification, and export or delete functions.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Receive, verify, assign and evidence a data-subject or grievance request through completion.

Temple outcome to test

A controlled queue may reduce missed deadlines and fragmented response evidence.

Measure: verified requests · response cycle time · overdue requests · identity or scope exceptions

Adoption path

Pilot internal staff intake with documented identity proof, scope, exemptions and professional escalation before public launch.

Direct cost drivers

Fixed: privacy-policy and legal-control maintenance; secure workflow and evidence design; staff training and response playbooks.

Variable: request, export and evidence storage; notifications, processing and audit events; privacy review and response labour.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop public intake when identity, legal scope, provider-held data, deletion authority or response staffing is unresolved.

High-stakes recurring privacy operation; a CSV export alone is not a DSAR workflow.

081Breach Response & Notification WorkflowPer seatP2Security lead, trusteeNot built

What exists

No incident or breach workflow.

Current limit

Counsel-approved timelines and templates plus incident roles.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Open, triage and coordinate a temple data incident with decisions, evidence and approved notifications.

Temple outcome to test

A rehearsed workflow may reduce response delay and missing incident evidence without guaranteeing compliance.

Measure: time to triage · actions without owners · notification decision time · post-incident actions completed

Adoption path

Create and tabletop-test one counsel-reviewed playbook with named responders before accepting live incident reliance.

Direct cost drivers

Fixed: privacy-policy and legal-control maintenance; secure workflow and evidence design; staff training and response playbooks.

Variable: request, export and evidence storage; notifications, processing and audit events; privacy review and response labour.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Escalate outside product and pause automation on legal uncertainty, severe incident, unavailable responders or stale playbook.

Concrete response-coordination job; software does not replace incident counsel or authorities.

082Data Retention & PurgeTemple baseP2Data stewardNot built

What exists

Lead TTL exists; no tenant-wide retention policy or purge engine.

Current limit

Entity retention schedule, legal holds, and deletion jobs.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Review records due for retention action and execute authorised deletion or hold with evidence.

Temple outcome to test

A governed schedule may reduce over-retention and manual search for records due for action.

Measure: records reviewed by due date · deletions or holds completed · policy exceptions · failed downstream purges

Adoption path

Start with one low-risk data class, approved policy and reversible dry-run report before deletion execution.

Direct cost drivers

Fixed: privacy-policy and legal-control maintenance; secure workflow and evidence design; staff training and response playbooks.

Variable: request, export and evidence storage; notifications, processing and audit events; privacy review and response labour.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop deletion on legal hold, dependency uncertainty, backup/provider gap, failed verification or policy change.

Recurring privacy lifecycle job with irreversible-action controls.

083Multilingual Privacy Notice BuilderTemple baseP1Data steward, content editorNot built

What exists

Consent records carry noticeVersion; no authoring or publishing tool.

Current limit

Counsel-approved base notices and translation QA.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Assemble a multilingual privacy notice from reviewed processing facts and track its approvals and versions.

Temple outcome to test

A structured draft may reduce version drift and translation omissions without giving legal advice.

Measure: notices with current approvals · translation corrections · stale facts detected · review turnaround

Adoption path

Pilot one counsel-approved source notice and professionally reviewed translation; publish only exact approved versions.

Direct cost drivers

Fixed: privacy-policy and legal-control maintenance; secure workflow and evidence design; staff training and response playbooks.

Variable: request, export and evidence storage; notifications, processing and audit events; privacy review and response labour.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Do not publish on unreviewed law, purpose, recipient or translation changes; reprice specialist review separately.

Concrete controlled-document job; generated language is not legal acceptance.

084DPIA WizardPer seatP3Data steward, product ownerNot built

What exists

No assessment model or template.

Current limit

Counsel-approved methodology and review gate.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Guide a named owner through a structured DPIA draft, risks, mitigations and approval evidence.

Temple outcome to test

A consistent assessment workflow may reduce missing risk questions and review preparation time.

Measure: assessments completed · risks without owners · review findings · time to approved decision

Adoption path

Pilot one high-risk processing change with privacy counsel; use templates only as prompts, never automated approval.

Direct cost drivers

Fixed: privacy-policy and legal-control maintenance; secure workflow and evidence design; staff training and response playbooks.

Variable: request, export and evidence storage; notifications, processing and audit events; privacy review and response labour.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Stop or escalate when risk exceeds template scope, counsel is unavailable or mitigations lack accountable owners.

Specific compliance workflow if counsel-backed; not a generic AI checklist.

085Aggregate-Only Analytics GuardrailTemple baseP2Data engineer, auditorNot built

What exists

No k-anonymity or aggregate query policy engine.

Current limit

Query policy, threshold design, and adversarial privacy tests.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Consolidate or remove

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Enforce minimum cohorts and suppression rules before another module releases aggregate analytics.

Temple outcome to test

A shared guardrail may reduce accidental disclosure, but it creates no operator outcome by itself.

Measure: queries suppressed · policy violations prevented · false suppression reviews · modules covered

Adoption path

Implement inside one analytics release with privacy review, test data and documented thresholds before reuse.

Direct cost drivers

Fixed: privacy-policy and legal-control maintenance; secure workflow and evidence design; staff training and response playbooks.

Variable: request, export and evidence storage; notifications, processing and audit events; privacy review and response labour.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Block output on policy ambiguity, small cohorts, inference risk or validation failure; do not market separately.

Privacy foundation that belongs inside concrete analytics products, not a stand-alone sellable tool.

086Consent Preference Centre & Data ExportTemple baseP1Devotee, data stewardCustomer beta

What exists

src/lib/emailPreferences.ts, the opaque signed /email-preferences flow, standard one-click unsubscribe headers, /api/consent-export, and the Devotees UI provide destination-bound email purpose suppression/withdrawal plus OWNER/ADMIN current-state and append-only consent CSVs with release-time authorization, audit-bound hashes, formula safety, exact row caps, and a 25 MiB fail-closed budget.

Current limit

This bounded customer beta is email-only self-service plus synchronous operator records, not a complete tenant or DSAR export. SMS/WhatsApp preference links, requester identity proof, provider-held data, delete/purge, background jobs, distributed export rate limiting, an atomic multi-page snapshot, and authenticated production-AWS proof remain unavailable.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Include with the core

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Let a recipient withdraw email consent or request a bounded consent-record export while staff reviews exceptions.

Temple outcome to test

Self-service preferences may shorten withdrawal handling and reduce unauthorised follow-up.

Measure: withdrawals applied · suppressed sends · export preparation time · preference disputes

Adoption path

Pilot signed recipient links for email purposes and small formula-safe exports before other channels or full DSAR scope.

Direct cost drivers

Fixed: privacy-policy and legal-control maintenance; secure workflow and evidence design; staff training and response playbooks.

Variable: request, export and evidence storage; notifications, processing and audit events; privacy review and response labour.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Stop export or preference changes on identity, signature, cap, source-consistency or provider-data gaps.

Required consent control with a bounded customer-beta source slice; not a full tenant or DSAR export.

12

Analytics and reporting

6 shown
087Real Temple KPI DashboardTemple baseP0Owner, managerSource complete

What exists

src/lib/stats.ts; /api/stats; dashboard UI query tenant-scoped real counts and honest empty states.

Current limit

Materialized counters may be needed at scale; authenticated production integration proof remains separate.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Include with the core

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Review current tenant-scoped counts and operational exceptions without fabricated sample data.

Temple outcome to test

A truthful summary may reduce time spent assembling basic status and highlight missing work.

Measure: dashboard views leading to action · metric discrepancies · time to weekly status · stale metric incidents

Adoption path

Baseline existing real counts, reconcile against source records and add metrics only with named definitions and owners.

Direct cost drivers

Fixed: metric definitions and data-quality governance; dashboard and pipeline maintenance; privacy and access review.

Variable: event ingest, storage and transformations; query bytes and dashboard reads; analysis, reconciliation and support time.

Requires onboarding guidance and exception support; no support allowance is set until pilot time is observed.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Remove or label a metric when definition, freshness, completeness or source reconciliation fails.

Core operator orientation surface with a bounded source-complete implementation.

088Donation-ledger analyticsTemple baseP1Trustee, fundraiserCustomer beta

What exists

src/lib/donationAnalytics.ts; /api/donations/analytics; /dashboard/donations/analytics aggregate effective immutable-ledger states by currency with bounded filters, modern/legacy deduplication and explicit completeness. A narrow analytics capability lets STAFF read aggregates without exposing donor ledger detail or CSV.

Current limit

Reads are capped at 5,000 states and 10,000 events, become truthful lower bounds when capped, and are not a transactional point-in-time snapshot. No settlement, statutory, trend or category-group claims and no authenticated AWS production proof.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Review bounded donation-ledger totals and completeness limits for internal reconciliation decisions.

Temple outcome to test

A transparent aggregate may shorten manual ledger summaries without implying settlement or statutory truth.

Measure: reports reconciled · capped or incomplete reports · variance investigations · summary preparation time

Adoption path

Compare a small, reconciled period to manual totals and require operators to acknowledge any completeness cap.

Direct cost drivers

Fixed: metric definitions and data-quality governance; dashboard and pipeline maintenance; privacy and access review.

Variable: event ingest, storage and transformations; query bytes and dashboard reads; analysis, reconciliation and support time.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Stop decision use on caps, source mismatch, currency ambiguity, reconciliation failure or query cost above limits.

Specific finance-analysis job with an honest customer-beta source slice.

089Footfall & Crowd InsightsUsageP3Operations, securityNot built

What exists

No footfall source.

Current limit

Crowd input, privacy guardrail, and aggregation.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Review privacy-bounded footfall or crowd trends from an approved, quality-scored source.

Temple outcome to test

Trend visibility may improve staffing plans without identifying individuals or guaranteeing safety.

Measure: data coverage · source error rate · planning changes recorded · privacy or safety exceptions

Adoption path

Pilot one non-identifying source for planning only, compare to manual counts and publish confidence limits.

Direct cost drivers

Fixed: metric definitions and data-quality governance; dashboard and pipeline maintenance; privacy and access review.

Variable: event ingest, storage and transformations; query bytes and dashboard reads; analysis, reconciliation and support time.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

Each metered unit must cover reconciled provider, cloud, retry and support cost using a current rate card; included units and margin remain unset until pilots.

Stop or reprice: Stop on surveillance risk, poor calibration, sparse coverage, unsafe inference or sensor/provider cost change.

Specific planning outcome if a lawful input exists; no source exists today.

090Campaign submission statusTemple baseP1Comms staffCustomer beta

What exists

Campaign records store audience and submitted, pending, or blocked outcomes.

Current limit

Provider events, normalized metrics, and consent-safe reporting.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Consolidate or remove

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Review whether a campaign submission was blocked, pending or accepted by the current provider path.

Temple outcome to test

Visible submission state may reduce repeated checks, but it does not prove delivery or campaign performance.

Measure: submission states reconciled · stuck submissions · provider-event gaps · support contacts

Adoption path

Attach to each real channel workflow with provider events and explicit delivery distinctions; do not sell separately.

Direct cost drivers

Fixed: metric definitions and data-quality governance; dashboard and pipeline maintenance; privacy and access review.

Variable: event ingest, storage and transformations; query bytes and dashboard reads; analysis, reconciliation and support time.

Requires onboarding guidance and exception support; no support allowance is set until pilot time is observed.

Contribution gate

The institution-base allocation must cover reconciled cloud usage, allocated fixed cost and observed support at positive contribution; no price or margin is claimed yet.

Stop or reprice: Consolidate into campaigns; hide state when provider events are stale, ambiguous or unreconciled.

Too narrow to count as a stand-alone product; it is a status view within communications.

091Custom Report BuilderPer seatP3Trustee, analystNot built

What exists

No report definition, query, or export UI.

Current limit

Governed metrics layer and tenant enforcement.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Consolidate or remove

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Assemble a named, governed temple report from approved metrics and filters for a recurring decision.

Temple outcome to test

A reusable report may reduce analyst preparation time only after the decision and metric set are concrete.

Measure: report reuse · preparation time · metric corrections · decisions linked to reports

Adoption path

Build one fixed report for a verified board or operator decision; generalise only after repeated customer evidence.

Direct cost drivers

Fixed: metric definitions and data-quality governance; dashboard and pipeline maintenance; privacy and access review.

Variable: event ingest, storage and transformations; query bytes and dashboard reads; analysis, reconciliation and support time.

Likely needs migration, configuration and recurring specialist support; price only after loaded labour is measured.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Do not ship an unrestricted query builder; consolidate when custom reports become unbounded consulting work.

Generic suite filler until replaced by named decision-grade reports with governed metrics.

092Anonymous Network BenchmarkUsageP3Board or temple leadershipNot built

What exists

No aggregate warehouse or privacy engine.

Current limit

Aggregate-only guardrail, minimum cohort policy, customer consent, and data quality.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Consolidate or remove

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Compare a temple's approved aggregate metric with a sufficiently large, consented and quality-controlled cohort.

Temple outcome to test

A safe benchmark might reveal operational gaps, but no useful cohort or customer proof exists.

Measure: eligible cohorts · suppressed comparisons · data-quality exceptions · actions linked to benchmarks

Adoption path

Do not build until several tenants consent, metrics are comparable and a minimum-cohort privacy review passes.

Direct cost drivers

Fixed: metric definitions and data-quality governance; dashboard and pipeline maintenance; privacy and access review.

Variable: event ingest, storage and transformations; query bytes and dashboard reads; analysis, reconciliation and support time.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

Each metered unit must cover reconciled provider, cloud, retry and support cost using a current rate card; included units and margin remain unset until pilots.

Stop or reprice: Remove or suppress on small cohorts, re-identification risk, incomparable data, low decision use or warehouse cost.

Speculative platform-shaped row with privacy risk and no validated recurring buyer job today.

13

Vedika intelligence, public tools, and learning

8 shown
093Date-level Panchang referenceFreeP0Devotee, priest, panditSource complete

What exists

src/lib/panchang.ts; /panchang; six-hour cache with null fallback

Current limit

Current keyless Vedika panchang endpoint availability.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Look up a date-level panchang reference for planning or editorial work, with unavailable data omitted.

Temple outcome to test

A consistent reference may reduce lookup time for staff and pandits without replacing local authority.

Measure: successful referenced lookups · unavailable responses · correction reports · upstream latency

Adoption path

Use as a free read-only reference with source, date and location context; collect correction feedback before deeper workflows.

Direct cost drivers

Fixed: versioned upstream contract certification; domain QA, provenance and claim policy; adapter and fallback maintenance.

Variable: upstream calls or entitlement units; cache, compute, storage and retries; domain review and correction support.

Expected to be self-serve after setup; pilot must still measure support minutes and documentation gaps.

Contribution gate

Keep free only within a funded public-good or acquisition budget and a measured per-user cost ceiling; otherwise cap, sponsor, consolidate or retire it.

Stop or reprice: Omit output on upstream failure, provenance gap, location ambiguity, unacceptable correction rate or unfunded call cost.

Bounded faith reference with source support; upstream availability is not a guaranteed service level.

094Muhurta + Choghadiya FinderUsageP0Pandit, priest, devoteeNot built

What exists

No lib or route; tested keyless paths did not provide the required data.

Current limit

Verified keyed Vedika contract; never approximate or fabricate.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Find a source-backed muhurta or choghadiya window for a specified date, location and purpose.

Temple outcome to test

A verified reference may reduce manual lookup time while leaving interpretation with the pandit or temple.

Measure: successful useful lookups · unavailable results · correction rate · cost per accepted lookup

Adoption path

Verify a keyed versioned Vedika contract and domain review, then pilot with pandits against trusted manual references.

Direct cost drivers

Fixed: versioned upstream contract certification; domain QA, provenance and claim policy; adapter and fallback maintenance.

Variable: upstream calls or entitlement units; cache, compute, storage and retries; domain review and correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

Each metered unit must cover reconciled provider, cloud, retry and support cost using a current rate card; included units and margin remain unset until pilots.

Stop or reprice: Remain unavailable or stop on missing inputs, contract drift, provenance failure, high correction rate or upstream repricing.

Concrete high-demand pandit workflow, currently blocked on verified upstream data.

095Kundli & MilanUsageP1Pandit, devoteeNot built

What exists

No jyotish lib or route.

Current limit

Product positioning decision, verified Vedika endpoints, and sensitive-data policy.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Generate a consented kundli or milan reference from minimal birth data for a pandit-led workflow.

Temple outcome to test

A verified computation may reduce calculation time without automating sensitive interpretation or decisions.

Measure: completed reports · input corrections · domain-review corrections · upstream cost per accepted report

Adoption path

Make a positioning and sensitive-data decision, certify versioned endpoints, then pilot only with trained pandit reviewers.

Direct cost drivers

Fixed: versioned upstream contract certification; domain QA, provenance and claim policy; adapter and fallback maintenance.

Variable: upstream calls or entitlement units; cache, compute, storage and retries; domain review and correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

Each metered unit must cover reconciled provider, cloud, retry and support cost using a current rate card; included units and margin remain unset until pilots.

Stop or reprice: Remain unavailable or stop on consent, data-minimisation, contract, provenance, interpretation-safety or rate-card failure.

Recognisable professional workflow; no current source or provider contract proves it.

096Rashifal / HoroscopeFreeP2Devotee, content editorNot built

What exists

No horoscope lib or route.

Current limit

Verified Vedika endpoint and editorial or claim policy.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Prepare a source-reviewed rashifal editorial reference for staff publication, with claim and freshness controls.

Temple outcome to test

A governed draft may reduce recurring editorial preparation time without promising predictive outcomes.

Measure: approved editions · editing and correction time · stale editions blocked · cost per approved edition

Adoption path

Define an editorial policy and source contract, then pilot staff-reviewed drafts on a fixed cadence.

Direct cost drivers

Fixed: versioned upstream contract certification; domain QA, provenance and claim policy; adapter and fallback maintenance.

Variable: upstream calls or entitlement units; cache, compute, storage and retries; domain review and correction support.

Software may be self-serve, but any execution by BMM is a separately scoped, approved and time-tracked managed service.

Contribution gate

Keep free only within a funded public-good or acquisition budget and a measured per-user cost ceiling; otherwise cap, sponsor, consolidate or retire it.

Stop or reprice: Stop publication on stale source, unsupported claims, low review quality, cost ceiling or lane conflict.

Potential editorial acquisition workflow; generic generated horoscope copy is not sufficient.

097Vastu ToolsUsageP2Pandit, temple planner, devoteeNot built

What exists

No current route or provider wrapper.

Current limit

Verified Vedika endpoint and bounded non-professional-advice UX.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Run a bounded source-backed vastu reference for a pandit or temple planner to interpret.

Temple outcome to test

Structured inputs may reduce manual calculation time without giving architectural or professional guarantees.

Measure: completed useful references · input corrections · domain-review findings · cost per accepted result

Adoption path

Verify a versioned provider workflow and non-professional-advice boundary, then pilot with trained reviewers.

Direct cost drivers

Fixed: versioned upstream contract certification; domain QA, provenance and claim policy; adapter and fallback maintenance.

Variable: upstream calls or entitlement units; cache, compute, storage and retries; domain review and correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

Each metered unit must cover reconciled provider, cloud, retry and support cost using a current rate card; included units and margin remain unset until pilots.

Stop or reprice: Stop on contract drift, unsafe interpretation, missing context, high correction rate or provider repricing.

Specific professional reference workflow, not a generic content page.

098Numerology & Namkaran ToolsFreeP2Pandit, aspirant, devoteeNot built

What exists

No numerology or name source in the current repo.

Current limit

Verified Vedika endpoint, privacy-minimal inputs, and language QA.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Generate a privacy-minimal numerology or namkaran reference for a pandit-led consultation or learning exercise.

Temple outcome to test

A verified computation may reduce lookup time while leaving naming and interpretation decisions with the user.

Measure: accepted references · input and language corrections · domain-review findings · cost per accepted result

Adoption path

Certify the provider contract, minimise personal inputs and pilot professionally reviewed output in one language.

Direct cost drivers

Fixed: versioned upstream contract certification; domain QA, provenance and claim policy; adapter and fallback maintenance.

Variable: upstream calls or entitlement units; cache, compute, storage and retries; domain review and correction support.

Requires high-touch domain review, controlled corrections and current legal or professional sign-off; no statutory outcome is implied.

Contribution gate

Keep free only within a funded public-good or acquisition budget and a measured per-user cost ceiling; otherwise cap, sponsor, consolidate or retire it.

Stop or reprice: Stop on privacy, provenance, language-quality, interpretation-safety or unfunded usage-cost failure.

Bounded faith reference with a defined reviewer, currently unbuilt.

099Festival editorial draft libraryFreeP1Priest, devoteeCustomer beta

What exists

src/data/festivals.ts and /festivals content pages exist.

Current limit

No per-location live calendar or reminders; verified dates, yearly refresh, and reminder engine remain.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Select and adapt an approved festival editorial draft while verifying date, location and temple-specific facts.

Temple outcome to test

A reviewed draft library may reduce repeated first-draft work without fabricating live calendar data.

Measure: drafts reused · editing minutes · date or fact corrections · stale drafts retired

Adoption path

Use a small owned library with annual named review, explicit draft labels and no automated date claims.

Direct cost drivers

Fixed: publishing templates and editorial governance; accessibility, SEO and reliability monitoring; content and domain support playbooks.

Variable: CDN, build, storage and egress usage; research or generation credits; human review, publishing and support time.

Software may be self-serve, but any execution by BMM is a separately scoped, approved and time-tracked managed service.

Contribution gate

Keep free only within a funded public-good or acquisition budget and a measured per-user cost ceiling; otherwise cap, sponsor, consolidate or retire it.

Stop or reprice: Retire on stale dates, source uncertainty, low reuse, language-review backlog or unfunded editorial cost.

Concrete editorial reuse job with an existing draft library and honest limits.

100Pandit / Vedshala Learning & CertificationPer seatP2Pandit, vedshala, aspirantNot built

What exists

/for-pandits, /for-vedshalas, and /learn are roadmap and interest-capture pages, not a learning product.

Current limit

Course content, assessment, entitlement, certificate issuance, curriculum ownership, and credential policy remain.

Commercial viability · hypothesis only

A practical job, measured before it is priced.

Validate with a pilot

No customer ROI, price, cost or margin is validated for this tool. The temple remains seller, fulfiller, data owner and payment destination; BookMyMandir takes 0% of offerings.

Recurring operator job

Enrol in a reviewed pandit or vedshala course, complete assessments and verify a bounded credential.

Temple outcome to test

Structured learning may improve completion and evidence skill attainment without promising employment or accreditation.

Measure: active learners · course completion · assessment integrity exceptions · credential verification events

Adoption path

Pilot one curriculum with named owners, qualified reviewers, assessment policy and a clearly scoped certificate.

Direct cost drivers

Fixed: curriculum, assessment and credential policy; learning-product and moderation maintenance; instructor and support playbooks.

Variable: media delivery and assessment attempts; credential issuance and verification; learner, instructor and appeal support.

Requires ongoing moderation, verification, abuse response and appeals; backlog and SLA are commercial gates.

Contribution gate

An active-seat charge must cover measured per-seat platform use, allocated fixed cost and observed role-support burden at positive contribution; no seat price is set yet.

Stop or reprice: Keep unavailable or stop on curriculum rights, assessment integrity, credential confusion, moderation backlog or negative learner support economics.

Explicit education vision; landing pages and interest capture are not a learning product.

Proposed packaging

Pay for software. Never a share of offerings.

These labels show the proposed commercial model only. Paid checkout, extra-seat purchase, usage billing, invoicing and plan activation are not available.

Read the pricing proposal

tenant/base

Temple base

Proposed temple-workspace pricing, independent of devotee or offering volume.

per-seat

Per seat

Proposed pricing for staff access, not for devotee records or offerings.

usage

Usage

Proposed charges for disclosed messaging, compute, storage or delivery use.

free

Free

Public and discovery tools proposed without a temple charge.

Start with available workflows

Run today's work. Keep the full plan visible.

100 temple-operator tools — availability by tool · BookMyMandir™