How Kestevo works

The most common question from companies evaluating Kestevo is also the simplest one: how does it actually work? Not what it promises, not what it does "in theory", but what happens between day one and the moment your business starts getting value.

Three steps. Seven to ten days in total. No IT project.

1. It connects to your systems, in hours

On day one Kestevo connects to your ERP, CRM, e-invoicing (SDI), email, spreadsheets, contracts and document repositories. The connection is read-only: Kestevo reads, doesn't write, doesn't move data, doesn't touch your processes.

You don't need to clean your data first. Kestevo is built specifically to work on data as it is: messy, duplicated, incomplete, spread across different systems. A traditional integrator promises "tidy up first, then integrate". We promise the opposite: bring what you have, we'll handle the rest.

Traditional integration	Kestevo
3-6 months of setup	One day of setup
IT project with a dedicated team	Pre-built connectors
Requires upstream data cleanup	Works on existing data
Manual mapping per system	Automatic reconciliation
Changes internal processes	Leaves your processes alone

What you do at this stage: grant access to the systems (SSO or dedicated service credentials) and name an internal contact who can clarify questions if they come up. Everything else happens in the background.

2. It processes in the background, for a few days

Over the next two to four days, Kestevo processes what it has read. Not in production, not under your eyes: in a dedicated pipeline that reconciles entities (clients, suppliers, products, contracts), reconstructs timelines and resolves inconsistencies.

Here's the interesting part. The same record often exists in several versions. Supplier "ALFA SRL" in the ERP is "Alfa Srl" in the CRM, "alfa@alfa.it" in email threads, and "VAT 01234567890" in contracts. Kestevo figures out on its own that those are the same entity, deduces which source is authoritative for each attribute (VAT from the contract, commercial email from the CRM, payment status from accounting) and keeps track of meaningful divergences so it can flag them later.

If it really can't decide, and that's rare, it asks. Not serially, not with a spreadsheet to fill out. Targeted questions when the stakes are high: "Supplier X in the ERP and Supplier Y in the contracts look like the same entity but have different VAT numbers: spin-off, anagraphic error, or two different companies?". One choice, one click, moving on.

What it resolves on its own	What it asks you
Same entity, different names	Recent mergers, spin-offs, asset sales
Typos and abbreviations	Ambiguous legal-name changes
Inconsistent dates across systems	Amount conflicts above a threshold
Multiple versions of the same document	Specific company-policy cases

From your side, you see a status dashboard with progress per category. When processing finishes, you get a notification with your company's first Health Score.

3. From here on, it reasons

Once setup ends, Kestevo isn't a project anymore: it's an active service that watches the flow of data through your systems and signals when issues, operational inefficiencies or opportunities emerge.

What "reasoning" means, concretely:

• It answers any question about your business. Ask Kestevo in plain English: "what's the real margin on the Bianchi project, indirect costs included?". It answers by drawing on every connected system, citing the source of each number. No reports to build, no ERP extractions.
• It signals when something changes. A supplier raising prices quietly. A client stretching payment terms. A CSRD deadline 90 days out with a supplier filing for restructuring. Kestevo sees it before you do and sends you a signal: what happened, why, and what to do.
• It predicts scenarios. "If steel goes up 15%, which lines suffer?". Kestevo applies the hypothesis to your real data and returns specific numbers, not generic templates.

From this point on, your involvement drops to near-zero. Nothing to update, nothing to sync, no pipeline to maintain. Your systems keep doing what they were doing. Kestevo sits on top, quietly, until it has something worth telling you.

Three steps, one line each

Phase	Duration	What Kestevo does	What you do
Connection	A few hours	Connects read-only to your systems	Grant access, name a contact
Processing	2-4 days	Reconciles, deduces, tracks divergences	Answer targeted questions, if needed
Operation	Continuous	Answers, signals, predicts	Decide on proposed actions

What Kestevo doesn't do

Worth saying explicitly what Kestevo doesn't promise.

It doesn't replace your ERP. It doesn't ask your team to learn a new tool. It doesn't write into your systems. It doesn't generate reports in place of your controller, doesn't make decisions in your place. It doesn't promise outcomes without someone inside the company reading the cards, validating them and acting.

What it does is close one specific gap: between the data your business already produces and the decisions your people already make. Nothing more, nothing less.

Want to see it on your data?

We're picking the first companies for the private pilot. If you're curious to see what would emerge in your specific context, request pilot access. When we open the next slot, we'll reach out with a first read on your business.