For legal and compliance teams
The routine work arrives already sorted
Route the requests, fill the standard templates, review incoming paper against your playbook and surface every date buried in a contract — with the judgement still a lawyer’s.
The judgement stays a lawyer’s: it never gives the final answer on its own.
Where the week actually goes
A legal team’s queue is mostly the same few things: another NDA, another vendor contract to read, another date somebody needs reminding about. The volume is what makes it hard, not the difficulty. Awish clears the routine from your description of the playbook you already wrote.
It fills the approved template and names any deviation from it, compares incoming paper to your playbook clause by clause, and pulls the obligations out of a signed contract into a calendar. Each system is granted on its own and can be withdrawn; every comparison it made is on the record.
The week today
A legal team’s queue is mostly the same few things: another NDA, another vendor contract to read, another date somebody needs reminding about. The volume is what makes it hard, not the difficulty — and the cost of the volume is that the genuinely hard question waits behind twenty routine ones.
With Awish
Awish clears the routine. It fills the approved template and names any deviation from it, compares incoming paper to the playbook you already wrote, and pulls the obligations out of a signed contract into a calendar. What it never does is decide: the exceptions, the redlines and the advice stay with counsel.
The workflows, end to end
Three workflows a legal team runs, end to end — each with its trigger, the apps it touches, and the step where a person approves.
- 01
Turn an NDA request into a signature-ready draft
“When someone asks for an NDA, collect the counterparty and the purpose, fill the approved template, and send the standard version for signature — anything non-standard goes to legal.”
SlackDocuSignGoogle DriveNon-standard goes to legal
- 02
Review an incoming contract against your playbook
“When a third-party contract is uploaded, extract the clauses, compare them to our playbook, flag what is missing or high-risk, and hand counsel a summary.”
Google DriveSlackNotionCounsel decides, always
- 03
Never miss a date buried in a contract
“When a contract is signed, pull out the renewal, notice, payment and reporting dates, put them in the calendar, and remind the owner before each one.”
Google DriveGoogle CalendarSlackAmbiguity goes to legal
Ready to start from
Described requests this team already runs — pick one and it lands in your chat, with its approval points intact.
Compliance Evidence and Audit Pack
An evidence window opens or an audit begins
VantaGoogle DriveJiraSlackDo not mark a control compliant just because a document exists; require the configured validation or attestation.
Awish checks that the contract, request or evidence was filed with its approval
Use this automationContract Approval Across Sales, Finance and Legal
A deal reaches contract-ready stage or non-standard terms appear
SalesforceContractbookSlackNetSuiteNo signature request until every required approval is recorded and the contract version is locked.
Awish checks that the contract, request or evidence was filed with its approval
Use this automationContract Obligation and Renewal Monitoring
A contract is executed, then a daily check on upcoming dates
ContractbookGoogle DriveGoogle CalendarSlackEscalate ambiguous terms to legal rather than reading them as definitive obligations.
Awish checks that the contract, request or evidence was filed with its approval
Use this automationContract Review Against the Playbook
A third-party contract is uploaded for review
ContractbookGoogle DriveSlackThe final legal judgement stays with counsel; do not send redlines outside the company without approval.
Awish checks that the contract, request or evidence was filed with its approval
Use this automationData Subject Request Orchestration
A data subject request is submitted
ZendeskJiraGoogle DriveNever disclose or delete data without the required identity verification and privacy approval.
Awish checks that the contract, request or evidence was filed with its approval
Use this automationLegal Request Intake and Matter Routing
A colleague submits a legal request
TypeformSlackJiraContractbookRoute sensitive and high-risk matters privately; the automation never gives final legal advice — that stays with counsel.
Awish checks that the contract, request or evidence was filed with its approval
Use this automation
The tools this runs across
The apps these workflows connect. Each one is granted on its own, before anything runs, and can be withdrawn.
- Slack
- Docusign
- Google Drive
- Notion
- Google Calendar
- Google Docs
- Google Super
- Affinda
- Agility cms
- Algodocs
- Api2pdf
- Aryn
- Boldsign
- Boloforms
- Box
- Carbone
- Castingwords
- Cloudconvert
What stays under your control
It never gives the final answer
Awish prepares, compares and routes. The legal judgement — approve, redline, advise — stays with the people qualified to give it.
A changed clause is named, not absorbed
Deviation from the approved template is flagged explicitly. A protected clause is never quietly accepted because the rest of the document looked standard.
Nothing external sends without approval
A redline, a signature request or a reply to the other side is drafted and held. A person releases it, in the channel they already watch.
Common questions
Does it give legal advice?
No, and it is not built to. It applies the rules you already wrote down — your template, your playbook, your approval matrix — and routes anything outside them to a person. The advice is always a lawyer’s.
Can it send a contract to the other side?
Only after approval. Signature requests, redlines and external replies are prepared and held for a person; a declined draft is never sent.
How does it know what our playbook says?
From the playbook itself. You point it at the approved positions and fallback language you already maintain, and the review compares clause by clause against those — not against a generic standard.
What does it need access to?
Only the apps the plan names, granted one at a time. A contract-review workflow typically asks for the drive the contracts sit in and the channel you review in; it cannot reach anything else, and access can be withdrawn at any time.
Start with the NDA request that came in this morning
Describe how it should be handled. You will see the plan, and the approval points, before anything connects.
Free plan · No credit card required