Understand
We learn the systems, people, dependencies, constraints and your definition of success.
We start with what you already have, focus on the risks and outcomes that matter, then deliver in controlled stages.
You always know what is changing, why it matters, who owns it and what happens next.
Each one produces something you can read and evaluate before the next begins.
We learn the systems, people, dependencies, constraints and your definition of success.
We separate urgent operational risks from valuable improvements and longer-term work.
Changes move through sensible stages with communication, testing and rollback planning.
We monitor results, review what changed and refine the environment as needs evolve.
No forced rebuild and no generic prescription. The first job is understanding what exists and why.
Services, providers, data flows, deployments and the components each workload relies on.
Exposure, single points of failure, backup coverage and what recovery would actually involve.
Who uses, owns and administers each system, including access constraints and escalation paths.
Deadlines, compliance obligations, budgets and the outcomes that matter most.
Recommendations include the reason, expected result, effort, risk and dependencies. You see the trade-offs before deciding what proceeds.
Failures or exposure that need prompt attention.
Changes that improve reliability, security or delivery.
Scaling, replacement and capability decisions that need more time.
Six standards that apply to every piece of work, whatever its size.
Three ways to engage, depending on whether you need a defined outcome, continuous cover or extra hands.
A defined outcome, scope and delivery window for audits, migrations, hardening or software work.
Monitoring, maintenance, incidents, documentation and continuous operational improvement.
Additional engineering capability alongside your internal team when specialist help is needed.
The practical questions that come up on almost every first call.
Yes. Most work begins with an existing environment. We keep what is sound and focus effort where it creates a useful result.
We agree the minimum access required, use named accounts and secure methods, then document or remove that access when the work finishes.
Not always. Where downtime is necessary, we explain why, agree a suitable window and prepare a rollback path before starting.
You receive the agreed documentation and handover. CraftSupport can remain involved through ongoing support or hand ownership back cleanly.
Start with the situation rather than the solution. We will tell you what we would do first and why.
You leave the call with a written summary, whether or not you hire us.