Features
Everything it does, one card at a time.
140features · 10 groups
For advocates and firms. Open any card for the problem it solves, how it works and the numbers behind it.
Bando asks
What slows your practice down?
140 features shown
01 / 10
Workspace and court day
The day before you ask for it: the board, the diary, the inbox and what changed in the law overnight.
18 features
02 / 10
Cases and the Case room
The matter is the unit. Everything you do attaches to it and lands on its timeline.
15 features
03 / 10
Court data and eCourts
Public court records read for you from official sources: case status, cause lists, tribunals and orders.
7 features
04 / 10
Drafting Studio
Formal parts by code, prose by AI, and checks that stand between a draft and the export.
18 features
05 / 10
Research and Munshi AI
Search everything at once. Ask Munshi and get answers that cite the page, or say they cannot.
25 features
06 / 10
Record room and case prep
Read thousands of pages once, remember them, and prepare the case from what they actually say.
12 features
07 / 10
Clients and portal
From the first enquiry to the engagement and every update after, with consent on file.
11 features
08 / 10
Billing and money
Time captured from the day, GST invoices, payment links and advances, in rupees.
16 features
09 / 10
Firm and practice
Members and roles, firm reports, the firm’s own files, and the language you work in.
10 features
10 / 10
Security and privacy
Each firm sealed off in code, a person in charge of every send, and everything exportable.
8 features
A day in court
Which features work for you, hour by hour.
One ordinary day. Tap any feature to open it.
07:00
07:00 → 22:00
07:00
The list has already been read.
Today's cause lists are matched to your cases before chai. The board shows court, item and who is appearing.
07:30
What changed in the law, overnight.
The digest names the judgments and circulars that touch your matters, and why.
10:30
In the corridor, no signal.
The live board nudges you as your item nears. The outcome goes in offline and syncs later.
13:00
An order comes in.
It is read, its directions become proposals, and the deadline is counted from the rule. You accept.
15:30
Back in chambers, the draft.
Formal parts are already right. Munshi finds cases for and against; the checks hold the export.
17:30
The client hears, after you approve.
The next date goes out on its own if you allow it. The update about the order waits for your tap.
19:00
Tomorrow, and the bill.
Tomorrow's lists are read. The day's work is suggested as time, ready for the invoice.
22:00
Munshi reads the record while you sleep.
A Brief run works through the bundle in the background and pushes you when the submissions are ready.