Mindden
EN·ES Contact

Home / How we work

We start with your problem, not with the technology.

Four phases with fixed deliverables and timelines. You decide how far to advance in each one — and the KPI is agreed before we begin.

KPI firstThe outcome is agreed and measured. No project without a number.
No migrationsWe work on your ERP, CRM or SCADA exactly as they are.
Governance built inPermissions, traceability and measured cost from day one.
Integrated teamsSquads that work with your people, not alongside them.
The four phases

From the first meeting to continuous operation.

01

Diagnosis

2–3 weeks

Working sessions with operations and systems to understand the real process — not the one in the manual — and prioritize where the technology pays off.

What we do

  • Workshop session with operations and systems
  • Analysis of available data and processes
  • AI maturity assessment

Who takes part

  • Your operations and systems leadership
  • Our area lead
  • A senior domain engineer

Deliverable

  • Dossier with 3–5 prioritized use cases
  • Estimated impact and effort per case
  • A recommendation on where to start
02

Proof of value

4–8 weeks

A pilot with real data on a bounded scope and an agreed KPI. If the number doesn't add up, you know early and cheaply.

What we do

  • Development on the real data of the case
  • Bounded integration with your systems
  • Continuous measurement against the KPI

Who takes part

  • Business sponsor for the case
  • Mindden squad: engineering + data
  • Your systems team, without overload

Deliverable

  • A working system in a real environment
  • Impact measured against the KPI
  • An industrialization plan with costing
03

Industrialization

8–12 weeks

From pilot to system: deployment on your infrastructure — cloud or on-premise — with governance, traceability and controlled cost.

What we do

  • Full deployment and integration
  • Permissions, audit trails and monitoring
  • Training for your teams

Who takes part

  • Mindden squad + your IT
  • Your own QA and security
  • Key operational users

Deliverable

  • A documented system in production
  • A dashboard for the KPI and the cost
  • A support and evolution agreement
04

Continuous operation

Ongoing

Support, evolution and continuous improvement. Each use case strengthens the next: the knowledge from the first lowers the cost of the second.

What we do

  • Support backed by service-level agreements
  • Evolution driven by a quarterly roadmap
  • Periodic review of impact

Who takes part

  • Support and operations team (C.A.T.)
  • Your process owner
  • A quarterly steering committee

Deliverable

  • A quarterly impact report
  • A prioritized backlog of improvements
  • New candidate use cases
Entry points

Three ways to start, depending on your maturity.

A

Opportunity mapping

You don't yet have a prioritized case

Starts in phase 01. You leave with a dossier of prioritized use cases — and the judgment to decide, whether or not you invest with us.

2–3 weeks
B

Proof of concept

A case with a defined sponsor and scope

Goes straight into phase 02: a pilot with real data and impact measured against an agreed KPI.

4–8 weeks
C

Agentic platform

You want the capability in-house

Deployment of the platform on your infrastructure and the first use cases on top of it, with training for your teams.

8–12 weeks