Feature scope - proposed scope
White Label Astrology Platform Features: Billing Comes First
This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.
Scope areas for this kind of build
The Feature Set, Role by Role
Six kinds of user work inside the product, and every one of them is reading from the same 170 table schema.
The Seeker
- Browses practitioners by skill, language, price and rating, then opens a chat, an audio or video call or a live stream. The wallet is debited minute by minute and can be topped up mid-session without ending it. Chat is end-to-end encrypted with translation as messages arrive, and free kundali, guna milan, panchang and muhurta tools give people a reason to visit before they spend anything.
The Practitioner
- Submits KYC documents before any public listing appears, sets availability windows, works a request queue that sweeps out stale requests on its own, and can pay for a 24 hour visibility boost. Earnings pass through the commission waterfall. Withdrawals go by UPI, bank transfer or PayPal above a minimum you set, with TDS applied and the PAN taken when the request is made.
The Assistant
- A sub-account attached to one practitioner, holding its own permission matrix. A popular astrologer can hand the queue, the chats or the diary to a colleague without sharing the login that receives the earnings. It is the feature that lets one in-demand name grow beyond the hours in a day.
The Finance Desk
- Works from an admin commission ledger with one entry per event. The rate is picked in a fixed order: an active boost override, the practitioner's own rate, then the system default. Beyond that sit TDS reports in CSV and PDF, a queue for approving withdrawals, wallet bonuses granted one at a time or in bulk, and the conversion rate stamped on every transaction row.
The Moderator
- Reads chat and call records, applies block-keyword rules to messages, handles reviews written by both sides of a session, and approves any puja package a practitioner creates before it reaches the catalogue. A marketplace selling guidance instead of goods lives or dies on this surface.
The Operator
- One word carries the profession across more than forty routes and every piece of copy. Swapping it relaunches the same deployment as a tarot, vastu or counselling marketplace, and that is a setting rather than a fork.
One Session, From First Visit to Payout
The server enforces each step rather than the app on the phone, which is why the numbers can be reconciled later.
Free tools earn the visit
- A kundali report in seven sections, guna milan matching, geolocated panchang, a muhurta finder for six purposes and daily, weekly and yearly horoscopes across twelve signs. None of it is charged for. Its job is to draw people who are already curious, not to bring in revenue itself.
A practitioner is chosen
- Filters cover skill, language, price and rating, and only practitioners who have cleared KYC show up publicly. Availability windows say who can be reached right now. Paid boosting decides who appears first, so visibility becomes something you sell instead of an algorithm you cannot steer.
The wallet is funded
- Money comes in one time, through whichever of the twenty gateway configurations suits the market: India, the Gulf, Turkey, Africa, Europe, Latin America or global cards. Each gateway has its own currency, symbol and pair of test and live keys, and each transaction keeps the conversion rate in force that day.
Minutes are metered
- Chat, audio, video and live streams draw down that balance per minute. Media travels over Agora, Zego or 100ms behind a single switch, with Exotel PSTN calling masked numbers when data calling will not work. A low balance prompts a top-up inside the session, so the seeker stays connected.
Or a machine replies
- With no practitioner online, ten AI verticals take the request: counsellor personas, a site-wide master bot, tarot on a 78-card deck, numerology, vastu, vision reading, transit analysis, paid questions, the remedy engine and paid AI remedy reports. Every one has its own price and its own switch, and every one debits the same wallet.
The split is worked out
- Each consumption event adds a row to an append-only ledger together with its commission and tax details. The waterfall looks for a boost override, then the practitioner's own rate, then the default. Live sessions charge by the minute and give the practitioner seventy percent unless you change it.
The practitioner is paid out
- Tax is withheld when the payout is settled, with the PAN recorded on the withdrawal request. Reports leave as CSV or PDF, and money goes out by UPI, bank transfer or PayPal Payouts, in bulk where needed. Payouts are where home-built systems tend to fall over, and practitioners judge an operator on them.
- The same wallet also pays for remedies in a GST-aware checkout, puja packages streamed live, course places and gifts sent mid-stream, each with its own commission treatment.
Why Each Module Is in the Base Build
Every line below is present because a metered marketplace breaks without it, whatever other products happen to list.
Under all of this run 8 scheduler tasks and 6 queue job classes, which take horoscope generation, appointment and puja reminders, commission settlement and notifications out of the web request path.
The Technology Under the Features
Chosen to be ordinary, since whoever operates the platform has to be able to hire for it.
The framework is not where the engineering effort went. The flag store and the ledger are. Typed flags let pricing and packaging change without a release, and a ledger that stores the applied rate lets a month in several currencies close cleanly.
Boundaries we state in writing for your build
Set out before you buy, not after the invoice arrives.
No audit trail yet
- The security review rates audit logging as weak. No log records sign-in events, and none records what an admin did, so operator actions cannot be rebuilt after the fact. For software that handles money this is the first item to schedule, and it is a named gap ahead of launch.
Five CRM modules of twenty-five
- The CRM specification runs to twenty-five modules and five are functional: a Customer 360 timeline, nine computed behavioral tags, health metrics such as lifetime value, retention and churn, a recommendation engine and a central notification engine. Leads, pipelines, tasks and campaigns have no tables, models or routes so far.
Outside accounts belong to you
- You hold MSG91 for OTP, Agora, Zego or 100ms for media, OpenAI or OpenRouter for the AI layer, Exotel for PSTN fallback, FCM and OneSignal for push, Firebase for admin support chat, Google Maps for geocoding, an astrology chart API and a merchant account for each gateway you turn on.
What has been built is real
- The whole pre-launch hardening list, and what closing each item involves, is on the Provider page. Nothing on this page amounts to a security certificate or an uptime guarantee, and none is offered.
Watch a wallet turn into a payout
Fund a wallet, ask an AI vertical a question, then open a human chat and follow each debit into the ledger. In the operator console you can read the commission split and the tax withheld on the same row.
Money comes in once and is spent many times
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Astrotalk , AstroSage , or any other astrology or spiritual consultation service.
White label AI astrology platform describes a category of product, not any one company. Brand names appear elsewhere on this site only to describe the kind of platform being built and the terms buyers search for.
Discuss this scope by message
Tell us your market and audience, and we will respond with a practical read on scope.
team@omnistu.com