Become the cplace expert your projects need
1. Understanding the roles
Project scope and setup determine which roles you need. You don’t have to staff every role from your own team. You can collaborate across the cplace network, or develop your own people through coaching on the live project.
The boundaries are fluid
These roles are orientation points, not rigid boxes. In practice they blend depending on a person’s skills, experience and interest: a Consultant who enjoys the technical side drifts toward Engineer, a Business Consultant who likes configuring takes on simple no-code configuration. The paths sketch idealized profiles. Anyone moving between two roles simply combines the building blocks that fit.
Four roles, each with its own focus
Every cplace project draws on these four roles. Find out what each one does and see its typical work on a project.
Which roles does your project need?
+ Solution Engineer
The development-heavy role beyond standard configuration, above all complex Low-Code (and Pro-Code when it is genuinely needed).
Required depending on the project: when more custom development and complexity come in, up to and including pro-code.
Typical work on a project:
- Design and implement complex low-code patterns
- Build reusable components
- Add pro-code extensions on concrete demand
+ Solution Architect
The senior technical role that owns solution architecture, safeguards quality in complex scenarios and sets the technical guardrails.
Required depending on the project: when solutions get large, span several business domains or complex structures, with concrete architecture requirements.
Typical work on a project:
- Design solution architecture and own the design decisions
- Safeguard technical quality and reusability
- Support complex or critical delivery topics
- Mentor Solution Consultants and Engineers
- Keep system landscape and deployment in mind
+ Business Consultant
The domain consulting role. Advises customers on PPM use cases and positions the right solutions, without configuring deeply.
Required depending on the project: when processes have real depth, or the customer has a clear advisory need, such as collaborative scheduling.
Typical work on a project:
- Advise customers on their PPM processes
- Elicit and structure requirements
- Position the right cplace solutions and modules
2. Enablement Paths
Everyone starts with cplace Fundamentals
One day, no prior experience. Fundamentals covers cplace as a platform and as a PPM solution, the no-/low-/pro-code spectrum, first hands-on adjustments in the UI, and the documentation map. It is the shared vocabulary every role path builds on, which is why it sits before the paths rather than inside them.
- The base for every role: Each of the four paths below assumes Fundamentals as its starting point.
- A first look for new partners: Still evaluating whether cplace fits your service portfolio? Start here before committing to a path.
Solution Consultant
The central delivery role. A Solution Consultant clarifies requirements with the customer and builds the cplace solution end-to-end with no-/low-code.
Solution Engineer
The development-heavy role for everything beyond standard configuration, above all complex low-code, and pro-code when it is genuinely needed.
Solution Architect
The senior technical role. An Architect owns the solution architecture, safeguards quality in complex scenarios and sets the technical guardrails.
Business Consultant
The domain consulting role. A Business Consultant advises customers on PPM use cases and positions the right solutions, without configuring deeply themselves.
The learning paths
Solution Consultant
The Solution Consultant covers the full arc from requirement to configured solution.
Prerequisites: None beyond the base. The path builds up the no-/low-code fundamentals itself.
Solution Engineer
The Engineer builds complex, reusable custom solutions, with rollout and pro-code added as the project demands.
Prerequisites: Programming experience. The no-/low-code fundamentals are part of the path.
Solution Architect
The Architect designs and owns solution architectures and leads Solution Consultants technically.
Prerequisites: Builds on Solution Consultant or Solution Engineer plus project experience. The order below is a recommendation, not a strict sequence.
Good to know: The Architect role is hard to build through training alone. What counts most is real project experience. Still, the trainings below cover an important base of topics an Architect needs to know in cplace.
Business Consultant
The Business Consultant advises with domain depth and elicits requirements.
Prerequisites: Solid domain knowledge (PPM / project management). Deep low-code is not needed for this role; no-code fundamentals are helpful.
Good to know: The domain focus varies widely. One Business Consultant specializes in risk management, another in schedule consulting, a third in cost control. The Masterclass below is one example of a domain deep-dive, yours depends on your specialization. As the Academy catalog grows, more domain modules slot into this path.
Which training maps to which role
✓ core building block | recommended / inherited | – Not in this path
| Training format | Solution Consultant | Solution Engineer | Solution Architect | Business Consultant | |
|---|---|---|---|---|---|
|
cplace Fundamentals |
✓ |
✓ |
✓ |
✓ |
|
|
No-Code Implementation |
✓ |
✓ |
✓ |
recommended |
|
|
Low-Code with AI |
✓ |
✓ |
✓ |
– |
|
|
cplace Requirements Engineering |
✓ |
recommended |
✓ |
✓ |
|
|
cplace Solution Design |
✓ |
✓ |
✓ |
– |
|
|
Advanced Low-Code |
– |
✓ |
✓ |
– |
|
|
cplace Release & Deployment |
recommended |
recommended |
✓ |
– |
|
|
Pro-Code Coaching |
– |
recommended |
recommended |
– |
|
|
Masterclass Collaborative Schedule Management |
– |
– |
– |
✓ |
More building blocks are on the way
The Academy catalog keeps expanding, and the role paths grow right along with it. New training formats are added continuously, and role certifications on the roadmap will slot into these paths later.
3. Learn what you need, when you need it
You don’t have to book every training for every role up front. Enablement follows real demand, and there is a sensible order to it.
Before a project
Start light, sharpen understanding
A few simple entry trainings, starting with cplace Fundamentals, are enough to build a solid grasp of cplace, and they already pay off in pre-sales. No need to enable every role while no concrete project is in sight.
Once a project is live
Enable along the way
When a project materializes, enablement can happen during delivery, targeted to what that project actually needs. Build up exactly the roles the work calls for.
