Issue #7

When Self-Serve IT Stops Working (And What Comes Next)

How to choose the right IT support model as your nonprofit grows from 20 to 50+ people—without breaking your budget or your brain

​
​

Welcome to The Accidental Techie Newsletter - Issue #7

Hey there, fellow accidental techie! 👋

Reader, I saw a post this week asking whether to hire an MSP or bring IT support in-house. The conversation in the comments went everywhere—budget constraints, organization size, whether part-time made sense, horror stories about MSPs who didn't understand nonprofits.

It made me think about my own path through this decision.

At Democracy Fund, I hired our first MSP when we were still all in-person and growing. We scaled that relationship over time—more hours, eventually onsite presence, finally bringing someone on staff.

At Groundwork Collaborative, I worked closely with one consultant for everything tech-related. When the pandemic hit and we went fully remote, I was troubleshooting from home but had that consultant relationship to lean on.

At TAG, our tech-savvy staff could handle most day-to-day issues. We brought in specialists when we needed specific expertise we didn't have in-house.

Each approach worked. But each worked for different reasons at different organizational stages.

Here's what I learned: there's no one right answer. But there is a way to figure out YOUR right answer based on your size, your constraints, and what you're actually trying to accomplish.

What You'll Find in This Issue

This week, we're breaking down the IT support decision with something practical:

✅ The four IT support paths - Self-serve, single consultant, MSP, or in-house hire—what each one actually looks like, what it costs, and what you need to make it work

✅ Real examples from my experience - Democracy Fund (MSP to in-house), Groundwork (consultant relationship), TAG (self-serve with specialists)—and why each approach matched the organization's needs

✅ Decision framework by organization size - Specific guidance for under 20 people, 20-50, and 50+—including whether you're remote or in-person

✅ The hybrid reality - Why most successful approaches combine elements, and how to be intentional about what you handle versus outsource

✅ Three actions for this month - Document your current reality, define your non-negotiables, test before committing—with clear success metrics for each stepLet's turn that security overwhelm into a plan you can actually execute.

The Four Paths (And What They Actually Look Like)

Path 1: Self-Serve (aka "We'll Figure It Out")

This means someone on staff—usually operations, sometimes dev or finance—handles tech issues as they come up. You rely heavily on vendor support lines, your own hard earned experience, Google, and YouTube tutorials. Each person becomes the "expert" for whatever tools they use most. You lean on cloud-based platforms with built-in support like Microsoft 365 or Google Workspace.

At TAG, we had tech-savvy staff across the board. Hands-on IT support wasn't the daily bottleneck. When specialized needs came up—infrastructure planning, security audits, complex integrations—we brought in experts for those specific skills.

It worked because staff could handle tier-1 issues themselves. We had a clear understanding of when to call in specialists. And we had budget for expert consultation when we needed it.

For this path to work, the person leading Operations must have enough experience to manage vendors and know enough about most technology areas in an organization to be able to have meaningful and fruitful conversations with vendors.

The advantages: Lowest immediate cost. You can pivot quickly. You build direct knowledge of your specific systems and workflows. No vendor relationship to manage.

The challenges: Whoever "figures it out" becomes the bottleneck. There's no coverage when that person is out or leaves. If the lead person doesn’t have enough experience managing tech and operations, they won’t know which security gaps exist that you don't even know to look for. Strategic planning gets sacrificed to tactical firefighting.

And here's the hidden cost: your operations person spending 15 hours a week on IT instead of their actual job.

What you need to make this work: Your designated staff person needs baseline tech literacy, comfort with uncertainty, ability to learn on the fly, and—critically—knowing when they're in over their head.

Your organization needs patience with response times, realistic expectations, and budget for occasional specialist help.

---

Path 1.5: The Single Consultant Relationship

This is the option between pure self-serve and a full MSP. One trusted technology consultant who knows your organization intimately. They handle everything from troubleshooting to strategic planning. Usually contract-based with flexible hours.

At Groundwork Collaborative, I worked closely with one consultant for everything tech-related. When the pandemic hit and we went fully remote, I was troubleshooting issues from home—but I had that consultant relationship to lean on for the things beyond my expertise.

It worked because we'd built trust over time. The consultant understood our culture and constraints. They were flexible enough to scale up during crisis (hello, pandemic transition) and scale down during stable periods.

The advantages: Personal relationship and organizational knowledge. More affordable than a full MSP. Flexibility in scope and hours. Direct communication—no ticket system. Can grow with you.

The challenges: Single point of failure if your consultant becomes unavailable. Limited to that consultant's specific expertise. May lack 24/7 coverage. Boundaries can blur—when is it a "quick question" versus billable work? Harder to scale if you outgrow what one person can handle.

What you need to make this work: Your staff liaison needs clear communication about issues, ability to triage what's urgent versus what can wait, and trust in the relationship.

Your organization needs realistic expectations about response times, willingness to pay for expertise, and patience during your consultant's vacation or busy periods.

---

Path 2: Managed Service Provider (MSP)

An external company provides IT support via contract. Usually includes helpdesk, network monitoring, security patching, and strategic planning. Typical models are fixed monthly fees or per-user pricing. Response times are defined in your contract, often in tiers.

At Democracy Fund, the organization had recently transitioned from a separate foundation to its own nonprofit when I arrived as operations manager. Everything was in-person. I hired our first MSP to build proper IT infrastructure. As we grew, we increased MSP hours. Eventually we had someone onsite from the MSP regularly. Finally, we brought someone on staff—but we got there incrementally.

It worked because we matched MSP engagement to organizational growth. We didn't jump straight to a full-time hire. We tested what level of support we actually needed.

The advantages: Professional coverage, including evenings and weekends. Broader expertise than one person can provide. Proactive monitoring and security. Predictable budgeting. Can scale hours and services as you grow. Coverage when your team is out.

The challenges: Roughly $80-$300 per user per month, though this varies wildly. Many MSPs don't understand nonprofit constraints or pace. Finding the right fit takes work—not all MSPs are created equal. You still need someone internal to triage and translate. Can feel like you're at their mercy for strategic decisions. Contract terms matter—flexibility to adjust is crucial.

What you need to make this work: Your staff liaison needs ability to communicate issues clearly, enough tech understanding to evaluate recommendations, vendor relationship management skills, and willingness to push back when needed. Look for a nonprofit with an exclusive focus in nonprofits.

Your organization needs a realistic RFP process, budget commitment, patience during onboarding, and willingness to iterate on the relationship.

---

Path 3: In-House IT Person

A full or part-time staff member dedicated to technology. Handles everything from password resets to infrastructure planning. Usually reports to operations or directly to the ED or COO. May still contract specialized work like network engineering or security audits.

After years of scaling MSP engagement at Democracy Fund—from contract hours to onsite presence—we finally brought IT support in-house. By then, we knew exactly what the role needed to be because we'd lived through each growth stage.

It worked because we didn't guess what we needed. We had real data from our MSP experience. Clear role definition from the start. The organization was ready to support the hire.

The advantages: Immediate response to issues. Deep knowledge of your specific systems and culture. Can align IT strategy with organizational goals. Builds institutional knowledge. Usually cheaper than MSP at scale. Physical presence (if you're in-person) builds trust and relationship.

The challenges: $80K-$120K+ for a professional with several years of experience, plus benefits. Single point of failure—what happens when they're sick or on vacation? Nonprofit salaries often can't compete with corporate offers. Scope can quickly become overwhelming for one person. May lack specialized expertise in areas like security, compliance, or enterprise systems. Wrong hire is an expensive mistake.

What you need to make this work: Your IT person needs broad generalist skills, nonprofit cultural fit, comfort working independently, and ability to prioritize. You may also need to couple this with additional MSP or consultant support. Unicorns (people that know all areas) are rare, so play on your hire’s strengths, create a development plan for them, and trust them to advise you on what you need. Be prepare and make a plan for this position to eventually be at the Director level and not reporting to you.

Your organization needs a realistic job description, professional development budget, backup plan for coverage, and clear reporting structure.

The Hybrid Reality

Here's what I learned across 15 years and four organizations: few nonprofits fit neatly into one category.

Most successful approaches combine elements. Self-serve for tier-1 support. MSP for infrastructure. Consultant for special projects. The key is being intentional about what you handle, what you outsource, and what you decide to just... not do right now.

---

Your Decision Framework

Start with an honest assessment of where you are today.

Current state questions:

• How many hours per week does someone spend on IT?
• What's NOT getting done because of IT time drain?
• What breaks repeatedly?
• What keeps you up at night?

Calculate your true cost: Add up what you're actually spending. Staff time, tools, emergency fixes. That number is probably higher than you think.

Know your risk tolerance: What's your exposure if systems go down for four hours? Twenty-four hours? A week? Your answer here matters more than you realize.

What Makes Sense at Your Size

Under 20 people:

If you're fully remote: Self-serve plus reliable SaaS tools plus a consultant relationship for projects.

If you're in-person: Self-serve plus a local IT consultant for quarterly check-ins.

Why this works: Your tech footprint is still manageable. Invest in good tools that include support—Microsoft 365 Business Premium, not just Basic. Let the vendors carry some of the weight.

Red flag you need to level up:

🚩 Staff spending more than 10 hours per week on IT, or the same issues recurring every month.

🚩 Your organization works with vulnerable populations or sensitive data

🚩 You need a more robust digital security approach and mature policies

20-50 people:

This is where it gets real. Self-serve breaks down. Full MSP might be overkill.

Sweet spot: Part-time IT coordinator (20 hours per week) plus consultant for specialized work.

Alternative: Lean MSP contract (monitoring and emergency support) plus internal liaison.

Why this works: You need dedicated focus, but you probably don't need 40 hours per week yet. Someone needs to own this, but they don't need to know everything.

Red flag you need to level up:

🚩You can't respond to issues within 24 hours, security concerns are keeping you awake, or a major project has stalled due to technical gaps.

50+ people:

A full-time IT person or department is non-negotiable at this point.

Your decision becomes: Solo IT person plus consultants, or IT person plus MSP for infrastructure?

Why this works: Your technology is now mission-critical infrastructure, not just tools. It needs dedicated professional attention.

Consider: At 75-100 people, you might need an IT person plus a systems administrator, or a comprehensive MSP arrangement.

---

Three Actions You Can Take This Month

1. Document your current reality (this week)

List every recurring IT issue from the last three months. Calculate hours spent by staff on tech support. Identify what's NOT happening because of IT time drain.

Success looks like: A one-page document showing real costs and gaps.

2. Define your non-negotiables (next two weeks)

What must work 99% of the time? Email? Your CRM? Payroll? What security or compliance requirements do you actually have? What response time do you need?

Success looks like: Clear criteria for evaluating your options.

3. Test before committing (month two)

If you're considering an MSP: Start with project-based work before signing a monthly contract.

If you're considering a hire: Start with a part-time contractor before creating a full role.

If you're staying self-serve: Invest in tools with included support. Stop relying on free versions that offer nothing when things break.

Success looks like: A 90-day trial that proves your approach before you make a long-term commitment.

The Question to Keep Asking

1. "Is our current IT approach limiting what our organization can accomplish?"
2. If the answer is yes, it's time to level up.
3. If the answer is "sometimes, but we're managing," you're probably right-sized for now.
4. And if you're reading this at 11 PM because something broke and you're the only one who can fix it? You already know the answer.

Adjusting for Your Context

The framework above works for "typical" nonprofit scenarios. But your organization might not be typical. Here's how to adjust based on what makes you different.

Severe budget constraints (less than $200/user/year for all IT)

If your technology budget is extremely limited, your options narrow fast. Self-serve becomes less of a choice and more of a necessity.

What changes: Skip the MSP entirely—you can't afford the minimum engagement most require. Instead, invest in tools with included support (Microsoft 365 Business Premium instead of Basic, for example). Build a relationship with one affordable consultant you can call for emergencies. Set a "break glass" fund of $2,000-$3,000 for when something critical fails.

Watch out for: Free tools that seem like budget savers but create more work. Your staff time costs money too. Sometimes paying $10/user/month for proper support is cheaper than spending 10 hours troubleshooting.

Fully remote team

Remote changes almost everything about IT support. You can't walk over to someone's desk. You can't physically touch hardware. Your security surface is much larger.

What changes: Self-serve becomes much harder—troubleshooting over video calls is painful. A consultant or MSP who understands remote support is essential. You need remote monitoring tools, strong security policies, and clear processes for shipping/receiving equipment.

Consider: MSPs with strong remote support experience, not just local shops that assume they can visit your office. Your internal liaison needs to be comfortable with remote troubleshooting tools.

Good news: Remote-first MSPs often have better pricing because they're not tied to geographic markets. You're not limited to consultants in your city.

Large physical space or multiple locations

If you're managing server rooms, network infrastructure across buildings, or multiple office locations, self-serve stops being viable much earlier.

What changes: You need infrastructure expertise, not just "can you reset my password" support. This pushes you toward MSP or in-house faster—probably around 30 people instead of 50.

Consider: Hybrid approach with onsite infrastructure support (MSP or part-time) plus remote support for day-to-day issues. Physical infrastructure needs regular maintenance that video calls can't solve.

Watch out for: MSPs that charge premium rates for onsite visits. Get clear pricing on how many onsite hours are included versus billed separately.

Unique security or compliance requirements

If you handle health data (HIPAA), work internationally with data privacy regulations (GDPR), manage sensitive research, or face specific threat profiles, generic IT support won't cut it.

What changes: You need specialized expertise. A general MSP might not understand your compliance requirements. A single consultant might not have the depth you need. This is where you either pay for specialized MSP services or hire someone with specific credentials.

Consider: MSPs that specialize in nonprofit sectors with compliance requirements (healthcare, legal services, international work). Budget for security audits and compliance reviews beyond basic IT support.

Be realistic: Compliance isn't optional and it isn't cheap. If you're subject to HIPAA or GDPR, plan for this to cost 50-100% more than standard IT support.

Very small team (under 10 people) with complex systems

Sometimes small organizations have disproportionately complex technology because of your program work—research databases, custom applications, specialized tools.

What changes: Self-serve won't work even at small size. You need expertise but can't afford full-time. This is the perfect scenario for a strong consultant relationship—someone who knows your specific systems deeply.

Consider: Finding a consultant who specializes in your specific tools, not just general IT. If you use Salesforce heavily, find a Salesforce consultant who can also handle general IT, not the other way around.

Watch out for: Trying to piece together multiple specialists. At your size, one generalist who can learn your systems is better than three specialists who don't talk to each other.

Where to Find Help and Learn More

Finding and evaluating MSPs:

Start with nonprofit-focused MSPs. They understand your constraints, budget realities, and the tools you actually use. Ask your nonprofit network for referrals—other organizations in your city or region who work with MSPs.

When evaluating MSPs, ask:

• What percentage of your clients are nonprofits?
• What's your average response time for urgent issues?
• How do you handle onboarding and offboarding staff?
• What's included in your base price versus add-ons?
• Can we start with a project before committing to monthly service?
• What happens if we need to scale down or pause service?

Red flags:

• Won't provide client references.
• Can't explain their pricing clearly.
• Pushes enterprise solutions for your 20-person team.
• No experience with the tools you actually use (Google Workspace, Salesforce, common nonprofit platforms).

Get at least three quotes. But don't just pick the cheapest—pick the one that understands how nonprofits actually work.

What's your current IT support situation? Have you made the jump from self-serve to MSP or in-house? What surprised you? Reply to this email and let me know

Know Someone Who Needs This?

Forward this newsletter to another accidental techie drowning in security advice. Help them move from panic to plan. They'll thank you (probably around 3am when they're not lying awake worrying).

---

Support This Work

If this newsletter saved you from:

• A $15,000 pentest you didn't need yet
• Hours of research trying to figure out what matters
• That 3am panic about whether you're doing security wrong
• One conversation where you couldn't explain your security priorities

Consider supporting this work.

Your contribution keeps these resources free for the accidental techie at a five-person nonprofit who has zero budget but desperately needs this guidance.

The Accidental Techie Newsletter is published twice a month for nonprofit operations professionals who never planned to become the tech person but somehow ended up troubleshooting systems at 11 PM. You're receiving this because you signed up at the waitlist link or someone forwarded it to you (thank them!).

P.S. - Found this helpful? Forward it to that colleague who's always getting "simple" requests. They'll thank you.

Questions about making the transition from accidental techie to intentional leader? Hit reply and I can help.