---
title: "Sitemap: every page of this site"
description: "Every page of the Cureman site in English: modules, articles by subject and reference pages, with links to the machine-readable versions."
url: https://www.cureman.de/en/sitemap
language: en
updated: 2026-11-17
alternate_de: https://www.cureman.de/de/sitemap.md
---

# Sitemap

> Every page of this site in English. The same list for crawlers is at /sitemap.xml, and for assistants at /llms.txt.

- [Home](https://www.cureman.de/en)

## Modules

- [Licence optimisation: seats, plans and renewals](https://www.cureman.de/en/modules/licence-optimisation): The licence optimisation module reads seats, plans and activity from vendor APIs, finds unused seats and oversized plans, and asks seat holders after approval.
- [AI spend audit: model costs by provider, model and project](https://www.cureman.de/en/modules/ai-spend-audit): The AI spend audit reads usage reports from model providers, prices every token against a model price list and shows spend by provider, model and project.
- [AI gateway: one endpoint that meters, classifies and routes](https://www.cureman.de/en/modules/ai-gateway): The AI gateway sits in front of every model provider, records tokens and cost per request and, under your policy, serves simple requests from a cheaper model.
- [Context optimiser: long conversations sent with less history](https://www.cureman.de/en/modules/context-optimiser): The context optimiser leaves earlier exchanges that a long conversation no longer needs out of the upstream request, and only when that is computed to pay.
- [Prompt insights: what the models are asked to do, and by whom](https://www.cureman.de/en/modules/prompt-insights): Prompt insights classify gateway traffic by task, attribute it to users and tags, and recommend a better-suited tool where the numbers support it.
- [AI workspace: an employee chat paid by the tokens used](https://www.cureman.de/en/modules/ai-workspace): The AI workspace is a chat front end for employees on the AI gateway. You pay the provider for the tokens used instead of a seat licence for everyone.
- [Invoice audit and spend analysis: every invoice read and checked](https://www.cureman.de/en/modules/invoice-audit-and-spend-analysis): The module takes invoices as PDFs, e-invoices or CSV, checks each line against its arithmetic, earlier invoices and agreed prices, and adds up the spend.
- [Sourcing and negotiation: quotations, rounds and agreed prices](https://www.cureman.de/en/modules/sourcing-and-negotiation): The sourcing module turns what you buy into a request for quotation, compares the offers by arithmetic and prepares each negotiation round for your approval.

## Articles: Software licences

- [SaaS licence management: what to track and when](https://www.cureman.de/en/articles/saas-licence-management-basics): What SaaS licence management is, which records to keep for every application (seats, plans, renewals, owners) and the yearly rhythm that keeps them true.
- [Reducing software costs: where to look first](https://www.cureman.de/en/articles/reduce-software-costs): Seven places to look when software costs have to come down, ordered by how strong the evidence is and how soon the money stops flowing.
- [How to find unused software licences](https://www.cureman.de/en/articles/find-unused-software-licences): A step-by-step method to find unused software licences from the vendor's own data, ask the seat holders, and remove seats before the renewal date.
- [Right-sizing SaaS plans](https://www.cureman.de/en/articles/right-size-saas-plans): When a cheaper SaaS tier is enough, how to set a usage threshold per tier, when to ask the seat holder, and how to compute the saving of a downgrade.
- [Asking employees about their licences](https://www.cureman.de/en/articles/ask-employees-about-licences): How to ask seat holders whether they still need a licence, with the wording, the answers, one reminder, the manager step and the people who are never asked.
- [Preparing a SaaS renewal](https://www.cureman.de/en/articles/prepare-saas-renewal): How to prepare a SaaS renewal. Work out the notice date, the seats you need and the plan mix, and decide what to ask the vendor for before the deadline.
- [Overlapping SaaS tools: find and consolidate them](https://www.cureman.de/en/articles/overlapping-saas-tools): How to find two SaaS applications that do the same job, count the people who hold a paid seat in both, and consolidate at the renewal of the tool you drop.
- [Licences at offboarding: seats of people who left](https://www.cureman.de/en/articles/offboarding-licences): How to find paid seats still held by people who have left by joining each seat list with the directory, and how to close the gap in the offboarding process.
- [Microsoft 365 licences: plans, inactive accounts, right-sizing](https://www.cureman.de/en/articles/microsoft-365-licence-optimisation): Which Microsoft 365 licences can go or move to a lower plan, found from purchased licences, assigned accounts, last sign-in and a question to the holder.
- [Shadow IT: find software nobody approved](https://www.cureman.de/en/articles/shadow-it): How to find software that departments bought themselves, using invoices, card statements and the application inventory, and what to do with each find.

## Articles: AI costs

- [Reducing AI costs: the levers, from model choice to context](https://www.cureman.de/en/articles/reduce-ai-costs): The levers that lower a model bill, in the order to pull them. Measure first, then model choice, output length, prompt caching, context, repeats and budgets.
- [How to audit AI spend in five steps](https://www.cureman.de/en/articles/how-to-audit-ai-spend): Audit AI spend from the providers' own usage reports. Price every token, reconcile with the invoice, and break the total down by provider, model and project.
- [LLM token costs explained: input, output and cached tokens](https://www.cureman.de/en/articles/llm-token-costs-explained): What input, output and cached tokens are, why output tokens cost more than input tokens, and how to compute the cost of a single LLM request step by step.
- [What is an LLM gateway, and when do you need one?](https://www.cureman.de/en/articles/what-is-an-llm-gateway): An LLM gateway is a proxy between your applications and the model providers. What it meters per request, how upstreams and keys work, and when it is worth having.
- [LLM model routing: simple requests on a cheaper model](https://www.cureman.de/en/articles/llm-model-routing): How model routing works. Classify each request, set thresholds in a policy, serve simple requests from a cheaper model, and measure the price difference per request.
- [Prompt caching and context trimming for long conversations](https://www.cureman.de/en/articles/prompt-caching-and-context): How prompt caching and context trimming lower the input cost of long LLM conversations, how to compute each, and when trimming costs more than it avoids.
- [AI chat for employees: seat licence or pay per token](https://www.cureman.de/en/articles/ai-chat-seat-licence-or-pay-per-token): How to compute, per person, whether an AI chat seat licence or paying per token is cheaper, with the break-even formula and a worked example.
- [How to allocate AI costs to teams, projects and people](https://www.cureman.de/en/articles/allocate-ai-costs-to-teams): A method to attribute LLM spend to teams, features and people with keys, tags and user identifiers, price every request and reconcile with the provider.
- [AI budgets and limits: per key, per user, per model](https://www.cureman.de/en/articles/ai-budgets-and-limits): How monthly budgets per API key and per user and model allow-lists work for LLM spend, what happens at the limit, and how to set the amounts.

## Articles: Invoices and spend

- [Invoice audit checklist: what to check on every invoice](https://www.cureman.de/en/articles/invoice-audit-checklist): Six checks for every supplier invoice before it is paid: formal details, arithmetic, price, duplicate, billing period and bank details, each with its rule.
- [How to detect duplicate invoices before and after payment](https://www.cureman.de/en/articles/detect-duplicate-invoices): Matching rules for exact and near duplicate invoices: normalised invoice numbers, amount and date, credit notes, and what to do once a duplicate is found.
- [How to find price increases on supplier invoices](https://www.cureman.de/en/articles/price-increases-on-invoices): Build a unit price history per item and supplier from invoice lines, spot the increase, compute what it costs per year and check it against the agreement.
- [Spend analysis basics: from invoices to a spend cube](https://www.cureman.de/en/articles/spend-analysis-basics): How to build a spend analysis from invoice lines: clean suppliers, items and units, assign categories, and read spend by category, supplier, item, month and site.
- [E-invoices: XRechnung, ZUGFeRD and what changes for checks](https://www.cureman.de/en/articles/e-invoices-xrechnung-zugferd): What an e-invoice is under EN 16931, how XRechnung, ZUGFeRD, Factur-X and Peppol differ, what German VAT law requires, and which invoice checks change.
- [Changed bank details on an invoice: catch it before paying](https://www.cureman.de/en/articles/changed-bank-details-on-invoices): How payment diversion fraud works, the warning signs on an invoice, and the control that stops it: compare the account with the record and verify by call-back.
- [Tail spend: how to see and bundle small purchases](https://www.cureman.de/en/articles/tail-spend): What tail spend is, how to measure it from invoices by supplier, invoice count and category, and how to bundle the purchases that repeat.
- [Early-payment discounts: when they pay and how not to miss them](https://www.cureman.de/en/articles/early-payment-discounts): When an early-payment discount is worth taking, how to compare it with the cost of paying early in plain amounts, and how to find the invoices that offer one.

## Articles: Sourcing

- [How to write a request for quotation (RFQ)](https://www.cureman.de/en/articles/write-a-request-for-quotation): What a request for quotation must contain so that offers come back comparable: items, yearly quantities, delivery terms, a deadline and one answer format.
- [How to compare supplier offers on the same basis](https://www.cureman.de/en/articles/compare-supplier-offers): Compare supplier offers by arithmetic: same unit and quantities, shipping per year, incomplete offers kept apart, and a comparison table that shows every step.
- [Negotiation rounds with suppliers: targets and wording](https://www.cureman.de/en/articles/negotiation-rounds-with-suppliers): How to run negotiation rounds with suppliers: target prices taken from the comparison, what may be said about other offers, and when to stop and award.
- [Sourcing for multiple delivery sites](https://www.cureman.de/en/articles/sourcing-for-multiple-sites): How to buy for several delivery sites: quantities per site from invoices, one request or several, comparing offers site by site with freight, and site prices.
- [How to follow up with suppliers who do not answer](https://www.cureman.de/en/articles/follow-up-with-suppliers): When and how to follow up with a supplier who has not answered: timing, wording, what counts as an answer, when to escalate, and how to keep the thread.
- [Checking invoices against agreed prices](https://www.cureman.de/en/articles/price-agreements-on-invoices): How to check later invoices against agreed prices line by line, claim back what was billed above them, and measure the saving on what was actually billed.

## Articles: AI in procurement

- [AI in procurement: what works today and where a person decides](https://www.cureman.de/en/articles/ai-in-procurement): What a language model does reliably in purchasing today, what belongs to plain code, and which steps stay with a person. With a table by task.
- [Human approval for AI agents in procurement](https://www.cureman.de/en/articles/human-approval-for-ai-agents): What an AI in procurement may do alone, what needs a person's approval, and how to design the approval point so that it is a real check.
- [Why AI must not invent figures in procurement](https://www.cureman.de/en/articles/why-ai-must-not-invent-figures): A language model writes plausible numbers, not computed ones. How to keep model-made figures out of savings reports, supplier messages and invoice data.
- [MCP in procurement: connecting your own AI assistant](https://www.cureman.de/en/articles/mcp-in-procurement): What the Model Context Protocol is, how it connects a company's own assistant to procurement data, and why the assistant should read and propose only.
- [How to prove procurement savings](https://www.cureman.de/en/articles/prove-procurement-savings): A method for proving procurement savings. Keep in question, agreed and realised apart, separate one-off from yearly, and measure on invoices.
- [Browser agents for vendor portals: five rules](https://www.cureman.de/en/articles/browser-agents-for-vendor-portals): How to let an AI agent work in a vendor's or supplier's website. Approved values, allowed hosts, hidden logins, a stop before submit and a full record.
- [The procurement decision list: one place for approvals](https://www.cureman.de/en/articles/procurement-decision-list): One list of everything in procurement that waits for a person, ordered by deadline and worth, with decide, waiting and automatic kept apart.

## Pages

- [Request a demo: the list for a company like yours](https://www.cureman.de/en/demo): Ask for a demo of Cureman. We build a fictional organisation that fits your company and show what the platform finds there.
- [How it works: from your data to a saving that is done](https://www.cureman.de/en/how-it-works): Cureman reads vendor APIs, invoices, mailboxes and AI traffic, computes findings, prepares the next step and follows up. A person decides what goes out.
- [Privacy notice for this website](https://www.cureman.de/en/privacy): Which personal data this website processes, for what purpose, on which legal basis and for how long, and the rights you have towards its operator.
- [Principles: what the AI may do and what a person decides](https://www.cureman.de/en/principles): The rules built into Cureman. Code computes every figure, unverified data is labelled, and nothing leaves the organisation without a person's approval.
- [Pricing: a platform, booked modules and what each one meters](https://www.cureman.de/en/pricing): How Cureman is charged. The platform plus the modules you book, each stating what it meters. Terms are agreed per organisation, so this page names no rates.
- [Security: how access, data and automation are controlled](https://www.cureman.de/en/security): The controls built into Cureman. Sign-in by one-time code, permissions, tenant isolation, encrypted secrets, read-only connectors and an audit log.
- [Glossary: terms of licences, AI costs, invoices and sourcing](https://www.cureman.de/en/glossary): Short definitions of the terms used in software licence management, AI cost control, invoice audit, spend analysis and sourcing, and in Cureman itself.
- [FAQ: what buyers, IT, finance and security ask first](https://www.cureman.de/en/faq): Answers to the questions asked before a first call about Cureman, on data needed, prompts, who sees figures, measured savings, follow-ups and limits of the AI.
