FAQ

FAQ: what buyers, IT, finance and security ask first

Updated Markdown
In short

The questions buyers, IT leads, finance leads and security reviewers ask about Cureman before a first call, each with an answer that stands on its own. They cover which data is needed to start, what happens to prompts and documents, who can see figures, how savings are measured, what happens when a supplier or an employee does not answer, running the product under an organisation's own name, connecting an organisation's own assistant, what the AI is not allowed to do, and how a pilot starts.

Before a first call, buyers, IT leads, finance leads and security reviewers tend to ask the same questions about Cureman. This page answers them one by one, and each answer stands on its own. None of them promises a result or a date: what a saving amounts to is known once it has been computed from an organisation's own data.

Four pages go deeper than the answers below. How it works follows the path from data to a saving that is done. The principles list what the AI may do and what a person decides. Pricing explains what each module meters and which kinds of terms exist. Security describes sign-in, permissions, tenant isolation and how secrets are kept.

What the platform covers is split into modules that are booked one by one, and the module list says what each of them reads, finds and measures. Terms that are unfamiliar are defined in the glossary.

Questions and answers

Which data do we need to start?

One source is enough to start with one module. For licences that is an API credential for a vendor's admin interface, for invoices a set of invoices as e-invoices, PDFs or a CSV export, and for AI costs the usage reports of a model provider or one application pointed at the gateway. Connectors only read, and further sources can be added later.

What happens to the prompts our applications send through the gateway?

The gateway forwards each request to the model provider the organisation configured, with the organisation's own provider key, and it never changes the caller's own conversation. For each request it stores token counts, cost, the task type and a user reference. Prompt and response text is not stored unless the organisation switches prompt samples on. Where a request is classified or a long conversation is shortened, excerpts go to a small model at the same provider the full prompt goes to anyway.

Where do invoices and supplier replies go when a model reads them?

A PDF, a scan or the text of a reply is sent to the model provider the operator has configured. What comes back is stored as data, checked by arithmetic and labelled as read by the model until a person has reviewed it. Structured e-invoices such as XRechnung and ZUGFeRD and CSV exports are read without a model, so an organisation can choose ways in that involve none.

Who in our organisation can see prices and savings?

Only people whose role holds the permission to see figures. Among the built-in roles, procurement, finance, budget owners and auditors see them, the IT admin role works without contract figures, and employees who only answer questions see none. An organisation can define roles of its own from the same permissions, and the digest mail leaves figures out for people who may not see them.

How is a saving measured, and when does it count?

Every saving is measured from records, and it counts when it is done or billed. A licence finding counts once it is marked done, an invoice finding with the amount recorded as recovered, and a sourcing saving on later invoices as quantity times the difference between the price before and the price billed. Amounts recovered once are kept apart from yearly savings, and a saving nobody has quoted or billed is not counted.

What happens when a supplier does not answer?

Every conversation has a follow-up clock. After the number of working days the organisation has set, a follow-up is drafted in fixed wording and waits for approval; only the first one may go out by itself, and only where the organisation has switched that on. After the last follow-up the conversation comes back to a person as unanswered, to call, try another contact or close it. Requests of a sourcing event follow the event's deadline instead, with one reminder before it.

What happens when an employee does not answer a question about a licence?

The person gets the reminder that was shown and approved together with the campaign. If the approved plan includes it, the question then goes to the person's manager; that step is off unless the organisation switches it on. No seat is removed because somebody stayed silent. Whoever is on the organisation's do-not-contact list is never asked at all.

What does running it under our own name involve?

An organisation sets its product name, logo and accent colour and can register host names of its own for the dashboard and for the gateway endpoint. Each host name is trusted only after a DNS record has proved control of it, and it is used in links once the operator has put a certificate in place. Text that employees and suppliers see never names the platform, and with a connected mailbox messages go out from the organisation's own address.

What can our own AI assistant do once it is connected?

Over MCP it can read purchasing data, including an overview of spend, the items that could be put to suppliers, delivery sites, suppliers and earlier sourcing events. With the scope to propose it can leave a proposal for a request for quotation, whose quantities and amounts are computed from invoices and which a person approves or dismisses. A key can be made blind to amounts. The assistant cannot send, approve, award or change anything, and this access belongs to the sourcing module.

What is the AI not allowed to do?

It may not produce a figure that is displayed as fact, and a draft that states a figure of its own is discarded. It may not send a message, approve, award, change anything at a vendor, switch a policy or book a module. An agent that works in a website enters only approved values and never sees a login. These limits are part of the product and cannot be switched off by a setting.

Does it replace our accounting system or our invoice archive?

No. It works on invoices and exports from those systems and keeps a copy of each document for checking and analysis. It does not post or pay anything, and it is not an archive. The accounting system stays the system of record, and invoices still have to be kept where the organisation keeps its business records.

How does a pilot start?

With one module and one source of data. The operator creates the organisation with its first owner, who signs in with a one-time code, adds colleagues and assigns their roles. Then one vendor is connected, a set of invoices is imported or one application is pointed at the gateway, and findings appear with their calculation. Nothing is sent to anyone until a person approves it, and the terms that apply are agreed with the operator.