Introduction of Can Do: Approach, Duration and Internal Effort

As an enterprise solution, Can Do is typically implemented across the entire organization – often including integration with existing systems such as ERP, CRM or HR.

For this reason, the process does not start with a purely isolated test environment, but with a structured implementation phase designed from the outset for productive use.

Objective of the Implementation Phase

Can Do is set up together with you to be ready for productive use – based on real projects, actual resources and clearly defined target scenarios.

Two Proven Onboarding Models: Both models are milestone-based. They do not differ in content, but in intensity, pace and level of commitment.

Option 1: Retainer-Based Onboarding

Over a period of six months, a structured and intensive onboarding is carried out with a clear objective: a stable productive environment starting from month seven.

This model provides a high level of planning reliability, close support and a setup tailored to your organization.

Typical scope of services:

• Setup of real project, resource and role structures
• Full customization of the system configuration
• Training and active support of key users
• Workshops, feedback loops and hands-on use cases
• Preparation of interfaces, BI modules and rollout

Suitable for: organizations aiming to establish Can Do in a structured and timely manner.

Option 2: Onboarding with Service Contingent

The implementation is carried out step by step over an individually defined timeframe. Content and pace are managed flexibly along predefined milestones.

Typical scope of services:

• Support of a defined core team (approx. 5 users)
• Setup of selected projects, resources or roles
• Training and guidance along agreed milestones
• Flexible use of a service contingent
• Optional extensions (e.g. interfaces, BI, rollout)

Suitable for: organizations with a clear roadmap and a need for maximum flexibility.

Internal Effort

Regardless of the chosen implementation model, it is advisable to define dedicated internal contacts who support and coordinate the rollout.

Guidance:

• Internal project lead: approx. 1 day per week
• Additional stakeholders: approx. 0.5 days per week

The actual effort may vary depending on the initial situation and objectives.
Continuous internal involvement typically accelerates the implementation and leads to more reliable results.

Conclusion

Both onboarding models provide a structured entry into Can Do.
The difference lies in the speed and intensity of the implementation – not in its scope.