Approach·Four steps

Listen, walk the floor, document, operate.

We start by listening, walk the floor in person, document what we find, and then either operate the environment or hand it back hardened. No SDR funnel. No portal-only intake. No demo theater.

01·Listen

Listen.

~30 minutes · phone

A real call with a real engineer. Not a sales associate, not a discovery rep — the same kind of person who'd be in your environment if we end up working together. We ask what's actually broken, what's worked before, what's at stake, and what you'd want different.

  • What is the work being done that IT enables?
  • What incident kept you up at night this year?
  • What did the last MSP get right and wrong?
  • What does the next 12–24 months look like?

We don't quote on this call. We listen, take notes, and tell you whether we're a good fit. If we're not, we'll point you to someone we'd send a friend to.

02·Walk the floor

Walk the floor.

~2 hours · on-site

For neighbors of 660 Glades Rd, this is on us. We come to the office, see the closet, trace the cables, watch the front-desk person work, look at what's on the wall. Software tools tell you about ports and processes; a floor walk tells you about humans and habits.

  • Network closet inventory and photographic baseline
  • Workstation sample (5–10 machines) — patch state, EDR, encryption, drift
  • Identity walk — accounts, roles, MFA enrollment, dormant access
  • Backup walk — what's protected, what isn't, when did it last restore
  • Vendor surface — payroll, payment, EHR, OMS, what's connected and how
03·Document

Document.

~5 business days · written

You receive a written environment baseline document — typically 30–50 pages — before any quote. It's yours to keep either way. Sections include current state, observed risks, quick wins, recommended remediation roadmap, and an honest read on what we'd do differently if it were our environment.

  • Current-state diagrams (network, identity, data flows)
  • Risk register with severity, likelihood, and recommended mitigations
  • Quick-wins list — items remediable inside two weeks at low cost
  • Compliance gap map for your applicable framework
  • Plain-English recommendations with cost ranges

The document is sharable with auditors, insurers, and your board. We've had clients use it as evidence in renewals before they ever signed a Statement of Work with us.

04·Operate

Operate.

Ongoing · or one-time

Either we run it (managed retainer), or we hand it back hardened (professional services). The choice is yours, not ours. We bias toward what's right for the client — sometimes that's a 12-month retainer relationship, sometimes it's a 60-day project followed by a polite goodbye.

  • Retainer path: 30-day onboarding, RMM/EDR rollout, identity baseline, backup baseline, runbooks documented, on-call rotation begins.
  • Project path: SOW signed, weekly burn report, milestone demos, written handoff and operator-training session at completion.
  • Hybrid: Project to remediate, then retainer to keep it that way. Common with security cleanups.
Next

Step 01 starts with a call.

Pick a time. We'll keep it to 30 minutes. No deck.

Talk to an engineer