Environment size
Footprint and ownership
User count, system count, cloud footprint, and who owns day-to-day administration change the amount of follow-through.
Engagement Scoping
Size the work before it starts.
The same service changes with footprint, depth, cadence, and delivery model. Scoping turns those inputs into a work shape.
Bring these numbers
UsersWorkstationsServersWeb applicationsCloud tenantsAdmin owners
Scope inputs
Footprint, depth, cadence, and delivery determine the lift.
Sizing matrix
The goal is to estimate work honestly before delivery starts.
How scoping works
Four inputs set the shape.
How to read this
These scope drivers are planning anchors, not fixed packages. Final sizing depends on platform mix, admin maturity, and how much security oversight belongs in the work.
Delivery model
Recurring or project-based
Some problems need ongoing operational cadence. Others need a defined project with an endpoint. The delivery model changes pacing and lift.
Review depth
Baseline or deeper validation
Scope expands when the work needs broader validation, deeper testing, or review across several systems.
What changes scopeTypical effect
Environment sizeMore systems, more ongoing lift
Review depthBroader validation and testing time
Delivery modelOne-time project or recurring cadence
Managed Support Sizing
Footprint drives support load.
How to read this
These support bands are planning anchors, not fixed packages. Final sizing depends on platform mix, admin maturity, and how much security oversight belongs in the support motion.
Sizing example
Band 1
Up to 10 users, 10 workstations, and 5 servers
Small teams that need support ownership and routine hygiene.
Light recurring cadence with baseline review and priority guidance.
Sizing example
Band 2
Up to 50 users, 50 workstations, and 20 servers
Growing environments where admin practice and support coordination need structure.
Recurring support with change-window help and broader operational review.
Sizing example
Band 3
Up to 200 users, 200 workstations, and 50 servers
Larger teams that need deeper support, review, and prioritization.
Ongoing review of support hygiene, posture drift, and operational decision points.
Sizing example
Band 4+
Over 200 users, over 200 workstations, or over 50 servers
Environments where support, security review, and architecture need custom sizing.
Custom support shape based on platform mix, operational complexity, and exposure.
Consulting Scope Area
Advisory depends on involvement.
Scope Track
Operational Advisory
For teams cleaning up IT process, support ownership, and admin friction.
- Support process review
- Operational bottleneck identification
- Recommendations for steadier execution
Scope Track
Development & Automation
For application, workflow, or automation work that needs design review and implementation guidance.
- Workflow and integration review
- Automation design guidance
- Implementation planning and handoff
Scope Track
AI Support & Workflow Advisory
For teams using AI to streamline work while keeping adoption supportable.
- AI use-case and workflow review
- Adoption plan and operating guidance
- Integration planning for internal teams
Scope Track
Specialized System Advisory
For domain-specific or revenue-critical systems where workflow, architecture, and delivery risk need review together.
- Domain and workflow discovery
- Architecture and dependency review
- Execution planning for sensitive systems
Security Scope Area
Security scope follows the attack surface.
Scope Track
Architecture & Threat Review
When system design, identity flow, or trust boundaries are the main unknown.
- Threat modeling and trust-boundary review
- Architecture gap identification
- Prioritized remediation direction
Scope Track
Application Security Assessment
When a web app or API needs direct testing and fix order.
- Application and API testing
- Risk-ranked findings
- Remediation guidance tied to the code path
Scope Track
Host & Platform Hardening
When Windows, Linux, or cloud systems need a stronger baseline.
- Baseline and control review
- Privilege and configuration hardening guidance
- Operational next steps for ongoing maintenance
Scope Track
Deeper Validation Work
When the work needs a wider attack path or combined testing surfaces.
- Scope expansion beyond baseline review
- Cross-system validation and deeper testing
- Custom scoping around critical assets and exposure