CMXFeatures

Every feature of CMX, in twelve groups.

Each card says what CMX does. Core or Enterprise is marked on each.

Enlarge

• Bring in contracts from anywhere.

  Drop PDFs, Word files, images or one ZIP, or forward them to your workspace’s email-in address. Add the old register as a CSV or Excel manifest: its values take precedence and any mismatch is flagged.

  The problem: signed contracts sitting in folders, mailboxes and an old spreadsheet.

  Core

• Duplicates are caught.

  Exact duplicates are linked and never processed twice. A near-duplicate is flagged with a link to the likely original, and a person decides.

  The problem: the same contract filed three times.

  Core

• Amendments find their parent contract.

  A document that reads as an amendment, addendum or schedule is proposed to its parent; a person confirms the link.

  The problem: amendments and schedules that float loose.

  Core

• Unsigned copies are held back.

  With no signature found, confirmation waits for the signed copy, or a person confirms it unsigned with a reason.

  The problem: unsigned copies treated as contracts.

  Core

• Missing pages are flagged.

  Gaps in page numbering and a truncated last page are flagged before anyone relies on the copy.

  The problem: scans with missing pages.

  Core

• Files that aren’t contracts are set aside.

  They are marked, kept for a set number of days, and can be restored from the job.

  The problem: files that are not contracts.

  Core

• AI reads every contract.

  AI classifies each contract and extracts its fields, and every obligation as its own record.

  The problem: reading every contract by hand takes weeks.

  Core

• Every value shows its source.

  Every value points to its page and words, with Show in document. A value it cannot ground is left empty, never guessed.

  The problem: AI output nobody can check.

  Core

• A person confirms what counts.

  Dates, amounts and parties are confirmed by your people, always the first time for a counterparty and contract type.

  The problem: a model signing off a date.

  Core

• It learns from your corrections.

  A correction teaches the next extraction for that counterparty and contract type, in your workspace only.

  The problem: making the same correction again and again.

  Core

• Risk scored against your playbook.

  The AI proposes a position per clause against your playbook (the position you accept on each kind of clause), with its reason and the clause cited. The level is a fixed calculation, never a model’s opinion.

  The problem: not knowing which contracts carry the risk.

  Enterprise

• Answers with every statement cited.

  Ask across all your contracts, or one, and get an answer with every statement cited. A statement with no citation is removed.

  The problem: a simple question takes an afternoon.

  Enterprise

• AI kept in bounds and on budget.

  It never sees a contract the asker cannot open. Contract text is data, never instructions. Zero retention and no training on your data. A daily spend cap you set.

  The problem: AI that leaks, or runs up a bill.

  CoreEnterprise

• The right fields for each contract type.

  Per type: parties, our entity, effective, start and end dates, notice period, auto-renewal, term, value and currency, payment terms, escalation, governing law, liability cap and termination rights.

  The problem: every contract type has different fields.

  Core

• Review beside the document.

  The document sits beside the values with each span highlighted. Accept, edit, split, merge or reject each obligation, and confirm the fields that agree in one step, on a phone too.

  The problem: slow review.

  Core

• Your companies and counterparties, matched.

  Our entity is found by registration or VAT number, a counterparty by registration number, then name and aliases. Ambiguity stops the item; nothing merges silently.

  The problem: your own companies not recognised.

  Core

• Impossible dates are caught.

  An end before the start, a notice deadline after the end, or auto-renewal with no term is flagged, and alerts stay off until it is fixed.

  The problem: dates that contradict each other.

  Core

• Obligations belong to roles, not people.

  Every obligation is owned by a role. A person holds it for a period, the next person in the role takes over open work from a set date, leave and cover are recorded, and a role with nobody in it is reported daily.

  The problem: obligations live in people’s heads, and a resignation loses them.

  Core

• Both sides’ duties are tracked.

  Each obligation records who owes it: us, or them. Supplier SLA reports, rebates and insurance certificates are tracked like your own.

  The problem: the other side’s duties going unwatched.

  Core

• Every kind of due date.

  Fixed, recurring, relative to an event, or ongoing. Recurring obligations are scheduled 12 months ahead, and a due date on a weekend or public holiday moves to the next business day.

  The problem: due dates that are not simple.

  Core

• Done means proven.

  A type that needs evidence can’t be completed without a file, note or link, and a second person, never the one who did it, verifies or sends it back.

  The problem: “done” without proof.

  Core

• A waiver needs a reason and an approver.

  A waiver needs a reason and an approver who isn’t the person in that role. A snooze never moves the due date.

  The problem: waivers without accountability.

  Core

• Amendments update the obligations.

  An amendment closes the obligations of the clause it changes and proposes replacements for a person to confirm.

  The problem: amendments that silently change duties.

  Core

• Reminders on time, on business days.

  Lead times per obligation type: 30, 7 and 1 days and the due day by default. Overdue items escalate to the contract owner. A reminder that falls on a holiday goes the business day before.

  The problem: reminders that arrive too late or never.

  Core

• Renewal alerts from the notice deadline.

  Renewal alerts count back from the notice deadline at 90, 60 and 30 days. The decision is recorded with a reason, and an auto-renewing contract with no decision rolls forward, audited.

  The problem: a missed renewal window.

  Core

• Each person picks their channels.

  Each person picks channels per kind: in-app, email, and Teams or WhatsApp where connected, with a daily or weekly digest. Overdue items always get through. Teams and WhatsApp are set up per customer at go-live.

  The problem: too much noise.

  Core

• Due dates in your calendar.

  A Calendar view, and a feed to each person’s Outlook or Google calendar, set up per customer at go-live.

  The problem: nothing in your calendar.

  Core

• A weekly summary every Monday.

  An opt-in weekly digest on Monday at 07:00, by email and Teams, counted for each recipient.

  The problem: no picture of the week ahead.

  Core

• One register of every obligation.

  A company register of every obligation you may see, with filters, saved views, grouping and Export to Excel.

  The problem: no single view of what is owed.

  Core

• Find any contract you can open.

  Keyword search and filters, and a contract record with its details, documents, obligations, amendments, access and audit.

  The problem: hunting for a contract.

  Core

• Every counterparty in one list.

  Each one with its contracts, what’s owed each way and the next notice deadline, counted only from the contracts you can open.

  The problem: no single view of who you deal with.

  Core

• Each counterparty on one page.

  Its contracts, what it owes you and what you owe it, and how it performs.

  The problem: a supplier’s contracts and duties scattered across the business.

  Core

• A dashboard for every manager.

  The obligations dashboard in My, Team and Company views: overdue, due this week, waiting for evidence or verification, ageing, on-time rates and roles with nobody in them.

  The problem: managers who can’t see the state of play.

  Core

• Numbers that open their list.

  Every number counts only what you can open and opens the register with exactly that filter. The register is always current.

  The problem: dashboard numbers nobody trusts.

  Core

• Restricted contracts stay hidden.

  Who sees what is decided in the database, behind every list, search, count, export, notification and AI answer. A restricted contract carries a named access list and never appears for anyone not on it.

  The problem: HR, M&A and executive contracts that must not leak.

  Core

• Admins can’t read contracts.

  Admin roles give no contract access. Department admins manage only their own department, and nobody changes their own roles.

  The problem: admin tools that can read everything.

  Core

• Leavers are handed over in order.

  Removing a person is an ordered, audited step: their roles, cover and access lists are reassigned first.

  The problem: people who leave with work still assigned to them.

  Core

• A quarterly access review.

  A quarterly access review per department: keep, remove or refer, then sign-off locks it.

  The problem: nobody knows who has access to what.

  Core

• Settings you change yourself.

  Contract types, fields, reminder rules, thresholds, non-business days, the AI spend cap and retention are settings with admin screens, and every change is audited.

  The problem: settings only a developer can change.

  Core

• Every change is recorded.

  Every change is recorded, with who made it, and can’t be edited. Exports are recorded too.

  Core

• Your playbook, versioned and weighted.

  A versioned playbook sets preferred, fallback and unacceptable positions per clause type, with weights. The AI proposes each position with a cited reason; a contract manager can change it with a reason, audited.

  The problem: not knowing which contracts carry the risk.

  Enterprise

• A risk heat map.

  A heat map by counterparty and contract type. A counterparty is named only when 3 or more of its contracts sit in a cell.

  The problem: no view of risk across all your contracts.

  Enterprise

• Ask in plain words.

  A question about fields becomes register filters you can edit. Anything else is answered from contracts you can open, every statement cited, quarters in your financial year.

  The problem: questions that need someone to write a report.

  Enterprise

• Committed value, counted honestly.

  Committed value by type, department, counterparty and entity, value expiring in the next 12 months, and contracts without a usable value counted, never shown as R 0.

  The problem: nobody knows what your contracts are worth.

  Enterprise

• CMX’s own dashboards.

  CMX’s own dashboards, no other tool needed: up to 12 widgets from a fixed list, each viewer seeing only their own data.

  The problem: every executive wants a different page.

  Enterprise

• Board packs that send themselves.

  Scheduled reports, weekly or monthly, in PDF and Excel, made for each recipient.

  The problem: board packs made by hand every month.

  Enterprise

• A Microsoft Power BI feed.

  For teams that already use Microsoft Power BI: a read-only feed. Each connection sees only what the person who set it up can open, expires after 90 days, and every refresh is audited.

  The problem: the BI team wants the data.

  Enterprise

• Automatic follow-up.

  Automation rules on dates, overdue items and changes: create a task for a role, send a message or call a signed webhook. A rule never changes contract data and is previewed on the last 30 days first.

  The problem: follow-up that depends on memory.

  Enterprise

• Approval steps on waivers and renewals.

  Optional approval steps per contract type and value band, with a role as approver, and an Approvals inbox: Waiting on me, Decided by me, Sent by me.

  The problem: waivers and renewals that need sign-off.

  Enterprise

• Approve in Microsoft Teams.

  Cards for approvals, verification and My obligations, with access checked at the click. The Teams app is set up per customer at go-live.

  Enterprise

• A request form for every contract type.

  A request form per contract type. Any employee requests for free, and the form says before Submit whether it is drafted now or goes to Legal, and why.

  The problem: “Can I get an NDA?” by email.

  Enterprise

• Low-risk contracts draft themselves.

  A self-service template drafts at once when every answer is given, the value is under the threshold and nothing deviates. Everything else goes to a legal queue with an SLA.

  The problem: low-risk contracts clogging Legal.

  Enterprise

• Templates checked before publishing.

  A Word template is published only when every field is filled correctly and a second person approves it.

  The problem: templates that drift.

  Enterprise

• A clause library of approved wording.

  A clause library by clause type, with preferred and fallback positions, owner role, lock and versions. Insert or replace a clause from the draft.

  The problem: approved wording that lives in someone’s inbox.

  Enterprise

• Every changed clause is listed.

  Each version uploaded is compared clause by clause with the library. A change to a locked clause stops the draft being finalised until a legal reviewer accepts it with a reason.

  The problem: not knowing what was changed.

  Enterprise

• One editor at a time.

  Editing is in Word by check-out: Download takes the lock, upload releases it.

  The problem: two people editing the same file.

  Enterprise

• Drafts stay out of the numbers.

  Contracts before signature never count in any number, feed or answer. They live in Requests, Drafts, Signing and the Pipeline view.

  The problem: drafts that pollute the numbers.

  Enterprise

• Agreements between your own companies.

  A contract type marked internal: every party is one of your entities, with internal signers only.

  The problem: internal agreements with no counterparty.

  Enterprise

• The PDF matches the Word file.

  The PDF is made through your Microsoft 365 when it is connected; otherwise it is checked word for word against the Word file and confirmed by the sender.

  The problem: PDFs that don’t match Word.

  Enterprise

• Signing inside CMX, no fee per signature.

  Send for signature from a final draft: internal and external signers, in order or together, with due dates and reminders. No fee per signature.

  The problem: a fee per signature, and another portal.

  Enterprise

• Outside signers need no account.

  A secure single-use link and a one-time PIN by email. The signer reads to the end, consents, types or draws, or declines with a reason.

  The problem: outside signers made to create accounts.

  Enterprise

• Staff sign with their own sign-in.

  Staff sign inside CMX with their Microsoft or Google sign-in as the proof.

  Enterprise

• The evidence travels with the PDF.

  Signatures applied in order, an audit certificate as the last page and the executed PDF’s hash recorded. The evidence bundle downloads as a zip.

  Enterprise

• Copies signed on paper are compared.

  Upload the signed copy: CMX compares it with the final version, flags any change other than signatures, initials and dates, and sends it to the Confirm queue.

  The problem: contracts signed on paper anyway.

  Enterprise

• Signed contracts go straight to work.

  On completion the signed PDF goes straight to the Confirm queue, and its obligations run like any contract’s.

  The problem: signed, then forgotten.

  Enterprise