Step 04 of 4
Launch, training and handover
I put the system into production, train your team and hand over documentation and access. The code lives in your repository from day one, not with me.
- Length
- 1–2 weeks
- Support
- 2–4 weeks after launch
- Ownership
- 100% yours
- Lock-in
- None
How it works
Going live
1–3 daysI move the data over from the old spreadsheets, we check it and switch on. Ideally in a calmer period, not in the middle of month-end.
Team training
1–2 hoursShort sessions by role — everyone sees only what they need. Plus recordings for later.
Handover
1 dayDocumentation, access, the repository and passwords move into your hands. Nothing stays only with me.
Fine-tuning in use
2–4 weeksThe first weeks of real use reveal the details. Fixes and small tweaks are included.
What I need from you
- Who will be the main user or administrator.
- 1–2 hours of team time for training.
- A decision on the launch date.
Common questions
What happens after the support period?
You can continue with optional development and maintenance. It’s not a requirement — the system, the code and the access are yours.
Can I continue with someone else afterwards?
Yes. The code comes with documentation and a sensible structure so anyone else can pick it up.
Want to start?
The first step is always a short, no-strings call. We’ll find out whether it makes sense.