The people working hardest to make the world fairer have the least to work with. That's backwards — and it's the reason this whole thing exists.

It's Tuesday. You run a three-person nonprofit. Right now you're typing the same donor into two systems that were never built to talk to each other, because the "free for nonprofits" platform assumed you'd have an IT person to wire them together. You don't. So the work that actually matters — the families, the kids, the river — waits while you do the work the software should have done.

That gap has a name we don't use enough. When most people say "the digital divide," they mean one thing: who has internet, devices, a signal. That divide is real — roughly 2.6 billion people, about a third of humanity, are still offline (ITU). But there's a second divide underneath it, and it doesn't close when the wifi shows up: the distance between technology built for you and technology built for someone else and handed down to you. Call it the relevance gap. It's the one I can't stop thinking about.

The lesson wasn't mine to teach

I learned to see it the slow way. Years ago I helped build something called The Little Digital Library — offline digital learning for communities without reliable internet. My job was the technology. I was the outsider who flew in, which is worth saying plainly, because it's the whole point of what happened next.

The version we first brought didn't get used. The tablets sat in a cupboard. The lessons were in a language that wasn't the kids' own, set in places they'd never seen, and needed a signal that never came. The message, once I was quiet enough to hear it, was plain: it wasn't built for them. That wasn't a complaint. It was a diagnosis — one the community had been making long before I showed up. It took me too long to hear it.

So we rebuilt it with them, not for them. Content in their own language. Stories set where the kids actually lived. Everything working offline, on the hardware already in the room. Before long the tablets were out of the cupboard and in use — not because we brought better machines, but because it finally spoke to the people in front of it. Access mattered. Relevance mattered more. That's the whole lesson, and it wasn't mine — the community handed it to me.

The divide isn't only about access to technology. It's about whether the technology was ever meant for you.

You're on the wrong side of it too

You feel this every week. You're resourceful — you do more with a shoestring than most enterprises manage with a department. But the good tools tend to flow toward whoever already has the most, and you get the hand-me-downs: the free tier with strings, the platform that assumes a technical team you don't have, the "solution" that makes more work than it removes. That's not a knock on you; it's a design failure. The software was never built with your Tuesday in mind.

And here's the part I can't get past. You — the people feeding neighbors, teaching kids, protecting rivers, housing families — are doing the most good with the least leverage. In a fair world you'd be first in line for good tools. Instead it's closer to the opposite.

The people doing the most good have the least to work with. We can change that.

Built with, not for

The lesson from that cupboard of tablets was never "bring people technology." It was: build it with them. Start from what an organization already knows and the constraints it actually lives inside. Leave capacity behind, not dependency. You measure whether it worked by whether people need you less over time. (How we think about measuring that: impact and reporting.)

What we actually do about it

Two names can be confusing, so here it is plainly: Tomorrow Labs is my studio. MissionAssist is the part of it that builds and fixes technology for nonprofits — websites, tools, and practical AI help, designed for a small team's reality. This is what I do for a living. I say so plainly because it's the reason I price the work the way I do: low enough that a three-person nonprofit can actually say yes. (Weighing whether to DIY, hire a freelancer, or bring in help? Real question — here's how to think it through.)

In practice it's unglamorous and specific: a site that works on the phones people actually carry (the checklist); a tool that fits the workflow you already use; an hour of busywork handed back to a staff of three. AI belongs on that list — used well, it gives your team back hours you never had, to back up your people, not replace them (where to start with it). Small things, aimed at the right people, compounding.

Closing the gap

The relevance gap won't close by waiting for it to trickle down. It closes when we decide the people doing the good deserve tools built for them — and then build those tools with them, the way that community taught me to.

The question was never "do you have access?" It was "was any of this ever meant for you?"

We're here to make the answer yes.

— Weston

CTA: Tomorrow Labs is the lab; MissionAssist is how we do it with your organization. If this is your work too, let's talk. And if you're not ready for a conversation, the free Nonprofit Digital Audit is a no-cost way to see where you stand — no call, no pitch.

Author: Weston Cox — founder of Tomorrow Labs and MissionAssist. It started with the relevance gap; it still does. Portland, OR.