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.

Illustrated team walkthrough · fictional matter

One motion. Four accountable handoffs.

Aster Ridge Manufacturing, LLC needs a motion to compel. Follow the record from preparation to attorney review. This illustration does not create a firm, grant access or send a document.

  1. 1. Prepare the record

    The paralegal organizes Requests 14 and 17, responses, conferral correspondence and the production index. A missing attachment remains a gap in the record.

  2. 2. Review the draft and challenge

    The attorney inspects the foundations and the disagreement over relief. A proposed edit removes an unsupported allegation of deliberate withholding.

  3. 3. Decide and supervise

    Counsel narrows the prayer to the conferral scope. A handoff identifies the exact version and unresolved privilege issue; it grants neither access nor approval.

  4. 4. Approve the intended output

    Review the motion, exhibit references and proposed order separately. Approval, export permission and recipient delivery each need their own recorded state.

Try the motion walkthrough →Open your firm console →Review access and data controls →

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; the API and MCP door is built and closed today, and its contract is published on the developers page, every statement with its evidence.

IntegrationsThe Word add-inThe API contract

The referral lane

Where DraftCounsel would receive a packet a person organized on FamilyLawGPS or TrialVector and asked an attorney to review, for an attorney admitted in its state to claim. It is built dormant and receives nothing until counsel reviews it; its page says why, state by state.

The referral lane

Enterprise and the editions

Enterprise, the legal aid edition and the mediator edition are arranged directly, never sold through checkout: once the procurement package and the data controls are agreed, the owner records the arrangement for the firm, and it grants packs exactly as a plan does. An Enterprise firm’s client intake links carry the firm’s own name, without the platform’s navigation, and say who keeps the answers.

The plan ladderAsk about an arrangement

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. The data processing agreement is published as a template for a firm’s counsel to review; a firm’s agreement is completed from it per engagement and is in force only when the owner and the firm sign it.

The DPA templatePrivacy policyRequest a signed 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 fictional motion to compel discovery from disputed discovery to scoped revision. 2. Read the trust evidence and the refusals. 3. Evaluate one authorized matter with one attorney and one paralegal. 4. Decide on the console rollout using the recorded results.

The thirty-day evaluation, run by yourselfThe discovery-motion storyThe product directory