Pricing
A free plan that is the whole workspace at a daily allowance, and paid plans that add the diary, the file system and the firm’s shared precedent bank.
₹0forever
The whole workspace at a metered daily allowance. Not a crippled demo — the same grounding gate, the same export.
₹999per month
The daily workspace with the practice diary: hearings, limitation, cause lists, time capture and client invoicing.
₹799per seat / month
Everything in Advocate, plus the shared precedent bank — the chamber’s own drafts become what the next draft is built from.
Pricing on request
Legosphere Factory as an engine your systems call, with cross-jurisdiction conversion and the security review an enterprise procurement actually runs.
Prices shown are indicative while the products are in build. Anything agreed on a walkthrough is what applies to you.
How billing works
Usage is metered from what the models actually returned, not from counting words in a text box. The number in your dashboard reconciles against your usage log.
When an allowance runs out you get a clear state and an upgrade path, never a silent failure or a half-finished draft.
Legosphere billing (what you pay us) and client billing (what you invoice your client) are separate systems that never touch each other.
Questions
The ones that decide whether this software is safe to put in front of a client's matter.
Two products built on one engine. Legosphere Drafter is the daily workspace for an advocate — drafting, grounded case-law research, plain-language editing, export, and the practice diary. Legosphere Factory is the document engine underneath it: a matter file system, a generation engine that drafts from your own precedents, and a cross-jurisdiction conversion engine. Factory is also sold on its own to teams who want to call it from their own systems.
If you are an advocate or a chamber doing litigation and contract work, you want Drafter — Factory runs underneath it and you never have to think about it. If you are an in-house or engineering team that wants document generation or cross-jurisdiction conversion inside your own product or workflow, you want Factory directly.
Sixteen document types today across three drafting paths. The court path covers writ petition, PIL, civil suit, criminal complaint, bail application and vakalatnama, with the structure a court expects — synopsis and list of dates, index, memo of parties, continuous paragraph numbering, lettered grounds, prayer, affidavit and verification. The contract path covers nine agreement types, and there is a notice path. You can also upload any document you have settled before and get a new one in that exact shape.
Yes. Court formats, the Limitation Act 1963, cause lists and Indian case-number forms, the statutory corpus a practice here actually touches, and rupee-exact billing. The cross-jurisdiction conversion engine in Factory extends beyond India — US, EU, UK and China — but the daily workspace is designed around Indian litigation practice rather than adapted to it after the fact.
Practising lawyers, working with engineers — and the specification came from the legal side, not the other way round. You can check that claim rather than take it: the limitation engine refuses to give you a bare date, cause-list matching is exact-or-normalised rather than fuzzy, the court path knows what a synopsis and list of dates is, and the software will not decide your GST position. Every one of those is a decision that costs something technically and only makes sense to someone who has filed things.
That is the assumption the whole product is built on. Nothing is filed by the software, nothing is sent anywhere, and nothing loses its watermark until a named advocate approves it. Think of it as the most thorough junior you have ever had, not as a replacement for your judgment.
Get in touch
No chatbot, no ticket queue. Tell us what you are trying to do and someone who has worked on the software will reply.
info@legosphere.com