You already run approvals in your chat suite. Why add a contract system?

Running contracts through approvals usually looks like a form plus an attachment: the business fills in counterparty, value and term, attaches a Word file, the request routes by value to the right level, legal leaves comments in the thread, and the business re-uploads after editing. Where contract volume is modest and terms rarely change, this works, and many companies have run it steadily for years.

The ceiling shows up at the attachment field. An attachment is opaque; the workflow engine cannot see inside the file, so everything clause-related degrades into human memory and free text in a comment thread. Telling what changed between version three and version five takes manual comparison. If legal said payment terms could stretch to sixty days and version six quietly restores ninety, the workflow engine raises nothing.

The second ceiling is on the timeline. An approval instance ends when the last person clicks approve, while a contract's life effectively starts at signature: renewal dates, payment milestones, amendments. Those events occur after the approval closed, and no instance is still watching for them.

The single most reliable signal for whether a contract system is warranted is whether documents go back and forth with people outside the company.

As soon as external negotiation exists, the process spills outside the collaboration platform. The counterparty is not in your tenant, so drafts travel by email or messaging, versions bounce between two organisations, and each round needs someone to carry the latest file back into the approval. That spilled portion is exactly where risk concentrates, and it sits outside the system. A contract system addresses it by pulling the rounds, the version comparison and the redline history into the contract's own lifecycle, while approvals continue to decide who signs off internally.

The reverse also holds. If contracts are mostly internal sealing of standard templates with almost no clause changes, such as repetitive purchase orders or formatted service agreements, the negotiation stage does not exist, the approval workflow genuinely is enough, and the return on a contract system is limited.

A common group structure is several legal entities each running their own collaboration tenant, or part of the organisation on a modern suite and part still on an older OA system. Approvals are organised by tenant and do not cross tenant boundaries, so when group legal asks how many in-flight contracts across all entities departed from the standard liability clause, no single screen can answer. Each tenant exports its own list and someone merges them by hand.

What a contract system contributes here is not replacing anyone's approvals but closing over them: each entity keeps its existing entry point and approval habits, while contract versions, authority decisions, AI review results and the register are consolidated in one place, giving legal a view that spans entities.

Coexistence does not mean putting two systems side by side and letting staff choose. The workable pattern is that the collaboration platform keeps doing the few things it is good at, the contract system carries the content layer, and there is exactly one handover point between them.

Identity and directory

Sign-in goes through the collaboration platform, and the directory and joiner-mover-leaver changes sync from it, so no second address book is maintained. To staff it feels like working where they always worked, except that opening the task card lands them in a contract interface.

Tasks and reminders

Approval tasks, signing prompts and renewal reminders are pushed back into the platform's message and task centre. This detail decides whether the system gets used: if reminders live only in the contract system's own inbox, most people will not check it daily.

Approval orchestration

Who approves is decided by the platform's org relationships; what is being approved comes from the contract system. A clause beyond delegated authority triggers the matching approval level, the judgement is made by the contract system, and the resulting task still lands in the platform's inbox.

If adding any system is off the table for now, there is a lighter starting point: leave the contract process where it is and connect only AI review to the existing approval flow, with results returning to the same form and comment thread. The trade-offs of that path are covered in the related reading below.