Start your own cricket betting panel in 7 days

What a panel actually is

The four tiers in one table

What actually changes as you go up a tier

Each tier is the same software with a wider view. A DL sees its own players. An MDL sees its DLs and can move points between them. An SMDL sees MDLs. The Admin sees the entire tree and is the only one who sets the share split and the settlement schedule.

That is why the price jumps by tier: you are not buying more software, you are buying more of the book.

What a build includes (the honest list)

• Admin + master + agent hierarchy with share % per user
• UPI deposits with UTR duplicate checking
• Withdrawal queue with per-panel limits and settlement schedule
• Promotions, notices and marquee text you control
• Your domain, your logo, your brand — the code is yours
• Mobile-first pages, multi-language, no app-store dependency
• 7-day delivery including setup and handover

What it does not include

Odds or a sports feed. Those are licence and integration decisions you make separately — an API provider, a book, or your own traders. Anyone who tells you a panel includes a live odds feed for free is selling you a demo, not a platform.

We will tell you which feed providers are currently reliable and which have burned operators, but we do not resell feeds.

How the money works, in one example

You buy 1,00,000 points at a 75/25 split. Your payable is 75% of the points value — ₹75,000 — and the 25% is the operator's share of the book. Your agents buy points from you at your rate, and you keep the difference between your rate and theirs.

The panel shows every one of those movements: what came in, what went out, what is pending, and who approved it.

How to start this week

• Decide the tier you actually need — most first-time operators need an MDL, not an Admin panel.
• Pick a domain and a brand name you can keep (we build on yours, not a subdomain of ours).
• Get the deposit flow tested with a real ₹100 transaction before you take a single customer.
• Write your rate card before your first agent asks. Hesitating on price is what loses agents.

Who this is for — and who it is not

It fits you if you already have agents, a rate card in your head and a phone that does not stop ringing. You need a panel because the spreadsheet has become the bottleneck, or because you are paying someone else a cut of your own book.

It does not fit you if you are looking for the software to bring the customers. A panel is infrastructure. It makes an existing operation faster and more trustworthy; it does not create demand, odds or capital.

What happens after you enquire

• You tell us the tier and the number of agents — that decides the scope, not the price list.
• You get a written rate card and a delivery date the same day.
• You pay 50%. The slot is booked, the build starts.
• Day 3: a staging link on our server, with your brand, so you can click through it.
• Day 6: walkthrough with your own numbers and your own rate card.
• Day 7: handover — your domain, your hosting, the source code, and a backup you keep.

The three objections we hear most

"What if the panel goes down?" — Ask any provider this and listen for a specific answer: who is paged, in what time, and what happens to deposits in flight. Ours is written into the handover document, not promised verbally.

"What if my agents do not like it?" — Agents care about three things: deposits landing in seconds, withdrawals arriving on the promised day, and being able to see their own numbers. Everything else is decoration.

"Can you make it look like [competitor]?" — We can match structure and flow. We will not copy another operator's brand or content; that is how domains get taken down.

What it costs to run, month by month

The software line is the smallest line on that table. Anyone budgeting only for the build is budgeting for the first month only.

The deposit flow, step by step

The last line is what separates a real panel from a spreadsheet. A rejection on one phone must never free the same reference for another phone; that is how one screenshot gets used twice.

• The player asks the agent for points; the agent sends a UPI request from the panel.
• The player pays and submits the UTR - the panel checks it against every reference already used.
• The deposit lands in the agent's queue with the amount, the reference and a timestamp.
• The agent approves; points appear on the player's line instantly.
• If the reference is a duplicate, the panel blocks it and flags the row for the admin - per phone number, not globally.

What happens when a player wins big

The points move, the balance goes negative on the agent's line, and the agent tops up or settles with you on the agreed day. None of that should require a phone call - if the panel cannot show the movement, the argument is already lost.

Set per-player and per-market limits before the first big fixture. A book that accepts everything from everyone in one city on one team is not a book, it is a bet.

Mistakes we see in the first month

• Taking deposits before testing a withdrawal end to end.
• Recruiting ten agents before the rate card exists in writing.
• Mixing personal money with the float - separate account, day one.
• One admin login shared by three people.
• Settling late once. Everything else is recoverable; that one is not.

Where the software ends

A panel manages points, approvals and records. It does not decide whether your operation is legal where you are, provide odds, or protect you from your own exposure. Those are operator decisions, and a serious provider says so plainly instead of selling comfort.

What it must do is let you prove what happened: who approved what, when, and from where. In this business the audit trail is the only thing that ends an argument.

Questions people actually ask