Meeting-room requirements.
What gets built is what was said in a room, not what happens in the operation.
AI by product phase · Discovery
The expensive mistake is made before any code.
Half of all projects fail because they solve the wrong problem. We start by measuring what the problem costs today and deciding whether software is the answer. Sometimes it is not, and we say so.
Building the wrong thing.
Open-ended scope.
With no clear limit, the project grows until the budget runs out.
No cost for the problem.
If you do not know what it costs today, you cannot know whether the solution pays.
Four concrete deliveries.
Two or three weeks. You come out with the decision made, the scope fixed and a budget — even if the decision is not to do it.
-
01
Map of the real process
How it works today, where it breaks and who holds it up. Observed, not assumed.
-
02
Cost of the problem
Hours, errors and lost opportunities, in euros. The basis for deciding.
-
03
Scope and architecture
What is in, what is out and how it gets built. With a fixed price.
-
04
An honest decision
If a process change or an existing tool solves it, that is the recommendation.
-
Scope document
Functionality, limits, risks and acceptance criteria.
-
Fixed estimate
Price and timeline per phase, no open-ended hours.
-
Priority with return
What gets built first and why that before the rest.
What we bring from what is already running.
What stands in for a case of our own here is the method, not a product: the six that are in production all started in this phase, and one of its possible outcomes was not to build. ADG came out of measuring what it cost a public body not to know its digital maturity; Eco-Impacto, out of the fact that the sensor data existed and nobody was looking at it. Measuring the cost of the problem before writing code is what stops you building the wrong thing very well.
Highest-impact use cases
-
01
The cost of the problem, in euros
Hours from the people holding it together by hand, errors that get paid for and opportunities lost. Without that number there is no way to know whether software pays off.
Turns a hunch into an investment decision.
-
02
The real process, not the one in the manual
We interview whoever operates it and follow one case end to end. Almost always two steps show up that nobody knew existed.
Scope stops resting on what people think happens.
-
03
Closed scope, with what is left out written down
What is in, what is not and in what order. What is out gets documented so it cannot come back through the side door halfway through.
It is what stops scope opening on its own.
-
04
The answer can be no
If the problem is solved by changing the process, buying something that already exists or doing nothing, we say so. Charging to build the unnecessary is easy and expensive for both sides.
A timely no is worth more than a whole project.
What it is built with.
Before you call us, read this.
-
First Optimizer, Second AI: why the real brake on AI is not the tool
The industry has fallen in love with "AI-first". But the real bottleneck in adoption was never technological: it is the absence of a way of thinking about processes. A reflection on the discipline that should come before touching AI.
-
How to prioritise AI integration in your company: a quantitative model
Where do you start implementing AI? Most people answer with a hunch. But deciding where AI goes is a quantifiable problem: it has variables, formulas and a rankable result. This article is that model, with a case worked through step by step.
- Design Architecture, flows and data model before the code.
- Build Code with tests, reviewed and signed off by an engineer.
- The AI inside Agents and models integrated where they multiply.
- Validation Security, performance and accessibility before shipping.
- Operation and scale Live, measured and with the internal team in charge.
Not sure where to start? Measure your organisation’s AI maturity for free in 3 minutes, or book 30 minutes of direct diagnostic.
Let's start
Let's talk about your operation.
Tell us what costs more than it should. We come back with a concrete plan, realistic timelines and a clear yes or no.
contacto@plantekia.com