Fictional
The people, companies and configurations are invented. Please read them as model cases.
Fictional support scenarios
See how we work through fictional scenarios.
The scenarios below are made up to show how we approach each service. They are model cases, not client work. We publish real projects separately, and only when the client has agreed and the facts can be checked.
How to read them
Each one shows what we check first and which decision it leads to. Results and benefits are settled only by checks in a real environment.
Cost review example
For the cost side, the sample report shows real program output on made-up billing data.
Scenario 01 / Cloud migration
A phased cloud migration
- Fictional problem
- The company wants to move from on-premises to AWS, but the order, acceptable downtime and shared platform are unclear.
- What we check
- Split the estate into migration units and settle permissions, logs, monitoring and the cutover plan first.
- What becomes decidable
- Downtime risks are separated from open questions, and the test scope for the next phase is set.
Scenario 02 / Monitoring
Monitoring and operations
- Fictional problem
- There are so many alerts that important signals get buried, and each engineer responds differently.
- What we check
- Separate how large the impact is from who acts and when.
- What becomes decidable
- The line between act now, act in business hours and record only, and which runbooks to write first.
Scenario 03 / Security review
Preparing permissions and logs for an audit
- Fictional problem
- Responsibility for permissions, logs, evidence and change records is unclear.
- What we check
- For permissions, records and change procedures, separate what can be explained from what cannot.
- What becomes decidable
- Which boundaries cannot yet be explained before the audit, and the priority of technical settings versus operating rules.
Choose your starting point by deliverable and scope.
No customer names or detailed configurations needed.