Work flow
How we work
10 steps. One order. Each phase starts when the previous one is closed.
Here we explain what happens, what is decided and why each step exists.
The process
- 01–03
Entry
Contact, listening and first assessment.
- 04–05
Agreement
Initial proposal, contract and payment.
- 06–08
Execution
Audit, development and implementation.
- 09–10
Handover
Delivery and optional maintenance.
Step by step
Entry
01
Contact
You write or call and explain what you need. We listen. We do not propose yet.
Why
Proposing before we hear you would sell our work, not solve yours.
Entry
02
Listening
We hear the request and ask for the missing material. We record situation, goal and timeline. We do not close a diagnosis yet.
Why
Without data and a clear request we would invent the problem.
Entry
03
First assessment
We decide if the job needs a system. If it is not our work, we say so. If it is, we open the proposal.
Why
Not every request needs a system. Deciding it here avoids unnecessary work and cost.
Agreement
04
Initial proposal
We record the request, situation, goal, problem, system and terms. We give an indicative price. It is not the final quote.
You decide if it makes sense to continue.
Why
You need to know what we would do and at what cost before you sign.
Agreement
05
Contract and payment
We formalize the contract and receive the agreed payment. Then the audit starts.
Without contract and payment we do not start audit or development.
Why
The audit is already work. It is not used to persuade and it is not given away.
Execution
06
Audit
We review data, processes and constraints. We define the strategy, the structure and the real scope.
If the cost changes, we state the figure here.
Why
The proposal starts from the information available. The audit checks what actually exists. Mixing them would be a blind promise.
Execution
07
Development
We build what was agreed. Any change of scope is priced before it is added.
Why
Added work without a price or a decision is not quality. It is disorder.
Execution
08
Implementation
We put the system into operation and test it with real data.
Why
A system that does not run on the client's data is not delivered.
Handover
09
Delivery
We deliver the system. Owner, test and closing date are defined.
Why
Without an owner the system is abandoned. Without a test and a date there is no verifiable close.
Handover
10
Maintenance
Maintenance starts only if you ask for it. It has its own price and scope.
Why
Maintenance is another job. Including it without agreement would falsify the price.
Start with contact
Write what you need. The first conversation is for listening, not for a closed proposal.
Contact