The lifecycle
- Assess
- Design
- Deploy
- Migrate
- Operate
- Improve
| Step | What happens | What you get |
|---|---|---|
| Assess | Interviews, inventory, health checks, risks | Findings report and priorities |
| Design | Architecture, sizing, costs, plan | Design document and quote |
| Deploy | Install, configure, test | Working system and as-built documents |
| Migrate | Waves, test runs, cut-over, rollback ready | Moved workloads, sign-off per wave |
| Operate | Monitoring, maintenance, support under service levels | Monthly service report |
| Improve | Reviews of incidents, capacity and costs | Improvement plan for the next quarter |
Ways to work with us (engagement models)
| Model | Best for | How it's priced |
|---|---|---|
| Managed service | Ongoing responsibility for systems | Monthly, by devices, users or services |
| AMC | Planned maintenance and repairs for hardware | Yearly, by equipment |
| Project | A defined result: a build, a migration, an app | Fixed scope and price |
| Time and materials | Work that's hard to scope in advance | By the hour or day, with timesheets |
| Dedicated engineers | Extra hands in your team, short or long term | Monthly per engineer |
How a support request flows
Text version of this diagram
- You raise a ticket or an alert fires → Triage and priority
- Triage and priority → Fix remotely?
- Fix remotely? → Engineer fixes and confirms (yes)
- Fix remotely? → On-site engineer or vendor case (no)
- On-site engineer or vendor case → Engineer fixes and confirms
- Engineer fixes and confirms → Ticket closed with a report
- Ticket closed with a report → Monthly review