The contract that lived in an inbox for a week
A rep closes a deal on Friday. He builds the contract from last year’s file, swaps the customer name, misses the bank details, and emails it to legal. Legal is out. Finance first sees it when the customer asks for an invoice. A week later, nobody knows which version is final or who signed off on it.
DOCUS removes that loop. Contracts are assembled from a template in three steps, data flows in from the deal and from accounting, the approval route starts on its own, and each approver gets a button where they already work. At any moment you can see who has the document and how long it has been sitting there.
How DOCUS works with the rest of PRANUS
DOCUS is not a separate tool you wire up with integrations. It sees the same people, customers, and money as the rest of the system.
- From deal to contract. When a deal in the CRM reaches the right stage, a “prepare contract” request appears with the customer, amount, and line items already filled in.
- Approvals where the work happens. Approval buttons land in the team messenger, and every document gets its own discussion room.
- Routes by role. “Legal” and “department head” come from the org chart. When someone leaves, the route still works and the document goes to their replacement.
- Finance without re-entry. Bank details and invoices come from finance and accounting, and signed documents flow back into the books.
- Policies become company knowledge. One click publishes a document to the knowledge base, so AI employees answer questions with a link to the exact clause.
What the AI does
The AI handles preparation. People make the decisions.
- Drafts a template from a description, or edits one on request: “add a late-payment penalty clause.”
- Helps mark the fields in an uploaded contract so the template works right away.
- Works out who must acknowledge a new policy, based on departments and job titles.
- Builds a quote from catalog items and deal data.
Signing, approving, and putting a document into effect stay with people. Once signed, a document can’t be quietly changed: it is stored immutably and its fingerprint is verified.
Policies with a real audit trail
Internal policies are their own headache. The handbook sits in a shared folder, three people know about the new version, and there is no record of who read what.
In DOCUS, a policy goes through staged approval, takes effect on a set date, and the previous version is retired automatically. Each acknowledgment is tied to a fingerprint of that exact version, so it can’t be backdated. The list of who must read it is built from your org structure instead of a hand-made spreadsheet.
How you get started
The onboarding agent asks which documents you use and requests samples in Word. It marks up the templates, generates a test contract, and sets approval routes based on your org chart. Each change shows up as a plan card and is applied only after you say yes. See how the two-week onboarding works.
Who it’s for
- Legal teams — templates, counterparty redlines as tracked changes, immutable storage.
- Sales — a quote and contract straight from the deal, shared by link.
- HR — employment orders and policy acknowledgments routed by org structure.
- Leadership — a clear view of where every document is stuck and why.
If your contracts live in email threads and folders full of “final_v2” files, book a demo and we’ll walk a real deal from quote to signed contract.