An industry-specialist MSP, not a generalist who took your call

We do IT
specifically
for your kind
of firm.

The IndexEight verticals we keep, and the ones we turn down.127 firms · click to view detail
Currently viewing — Law

For when a brief is due Friday and Word keeps crashing on the partner.

Practice management migrations done over weekends. iManage and NetDocuments performance tuning. Conflict-of-interest mailbox segregation. Trust-account audit prep. All the things only law-firm IT actually has to do.

Halpern & Reed, LLP
78 attorneys · Cleveland
iManage 10 cutover, weekend, zero downtime
Voss Carrington
34 attorneys · Pittsburgh
M&A diligence room — 6-day spin-up
Margolis Group
112 attorneys · 4 offices
Co-managed; on retainer since 2017
Section 03 · Services

What's actually
on the menu.

Six things we do, written without acronyms or upsell tracks. Most clients buy a flat monthly plus the occasional project. No tier called Enterprise, no per-ticket charges, ever.

S · 01
Managed support
Flat per-user, per-month

Helpdesk by email or phone, 24×7 monitoring, patch management, vendor liaison (your printer guy, your ISP, your line-of-business app), inventory tracking, asset lifecycle.

S · 02
Security & compliance
Included in managed support

MFA enforcement, endpoint detection (we run Huntress + Microsoft Defender), encrypted backup with quarterly restore drills, written posture report your CFO and auditors can read, incident-response retainer.

S · 03
Cloud & infrastructure
Bundled or standalone

Microsoft 365 and Google Workspace administration, Azure tenant work, on-prem-to-cloud hybrid, identity (Entra, Okta), VPN and ZTNA, server lifecycle for the firms still running them.

S · 04
Projects
Fixed fee · written scope · we eat overruns

Office buildouts and moves, M&A diligence rooms, DMS and PM migrations, DR cutovers, ransomware recovery, hardware refreshes. We quote, scope in writing, and ship by the date.

S · 05
Strategic guidance
Included for managed clients

Quarterly seat at the table with your partners. Budget for the next twelve months, risk we want fixed, roadmap we agree on together. No surprise line items.

S · 06
Co-managed IT
Supplements your internal team

For firms with one or two internal IT people who need backup, after-hours coverage, project capacity, or a second set of eyes on architecture. About 30% of our book.

Section 04 · How we work

Four phases.
No reset button.

Most MSPs sell a sales process and call it onboarding. Ours is a working method we've used on every engagement since 2014. The phases overlap, but the order doesn't change.

01 · Weeks 0–1
Listen

Half a day on-site. Meet your office manager, your two power users, the partner whose laptop is always slowest. We bring no pitch deck. We leave with a one-page list of what hurts.

02 · Weeks 1–4
Stabilize

Document everything. Fix the urgent stuff in week one. Close the gaps that an auditor or an attacker would find first. End with a written posture report at month one.

03 · Month 2 onward
Run

Flat per-user monthly. Real engineers you've met. On-call rotation published on the client portal. Tickets answered within an SLA we publish, by people who own the answer.

04 · Every quarter
Plan

Two hours with your partners. Budget for the next twelve months, risk register, roadmap. No surprise line items between meetings. Most of our clients keep this on their calendar permanently.

The on-call eightThe engineers who'd actually be on your account this quarter.Rotation refreshed quarterly
portrait · b&w
Risa Ahn
Onboarding lead · Akron
11 yrsIdentity, M365, audits
portrait · b&w
Marcus Tilley
Operations manager · Cleveland
9 yrsOn-call, runbooks
portrait · b&w
Daniel Briere
Founder · Akron
Since 2014Strategy, escalations
portrait · b&w
Vivian Okafor
Security engineer · Pittsburgh
6 yrsEDR, IR, posture
portrait · b&w
Jorge Salinas
Field engineer · Cleveland
7 yrsOn-site, hardware
portrait · b&w
Hannah Krupa
Cloud engineer · Akron
4 yrsAzure, Entra, hybrid
portrait · b&w
Sam Whitelock
Network engineer · Pittsburgh
8 yrsFirewalls, ZTNA
portrait · b&w
Priya Raman
Service desk lead · remote (OH)
5 yrsTier 1–2, training
Section 05 · The questions

What firms
actually want
to know
about us.

Seventeen questions come up before a firm signs with us. The five we hear most are answered below — by the people who'd actually be on your account, not by marketing.

Last reviewed by the partners — May 2026
Filter by topic
Q · 01
Pricing

How is your pricing different from every other MSP we've talked to?

Flat per-user, per-month. No tiers called Enterprise. No per-ticket charges. Projects are quoted as fixed fees with a written scope; we eat overruns. Our entire price list is on the Pricing page — there's no version we send only to procurement.

Daniel Briere, founder
Q · 02
Switching MSPs

We're already with another MSP. What does switching actually look like?

A 30-day overlap is included. We document everything we find in your environment, fix the urgent stuff in week one, and don't touch your existing contracts until the overlap ends. About 60% of our clients came to us this way.

Risa Ahn, onboarding lead
Q · 03
Off-hours

Who answers the phone at 9pm on a Saturday?

One of eight named on-call engineers, all of whom you'll have met. Not a triage line in another time zone. Average pickup 41 seconds. We publish the rotation on the client portal.

Marcus Tilley, ops manager
Q · 04
Onboarding

We're a 90-person law firm. What does the first 90 days actually contain?

Week one: discovery, urgent fixes, documentation. Weeks two–four: backup verification, MFA enforcement, patch baseline. Month two: a written security posture report your CFO can read. Month three: a quarterly plan we agree on together.

From the Halpern & Reed onboarding playbook, 2019
Q · 05
Security

How will you tell us when something's broken before we notice?

A monitored event opens an internal ticket. If it's customer-impacting, you get a call from a human within 8 minutes — not an automated email. We'd rather wake you up than let you find out from your office manager.

From the runbook
+ 12 more questionsIncluding: who owns our data if we leave, what happens during a ransomware incident, and whether your engineers actually live in our region.
Section 06 · Field notes

Things we've
written down.

Once a month, one of the engineers writes about something that happened — an incident, a hard call, a thing we got wrong. No SEO copy, no top-ten lists.

Read the archive · 73 essays since 2017
Incident·May 202612 min read

What ransomware looks like from the inside, on a Tuesday morning.

A small accounting firm, a leaked credential, six hours from first alert to all-clear. Names changed; the timeline isn't.

Vivian Okafor · Security engineer
Pricing·Mar 20264 min read

Why we don't sell tiers.

There is no Premium, no Platinum, no Enterprise. There is one plan, and a project list. Here's what we figured out about the alternative.

Daniel Briere · Founder
Annual review·Jan 20269 min read

An honest accounting of our 2025 SLA.

We hit 96.3% of response targets. We missed twelve. Here's what we missed, why, and what we changed for 2026.

Marcus Tilley · Operations manager

Don't see your industry?

We turn down work outside the eight verticals above. It's the trade we make to be genuinely good at the eight we keep.

See who else might fit →