enaudo
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, across the rest of the EU and in the UK, otherwise remote in Europe.
-
Step 1 / 7
Clarify the problem
Together we identify where processes in your service business become disconnected and which software or automation would help.
- Capture current processes and bottlenecks in conversation
- Name goals, the people involved and affected tools
- First assessment of feasibility and value
- Start requesting access and sample data
Outcome
A clear picture of the problem and a shared understanding of the starting point.
-
Step 2 / 7
Agree the brief
The conversation becomes a tangible brief: what we will build, what we will not, and how you will judge success.
- Define scope and boundaries
- Set outcomes and milestones
- Align success criteria and acceptance conditions
- Clarify roles and contacts on both sides
Outcome
An agreed brief with measurable outcomes.
-
Step 3 / 7
Contract
Contract, data protection and responsibilities, before we start building.
- Finalise the contract and statement of work
- Settle data protection and access
- Set the timeline and communication channels
- Get approval to start building
Outcome
A solid contractual basis for working together.
-
Step 4 / 7
Access and data
Access and real sample data. Without them the solution stays theory. Often started in the first conversation, completed here.
- Record access and interfaces
- Collect sample data and typical edge cases
- Align data flows and formats
- Close open gaps before building
Outcome
A complete working basis for the build.
-
Step 5 / 7
Build and test
We build internally, test with your examples and make the solution fit for daily use.
- Set the structure and technology
- Implement flows and rules
- Test systematically
- Set up error handling and alerts
Outcome
An internally approved solution, ready to start in daily use.
-
Step 6 / 7
Start
The solution goes into use. Your team knows how to work with it.
- Activation and final checks
- Walkthrough and short training
- Handover of access and documentation
- First support after the start
Outcome
A running system in your operations.
-
Step 7 / 7
Operation and support
After that it keeps running: monitoring, small adjustments, further development if needed.
- Monitoring and handling faults
- Adjustments when processes or tools change
- Regular improvements based on feedback
- A contact route 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 it is running?
A tightly scoped flow can be running 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 the start?
The solution can still be monitored. Small fixes and incidents are part of operations. Larger rebuilds are separate orders, kept apart from day-to-day support.