Who's in your corner at 4:58 PM on a Friday?- Issue #12 of The Accidental Techie

Reader, let me ask you something.

When was the last time someone in your organization actually understood what you do?

Not the "you fix the computers" kind of understanding. I mean genuinely grasping the complexity of what you’re managing, the high-stakes decisions you’re making without a playbook, and the sheer number of systems you’re holding together on a shoestring budget and a lot of caffeine.

If you're like most accidental techies, the honest answer is: rarely. Maybe never.

We get good at working in a silo. At figuring things out quietly, Googling before the meeting, and solving the problem before anyone even notices there was one. What we don't get good at is building the relationships that would make all of that sustainable—the ones that move you from the lone fixer to the partner who actually shapes decisions.

This issue is about that. It's the second entry in my series on The Four Bridges: Skills, Relationships, Projects, and Communication.

What's in this issue:

✅ The fixer trap — why being the person who figures it out can keep you invisible in the rooms that matter

✅ The four relationships worth building — internal champions, vendors, peers, and your ED

✅ Three moves to start this week — none of which require a formal networking strategy

✅ The Four Bridges Assessment — a free 5-minute tool to see where you actually stand

✅ The Intentional Techie Cohort — 6 weeks of deep work starting June 2026

✅ Jobs in nonprofit tech — this week's roundup of roles worth a look

✅ What I'm reading — resources across the sector worth your time

Here's a moment you probably know.

It's 4:58 on a Friday. Something broke. The donor database is throwing errors, or the email platform is down, or a staff member just forwarded you a phishing link they already clicked. Your first instinct isn't to fix it. Your first instinct is to look around for someone to call.

There's nobody.

Nobody built a team around you. You just got handed the problem. And most of the time you solve it, but you do it alone, under pressure, hoping you don't make it worse.

So here's the question worth sitting with this week: who's actually in your corner?

Not in a vague "it takes a village" sense. Concretely. Who can you call at 4:58 on a Friday? Who in your organization has your back when you push for a new system? Who outside your org is doing the same job and willing to trade notes?

Most people doing this work would struggle to fill more than one or two of those slots. Nobody handed you a relationship-building playbook when they handed you the Salesforce admin login. That's where we start.

The relationship problem for accidental techies runs deeper than "you should network more."

That's generic advice, and you don't have time for generic.

Here's what's actually happening. Most accidental techies build a reputation as fixers. You're the person who figures it out. That's how you got here, and in many ways it's a genuine skill. But it creates a dynamic that's hard to see from inside it: people come to you when things break and leave you alone when things work. You're visible in a crisis, invisible in the planning meeting. A help desk arrangement dressed up as a working relationship. And it's exhausting.

The relationships that actually change your work look different. They're the ones where you're in the room before the decision gets made. Where your executive director trusts your read on a vendor before signing anything. Where a peer two organizations over tells you which CRM horror story you can avoid because they already lived it. Those relationships don't happen on their own.

There are four categories worth thinking about separately.

Internal champions. This is the person in your organization who understands the value of what you do and will say so when you're not in the room. Not necessarily your supervisor. Sometimes it's a program director who benefited from a system you built, or a development manager who actually uses the dashboard you created. These relationships matter because technology decisions in nonprofits are almost always political before they're technical. Having someone who can translate your work into mission language, for leadership and for the board, is worth more than most certifications.

Vendor relationships. Most accidental techies treat vendors as transactional. Vendor shows up, demos something, sends a quote. Think of it as building a support system before 4 PM on a Friday when everything's on fire. The right vendors, especially the ones with nonprofit pricing and real support, respond differently when they know you by name. I've gotten extensions, free licenses, and actual human beings on the phone specifically because I'd taken time to build a real relationship with someone on their team.

Peer network. This one gets used the least. There are thousands of people doing your exact job at organizations just like yours. They've already made the mistakes you're about to make. They know which tools actually work in resource-constrained environments. And most of them are just as isolated as you are, which means they're genuinely glad to hear from someone doing the same work. The nonprofit sector is relationally generous in a way a lot of sectors aren't. You just have to show up somewhere. NTEN, TAG, NGO-ISAC, LinkedIn groups, local roundtables — the communities exist. They're waiting.

Your ED or supervisor. This one's complicated, and I won't pretend otherwise. Some executive directors are genuine technology partners. Others see tech as a cost center and you as the person who keeps the lights on. The relationship worth building here isn't about getting them to love technology. It's about helping them understand what technology decisions cost when they're made without you in the room. A botched software purchase, a missed integration, a security incident that could have been avoided: these add up fast, and they're almost always rooted in a communication gap. You're the only one who can close it.

The through-line across all four: the most useful version of you isn't the person who fixes things. It's the person whose judgment people trust before things break. Getting there is relationship work.

Here's where to actually start. Three moves, this week.

1. Name your one internal champion, and do something to strengthen that relationship.

Who in your organization understands your work and would go to bat for you? If nobody comes to mind right away, that's useful information too. Pick the person closest to fitting that description and find a low-stakes reason to connect. Share something relevant, ask for their input on a tech decision, thank them genuinely for something they've done. You're not asking for anything. You're investing early.

2. Find one peer outside your org doing similar work.

You don't need to join everything. You need one person who will answer a message when you send it. Find them in an NTEN or TAG community thread, a LinkedIn comment section, a webinar chat. Introduce yourself. Most people doing this work are surprised and relieved when someone else reaches out.

3. Show up as a resource once this week, not just a fixer.

Forward an article that's genuinely useful to someone on your team. Share something you figured out with the person who always gets stuck on the same problem. Post a question in a community group. These are small moves. But they shift how you're seen, and more importantly, how you see yourself: not the person who fixes things, but the person who knows things and shares them. That's the foundation the other relationships get built on.

Before you dive into those steps, it helps to know where you actually stand.

I put together a short assessment that gives you a clearer picture of where you're strong, where you're surviving, and where the real work is across all four bridges.

Take it here: https://form.jotform.com/Hugo_Castro_hugo/the-four-bridges​

It takes about three minutes. Bring your results to the LinkedIn Live today at noon, it'll make the conversation a lot more useful.

This is the second of four bridges I'm exploring this spring, and honestly the one that gets the least airtime in traditional tech training. Nobody teaches relationship-building in IT certifications. But in nonprofit tech? It might be the most important bridge of all.

If you want to go deeper on all four bridges together and walk away with a real plan for your specific context, I'm hosting a free LinkedIn Live today at 12PM ET. I'll walk through the full Four Bridges Framework and share what crossing each one actually looks like in practice. Attendees also get early access to register for the June cohort at early bird pricing.