Service boundaries

Choose the service shape that matches the work.

Recurring care, end-user support, security review, and project delivery solve different problems. Clear boundaries make the next step more useful—even when ongoing stewardship is not the right answer.

Book a scoping call

Decision guide

Start with the pattern of demand.

Ask whether the work repeats, arrives as user incidents, needs specialist assessment, or has a defined finish line. The answer shapes the operating model more reliably than a broad “managed IT” label.

Tenant stewardship

Best for: recurring ownership, hygiene, lifecycle follow-up, and an administrative backlog.

Output: completed upkeep, assigned decisions, and a monthly summary.

Help desk

Best for: user questions, incidents, break/fix, and a sustained request queue.

Output: ticket handling and user-facing support workflow.

See how the handoff actually works ↗

Security review

Best for: posture assessment, deep hardening, and formal risk questions.

Output: review findings and a defined remediation path.

Project

Best for: migration, rollout, consolidation, or another transformation with a finish line.

Output: agreed deliverables completed against project scope.

See how a project gets scoped ↗

Mixed demand

A working boundary is a good sign.

One tenant can need more than one service.

A recurring care relationship may identify a migration, security review, or sustained ticket need. That does not make every type of work part of the monthly plan. It means the boundary has done its job: the work is visible early enough to choose an appropriate path.

The care backlog should retain the ownership question and route the larger item without making an unpriced delivery promise. Any separate scope, timing, or service expectation must be confirmed explicitly.

Five decision questions

Name the demand before choosing a provider.

Does the work recur because no one owns the tenant operating view?
Is the dominant need immediate end-user help or a queue of incidents?
Is the question a formal security or configuration assessment?
Does the desired outcome have a defined finish line and change plan?
Which business counterpart can make decisions the technician cannot?

Choose honestly

Use the readiness guide before choosing a plan.

It identifies recurring ownership gaps without producing an invented score or collecting tenant secrets.

Build a next-step list Compare recurring plans See where security basics fit Book a scoping call