How a project runs
Seven steps you can read before there is an order. Preferably on-site at the client, with travel for larger projects in Germany and across the rest of the EU, otherwise remote in Europe.
-
1 / 7
Problem identification
Together we clarify where time is lost in HR, customer service or admin, and whether automation is worth it.
- Capture current processes and bottlenecks in conversation
- Name goals, stakeholders and affected systems
- First assessment of feasibility and value
- Already kick off data access and sample data
Outcome: A clear problem frame and a shared understanding of the starting point.
-
2 / 7
Engagement definition
The conversation becomes a tangible brief: what we will build, what we will not, and how you will judge success.
- Define scope and boundaries
- Define deliverables and milestones
- Align success criteria and acceptance conditions
- Clarify roles and contacts on both sides
Outcome: An agreed engagement with measurable outcomes.
-
3 / 7
Contract framework
Legal and organisational frame: so collaboration, responsibility and operations are clear from the start.
- Finalise the contractual basis and statement of work
- Secure privacy and access questions
- Set the timeline and communication channels
- Obtain approval to start delivery
Outcome: A solid contractual basis for working together.
-
4 / 7
Data collection
All information, access and sample data needed for a stable solution. Often already started in the first conversation, completed here.
- Document system access and interfaces
- Collect sample data and typical edge cases
- Align data flows and formats
- Close open gaps before delivery
Outcome: A complete working basis for internal delivery.
-
5 / 7
Internal delivery
We build internally, test with your examples and make the solution fit for daily use.
- Define architecture and tech stack
- Implement workflows and logic
- Test systematically
- Secure error handling and alerting
Outcome: An internally approved, production-ready solution, ready for go-live.
-
6 / 7
Go-live
Go-live with handover: the solution runs in your environment, and your team knows how to use and monitor it.
- Production cutover and final checks
- Walkthrough and short training
- Handover of access and documentation
- Initial live support after launch
Outcome: A running system in your operations.
-
7 / 7
Maintenance & support
Operations, monitoring and further development so the automation stays reliable over time.
- Monitoring and incident handling
- Adjustments when processes or systems change
- Regular improvements based on feedback
- A support channel for your team
Outcome: Stable long-term operations and continuous improvement.
Questions about the process
Do we have to go through all seven steps?
Yes, in this order. Small orders are shorter inside each step, not because steps are skipped. We do not build without a clear brief and real sample data.
How long until go-live?
A tightly scoped flow can be live in a few weeks. Many interfaces, custom code or unclear ownership take longer. A reliable estimate comes after the first conversation, not before.
What does our team need to do?
Someone who can explain the current process, access to the tools involved, and time for questions. We do the engineering. With the usual operations model we also run the server and updates afterwards.
What happens after go-live?
The solution stays observable. Small fixes and incidents are part of operations. Larger rebuilds are separate orders, kept apart from day-to-day support.