- Home
- How it works
How it works: from your data to a saving that is done
Cureman works in six steps. It reads an organisation's own data through connectors, invoices, mailboxes and the gateway. Deterministic code computes findings, each with its calculation. The autopilot drafts the first step. Whatever needs a person waits in one list of decisions, each with what it is worth. Every message sits in a conversation with a follow-up clock. A saving is counted when it is done or billed, not when it is found.
Cureman works in six steps: it reads an organisation's own data, computes findings from it, prepares the first step of each finding, puts what needs a person into one list of decisions, follows up with whoever owes an answer, and counts a saving only once it is done or billed. A model reads and drafts, code computes every figure, and a person approves everything that goes out.
The six steps
| Step | What happens | Who acts |
|---|---|---|
| Read | Vendor APIs, invoices, mailboxes and AI traffic | The platform; connectors only read |
| Compute | Findings, each with its calculation | The platform |
| Prepare | The first step of a finding is drafted | The platform; nothing is sent |
| Decide | One list of what waits, each row with its worth | A person |
| Follow up | Conversations with a follow-up clock | The platform drafts, a person approves |
| Measure | Savings are counted when done or billed | The platform, from the records |
Read: connectors, invoices, mailboxes, the gateway
- Connectors read seats, plans, renewal dates and activity from the admin APIs of software vendors, and people from the directory. They only read.
- Invoices arrive as uploads, e-invoices, CSV exports or through an ingest endpoint. E-invoices such as XRechnung and ZUGFeRD are parsed without a model. A PDF or a scan is transcribed by a model, checked by arithmetic and labelled as read by the model until a person has reviewed it.
- Mailboxes are Google Workspace or Microsoft 365 accounts connected through the provider's consent page. Only replies to conversations started in the platform are stored; of other mail only the sender is looked at.
- The gateway sits between applications and model providers and records tokens, cost and the model served for each request. The providers' usage reports add spend by provider, model and project. Prompt text is not stored unless the organisation switches samples on.
Compute: findings with their calculation
A finding is produced by deterministic code: the same data gives the same finding. It says what was found, what it amounts to, how the amount was calculated (for example seats times price times months) and how confident it is. A finding that rests on a list price nobody has verified, or on a document only a model has read, is labelled and cannot have high confidence.
Amounts recovered once, such as a duplicate invoice, are kept apart from yearly savings. Some findings carry no figure: a supplier worth asking for a quotation is an action item, and the figure appears when offers arrive.
Prepare: the autopilot drafts the first step
After each analysis run the autopilot takes open findings with direct evidence that nobody has touched and prepares their first step: a draft campaign to seat holders, a drafted message to a vendor or supplier, or a draft sourcing event. It does not approve, send, change anything at a vendor, switch a policy or book a module. What it prepared appears in the list of decisions, marked as prepared.
Decide: one list, three kinds
Everything that waits for a person is in one list: a campaign to approve, a drafted message, an offer a model read from a reply, an invoice to review, a price to verify. Each decision shows its worth: the saving of the finding or the offer behind it, copied with a note saying whose figure it is. Unverified figures are shown and not added up. The list is ordered by deadline first and by worth second, and people see what their role may decide.
The interface keeps three kinds of thing apart, and they never look alike:
- Decide: something waits for a person: an approval, a review, a choice.
- Waiting: something waits for someone outside, such as an employee or a supplier. The row shows the date the platform acts next.
- Automatic: something the platform did or will do without a click, with a line in the audit log.
Follow up: conversations with a clock
Every message to a supplier, a vendor or an employee belongs to a conversation: everything exchanged with one counterpart about one thing. A reply is filed with its conversation and stops the clock. When no reply has come after the number of working days the organisation has set, a follow-up is drafted in fixed wording, without figures, and waits for approval. Only the first follow-up may go out by itself, and only where the organisation has switched that on, because it repeats a message a person approved. After the last one the conversation comes back to a person as unanswered.
Questions to employees escalate as the approved plan says: one reminder and, if the plan includes it, the question passes to the manager. Nobody on the do-not-contact list is asked.
Measure: counted when done or billed
- A licence finding counts once it is marked done: its annual saving, spread over the twelve months after completion.
- An invoice finding counts with the amount recorded as recovered when it is marked done.
- A sourcing saving is measured on later invoices: quantity × (price before − price billed).
- A routed request at the gateway counts with the price difference between the requested and the served model, minus the cost of classifying.
A saving that nobody has quoted or billed is not counted. These measured facts are also the basis of the monthly statement described under pricing. The rules behind each step are in the principles, and the modules say which data each one reads.
Questions and answers
Does the platform act on its own?
- It reads, computes, drafts and keeps track of who owes an answer by itself. Everything that leaves the organisation waits for a person's approval. What goes out without a further click was approved before, such as the reminder that was shown and approved together with a campaign.
What is a finding?
- A finding is something deterministic code detected in an organisation's data, such as seats without activity, an invoice billed twice or a price above an agreement. It states its amount with the calculation behind it and says how confident it is. A finding that rests on an unverified price is labelled and kept out of totals.
What do decide, waiting and automatic mean?
- They are the three kinds of thing the interface keeps apart. Decide means something waits for a person in the organisation. Waiting means something waits for someone outside, such as a supplier or an employee, and shows the date the platform acts next. Automatic means the platform did it without a click, and it has a line in the audit log.
When does a saving count?
- When it is done or billed. A licence finding counts once it is marked done, an invoice finding counts with the amount recorded as recovered, and a sourcing saving is measured on the invoices that follow an agreement. A saving that is only identified is shown as such and is not reported as realised.