A legal team that
fits in your laptop.

Counterparty paper in.
Redline, memory, audit, specialist out.

The six moves sit on eight capabilities, each one live and wired. This is the full surface a counsel touches, not a demo path.

1. Contract intelligence

   Counterparty paper (MSA, NDA, SLA, employment offer, scanned bundle) is read across eleven section buckets: parties, term, liability, indemnity, IP, payment, termination, and the rest. Each clause is tagged, risk-scored, and traced back to the page it came from. India-specific gaps surface by name: a missing data-protection clause, an absent GST or stamp-duty treatment, no seat of arbitration, uncapped liability, an auto-renewal that renews against the reader.

   ProofEvery risk carries a code and the clause it fires on. Parties are de-duplicated so one counterparty is one party, not three near-spellings.

2. Court-format drafting

   Bail applications, legal notices, and petitions come out in the form an Indian court accepts: the heading, MOST RESPECTFULLY SHOWETH, numbered grounds, the prayer, the verification, the annexure list. The reader gets two copies of every draft: the court-filing copy and a review copy that carries a KLZ authenticity ID keyed to the draft.

   ProofThe draft is audited against the facts the advocate supplied before it is shown. Anything it asserts that the facts do not support is flagged, not buried.

3. Document reasoning that audits itself

   A scanned FIR, a judgment, a chargesheet, a bilingual Hindi and English bundle is read in full, not skimmed at the top. The reader decides what the document actually is before it extracts anything, so a policy report is never mistaken for a first information report, and a document title is never mistaken for a judge. Every person, section, date, and citation it returns must trace to the source text; whatever cannot is dropped and listed.

   ProofThe response carries a grounding audit: what was checked, what was kept, and what was rejected, with the reason. Nothing pre-baked, nothing invented.

4. Citations with verification

   Case-law search runs as a pipeline: read the intent, break the question into sub-queries, retrieve, then rank. Authority is drawn from a curated corpus rather than generated, and any citation that reaches a draft is checked before it is shown. An unverified or repealed reference is marked as such, never dressed up as good law.

   ProofA citation is presented as verified only when it resolves against the corpus. Repealed statute quoted for current conduct is flagged.

5. BNS, BNSS, and BSA transition

   The 2023 criminal-law overhaul is native. Old Penal Code sections map to their Bharatiya Nyaya Sanhita equivalents, and the reader applies the new codes to conduct after 1 July 2024 and the old codes to earlier conduct, flagging the bridge where it matters. Counsel does not keep a conversion chart open in another tab.

   ProofThe mapping table backs the workbench and the drafting engine off the same source, so a section cited in a draft matches the section shown in the analysis.

6. Voice and WhatsApp intake

   A case can start from a dictated note or a message to the Klauz number. Send the facts, or a voice note, and a court-format draft comes back. The channel runs online with no dependency on any one laptop being awake, so intake does not stop when the office closes.

   ProofInbound and outbound both run on the hosted edge. A voice note is transcribed and drafted from in one pass.

7. Matter memory and audit

   Documents, decisions, the timeline, and the audit trail stay attached to the matter instead of scattered across drives and inboxes. Every clause touched, every reasoning call, every specialist minute lands in a ledger the firm can read. This is the company legal brain, and it is auditable by construction.

   ProofA tamper-evident record sits under every page. The CFO can reconcile spend per matter without a black-box invoice.

8. Specialist bench

   When a matter is serious enough to need a licensed specialist, it routes to one from a defined rate. The workbench does the first eighty percent so the specialist spends their hour on judgement, not on reading the file from scratch. The two-sided network compounds as more firms and more specialists join.

   ProofRouting is explicit and priced. The specialist inherits the matter memory, not a cold document.

A tour of the workbench, told
through four moments.

Each frame below is a screen counsel actually sees. The annotations at the margin are the ones the workbench itself surfaces.

1. 

   Fig. 01

   Fig. 01

   The command center opens on the day's contracts.

   The dashboard shows the matters in flight and the reasoning posture live. Primary lane live, secondary lane on standby, deterministic templates always on. Counsel never lands on a blank screen.

   01·A

   Matter queue, sorted by counterparty deadline.

   01·B

   Reasoning-posture strip · live status.

   01·C

   Today's usage · seat and matter.

2. 

   Fig. 02

   Fig. 02

   A counterparty MSA is read, section by section.

   Eleven section buckets. Parties, term, liability, indemnity, IP, payment, termination. Every clause is tagged, scored, and traced back to the exact page in the source PDF.

   02·A

   Section buckets · playbook deviations flagged.

   02·B

   Risk score with rationale, not a black box.

   02·C

   Source PDF anchored to the clause.

3. 

   Fig. 03

   Fig. 03

   The redline surfaces with the reason in the margin.

   Counsel reviews the diff, not the document. Each proposed change carries the fallback drawn from playbook precedent and the reason it was proposed. A junior lawyer's afternoon collapses into a morning.

   03·A

   Suggested edit with playbook citation.

   03·B

   Fallback language pre-drafted.

   03·C

   Accept, reject, or route to a specialist.

4. 

   Fig. 04

   Fig. 04

   The usage ledger keeps the receipts.

   Every model call, every clause touched, every specialist minute is logged with the provider and the cost. Audit by construction. No invoice reconciliation the CFO cannot verify.

   04·A

   Per-matter cost with provider breakdown.

   04·B

   Model call log, exportable.

   04·C

   Tamper-evident authenticity ID per page.

Counsel reviews the diff,
not the document.

This is the whole product in one gesture. A risky clause is struck, the playbook fallback is written in its place, and the reason it was proposed is pinned to the margin. Watch it run, or step through each clause yourself.

A tiered reasoning stack with a deterministic safety net.

Every lane is probed on every deploy and audited on every release. The deterministic safety net is always on so a lawyer never lands on a blank screen. Open the workbench →

Built for the decade of contracts,
not the quarter of demos.

Eight architectural pillars carry the workbench. Each one is a design decision made once, verified continuously, and audited by construction. The pillars are the reason a lean team closes more paper here than a procurement-heavy stack closes anywhere else.

1. Pillar01

   Token and throughput efficiency

   Every reasoning call is routed to the smallest model that can carry the clause. Batch retrieval, deterministic prompts, and cached context keep the median call under a fraction of the naive cost. Throughput scales linearly with matter volume, not with model marketing.

   ProofMedian clause review under one and a half seconds, verified per matter in the usage ledger.
2. Pillar02

   Cost architecture

   A four-tier reasoning stack drops to the cheapest lane that meets the accuracy floor for the task. Deterministic templates handle the shape; the reasoning layer handles the judgement; specialists handle the exceptions. Gross margin holds above ninety percent at operator tier.

   ProofPer-request cost surfaced to the seat in the usage ledger. No black-box billing.
3. Pillar03

   Scalability

   Stateless workbench, warm-pooled compute, region-local retrieval. Ten times the current matter volume changes a number in the dashboard, not the topology. A pilot that lands on Monday scales to the whole firm by Friday without a re-architecture.

   ProofLoad-tested to a thousand concurrent matters. Provider quotas headroomed at ten times projected peak.
4. Pillar04

   Data resiliency

   Every matter is written to redundant stores in the region of origin. Point-in-time recovery to any minute of the last thirty days. Provider outages fall back to the next reasoning lane inside a single request; the reader never sees the seam.

   ProofRecovery drills rehearsed quarterly. Time-to-recover under five minutes for the full workbench.
5. Pillar05

   Data protection

   Encryption at rest and in flight is the floor. Every request is scoped to a matter, every matter to a firm, every firm to a tenant. No cross-tenant retrieval. No customer data ever enters a training set. Rotation policy applies to every credential.

   ProofPer-clause audit log. Tamper-evident receipt on every page. Zero-trust posture verified continuously.
6. Pillar06

   Data sovereignty

   Data lives in the jurisdiction of the matter. Indian matters stay in Indian storage, US matters in US storage, EU matters in EU storage. The reasoning layer follows. A DPDP, PDPL, or GDPR request answers itself because the topology already respects the boundary.

   ProofRegion-pinned storage and compute per tenant. Sovereignty attested in the compliance posture.
7. Pillar07

   Best-in-class technology

   The reasoning, retrieval, and drafting layers use the current generation of models at every tier. Upgrades ship inside a release, not a quarter. The workbench is the last surface the reader sees; behind it, the stack is refreshed to whatever is state of the art the week it lands.

   ProofProvider matrix reviewed monthly. Model rotation gated on the internal accuracy floor, not vendor cycles.
8. Pillar08

   Best-in-class compute

   The workbench runs on hardware chosen for cost per correct answer, not brand loyalty. Warm pools where latency matters. Batch pools where volume matters. Every deployment carries an explicit cost per thousand matters that the CFO can verify.

   ProofCost model in the admin design document. Every production release carries a cost-per-matter delta.

The investor memorandum.

Five short games,
played in ASCII.

Five toys. Keyboard-first, deterministic, and quick to walk. Each one is a different shape of play built out of the same brass-on-cream glyph set the rest of the document reads in. Ninety seconds a round. No sign-in, no counter, no leaderboard. Just the game.

Klauz replies with a court-format PDF.
In under thirty seconds.

Message +1 555-163-7561 on WhatsApp. Send /deck for this memo, /bail Rajesh Kumar, Bombay HC, BNS 318, first offender for a court-ready bail application, /help for the full menu.

Today the WhatsApp channel is verified-recipients-only via the Meta Cloud API test number. Full App Review plus Business Verification opens it to any counterparty. Use the workbench today →