Process
From first question to steady operation
Nothing here depends on urgency theater. Each stage produces a written artifact, and you can stop after any of them.
Stages
Five stages
Assessment
Seven questions in your browser. You get a recommended starting service, one alternative, and the reasoning — or a plain not-a-fit result. Nothing is sent unless you submit the request form.
Readiness conversation
A working call, not a pitch. We confirm the trigger, the constraint, who owns what today, and whether the recommendation still holds once we hear the details.
Discovery
We document users, devices, identity, network, vendors, and current habits. This is where estimates become facts, and where most surprises appear.
Written scope and pricing
A written scope with responsibilities, coverage expectations, escalation path, exclusions, and price. If it does not make sense, this is the natural place to stop.
Steady operation and review
Work begins, documentation is published, and the engagement is reviewed on a set cadence against issue patterns, open risks, and upcoming changes.
Responsibility map
Who owns what during an engagement
Ambiguity is the actual failure mode in outsourced IT. This split is written down before work starts and adjusted per engagement.
| Area | Kanso IT | Your team |
|---|---|---|
| Support intake and triage | Runs it | Uses the documented path |
| Device standards | Defines and maintains | Approves the standard and budget |
| Purchasing | Specifies and coordinates | Approves spend and signs contracts |
| Identity and access | Operates and reviews | Approves who gets what |
| Security remediation | Plans and executes agreed items | Sets risk tolerance and priority |
| Roadmap and budget | Drafts and recommends | Decides |
| Vendor relationships | Manages day to day | Holds the contract |
Expectations
What we ask of you
- One internal decision-maker who can approve scope and spend
- Administrative access to identity and email platforms during discovery
- Honest answers about what is broken, including what was tried before
- Willingness to work from written standards rather than exceptions
- Time from your team during transition — usually a few hours a week
Limits
What we will not do
- Promise a response-time SLA before scoping the engagement
- Claim always-staffed coverage or continuous threat monitoring
- Certify compliance with any framework
- Guarantee that a breach cannot occur
- Quote a price before discovery
FAQ
Process questions
Do I have to complete the assessment to talk to you?+
No. The contact page reaches us directly. The assessment exists because it makes the first conversation shorter and more useful, not because it is a gate.
How quickly do you respond?+
We do not publish a response-time guarantee. Kanso IT is new and will not claim a service level it cannot demonstrate. Form submissions do reach us and are read, but no specific turnaround is promised.
What happens if we are not a fit?+
We say so and explain why, usually with a direction that would serve you better. That is also what the assessment does automatically.
When do we see pricing?+
After scoping. Pricing depends on employee count, locations, device standardization, identity complexity, coverage expectations, and cleanup volume, so a number before discovery would be a guess.