One practitioner. Accountable by design.

Ryan’s background

Ryan spent the better part of two decades in operational IT before founding TCG. His prior role as Director of IT at a Pacific Northwest MSP put him inside dealerships, law firms, medical offices, construction companies, and manufacturing operations — not as a salesperson, but as the person responsible for keeping the infrastructure running. That included Linux environments that other MSPs carved out, post-production data infrastructure at scale, and engineering-firm workflows where losing a design file at the wrong moment has real legal and financial consequences.

He built TCG around three practices that he kept running into in that prior work: managed IT for firms that had outgrown a single in-house tech, AI integration for operations that wanted AI wired into actual workflows rather than bolted on as a demo, and Linux specialization for the systems most MSPs simply don’t touch.

TCG’s principal practitioner has been in this work long enough to know where the failures hide. That’s not a marketing line — it’s what the prior role was for.

How TCG was built — and why those decisions matter

TCG was founded in 2025, which means every decision about how the practice runs was made recently, with current tools, without legacy client relationships creating pressure to keep old choices alive. Two founding decisions in particular are worth naming:

The questions worth asking directly

If you arrived here from the Managed IT or AI Integration page, you probably have at least one of these in the back of your head. They’re fair questions and they deserve straight answers.

• Why not go with an established MSP that’s been around since 2001? The tenure-based trust argument is worth examining. Established MSPs deliver through ticket queues and tier-1 support — you’re not talking to the practitioner, and the ticket handler reading your notes on a Saturday morning is not the person who knows your environment. Longevity doesn’t fix that. The honest case for TCG isn’t that it’s been around longer — it’s that it’s structured differently. The person you talk to in the first conversation is the person who manages your infrastructure.
• What happens when Ryan is sick or on vacation? For most managed IT situations, documented runbooks and monitoring automation mean a short absence doesn’t mean dark. Monitoring continues 24/7; automated remediation handles predictable failure modes (service restart, disk-pressure cleanup, certificate-expiry alerts). For situations requiring immediate hands-on response during Ryan’s absence, TCG has a written escalation arrangement with another PNW practitioner — non-emergency changes wait for Ryan’s return; emergencies trigger an escalation chain the client approves during onboarding. This is not a 40-person MSP bench, and we don’t pretend it is. It’s documented, accounted for, and tested.
• I’ve worked with small IT shops that said the right things and then couldn’t deliver. How is this different? The specific claim is practitioner depth across the environments TCG actually serves — dealership DMS integrations, Linux infrastructure, AI workflow wiring — not general IT competence. The way to evaluate this is the first conversation: if the technical specifics of your environment don’t connect to specific operational knowledge on TCG’s side, that’s a signal worth paying attention to.
• What happens when my business grows past TCG’s capacity? TCG serves the 10–100 person firm well. If a client’s growth genuinely requires a larger operation, TCG will say so before the client figures it out on their own — and will point to a specific transition path rather than letting the relationship stretch past what the model can serve.

What TCG is not — and who this isn’t for

Scope honesty is the most trust-building move available to a new firm. Here’s what TCG is not:

• Not a compliance certification body. TCG supports clients in preparing for HIPAA review, FTC Safeguards Rule requirements, and PCI 4.0 readiness — but does not certify, attest, or audit. That’s an assessor’s role. We work alongside those assessors; we don’t substitute for them.
• Not a 24/7 staffed SOC. If what you need is a security operations center with around-the-clock live analysts, that’s a different firm. TCG provides monitoring with same-day response — not a staffed overnight watch.
• Not a national MSP pretending to have local presence. TCG is Pacific Northwest, full stop. The geographic focus is real and it’s narrow on purpose.
• Not the right fit for firms over ~150 people looking for primary managed IT. At that size, the practitioner-led model runs up against its structural limits. TCG will tell you that before you sign, not after.
• Not an AI-everywhere vendor. TCG will tell you when AI is the wrong tool for a workflow. That happens more often than the AI marketing cycle would suggest.

What TCG doesn’t yet have is a client logo wall — we’re a 2025-founded firm, and the clients in the early book are confidential by their preference. The way we handle this is specific: we provide references in and out of a prospect’s industry where it’s reasonable to do so. If you’d prefer a direct introduction, we make one. If not, we get the client’s permission ahead of time and let the two of you have the conversation directly. No scripted testimonials, no logo-as-social-proof — a real client, your question, their answer. That’s the kind of social proof that actually tells you something.

See the Industries page for the nine verticals where TCG has the operational fluency to be concretely useful. Outside those nine, the honest answer on the first call is a referral.

The three practices

The architecture of TCG is three integrated practices under one flat-rate agreement. Each has its own page.