Platform in a Week
Make the baseline hold up: scope, cloud structure, platform layer, access and delivery.
Approach
From a first platform conversation to a manageable platform.
There is no default technology for every situation. The route separates a free introduction, paid discovery, fitting implementation, stabilisation and structural operations.
Support Subscription
Place maintenance, response, team questions and small improvements in fixed coverage.
Specialist modules
Add a missing feature or optimisation: access, cost, automation or delivery.
From question to continuity
The commercial route
First we establish fit. A detailed assessment then leads to a credible implementation estimate or confirmation that Platform in a Week meets the prerequisites.
- 01No-obligation and high-level
First platform conversation
We explore the situation, trigger and mutual fit, so the right next step becomes clear quickly.
A focused first exploration - 02Paid detailed assessment
Platform Discovery
We assess workloads, cloud resources, IaC, delivery, security, observability and support needs.
Substantiated scope and estimate - 03Fixed or phased scope
Implementation
A fixed baseline where constraints fit, or a phased engagement with clear deliverables and budget guardrails.
Build on confirmed choices - 04After go-live
Stabilisation
We validate behaviour, documentation, alerts, recovery and ownership before operations enter their normal cadence.
From delivery to control - 05Structural continuity
Platform Support
Bounded maintenance, monitoring response and platform or delivery support where needed.
Clear coverage and agreements
Paid assessment
Platform Discovery before a realistic implementation promise.
Discovery makes risks, dependencies, target architecture, phases, implementation estimate and budget guardrails explicit. You receive a practical decision framework for the next step.
What you know afterwards
- Which platform choices are responsible
- Which dependencies and risks need attention first
- Which phasing, estimate and support model are realistic
Starting atEUR 2,990 excl. VAT
What we assess in depth
- Applications, workloads and stateless versus stateful
- AWS or Azure resources and existing Terraform/IaC
- Accounts, subscriptions, networking, identity and secrets
- Delivery, DNS, certificates, storage and databases
- Backups, recovery, observability, security and governance
- Kubernetes versus simpler alternatives
- Target architecture, phases, estimate and support needs
Standardised foundation
Platform in a Week, where prerequisites demonstrably fit.
A fixed scope for a new or well-bounded baseline. Not a promise to migrate every legacy estate or all applications in one week.
- Beforehand
Intake and scope freeze
Lock cloud, CI/CD platform, cluster model and preconditions in the days or weeks before the delivery week.
- Day 1
Foundation and constraints
Confirm cloud structure, access paths and technical starting points so the build can start with focus.
- Days 2-3
Foundation and runtime
Landing zone, networking, identity boundaries and Kubernetes or runtime baseline as IaC.
- Days 4-5
Delivery and observability
Wire CI/CD, GitOps, logging, metrics and alerts into the stack.
- Days 6-7
Validation and handover
Test, document, capture decisions and define the sensible next steps.
Fixed scope within prerequisites and constraints confirmed in advance.
Confirmed in advance
- Cloud account or subscription and required rights are available
- Repositories, pipelines, identity owner, DNS and certificate paths are accessible
- A representative workload and technical decision maker are available
- Scope, stack, cluster model and acceptance criteria are confirmed before delivery
Acceptance criteria
- The platform can be rebuilt from code
- At least one representative application follows the agreed delivery path
- Secrets are not hardcoded in repositories or pipelines
- Identity, roles, logging, metrics and agreed alerts work
- Ownership, component versions, architecture decisions and runbooks are recorded
Outside fixed scope
- Application changes and workload migrations
- Unknown legacy and open custom integrations
- Stateful migrations without separate assessment
- Ongoing operations or extensive enablement without a separate agreement
Phased implementation
Complex existing environments remain transparent custom work.
Professionalising existing AWS or Azure, VM containerisation, stateful services, complex networking and environment automation usually fit better in phases.
- 01
Clear phases
Deliverables and decision points are explicit for every phase.
- 02
Visible budget
Effort estimates or time and materials stay within an agreed budget guardrail.
- 03
Steady progress
Progress, decisions and budget are updated at regular intervals.
- 04
Preserve what works
Useful existing infrastructure stays in place where that is responsible.
Structural continuity
Support starts with clear coverage, not a vague helpdesk promise.
Supported clusters, environments, components, support window, response, monitoring ownership and change allowance are recorded after implementation or paid onboarding. Response time is not guaranteed resolution time.
From EUR 1,990 per month — For Level 1 Platform Maintenance. Clusters, environments, components, support window and change allowance are agreed before the start.
Platform Maintenance
- Coverage
- Cluster and environment counts are recorded contractually after onboarding.
- Window
- Planned maintenance in an agreed working window; no implied 24/7 coverage.
- Response
- Incident response is not included. Response time is not resolution time.
- Included
- Periodic updates, patching, health checks and small corrections for agreed platform components.
- Outside scope
- Application work, major upgrades, redesign and new platform modules remain separate project work.
Monitoring & Response
- Coverage
- Included clusters, environments, alerts and escalation channels are explicitly recorded.
- Window
- Response within the agreed support window; no 24/7 unless separately agreed later.
- Response
- Response time covers triage and starting the investigation, not guaranteed resolution.
- Included
- Level 1 plus response to agreed platform signals and investigation of instability.
- Outside scope
- Components that were not onboarded, application incidents and structural extensions are out of scope.
Platform & Delivery Support
- Coverage
- Platform and delivery components are named and bounded during onboarding.
- Window
- Availability and contact paths follow the agreed support window.
- Response
- Triage for platform, pipeline and deployment issues; resolution depends on cause and external parties.
- Included
- Level 2 plus developer questions and small changes within an agreed monthly allowance.
- Outside scope
- Unbounded project delivery, workload migrations and application development are not included.
Focused engagements
Specialist capabilities without obscuring the main route.
JIT Production Access
Temporary production access with approval, scope, audit trail and automatic revocation.
FinOps
Explain cloud cost and automate where waste is demonstrable.
Environment Automation
Repeatably provision or clone customer, test and acceptance environments.
Delivery & GitOps
Improve CI/CD, Argo CD, release flows and deployment reliability.
Which next step fits?
The first platform conversation exists to determine exactly that without imposing a tool or implementation shape.
Discuss your platform situation