Aiguro

Aiguro for IT

licence, cloud and vendor-contract savings with evidence

Turn licence lists, cloud bills and vendor contracts into validated FinOps savings hypotheses - with the invoice line or contract clause attached as evidence. See a real hypothesis card built on a licence sprawl finding.

Request access tell us about your team and we will get in touch to set up your workspace.

Hypothesis card: Reclaim inactive SaaS licences at the next contract windows The worked hypothesis from the it sample workspace. Method QU-6 Pooling of licences and reduction of needs, potential EUR 173,000 to 250,000 (45-65% of EUR 384,468 inactive licence cost, depending on contract windows.), effort 1 of 5, complexity 2 of 5. Supported by collaboration-suite-agreement.md, contradicted by crm-order-form.md on 'Reducible within 12 months'. Hypothesis In progress Reclaim inactive SaaS licences at the next contract windows METHOD QU-6 Pooling of licences and reduction of needs POTENTIAL EFFORT COMPLEXITY EUR 173k - 250k 45-65% of EUR 384,468 inactive licence cost, depending on contract windows. EVIDENCE Supports collaboration-suite-agreement.md Contradicts crm-order-form.md challenges: Reducible within 12 months From licence-inventory-2025.csv Sample workspace, fictitious data

The problem

"Our licence and SaaS spend grew faster than anyone tracked it, and nobody owns cleaning it up."

"Renewal season is here and we don't have a clear picture of what we actually use."

"The cloud bill keeps growing and finance wants an explanation, not a guess."

How it works

  1. Upload licence lists, cloud bill exports, vendor contracts.
  2. Findings Aiguro's discovery strategies surface licence, cloud and vendor-contract signals from your documents, news and market events.
  3. Hypotheses findings become structured hypotheses with a method, potential, effort and evidence.
  4. Pipeline a pipeline of licence, cloud and vendor levers ready to prioritise ahead of the next renewal cycle.
How Aiguro works Your business data, documents and market news feed scheduled discovery. Discovery turns them into findings, findings into hypotheses with a method, potential and evidence, and hypotheses into a prioritised pipeline of cost and efficiency levers. Underneath, a knowledge graph remembers every document, finding, decision and rejection, feeds that knowledge back into findings, hypotheses and the pipeline, and steers the next run. Your data Business data Documents News, markets Discovery Scheduled strategies analyse and cross-reference Findings Signals with evidence Hypotheses Method Potential Evidence Pipeline Prioritised Knowledge graph remembers every document, finding, decision and rejection remembered steers the next run

Proof

A worked example from the sample workspace: a licence list, a cloud bill export and two vendor contracts turn into a licence sprawl hypothesis with the invoice line attached as evidence.

Every hypothesis draws on the method catalogue, covering licence and SaaS optimisation, cloud FinOps and vendor contract levers. Your data stays yours: one isolated database per team, EU hosting, no training on customer data.

Why not a chatbot

A generic AI assistant starts every conversation from zero. Aiguro remembers what your team uploaded, found, decided and rejected, connecting licence lists, cloud bills and contracts in a knowledge graph - so a renewal decision from last quarter is never re-proposed and a new invoice is automatically checked against what you already know.

Value compounds: in week one it looks like a good chatbot; by month three the graph is steering every new analysis and findings arrive without anyone asking. See the full picture on the comparison page.

A chat window forgets, the Aiguro workspace remembers Left: a generic AI assistant starts every session from zero and suggests the same idea again. Right: in an Aiguro workspace every document, finding, hypothesis and rejection is a node in a knowledge graph. One contract supports the hypothesis, another contradicts it, market news supports the finding it was derived from, and a rejected idea that is similar is not proposed again. Generic AI assistant MONDAY Have you tried renegotiating this contract? starts from zero NEXT WEEK Have you tried renegotiating this contract? starts from zero NEXT MONTH Have you tried renegotiating this contract? starts from zero Aiguro workspace Every item becomes a node; enrichment links them supports derived from derived from contradicts similar to supports Contract A Spend export Finding Market news Contract B Rejected idea Hypothesis Not proposed again - already rejected

Pricing

Small Team a flat monthly price, 3 users, 1 shared workspace. The learning plan for an IT or FinOps team piloting the tool, no seat maths.

Pro priced per user, minimum 3 seats, workspaces scale with seat count, includes SSO. Built for IT teams running FinOps across a growing licence and cloud estate.

Enterprise custom, sales-led, for company-wide rollouts, SSO enforcement and negotiated contracts. Includes the Valuedesk integration: connect Valuedesk and export hypotheses to it. Talk to sales.

AI usage runs on a monthly credit budget: 5,000 credits on Small Team, 2,000 credits per user on Pro, custom on Enterprise. Chat, discovery runs and document analysis draw on it in proportion to the AI work they do - a quick question costs a few credits, a deep discovery run more. When the budget is used up, AI features pause until the next billing period or an upgrade.

FAQ: seats and workspaces every user also gets a private default workspace that never counts against your quota; shared workspaces are what the quota limits.

Security and compliance

Every team gets its own isolated database - never a shared schema. Data is hosted in the EU, and nothing you upload is used to train models. Pro and Enterprise include SSO (Entra ID); role-based access controls who can see and edit each workspace. A standard Data Processing Agreement (GDPR Art. 28) is available for download, with the sub-processor list published alongside it.

One isolated database per team, hosted in the EU Every team gets its own database, never a shared schema, inside EU hosting, with SSO and role-based access. AI models answer requests from the workspace and are not trained on customer data. EU hosting Your team SSO, role-based access Own database Another team SSO, role-based access Own database Another team SSO, role-based access Own database AI models Answer requests from your workspace No training on your data

FAQ

Do I need a FinOps analyst on the team? No - upload what you already have (licence lists, cloud bills, contracts) and Aiguro's discovery strategies do the first pass.

Does it replace our ITAM or FinOps tooling? No - hypotheses export into the programme tool you already use; Aiguro is where they are found and validated.

What happens to our data if we cancel? It stays yours and visible during the read-only period after cancellation; nothing is deleted immediately.

Can we try it before committing? Request access and we will get in touch to find the right way to start with your own documents.