How Kestevo Works: What You See, What Changes

The problem in 30 seconds

A procurement manager discovers at quarter-end that a supplier raised prices 8% over six months. The data was in the ERP, the invoices in accounting, the price change in email threads. Three systems, zero alerts. EUR 90,000 in margin lost on a single product line.

This pattern repeats in every manufacturing SME we work with. The data exists — spread across five, six, seven systems. Nobody cross-references it systematically. The CFO spends hours consolidating manual reports. The CEO decides on partial information and gut feeling.

Kestevo exists to close that gap. Not with another dashboard to check, but with a system that does the analysis and delivers conclusions to the people who decide.

What follows is what you actually see when you use it.

Day one: the Health Score

When Kestevo connects to your systems, the first thing you see is a number. From 0 to 100. Your company's Health Score.

It's not a generic rating. It's composed of four pillars, each with its own value:

Financial — margin by product line, DSO trends, revenue concentration across top clients, projected cash flow
Operational — production efficiency, delivery times, scrap rates, bottlenecks
Compliance — CSRD, CBAM, CSDDD deadline status, expiring certifications, reporting obligations
Supply chain — supplier concentration, lead times, delivery reliability, geopolitical risk

The overall number tells you how your company is doing today. The four pillars tell you where to look. If the financial score is 82 but supply chain is 54, you know immediately where to focus.

From day one, the Health Score surfaces anomalies that traditional reports miss. A supplier covering 40% of a critical component. A client representing 28% of revenue who is stretching payments. A margin eroding on a specific product line for three months running.

You don't have to go looking for this information. It's right there.

The weekly briefing

Every Monday morning you receive a brief in your inbox. It's not a summary of numbers. It's a structured analysis of what changed in the previous week, why it matters, and what to do.

A typical briefing contains:

What changed. The Health Score dropped from 71 to 68. The decline is concentrated in the financial pillar: margin on Line B fell 3.2% due to an unabsorbed raw material cost increase from Supplier X.

Why it matters. At current volumes, the erosion is worth roughly EUR 12,000 per month. If uncorrected by quarter-end, the annualized impact exceeds EUR 140,000.

What to do. Three concrete options: renegotiate with Supplier X (the contract allows price revision every 90 days, the window opens in two weeks). Request a quote from Supplier Y, which offers equivalent specifications. Adjust pricing on Line B by 2.5% to absorb the delta.

Every item in the briefing follows this structure. No charts to interpret. No raw data to process. Conclusions and actions, ready to discuss in a management meeting or execute directly.

The briefing covers all pillars: CBAM deadlines approaching, suppliers with systematic delays, strategic clients reducing orders. Everything that needs attention, in one document.

Ask anything with Indaga

The weekly briefing covers the most important items. But during the week, questions come up. Questions that normally require a call to accounting, an extraction from the ERP, a spreadsheet built on the fly.

With Indaga, you ask the question directly. In natural language, in Italian or English.

Examples of questions our users ask regularly:

"What is the real margin on the Rossi order, including indirect costs?"
"What's Supplier Bianchi's average delivery delay over the last six months?"
"If Client Verdi stopped ordering tomorrow, what would the impact on quarterly revenue be?"
"What compliance deadlines do we have in the next 90 days?"
"Compare production costs for Line A between Q1 2025 and Q1 2026"

Indaga answers by drawing on all connected systems. Not from the ERP alone, not from a single spreadsheet. From the full picture. And it cites sources: it tells you which system each data point comes from, so you can verify.

The difference from a generic chatbot: Indaga knows your company. It knows your suppliers, your clients, your products, your contracts. It doesn't give generic answers. It gives answers specific to your context.

Simulate before you decide

Some decisions have consequences that aren't obvious. What happens if steel prices rise 15%? Which product line gets hit hardest? How much margin do you lose if you don't adjust your price list? And if you do adjust it, how much revenue do you risk losing?

Simulations let you explore "what if" scenarios before making a decision.

Scenarios our users simulate:

Raw material cost change. "If resin prices increase 10%, what is the impact on margin and pricing for each product line?"
Losing a supplier. "If Supplier X stops delivering, which products stop? Are there qualified alternatives? What are the replacement timelines?"
Losing a client. "If Client Y cuts orders by 50%, what is the impact on revenue, plant utilization, and breakeven?"
Regulatory scenario. "If CBAM certificates increase to EUR 90 per tonne of CO2, how much does it add to procurement costs?"

Each simulation shows the impact on the Health Score and each pillar. It's not a spreadsheet with formulas to build. It's a model that uses your real data and returns specific numbers.

What connects, what stays the same

Kestevo connects to the systems you already use. No migration, no replacement, no IT project.

Seven categories of connectors:

ERP — SAP, Oracle, TeamSystem, Zucchetti, AS400, and other management systems
CRM — Salesforce, HubSpot, or your internal commercial system
SDI — electronic invoicing, accounts receivable and payable
Email — Gmail, Outlook — for contracts, negotiations, supplier communications that contain information not stored elsewhere
Spreadsheets — Excel and Google Sheets files with data that isn't in the ERP (production plans, budgets, ad hoc analyses)
Contracts and documents — PDFs, shared documents, document archives
Collaboration — Slack, Notion, internal communication tools

Connection takes days, not months. No dedicated IT team required. No training needed. No existing process changes.

Your team keeps working the way they always have. The ERP stays the ERP. The CRM stays the CRM. Kestevo reads from your systems, it doesn't write to them. Nothing changes in your operational flow.

An important point: data stays in Europe. EU infrastructure, GDPR compliant, no extra-EU transfers. For a manufacturing company handling financial data, client records, and supplier contracts, that's not a minor detail.

Every role sees what it needs

Not everyone in the company needs the same information. The CEO doesn't want to see every invoice detail. The CFO doesn't need the plant maintenance schedule. The COO doesn't track tax deadlines.

Kestevo presents different information to different roles:

The CEO sees the strategic view. Overall Health Score, pillar trends, emerging risks, opportunities. The CEO briefing focuses on what requires a management decision: a strategic client changing behavior, a regulatory risk affecting the business model, a risk concentration that needs diversifying.

The CFO sees margins, cash flow, DSO, credit exposure. The CFO briefing quantifies every anomaly in euros and proposes specific financial actions: contract renegotiation, price list adjustments, credit management.

The COO sees production efficiency, supply chain, lead times, bottlenecks. The COO briefing focuses on what's slowing production and how to intervene.

Same data, different perspectives. Nobody gets buried in information they don't need.

First results: weeks, not months

System connection: 3-5 business days. First Health Score available: within the first week. First complete weekly briefing: within the second week. Calibration to your company's specifics: first 4-6 weeks.

This isn't a digital transformation project. It doesn't require a steering committee, a program manager, or six months of requirements analysis. It connects, it starts working.

The most immediate value isn't a specific feature. It's the fact that you stop discovering things late. The supplier raising prices without anyone noticing — flagged at the first anomalous invoice. The client reducing orders — visible after the second week, not the second quarter. The compliance deadline that risked slipping — in the briefing 90 days ahead.

ROI in 90 days isn't a tagline. It's arithmetic. If the weekly briefing saves you even one late decision per month — an early renegotiation, a timely price adjustment, a supplier risk managed before it becomes a problem — the recovered value exceeds the cost of the service within weeks.

If you want to see how it would work with your data, request a free analysis. Within 48 hours, one of our analysts will contact you with specific observations about your industry and your company.