Astrotalk Clone Development Cost: What a Consultation Marketplace Costs
This page describes proposed scope and cost drivers for a build in this category, quoted in writing per project. Nothing here is a finished product, and no prices or timelines are published for any route.
On a metered marketplace the honest question is not the build number - it is whether the wallet, the commission waterfall and the payout desk exist, or are yours to build.
Four Routes to the Same Platform
What each route typically leaves you owning. The Omnistu column is proposed scope, agreed in writing per project - not an implemented product. Each route is quoted in writing; no dollar figures are published here.
| Route | What you end up owning | What to ask |
|---|---|---|
| Generic consultation script | Listings and a chat box. The wallet, the commission waterfall and the payout desk are what is usually missing. | Ask whether per-minute metering, an append-only ledger and settlement withholding exist, or are yours to build. |
| Freelance team | The screens you specified, and a payout process that can end up running on a spreadsheet. | Ask how the commission split, tax withholding and withdrawal approval are implemented before you commit. |
| Omnistu proposed build | Proposed scope: the metering, ledger and settlement engine included, deployed to infrastructure you control. | Scope agreed in writing before work starts, with the named limitations on this page. |
| Custom agency build | A bespoke platform scoped to your specification, with a longer path to the first billed minute. | Ask for a quoted milestone plan in writing, and whether the billing layer is scoped at the start. |
| Enterprise programme | For publishers, multi-market operators, franchises and white-label resellers. | Quoted against the final scope rather than listed here. |
The wallet is the business model on a metered marketplace. Whichever route you choose, price the billing layer first - the chat box is the easy part.
What the Proposed Scope Includes
Ownership transfers in full, which matters here because the flag store and the commission rules are the numbers your margin depends on. All of it is proposed scope from the supplied specification inventory - this preview does not implement or verify any of it.
Application core
Proposed: a Laravel application on MySQL carrying 170 database tables with incremental migrations, 179 controllers and 133 models, 8 scheduler tasks and 6 queue job classes.
Four surfaces
Proposed: the customer portal and the separate astrologer portal across roughly 191 website routes, a JSON API of roughly 363 routes under a JWT guard serving both mobile apps, and the operations back office across roughly 552 admin routes.
Operations back office
Proposed: 89 admin menu pages across 151 Blade views, team roles with per-page access control, 298 system flags in 47 groups with typed inputs, plus data monitoring and message moderation tools.
The money engine
Proposed: per-minute chat, call and live billing, a dual-currency wallet with an append-only ledger, the commission waterfall with tax withholding, twenty gateway configurations, and withdrawals over UPI, bank transfer and PayPal Payouts.
The astrology engines
Proposed: kundali, guna milan matching, panchang and muhurta engines, daily, weekly and yearly horoscope generation, ten metered AI verticals behind one provider interface, and the remedy engine with paid downloadable AI reports.
Commerce, ritual and learning
Proposed: the AstroMall catalog with tax-aware checkout, cart, address book and coupons, puja packages delivered over a live broadcast, courses with chapters and completion tracking, and a gift catalog carrying commission on send.
Mobile and documentation
Proposed: both Android builds - the customer app and the separate astrologer app, each with its own store listing and package name - 143 seeded languages with ten active app-side, five design sets with dark mode, and eleven documentation files including the schema, ERD, API collection and security review.
Proposed commercial terms
No runtime licence, nothing counted per seat, and no cut of your commissions - proposed commercial terms, confirmed in your written quote. We will walk the repository, the schema and the documentation set with your technical lead before anything is signed.
What Moves the Number
The base scope is fixed in the written quote. These are the things that genuinely sit outside it.
How many gateways you run
One rail is a straightforward setup. Several rails across several currencies is more configuration, more test and live key pairs and more merchant accounts. The supplied specification records server-side payment verification on three gateways - Tap, Sadad and PhonePe - as the template the rest are built against; this preview does not implement or verify any of them, so additional verified rails are scoped work.
The pre-launch hardening pass
The security review supplied with the specification records a test OTP bypass and test contact hooks in the codebase, to be removed before deployment, and no audit trail yet, which needs building. Removal, the keys move and the logging build are required scope, quoted before work starts - not work already performed.
Real-time and AI providers
Agora, Zego or 100ms for calls and live, Exotel for the PSTN fallback, and OpenAI or OpenRouter behind the ten AI verticals - proposed external dependencies, not verified integrations. Wiring your accounts, testing the media path and tuning the AI prompts is the work.
Reported inventory: five of twenty-five CRM modules
The supplied specification records functional implementations for five of twenty-five specified CRM modules. If lead management, sales pipelines, tasks or campaigns matter to your operation, those are built rather than configured, and each is scoped and quoted individually before anything starts.
Language and market activation
143 languages are seeded with ten active on the app side and five on web, per the specification inventory. Activating more means translation review rather than development, but it is real effort and it lands on your side unless you ask us to carry it.
Store publishing for two apps
There are two Android builds here rather than one, each with its own listing and package name. Developer accounts, signing and review are yours, and publishing is quoted separately.
Anything beyond the base is quoted after scoping. You approve a number before work starts rather than watching one accumulate.
The Path to Live, in Order
What we do, in the order we do it. The sequence and its exit criteria are agreed in writing per project; no fixed day counts are published.
Step 1 - Set the commercial numbers
We confirm your commission default, the per-minute rates, the feature price for each AI vertical, the referral reward and its cap, the withdrawal minimum and the withholding percentage. On a metered marketplace those flags are the business model, so they come before anything visual.
Step 2 - Branding, vocabulary and locales
Name, logo and colour scheme across both portals, the back office and both Android builds, a design set with dark mode configured, the profession vocabulary set if you are launching as something other than astrology, and your language packs activated from the seeded set.
Step 3 - Deploy and connect your accounts
The application and its database go onto infrastructure you control. Your gateway keys, MSG91 for OTP, the RTC provider for calls and live, the AI provider key, Exotel if you want the PSTN fallback, Firebase for push and admin support chat, and your storage provider - all connected with credentials you hold.
Step 4 - Hardening and the supply side
The pre-production security pass runs against the named list from the supplied security review: test OTP bypass and test contact hooks removed, live keys moved out of the flagged configuration - required scope, quoted before work starts, not work already performed. Alongside it, operator accounts are created against team roles and the astrologer KYC queue is configured with its gating rules.
Step 5 - Walkthrough and handover
We run the money loop end to end in front of your team: recharge a wallet through your live gateway, run a metered chat and watch the deduction land in the ledger, open the session in the console to see the commission split and the tax withheld, then approve a withdrawal. Source, schema and documentation transfer.
Step 6 - The support window
A defined support window - launch guidance, priority bug fixes and updates - agreed in writing per project. Additional verified gateways, the audit-logging build and store publishing usually run inside this window on their own scoped schedule.
What lengthens a launch here is almost always external: a merchant account per gateway, the OTP and RTC accounts, an AI provider key, and enough practitioner supply that a customer who arrives actually gets an answer.
How to Judge a From-Scratch Estimate
We do not publish a dollar figure or a duration for a from-scratch build, because any single number would be assumptions about your team, your region and your scope discipline presented back to you as a finding. Judge any estimate on these instead:
Ask for a quoted milestone plan in writing
A serious provider commits to a sequence with exit criteria, not a date pulled from a sales deck. Ask what happens when a milestone slips, and what the slip costs.
Ask whether the billing layer is scoped at the start
A dual-currency wallet, an append-only ledger with rate snapshots, a three-level commission waterfall, withholding at settlement and twenty gateway configurations are each unglamorous, mandatory and slow. A chart or chat screen is the easy part, and it is the part every estimate focuses on.
Ask what is configuration and what is build
Five of twenty-five specified CRM modules have functional implementations in the supplied specification; the rest are build work. The same question applies to gateways and languages. A quote that prices build work as configuration is a quote that will move.
Ask who runs the payout desk
On a metered marketplace the payout process is the part that breaks first under real volume. Ask to see it run - a withdrawal from request to approval to settlement - before you compare anything else.
What a Written Quote Commits To
Proposed commercial terms, confirmed in your written quote.
The scope is agreed in writing
What is quoted is what is delivered across the customer experience, the astrologer portal, the operator console and the two Android builds. There is no discovery phase that discovers the quote was optimistic.
No cut of your commissions
Proposed: we take nothing from consultation revenue, AI vertical sales, the remedy marketplace, puja bookings, courses or gifting. The commission waterfall, the feature prices and the boost rate are yours to set and yours to keep.
No per-practitioner fee
Proposed: your five hundredth astrologer costs you nothing extra from us, which on a marketplace whose growth is supply-side is exactly the wrong thing to be charged for.
The limitations are named first
Payment verification recorded at three of twenty gateways, the absent audit trail, the CRM at five of twenty-five modules and the test hooks recorded by the supplied security review are all stated on this page. Each is scoped and quoted before work starts.
External Costs Most Quotes Leave Out
None of these are ours to charge. They are yours to budget, and on a metered marketplace two of them scale with your success.
Real-time media minutes
Agora, Zego and 100ms bill per minute, so your RTC bill scales with exactly the thing you are monetizing. Model it against your commission rate before you set per-minute pricing, because a thin margin on a long call can invert.
AI inference
Ten verticals metered against the wallet also cost you per call at the provider. The pricing screen lets you set what the customer pays; what you pay sits with OpenAI or OpenRouter and moves with model choice and prompt length.
Practitioner acquisition
Supply is the constraint in this category, not demand. Recruiting, verifying and retaining astrologers is an ongoing cost with its own team, and no amount of software substitutes for having someone available when a customer arrives at three in the morning.
OTP and messaging
MSG91 for one-time passwords, plus FCM and OneSignal for push. Individually small per message, and material once signups are running, since every registration and every session notification passes through them.
Gateway fees per rail
Twenty configurations means potentially twenty merchant relationships, each with its own rate, settlement timeline and compliance paperwork. Recharges are the money-in event, so settlement timing affects your working capital directly.
Call recording storage
Recording to configured storage is a feature you will want and a bill that grows monotonically. Storage is selectable across local, AWS, GCS and DigitalOcean, and a retention policy is worth deciding before the first month rather than after the invoice.
The first two are the ones that decide whether your per-minute pricing works. Both are marginal costs on the exact transaction you are billing, so they belong in the rate calculation rather than in a general infrastructure line.
Frequently Asked Questions
What does the written quote cover?
Proposed scope: the Laravel application on MySQL with its 170 tables, both web portals, the JSON API, the 89 page back office, the wallet and commission engine, the astrology and AI engines, the commerce, ritual and learning surfaces, and both Android builds. What sits outside it is named on this page: additional verified gateways, the hardening pass, provider wiring, the unbuilt CRM modules, language activation and store publishing.
Why is there no from-scratch dollar figure or duration here?
Because any single number would be assumptions about your team, your region and your scope discipline, presented back to you as a finding. Judge a from-scratch estimate on the buyer criteria above: a quoted milestone plan in writing, the billing layer scoped at the start, and build work priced as build work.
Do you take a percentage of consultation revenue?
Proposed commercial terms: no revenue share and no per-practitioner fee. Consultation commissions, AI vertical sales, the remedy marketplace, puja bookings, course sales and gifting are all yours in full, confirmed in your written quote.
What does the hardening pass involve?
It is scoped against the named list from the supplied security review rather than priced as a block: removing the test OTP bypass and test contact hooks, moving live keys out of the flagged configuration, and building the missing audit logging. Each item is scoped, tested and quoted before work starts.
What does adding a verified payment gateway involve?
It is scoped per gateway, because the work is shaped by that provider's API rather than by ours. The supplied specification records server-side verification on Tap, Sadad and PhonePe as the pattern the rest follow; this preview does not implement or verify any of them. Tell us which rails you intend to run and we will quote each one before starting.
What usually lengthens a launch?
External accounts, not the build: a merchant account per gateway, an MSG91 account for OTP, an RTC account with Agora, Zego or 100ms, an AI provider key, and a Firebase project if push and admin support chat must work on day one. Practitioner supply is the other real constraint, and it is not a software one.
Independence and third-party names
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Astrotalk. "Astrotalk clone" is used descriptively - it is how the software industry refers to building a platform with similar functionality, and how buyers search for it. Astrotalk and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
Discuss your scope by message
Tell us which paid surfaces you would switch on at launch - metered consultations, AI verticals, the remedy marketplace - and which markets you are launching in. We reply by email with a scoped proposal - no calls required, no phone numbers collected.
