Baskets
Multi-leg ideas sent as one instruction, with the document generated and sent automatically on submit.
You decide the call. Everything after that — who is entitled to it, which channels it goes out on, what happens when you revise the stoploss, and the proof it arrived — is the platform's problem, not yours.
4,812 clients entitled Longest channel 2.8s 0 silent failures
No step here is a diagram. Each one is a screen, and each one leaves a record.
You set your house style once, per segment: how wide the entry range should be, the stoploss, the three targets, and how long a position is meant to be held. After that every ticket arrives already filled in and your job is to check it, not to type it.
Equity, stock F&O, index options and commodities are kept distinct at every gate, and entitlement comes from what the client actually bought. Nobody is in a group they should have left, and nobody misses a call they paid for.
Your app, your client portal, your WhatsApp number, your Telegram channel, your mailbox — and your API if you have somewhere else it needs to be. Your five hundredth client gets it in the same second as your first.
Stoploss moved, targets revised, a note of your own, an exit — each one goes to exactly the people who got the original, on the same channels, and is recorded against the same call. Nobody is left holding a version you have since changed.
A delivery record per message, per channel, with read receipts where the channel offers them. When a client says he never got it, you do not argue — you open the log. Every version of what you sent is retained.
The things a desk needs once it is publishing every day.
Multi-leg ideas sent as one instruction, with the document generated and sent automatically on submit.
Build a multi-leg structure leg by leg — spreads, straddles, strangles, calendars — and see the margin the whole structure needs before you commit to it.
An eight-sheet workbook showing what following your calls would have produced.
Realised profit and loss by month, quarter, half and financial year, as a spreadsheet and as an investor-grade PDF you can hand over.
If a delivery cannot be completed for any reason, a terminal record with the exact reason is written. Your client is never left with silence and neither are you.
Post your calls in over the API with a key, a secret and a code that rotates daily. Keep everything you have built and use the platform for delivery, records and compliance.
Because the question always comes later, not at the time.
Every version of every call, retained and retrievable.
Your company and SEBI registration number on every outgoing message.
Which channel carried it, when it was accepted, and what came back.
The audience is derived from plans, so it can be explained afterwards.
No, and we never will. You are the Research Analyst. We are the infrastructure underneath. Nothing is written, suggested or published by the platform on its own.
Every message has its own delivery record, per channel, with read receipts where the channel provides them. That log is the answer to the most common dispute an RA has.
The revision goes to exactly the people who received the original, on the same channels, recorded against the same call. There is no second list to maintain.
Yes. Post into the platform over the API and use it for delivery, entitlement, records and compliance. You are not throwing anything away, and you can stop posting any day.
9% of what the client pays you, stepping down to 5% as your research sales grow, or ₹75 for every 30 days of the plan — whichever is higher. Nothing is due until a client pays you.
All of them on one checkout, one invoice and one set of clients.
Fifteen minutes, your logo already on it. If it is not obvious in fifteen minutes, it is not for you.
A walkthrough takes about thirty minutes: onboarding and a signed agreement, a live publish, a portfolio rebalance, and the records behind them — with your first month costed on the spot.