CMXby QED Works

The contract system that makes sure what you signed actually happens.

AI you can check. Your contracts stored in your region.

Book a demoTalk to us
The CMX obligations dashboard, Company view: tiles for overdue, due in 7 and 30 days, waiting for verification, evidence missing and notice deadlines, with overdue ageing and renewals.
Every tile counts only what the viewer can open, and opens the register with that filter.

Where contracts lose money

Not in the drafting. After signature, when nobody is watching the dates.

It makes contracts happen, not just stores them.

Every obligation in every contract becomes a record owned by a role, with a person in that role, cover for leave, evidence, verification and reminders on your business days. When someone resigns, you fill the role; you don’t edit every contract.

My obligations in CMX: obligations due this week, each with its contract, the Contract Manager role and the evidence required.
Each obligation is owned by a role and says what evidence it needs. Someone in that role who can’t open the contract still sees the clause.

AI you can check.

CMX reads the contract and proposes dates, parties, amounts and obligations. Each one points to its page and words. Your people confirm. Nothing a model finds counts until someone does.

The CMX Confirm queue: four contracts from one import, two needing attention (possibly unsigned, an ambiguous counterparty) and two waiting for their first-time fields to be confirmed.
Each proposed value waits in the Confirm queue for a person. Nothing counts until someone confirms it.

Your region, your rules.

Your contracts are stored in your region: South Africa today, with EU and US hosting on request as a dedicated deployment. Every due date and reminder respects your public holidays. South Africa’s are set up for you; the calendar is yours to edit.

CMX Admin, Non-business days: the holiday calendar listing the Day of Reconciliation, Christmas Day and the Day of Goodwill 2026, each a South African public holiday, with Add a non-business day.
Your public holidays, in your calendar: a due date on a holiday moves to the next business day.

How CMX works

A contract’s life in CMX, in the order it happens. Each step opens its features.

Core includes the obligations dashboard: My, Team and Company views. Insights adds value, risk and board packs on Enterprise.

Step 6, up close

AI proposes, a person confirms.

Each value and obligation points to the words it came from. A person checks it against the page and confirms it; nothing counts until they do.

An obligation open beside its contract in CMX: its source clause marked, with Show in document, its monthly timing and the next three due dates, one moved from a weekend.
Each obligation shows the words it came from. Show in document opens the page.

Take the tour

Screens of CMX on demo data, one at a time.

  1. Ask for a contract

    The form says who it goes to, and why, before you submit.

    A contract request in CMX: the contract type, the answers form and, beside it, What happens next: it goes to the Legal reviewer, usually within 2 business days.
  2. Every changed clause listed

    A changed locked clause is listed beside the library text and stops the draft being finalised until a legal reviewer accepts it.

    A CMX draft with its Deviations tab: the liability cap clause in the library beside the changed clause in the draft, marked as stopping the draft being finalised.
  3. Your approved wording, by clause

    Approved wording by clause type: preferred and fallback, versioned, owned by a role, locked where it matters.

    The CMX clause library: clauses grouped by type, each with its declared position, version, owner role and whether it is locked.
  4. Signed outside CMX, compared

    A copy signed outside CMX is compared with the final version. Any change beyond signatures, initials and dates is flagged.

    A contract signed outside CMX: a banner says the signed copy differs from the final version, with the differences listed page by page.
  5. The signing evidence, kept

    Every signer, method and event is kept with the executed PDF.

    An executed contract’s signing evidence in CMX: two signers, one internal and one external, when and how each signed, the document fingerprints, and every event from sent to PIN verified, with Download signed PDF and the evidence bundle.
  6. Bring in the whole back-book

    One import for the whole back-book, with progress, failures and a needs-attention list.

    A CMX import job, Q3 supplier contracts.zip: four files processed, two waiting for confirmation and two needing attention, each with its counterparty, type and flags.
  7. A person confirms each value

    Each proposed value waits in the Confirm queue for a person. Nothing counts until someone confirms it.

    The CMX Confirm queue: four contracts from one import, two needing attention (possibly unsigned, an ambiguous counterparty) and two waiting for their first-time fields to be confirmed.
  8. Each obligation shows its words

    Each obligation shows the words it came from. Show in document opens the page.

    An obligation open beside its contract in CMX: its source clause marked, with Show in document, its monthly timing and the next three due dates, one moved from a weekend.
  9. Every number opens its list

    Every tile counts only what the viewer can open, and opens the register with that filter.

    The CMX obligations dashboard, Company view: tiles for overdue, due in 7 and 30 days, waiting for verification, evidence missing and notice deadlines, with overdue ageing and renewals.
  10. Every obligation in one list

    Owed by you and to you, filtered, saved and exported, counting only what you can open.

    The CMX obligations register: saved views, Export to Excel, filters for entity, department, owner role, counterparty, direction, status and due window, and three renewal notices, each with its notice deadline, counterparty, contract and owner role.
  11. Obligations owned by roles

    Each obligation is owned by a role and says what evidence it needs. Someone in that role who can’t open the contract still sees the clause.

    My obligations in CMX: obligations due this week, each with its contract, the Contract Manager role and the evidence required.
  12. Roles, and the people in them

    Obligations belong to roles. A role with nobody in it is reported to the department admin.

    CMX Admin, Owner roles: 8 roles, 3 with nobody in them; the Operations role shows No holder and that its tasks are reported to the department admin.
  13. Your holidays, your due dates

    Your public holidays, in your calendar: a due date on a holiday moves to the next business day.

    CMX Admin, Non-business days: the holiday calendar listing the Day of Reconciliation, Christmas Day and the Day of Goodwill 2026, each a South African public holiday, with Add a non-business day.
  14. Approval steps on waivers

    Approval steps on waivers and renewal decisions, by contract type and value band, with a role as the approver.

    CMX Admin, Approval steps: a step for renewal decisions on any type and one for waivers of R 3 000 000 and over, each approved by the Legal and compliance role.
  15. Your playbook, clause by clause

    Your playbook: the position you accept on each kind of clause, with fallbacks and weights.

    The CMX playbook: liability cap and indemnity, each with preferred, fallback and unacceptable positions and example wording.
  16. Risk, with the reason shown

    The AI proposes each clause position with its reason and the clause it read. The level is a fixed calculation.

    A contract’s Risk tab in CMX: risk level Medium, 48 of 100, and each clause position marked Proposed by AI with its reason and a link to the clause.
  17. What your contracts are worth

    Committed value by type, department and counterparty. Contracts without a usable value are counted, never shown as R 0.

    CMX Insights: committed value R 8 100 000, R 2 220 000 expiring in 12 months, high-risk and waiting counts, and value by contract type and department.
  18. Risk across your contracts

    Risk across your contracts by clause type and counterparty, counted only from contracts you can open.

    CMX Portfolio risk: contracts scored, low, medium and high counts, and unacceptable and not-found positions by clause type.
  19. CMX’s own dashboards

    Built from a fixed list of measures and groupings, with no other tool and no technical skills needed.

    The CMX dashboard builder: a catalogue of measures and groupings on the left and three widgets on a dashboard called Finance value pack.
  20. A daily AI spend cap

    A daily AI spend cap you set. At the cap, extraction pauses until midnight and everything else carries on.

    CMX Admin settings: the AI spend cap at R 100 per day with R 0 used today, beside the limits on AI calls, webhooks and the reporting feed.

AI assistance

AI proposes, your people decide.

CMX uses AI to read, find and score, and shows its working each time. A person makes every decision that counts.

What CMX does, every day

Each card opens its feature group. Core or Enterprise is marked on each.

See all twelve feature groups

Who it’s for

Your region, your rules.

Every line here is something CMX does today.

Security and trust

Security and privacy

Works with what you use

Core and Enterprise

About QED Works

QED Works builds software that proves what was agreed was done. It rests on more than twenty years of delivering document, workflow, contract and accounts payable systems to banks, insurers, retailers, manufacturers and government.

About QED Works

Questions

Where are our contracts stored?

Your contracts are stored in your region: South Africa today, with EU and US hosting on request as a dedicated deployment.

Does the AI decide anything?

No. AI proposes, your people decide. It proposes dates, parties, amounts and obligations, each pointing to its page and words, and a named person confirms them. A risk level is a fixed calculation from your playbook, never a model’s opinion.

Is our data used to train the AI?

No. The AI runs under our contract with an enterprise AI provider, with zero retention and no training on your data.

Do we have to change how we draft?

No. Word stays the editor. Templates and drafts are Word files, edited by check-out, and CMX never re-renders the document.

Can we bring in our old register or spreadsheet?

Yes. Add it to the import as a CSV or Excel file. Rows are matched to files by name, their values take precedence, and any mismatch is flagged for a person.

How is it priced?

Priced in rand, excluding VAT, by the number of active contracts. Only managers are paid seats; viewers and obligation owners are free and unlimited. Core is from R 1 750 a month and Enterprise from R 4 150 a month.

What happens when someone leaves?

Obligations belong to roles, not people. Give the role to someone else and they take over its open work from the date you set. Removing a person reassigns their roles, cover and access lists first, and is recorded.

How does CMX handle POPIA and other privacy laws?

CMX is built for POPIA and the privacy laws modelled on the same principles: data stored in your region, access decided in the database and limited to the people who need it, a record of every change, retention and deletion you set, signers’ details shown only to people who can open the contract, and a breach procedure.

See CMX with your own kind of contracts.

Book a demo