Templates and clauses
NDAs, service agreements, AMC, retainers, offer letters and more, with a clause library and variables.
From draft to signed, and on time after that
Draft agreements from Indian templates, send them for signature, and keep their dates and obligations on time.
Each domain keeps contracts numbered CTR/<financial year>/0001 with a type (client agreement, NDA, AMC, retainer, vendor, consultant, offer letter, MoU, SLA, other), the parties, a value in INR, start and end dates, auto-renew, a notice period and an owner, moving from draft through sent and signed to active, expiring, and expired or terminated. Documents are drafted from eleven Indian small-business templates and a library of 23 clauses with {{variables}}, or uploaded as a PDF to R2; each send locks a version with its SHA-256. Signers open /sign/<token>, in order or in parallel, confirm a 6-digit email code, tick a consent and type, draw or pick a typed-font signature; the record keeps the time, address, browser and the SHA-256 of the exact version, shown on an audit certificate and with the signed copy at /view/<token>. It is an electronic acceptance record, not Aadhaar eSign or a DSC. Obligations (deliverables, payment milestones, reports, notices) have due dates and owners. A daily 10:00 IST cron moves statuses with the dates, renews auto-renewing terms, reminds before notice deadlines, end dates and obligations, and nudges signers; signed contracts with an end date go to Renewals. An API for Client Portal (templates, create and send, contracts by email), webhooks, and Claude to summarise a contract, pull out obligations and draft or explain a clause.
What Contracts does for you.
NDAs, service agreements, AMC, retainers, offer letters and more, with a clause library and variables.
Signers confirm an email code and sign; the record keeps the fingerprint of the exact version.
Obligations, notice and end-date reminders, and renewals sent to Renewals.
A suggested path for Contracts. What you can do depends on your access in the app.
Start from a template or upload a PDF.
Add signers in order or together; each gets their own link.
Track obligations and act before the notice deadline.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each domain keeps contracts numbered CTR/<financial year>/0001 with a type (client agreement, NDA, AMC, retainer, vendor, consultant, offer letter, MoU, SLA, other), the parties, a value in INR, start and end dates, auto-renew, a notice period and an owner, moving from draft through sent and signed to active, expiring, and expired or terminated. Documents are drafted from eleven Indian small-business templates and a library of 23 clauses with {{variables}}, or uploaded as a PDF to R2; each send locks a version with its SHA-256. Signers open /sign/<token>, in order or in parallel, confirm a 6-digit email code, tick a consent and type, draw or pick a typed-font signature; the record keeps the time, address, browser and the SHA-256 of the exact version, shown on an audit certificate and with the signed copy at /view/<token>. It is an electronic acceptance record, not Aadhaar eSign or a DSC. Obligations (deliverables, payment milestones, reports, notices) have due dates and owners. A daily 10:00 IST cron moves statuses with the dates, renews auto-renewing terms, reminds before notice deadlines, end dates and obligations, and nudges signers; signed contracts with an end date go to Renewals. An API for Client Portal (templates, create and send, contracts by email), webhooks, and Claude to summarise a contract, pull out obligations and draft or explain a clause.
Price quotes and their acceptance belong to Quotations; email signatures belong to Signatures; renewal decisions belong to Renewals.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
contracts.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.