Skip to main content
DraftCounsel™

For firms

How a firm deploys DraftCounsel.

What each role does, how a rollout goes, where the data flows, what connects, what the trust evidence proves, and how to evaluate it on one matter. Administrators who already have a firm open the console; nothing here creates one.

Roles

Owner and attorney roles decide: they approve, reject or revise findings and finalize work product. Paralegals prepare: they attach sources, answer intake and draft proposals that wait for a decision. Administration manages members, matters and the playbook and never approves.

Every consequential act is checked against the signed-in account, the tenant membership, the matter and the purchase before it happens; a walled matter reads as not found to the walled user.

Security and governance

Rollout

Create the firm in the console, invite the first attorney and paralegal, open a matter, attach the firm playbook. Work happens in one governed workspace; the public tool pages are launchers into it.

Nothing gates a matter on the firm: every matter link keeps working; the console groups and aggregates the work the firm already does.

Administrators: open the firm console

Data flow

Uploads are checked (signature, size, archive bounds) before any parser reads them; extracted text and the matter facts reach the engines only for the run the attorney sent; the sources, the manifest and every decision land in the matter's record.

The engines are named on the trust page with what reaches each and whether it is built or reached; retention and deletion are stated in the data lifecycle.

The data lifecycleEngine status, computed

Integrations

The Word add-in inserts firm clauses and runs Cite Check inside Word. Research and firm-system connections are listed on the integrations page, each stated as built or reached; an API and a practice-system door are planned work, not shipped features.

IntegrationsThe Word add-in

Trust evidence

The trust page, the refusals catalogue, the engine status, the public scorecard and the transparency report are generated from registries the code enforces and laws prove. No certification is claimed that has not been earned.

Trust CenterRefusalsPublic scorecardTransparency report

Support

Support, complaints and refunds run through one page with its own service commitments stated there.

Support and refunds

Data processing terms

The privacy policy and the data lifecycle statement govern processing today. A signed data processing agreement for a firm is requested through support and prepared per engagement; none is published as a standing document yet, and this page will say so until one is.

Privacy policyRequest a DPA

Pricing

Per-matter purchases and engine upgrades, with the commercial door stated as live or frozen on the pricing page itself.

Pricing

Evaluation steps

1. Walk the sample matter (Mutual NDA · Florida, fictional matter — demonstration) from sources to packet verification. 2. Read the trust evidence and the refusals. 3. Run one real matter with one attorney and one paralegal. 4. Decide on the console rollout.

The sample matterThe product directory