Fit
Who we work with, and who we don't
Fit is not a formality here. The engagements only work when the company is large enough to need an operating model and small enough that one can be installed without fighting an existing IT organization.
Company profile
The band we design for
Size
50–300
Employees, in the United States. Below that, informal support is often still rational. Above it, companies usually build specialized internal functions.
Complexity
Too much
Multiple locations, mixed devices, real vendor relationships, and outside parties asking security questions.
Internal capacity
Thin
Nobody, one overloaded person, a small team without direction, or an executive doing it on top of their real job.
Buyers
Who usually starts the conversation
Different roles describe the same problem differently. The engagement gets scoped around what that person is actually accountable for.
COO or Head of Operations
IT problems surface as operational drag: onboarding delays, downtime, and sites that behave differently. Usually wants one accountable owner and predictable process.
CFO
Spend is growing without explanation, renewals arrive unmanaged, and insurance questions carry financial risk. Usually wants a cost baseline and a defensible plan.
CEO
A deal is stalled on a security questionnaire, or technology decisions keep landing on their desk. Usually wants the topic to stop consuming leadership attention.
Internal IT manager
Competent and outnumbered. Usually wants capacity, documentation, and someone senior to back the roadmap they already know is needed.
Triggers
Conditions that mean it is time
Most companies have several of these at once before they call anyone.
- Repeated employee IT issues with no root-cause work
- One internal IT person carrying the whole company
- Additional locations opened or planned
- Cyber-insurance application or renewal requirements
- Vendor or customer security questionnaires
- Inconsistent onboarding and offboarding
- Device complexity with no inventory or standard
- Unclear ownership of systems, vendors, and spend
- Leadership time lost to technology decisions
- An existing provider nobody is holding to expectations
Non-fit
Explicitly not a fit
| Situation | Why we decline | Better direction |
|---|---|---|
| Consumers and home IT | Our work is built around company-wide standards and multi-user environments. | A local computer support provider. |
| Five-person startups needing occasional laptop help | Ongoing coverage would be poor value at that size. | Ad hoc hourly help; revisit when headcount or obligations change. |
| Enterprises with mature global IT organizations | You already have the ownership structure we install. | Specialist vendors for the specific gap. |
| Custom software development | We operate technology; we do not build products. | A product engineering firm or internal developers. |
| Primary need is 24/7 SOC or MDR | Continuous staffed monitoring is a separate discipline and we will not imply we provide it. | A dedicated MDR provider; readiness work can precede it. |
The assessment applies these rules directly. If your answers land outside the band, it returns a not-a-fit result rather than a soft yes.