

The scope gets settled first: what needs to be built, which systems and data are there to build on, and the benefit the result should bring. All three are answered before an estimate is given, so the benefit is fixed before the first line of code and the result can be measured against it.

Feasibility, PoC, Cost
Feasibility gets checked before any money is committed: a small proof of concept tests the approach on the real task, with real data. It produces a solid cost estimate for the full build, broken down by component, and the decision on whether to build at all follows from it.

Delivery and Contact
Before the work starts, the plan names who delivers which part and who answers questions on both sides. Every task has one person behind it, with a deadline and the criteria it gets accepted against, so from day one it is clear who to reach when something is off track.
Fixed Before Spend
the target and its benefit are agreed before you commit budget
Test Before Build
the cost estimate comes from a real test on your own task
Clear Ownership
every deliverable is assigned to a name and a fixed deadline
Direct Line
named contacts on each side are fixed before work starts
From Scope to a Costed Plan
Settle the Goal and the Baseline 3 steps
01
The Build Target
The scope starts with a plain description of what needs to be built: which problem it solves, for whom, and how far it reaches. That description is written down before anything gets planned or estimated, so everyone involved starts from the same goal.
02
Systems and Data in Place
Existing systems, data and processes are mapped before anything new is built: which applications run today, which data is there and which parts of the task are solved. What the business has stays in use and gets built on.
03
The Expected Benefit
Every project states the benefit it should bring, in time, money or quality, and how that benefit will be measured. It is written down before the start, so the result can be checked against it later.
Check Feasibility and Cost 3 steps
04
Technical Feasibility Checked
Before any money is committed, the requirement gets checked against the systems and interfaces in place. Open technical questions are named and settled one by one before the build starts.
05
A Proof of Concept on the Real Task
A small proof of concept tests feasibility on the real task, with real data. The result shows whether the chosen approach holds before the full build starts.
06
A Cost Estimate for the Full Build
The proof of concept produces a solid cost estimate for the full build, broken down by component. The estimate is on the table before the decision, and it gets checked against the actual effort once building starts.
Delivery Owners 2 steps
07
Delivery per Task
Every task in the build gets a name behind it: who delivers it, by when, and what it gets accepted against. That assignment is fixed in the plan before the work starts.
08
One Owner Per Deliverable
Each deliverable has exactly one person responsible for it, from the first prototype to the handover, recorded in the plan next to the task.
Contact and Handover 2 steps
09
A Named Contact on Both Sides
Each side has one fixed contact for questions. Who decides on a deviation and who is reachable day to day is named before the start and recorded in the plan.
10
Handover With Clear Contacts
The plan leaves this phase with the target, the cost estimate and the list of contacts on both sides. That is what the build starts from without further back and forth, and what any later deviation gets measured against, by name.
Frequently Asked Questions
What does this phase hand over?
Three things: the written target with its expected benefit, a cost estimate for the full build from a proof of concept on the real task, and the plan with one owner per deliverable and a named contact on each side.
Does the proof of concept use our own data?
Yes. The proof of concept runs on the real task with real data, so the cost estimate rests on how the approach performs in your business.
What does a proof of concept cost?
A small proof of concept is billed in recorded hours at the stated rates, and it buys the cost estimate for the full build before any larger budget is committed.
Is the DSGVO and EU AI Act review a separate project?
It runs in the same pass, before AI reaches company data. The systems in production are checked, the risk tier under the EU AI Act is classified, and the places where personal data is processed are identified. Tasks involving personal data are flagged and reviewed, with onboarding material per role so people outside IT can act on it.
