From the request to handover
How a job moves
How deep each step goes depends on the number of processes and the people involved. Mapping the process can itself be a separate job, with a written result.
01
Request
Company, industry, the person to call, the problem, the units, a rough user count, and the programs in use.
02
Meeting
The main problem, today's method, the waiting, the result you want, and the constraints.
03
Today
Start and end of the work, roles, inputs and outputs, decisions, waiting, and the errors that repeat.
04
Next
Which step to remove or automate, and where a person's signature still has to stay.
05
Whether it can be built
Data volume, security, servers, connections, and whether a robot or a model is actually needed.
06
Proposal
Scope, what is deliberately left out, time, price, and the handover criteria.
07
Contract
Building starts after signature and the advance. One person on our side owns the project.
08
The detailed plan
Forms, data, flow, and, if needed, the agreement for connecting other programs.
09
Build
The work moves in pieces. Anything outside the scope is a change request.
10
Test
The right path, a bad input, a missing permission, and a failure in an outside service.
11
Training and go-live
The agreed data is moved, users are shown the work, and we watch the first days.
12
Handover
Handover means the written criteria were met. A new capability is estimated on its own.