Platform
Four levels. One contract record.
ContractSense is built in layers. Lifecycle capabilities your teams use every day run on a secure application foundation, which draws on shared technical features delivered by a small set of services that run in your environment.
- Level 0
- Lifecycle: draft, negotiate, enforce
- Level 1
- Application foundation
- Level 2
- Technical features
- Level 3
- Building blocks
Level 0 · Lifecycle capabilities
What your teams do.
Fifteen capabilities across three stages. Each one shares the same contract record, version history and audit trail.
Start right
Ingest & draft →
- Intake and requests
forms, inbound email, uploads - Drafting and proposals
templates, clauses, AI drafts - Playbook review
compliance check, analysis - Migration and binders
existing papers, split packs - Diligence rooms
tabular review across many documents
Agree faster
Negotiate →
- Redline and counters
tracked changes, email replies, walkaway - Collaboration
live editing, comments, spaces - Approvals
rules, delegation, Slack, Teams - Signatures
links, portal, sealed PDF - Counterparty portal
share links, external review
Get what you agreed
Enforce →
- Repository and search
extraction, RAG, assistant - Review queue
low-confidence fields verified - Obligations
dates, owners, notices - KPIs, SLAs and invoices
credits, audit, studio - Renewals and analytics
non-renewal notices, dashboards
Level 1 · Application foundation
What everything runs on.
Access, isolation, audit, AI spend control and integrations are part of the foundation, so every capability gets them by default.
Roles and permissions
Role-based and per-contract access.
Tenant isolation
Every read scoped to your organisation.
Audit chain
Tamper-evident and independently verifiable.
AI usage and caps
Budget reserved before each AI call.
Admin console
Users, AI keys and integrations.
Notifications
Email and in-app, per-user preferences.
Integrations
Webhooks, SMTP and inbound email.
Chat apps
Slack commands and Teams cards.
Content management
Prompts, skills and packs.
Custom fields
Per-organisation contract fields.
Data protection
PII policy, secrets, SSRF guard.
Portal access
Separate signing key, expiring links.
Monitoring and health
Probes, logs and alerts.
Marketing endpoints
Public contact, rate-limited.
EntitlementsRoadmap
Domains and packs per customer.
Level 2 · Technical features
What the capabilities need.
Twenty shared features, built once and reused across the lifecycle. Redline powers negotiation and playbook review. Extraction powers migration and enforcement.
| Feature | What it does |
|---|---|
| Ingestion and OCR | PDF, DOCX and scans, with hosted OCR. |
| Binder splitting | One PDF into its separate agreements. |
| Structured extraction | Parties, dates, clauses and values. |
| Hybrid search and RAG | Embeddings, rank fusion and citations. |
| Obligation scanning | Extract, tier and sync to dates. |
| Redline and tracked changes | DOCX diff, accept and reject. |
| Template engine | Variables, blocks, DOCX fill. |
| Real-time co-editing | Shared document sessions. |
| Workflow and rules engine | Approval routes and conditions. |
| Playbook rules | Run, find and target redlines. |
| E-signature sealing | PAdES signing with certificate. |
| Conflict detection | Document graph, superseded terms. |
| Agent chat and memory | Threads and project memory. |
| Tabular review | A grid of questions over documents. |
| PII redaction | Before text leaves the trust zone. |
| Prompt, skill and pack serving | Versioned, scoped and cached. |
| Model routing | Per-organisation keys and provider choice. |
| Usage reservation | Fails closed before each call. |
| PDF and DOCX rendering | HTML to PDF, DOCX export. |
| Tracing and metrics | Per-call cost, latency and health. |
Level 3 · Building blocks
What delivers them.
A small number of services, all deployed in your environment apart from the packs server. Analysis and agents never write records directly: the lifecycle API owns records, rules, permissions and audit.
Web app
A fast single-page application for every role.
Lifecycle API
Typed API with role-based access control.
Intelligence service
OCR, extraction and retrieval.
Agents service
Drafting, redline, approval and review agents.
Job workers
Queued background processing at scale.
Realtime collaboration
Live co-editing over websockets.
Packs server (MCP)
Industry packs, prompts and a usage ledger. The only part we host.
Customer connector
Runs in your network and polls outward. No inbound ports.
Data stores
Document database, cache and object storage.
Document services
PDF rendering and hosted OCR.
AI providers
Model-agnostic: route to the provider you choose.
Delivery and observability
Automated delivery, tracing and cost metrics.
Integrations
Connects to the systems where contracts happen.
Invoices, purchase orders, delivery records and service data reach ContractSense the way they already move in your business. Each incoming document is matched to its contract using the identifiers your systems actually use.
Long-running work such as drafting, extraction, review and scanning runs on background workers, so the interface stays fast while thousands of documents are processed.
ERP and finance
Work and service
Data feeds
See the platform on your contracts.
Run a proof of concept on three to five of your highest-value contracts. Measurable findings in eight weeks, on your data, with read-only access.