ROBOSISTEMS / Process
Assembly: from conversation to handover
Six stages. Each ends with something tangible you can check.

- 1
Conversation
A first message and a few written questions. We want to understand the goal, the people who will use the product and the limits: time, budget range, existing systems.
Result: a short summary you can correct.
- 2
Task map
We split the product into modules and mark dependencies. Unknowns are not hidden — they go on their own list.
Result: a module diagram and a list of open questions.
- 3
Proposal
We describe stages, what each includes, what is deliberately excluded and give a range estimate, explaining what drives the low and high ends.
Result: a document you can discuss point by point.
- 4
Iterations
We work in short cycles. Each ends with a demo of what works and a list of plan changes.
Result: a working build or prototype, not percentages.
- 5
Check
We walk through the quality criteria: accessibility, errors, slow networks, screen sizes. Findings are logged and fixed before release.
Result: a check report with open and closed items.
- 6
Release and handover
We publish or help publish, hand over access and documentation, and agree on support — or a clean handover to another team.
Result: everything the product needs to live without depending on us.
Rules we keep
In writing. Decisions and changes are written down so they can be found a month later.
Ranges. Estimates come with uncertainty explained, not a single number.
No surprises. If scope grows, we say so before the work is done.
Your access. Repositories, store accounts and hosting are registered to you.
