PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu
01 / Development company

Astrotalk Clone Development Company: Who Should Build Your Marketplace

This page describes proposed scope and due-diligence criteria for a build in this category, agreed in writing per project. Nothing here is a finished product, and no client engagement for this platform is claimed.

What a provider says about the ledger tells you more than any portfolio. Put the nine questions below to us and to whoever else is bidding.

Build scopeConfirm servicesDefine the features and exclusions
Delivery planAgree milestonesNo fixed launch duration implied
Source rightsWritten termsCheck licences and handover
OperationsTest before launchAgree acceptance and support
02 / Compare providers

Freelance Team vs the Proposed Omnistu Build

Where each route tends to fail once real money moves through it. The middle column is proposed scope, agreed in writing per project - not an implemented product. No prices or timelines are published for any route; each is quoted in writing.

What mattersFreelance team - what to askOmnistu proposed build
The walletAsk whether the wallet is rows in a ledger or a balance column, incrementedDual-currency, append-only ledger, rate snapshot per row
CommissionAsk whether commission is one percentage, edited in codeBoost override, then per-astrologer rate, then default
Tax on payoutsAsk whether withholding is applied at settlement or worked out in a spreadsheet each quarterWithheld at settlement, PAN captured, CSV and PDF
Changing a priceAsk whether a price change is a release, and a developerOne of 298 typed flags in 47 groups
Overnight demandAsk what answers a customer at three in the morningTen wallet-metered AI verticals
A second marketAsk whether a second currency means reopening the payments layerTwenty gateway configurations, currency per gateway
Stated limitationsAsk what is on their pre-launch list - an empty one means they have not lookedPublished before purchase, the awkward ones included
Price behaviourAsk whether the number can move after you are committedA fixed quote for agreed scope, in writing, before work starts

Good agencies exist and will build you a competent platform. What the table measures is whether the billing layer was designed in from the start or added after the first payout run went wrong.

03 / Due diligence

Questions Worth Asking Any Provider

Nine questions. All nine get answered on the first call, the uncomfortable ones included.

When exactly is a minute billed?

Before the service or after it. Billing after means chasing payment for advice already delivered, and that single design decision decides whether you have a collections problem forever.

What happens when the balance runs out mid-call?

Ask them to demonstrate it. If the session simply ends, you lose the minute, the sale and usually the customer. Topping up inside the session is the difference between a lapse and a renewal.

How many levels does commission resolve through?

One global percentage cannot express a promotional boost or a star practitioner's negotiated rate. Ask what happens when you want to pay one astrologer differently for one week.

Is the exchange rate stored on the transaction?

If a multi-currency month is reconciled against today's rate, the numbers will not match what happened. Ask to see a rate snapshot on a ledger row rather than a currency code.

Where is withholding applied?

At settlement, or in a spreadsheet afterwards. Ask whether PAN is captured at the withdrawal request and whether the tax report exports without somebody assembling it.

Which gateways are verified server-side?

A list of supported gateways and a list of gateways with server-side verification are different lists. The supplied specification records three of twenty, and we say so.

Can you reconstruct an operator action?

Ask who changed the commission rate last month and expect them to show you. The supplied specification records no audit trail for this, which is why it is the first item on our own list.

How much can you change without a developer?

Feature prices, commission defaults, section toggles and referral caps are the numbers your margin depends on. If any of them needs a release, your pricing will effectively never change.

What is on your pre-launch list?

Any provider whose list is empty either has not looked or is not telling you. Ours names the absent audit trail and the test hooks recorded by the security review supplied with the specification, and it sits further down this page.

04 / Process

The Development Process, 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

Commission default, per-minute rates, the feature price for each AI vertical, the referral reward and 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. Gateway keys, MSG91 for OTP, your 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 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 for both apps usually run inside this window on their own scoped schedule.

Step one carries more weight here than on most products. A commission default or a per-minute rate set casually is awkward to revisit once practitioners have signed up against it and customers have recharged behind it.

05 / Red flags

Red Flags That Mean Walk Away

Five answers that should end the conversation.

"We bill after the session"

Then you have built a collections business rather than a marketplace. Advice already delivered is the hardest thing in the world to invoice for, and the customer has no reason left to pay.

"The wallet is a balance on the user"

A number that gets incremented and decremented cannot tell you where value came from, cannot support a refund cleanly, and cannot reconcile a month. You need rows, not a field.

"Commission is a setting in the config file"

That is one rate for everyone forever, or a deployment every time you negotiate with a practitioner. Neither survives a real supply side.

"We support twenty payment gateways"

Ask how many are verified server-side. Supported and verified are different claims, and the gap between them is where fraudulent recharges live. The supplied specification records three of twenty, and we say so.

An estimate with no named exclusions

Software has edges, and marketplace software has provider accounts on top of them. A number presented without either was never costed properly.

Where we sit on this list

We are on the uncomfortable side of our own fourth flag, which is exactly why it is written here in the same words we would use on a call rather than left for you to discover.

06 / Non-negotiables

What a Metered Marketplace Has to Get Right

The parts that are cheap to design in and expensive to retrofit. Each is proposed scope, agreed in writing per project.

Metering before service

A prepaid wallet debited per minute across chat, call and live, with the balance checked before the session starts rather than invoiced after it ends. This single decision removes collections from the business model entirely, and it cannot be added later without changing everything downstream of it.

An append-only ledger

A row per consumption event carrying commission context, tax context, offer and free-minute usage, and a conversion-rate snapshot. The ledger is the only artifact that can explain a disputed month.

Commission that resolves in layers

A boost-active override first, then the per-astrologer rate, then the system default, with an admin commission ledger written per event. Real supply sides need promotional rates and negotiated rates simultaneously, and one global percentage cannot express either.

Withholding at settlement

Tax applied when the payout is computed rather than reconstructed quarterly, with PAN captured at the withdrawal request and reports exporting to CSV and PDF. Practitioners judge a platform on payout cleanliness more than on any feature.

A control plane, not a codebase

298 typed flags across 47 groups covering section toggles, feature pricing, commission defaults, offers, referral caps, withdrawal minimums and provider selection. If changing a price needs a release, your pricing will effectively never change.

Something that answers at 3 a.m.

Ten wallet-metered AI verticals covering the hours when no practitioner is online, each priced and toggled independently behind one provider switch. Unanswered intent is not deferred demand, it is lost demand.

07 / Platform trust

What Has Not Been Done Yet

Six items from the supplied specification, stated before a purchase rather than after one. This preview does not implement or verify any of them; the required build and security work is scoped, tested and quoted with you.

Reported gap: no audit trail

The security review supplied with the specification records no authentication-event log and no admin-action log, so operator actions are not reconstructable after the fact. On a platform where an operator can change a commission rate or issue a wallet bonus, this is the item we would schedule first.

Reported inventory: three of twenty gateways verified

The supplied specification records twenty gateway configurations with server-side payment verification on three - Tap, Sadad and PhonePe - as the template the rest are built against. We would rather write that plainly than let a count of configurations imply the same count of verified integrations.

Reported gap: test hooks recorded in the codebase

The security review supplied with the specification records a test OTP bypass and test contact hooks in the codebase. Removal and testing are required scope, quoted before work starts - not work already performed. You should hear it from us rather than find it.

Reported inventory: five of twenty-five CRM modules

Five have functional implementations per the specification: a Customer 360 timeline, nine computed behavioural tags, health metrics covering lifetime value, retention and churn, a recommendation engine and a centralized notification engine. Lead management, sales pipelines, tasks and campaigns have no tables, models or routes yet.

Every provider account is yours

Recorded in the supplied specification: MSG91 for OTP, Agora, Zego or 100ms for real-time 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 per gateway - proposed external dependencies, not verified integrations.

Proposed base scope

The supplied specification records end-to-end encrypted chat with participant authorization and key versioning, parameterized bindings across roughly 500 raw query fragments, an append-only wallet ledger with conversion-rate snapshots, and role-based access across the admin pages - all as proposed scope this preview does not implement or verify.

The supplied security review frames its findings as a pre-production gate rather than a clean bill of health. Every item on the hardening list is a configuration change or a code removal rather than an architectural rework, and each is scoped and quoted with you.

08 / Reference model

Modelled Reference Configuration

An authored scenario showing how the proposed platform is configured for an operator converting free-tool traffic into prepaid balance. It is not a client engagement, and no figures in it are reported outcomes.

Metered astrology consultation marketplace

What the situation makes hard: free astrology tools drawing traffic that never converts into a paid session; practitioner payouts reconciled by hand against commission, tax and refunds; and consultation demand arriving at three in the morning with no human supply available to answer it.

What an operator would want: every minute metered against a prepaid wallet rather than billed after the fact; practitioner earnings settling through one commission waterfall with withholding applied at settlement; the overnight hours covered by wallet-metered AI instead of idle capacity.

Proposed configuration

Per-minute metering across chat, call and live with mid-session top-up; a commission waterfall of boost override, then per-astrologer rate, then system default; twenty gateway configurations with a conversion-rate snapshot per transaction; and ten wallet-metered AI verticals answering when no practitioner is online.

We would rather show how the proposed platform configures for a market than borrow credibility from a deployment that has not happened.

09 / FAQ

Frequently Asked Questions

Is the platform secure, and what needs doing before launch?

We would rather answer plainly than reassuringly. The supplied specification records real strengths - end-to-end encrypted chat with key versioning, parameterized bindings, an append-only wallet ledger, role-based access across the admin pages - and an equally real pre-launch list: test OTP bypass and test contact hooks to remove, live keys to move, and audit logging to build. This preview does not implement or verify any of it; the work is scoped, tested and quoted with you.

Why publish your own gaps?

Because a security reviewer will find them, and finding them after payment is worse for both of us. It also means the platform you plan around is the real one rather than the marketing one.

What exactly do I own at the end?

Proposed handover: the Laravel application, the customer web portal, the astrologer portal, the JSON API, the admin back office, the 170 table schema with its migrations, and both Android builds with their own store listings and package names, plus the documentation suite - schema reference, entity relationship document, API collection, developer and security handbooks and the security review. No runtime licence, nothing per seat, no revenue share - proposed commercial terms, confirmed in your written quote.

Will you build the audit logging for us?

Yes, as scoped work quoted before it starts, and we would schedule it early rather than late. It is ordinary engineering rather than a rearchitecture: authentication events and admin actions written to their own tables with the actor, the target and the before and after values.

Have you deployed this for a live operator?

Not for this platform, and we say so plainly. The reference configuration on this page is labelled modelled because it is authored rather than reported. We would rather walk you through the proposed scope in detail than imply more than we can evidence.

Can we relaunch this as something other than astrology?

Yes, and it is a deliberate design choice. The profession vocabulary is a single token reaching more than forty routes, so the same deployment can present as a tarot, counselling or coaching marketplace without a fork. The metering, wallet, commission and payout engine underneath does not care what the practitioner is called.

11 / Next step

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.

PREVIEW ONLY - nothing you enter is submitted to or stored by Omnistu. The compose button tries to copy your scope text and open your own email app; if the copy does not work, the text appears below the button so you can copy it yourself. Nothing is sent until you press send in your own email app.
Email the team instead