Our engagement models
Our engagement models are design and roadmap, turnkey projects, ongoing consulting and managed services. Before the work begins, we put the scope, communication arrangements and deliverables in writing together with you, and define roles and responsibilities from the start.
Assess, build, operate.
Whichever model we work under, the work follows the same three-step logic. The output of each step is defined when the work begins.
We clarify the situation
Together we map out the current setup, risks and goals, and prioritize the work.
- Initial consultation and discovery
- Findings and priorities
- Measurable goals
We put the plan into practice
Where it makes sense, we first trial on a small scope and then roll out more widely; we share progress regularly.
- Phased plan
- Regular status reports and demos
- Measurement and improvement
We operate it or hand it over
We operate the setup under contract, or hand it over to your team with documentation and training.
- Runbooks
- Training and knowledge transfer
- 24/7 operations support under contract
The model that fits your needs.
The models can follow on from one another: many engagements start with a design or a project and continue with ongoing consulting or managed services. In every model, communication channels and availability terms are defined in the contract.
| Attribute | Design and roadmap | Design and implementation (project) | Ongoing consulting | Managed services and 24/7 |
|---|---|---|---|---|
| When does it fit? | When you want a well-reasoned architecture and implementation plan before a decision or an investment. | When there is a defined goal and scope: setup, migration or transformation, delivered turnkey. | When your team needs regular expert support alongside it. | When you want to hand over the operation of your systems fully or partly. |
| Scope | Current-state analysis, target architecture and a prioritized roadmap. | A work package with deliverables defined up front, from design through to go-live. | Architecture guidance, reviews and implementation support. | Monitoring, maintenance, updates and incident response. |
| Duration | Depends on scope. | Until the project is complete; support options afterward. | Monthly, with flexible extension. | For the term of the contract. |
| Availability | According to the work schedule. | According to the project schedule; outside business hours when planned cutovers require it. | Business hours; scope can be extended by contract. | 24/7 for the systems defined in the contract; response times are set out in the contract. |
| Reporting | Architecture document, roadmap and presentation. | End-of-phase report and demo. | Monthly summary. | Monthly service report, post-incident review. |
Design and roadmap
- When does it fit?
- When you want a well-reasoned architecture and implementation plan before a decision or an investment.
- Scope
- Current-state analysis, target architecture and a prioritized roadmap.
- Duration
- Depends on scope.
- Availability
- According to the work schedule.
- Reporting
- Architecture document, roadmap and presentation.
Design and implementation (project)
- When does it fit?
- When there is a defined goal and scope: setup, migration or transformation, delivered turnkey.
- Scope
- A work package with deliverables defined up front, from design through to go-live.
- Duration
- Until the project is complete; support options afterward.
- Availability
- According to the project schedule; outside business hours when planned cutovers require it.
- Reporting
- End-of-phase report and demo.
Ongoing consulting
- When does it fit?
- When your team needs regular expert support alongside it.
- Scope
- Architecture guidance, reviews and implementation support.
- Duration
- Monthly, with flexible extension.
- Availability
- Business hours; scope can be extended by contract.
- Reporting
- Monthly summary.
Managed services and 24/7
- When does it fit?
- When you want to hand over the operation of your systems fully or partly.
- Scope
- Monitoring, maintenance, updates and incident response.
- Duration
- For the term of the contract.
- Availability
- 24/7 for the systems defined in the contract; response times are set out in the contract.
- Reporting
- Monthly service report, post-incident review.
What stays the same in every engagement.
Clear roles and responsibilities
We assign a project lead to every project; architecture, DevOps, security and software specialists join at the relevant stages of the work.
Confidentiality
Where needed, we start the work with a non-disclosure agreement. Your information is used only for the work and shared only with those who need it.
Least privilege
Access is granted with the narrowest permissions required and is logged; every access has an owner and a justification.
Documented handover
What we build is handed over together with its architecture decisions, operating procedures and documentation.
Regular communication
Through status reports and end-of-phase presentations, we share risks and decisions openly and in good time.
Measurable goals
We measure success against criteria that we define together when the work begins.
About how we work
If you are not sure which model fits, let's work it out together in an initial consultation.
Let's clarify your needs together.
In a free initial consultation we discuss your current situation and goals, and share our first impressions and possible next steps in the same meeting.
- A technical conversation with specialists in your area
- First impressions of your situation and possible approaches
- Where it fits, a next step: an assessment, a project proposal or consulting
- A non-disclosure agreement before the meeting when needed
- A reply within 4 business hours