Engagement scope - proposed scope
Choosing a White Label Astrology Platform Provider: Four Routes
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
Typical scoping questions
Does the seeker pay before or after the session?
- Before is the answer to want. Billing afterwards means chasing money for advice already given, and that one design choice decides whether collections become a permanent job.
Who owns the source and the ledger?
- Ask for the repository and the transaction records by name. Permission to use software is not ownership, and the difference becomes obvious the first time you want to change how a payout works.
What happens the day you stop paying?
- On a rental, the site and often the seeker list disappear with the invoice. Where you own the platform, you continue with a hosting bill and little else. Get the answer written down.
Can a session survive an empty balance?
- Ask them to show it. If the call ends, the minute, the sale and often the seeker are gone. A top-up inside the session is what turns a lapse into a renewal.
How many levels does commission pass through?
- One rate for everyone cannot express a promotional boost or a negotiated deal with a star practitioner. Ask what it takes to pay a single astrologer differently for a week.
Which gateways verify payments server-side?
- Gateways supported and gateways verified are two separate lists. Ask for the second. Ours is short, and we say so on this page.
Can an operator action be traced afterwards?
- Ask who changed the commission rate last month and expect an answer from a log. Ours cannot give one today, which is why building audit logging heads our own list.
Where is the list of what is not included?
- A quote with no exclusions was never costed. Our list is set out below, and it names the audit trail, the CRM gap and the test hooks so that nothing arrives as a surprise.
The Six-Step Delivery Process
What happens after you say yes, in the order it happens.
Agree the money settings
- Default commission, per-minute rates, a price for each AI vertical, the referral reward and cap, the withdrawal minimum and the TDS percentage. In a metered marketplace these flags are the business model, so they get fixed before any screen is touched. On the same day you can begin applying for the slow external items, such as merchant accounts and store listings.
Harden and prepare the supply side
- The pre-production pass works through the written list: removing the test OTP bypass and test contact hooks and moving live keys out of the audited configuration. Meanwhile operator accounts are tied to team roles and the practitioner KYC queue receives its gating rules.
Follow the money, then hand over
- Your team watches a wallet funded through your live gateway, a metered chat, and the debit appearing in the ledger. Then the session opens in the console to show the commission split and the tax withheld, and a withdrawal is approved. Source, schema and documents change hands at the end.
Support with dates on it
- Day zero carries unusual weight. A commission default or per-minute rate chosen in a hurry is awkward to reopen once practitioners have signed up against it and seekers have loaded their wallets.
Red Flags That Mean Walk Away
Five statements that should end a sales call
- "We invoice after the session." That describes a collections business, not a marketplace. Advice that has been delivered is very hard to bill for, and the seeker has little reason left to pay.
- "The wallet is just a number on the user." A figure that gets added to and subtracted from cannot show where value came from, handle a refund cleanly or reconcile a month. What you need is rows, not a field.
- "You get a licence, the code stays with us." Then every change you want is a favor to ask. A platform you cannot alter is a rented storefront wearing your logo, and its margin levers sit in someone else's product.
- A fixed quote with no named exclusions. Marketplace software has edges, and it also relies on outside accounts. A figure that mentions neither was not built from your requirements.
What We Have Not Done Yet
Six limits, put in front of you before a purchase and not after one.
No audit trail exists
- The security review rates audit logging as weak. Nothing logs sign-in events and nothing logs admin actions, so what an operator did cannot be reconstructed afterwards. Where an operator can change a commission rate or issue a wallet bonus, this is the item we would schedule first, and it opens the list for that reason.
Verified payments cover three gateways
- There are twenty gateway configurations, and server-side payment verification is written today for Tap, Sadad and PhonePe. Those three are the model for building the rest. We say so plainly, so that a count of configurations does not suggest an equal count of verified integrations.
The CRM is five modules of twenty-five
- Five work today: a Customer 360 timeline, nine computed behavioral tags, health metrics for lifetime value, retention and churn, a recommendation engine and a central notification engine. Lead management, pipelines, tasks and campaigns have no tables, models or routes so far.
What exists is real
- End-to-end encrypted chat with participant checks and key versioning, which the security review names the strongest control in the stack. Bound parameters across roughly 500 raw query fragments, leaving a very small injection surface. An append-only wallet ledger with rate snapshots. Role-based access across all 89 admin pages.
- The VAPT reference presents its findings as a pre-production gate, not a clean bill of health, and it is not a certificate. Each hardening item is a configuration change or a code removal measured in developer-hours, and we complete that pass with you. No uptime figure is promised, because uptime rests on your hosting.
Modelled Reference Deployment
An authored illustration, not a client story. It shows how the platform would be configured for a media publisher with an existing audience and no billing system. Every figure describes the build, and none reports a result.
A Publisher Adding Paid Consultations to an Existing Audience
- A regional media house in India whose readers already use free horoscope and panchang pages, and which wants to sell readings and practitioner sessions under its own brand without building a payments and payout system first.
- The situation: steady traffic on free astrology pages, no way to charge for a minute or a reading, and a payout process for any practitioners that would have to be run by hand against commission, tax and refunds.
- The configuration: free kundali and horoscope tools kept open as the entry point, priced AI readings switched on first while the practitioner roster is still being recruited, and human chat and call sessions added behind a section flag once supply is worth showing. Sessions, readings and later purchases all debit one wallet.
- What is already in an initial scope: per-minute metering with mid-session top-up, the three-level commission waterfall, TDS withheld at settlement, twenty gateway configurations with a rate snapshot on every transaction, and KYC gating before any practitioner is listed.
Choose on the answers, not the pitch
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