Rasheeda Creighton didn’t post on Threads looking for a tech consultant.
She was looking for someone who could look at her five-year-old nonprofit operations—real programs, real funders, real staff — and answer a question most executive directors don’t even think to ask:
Before we scale, does any of this actually make sense?
That question is rarer than it should be. And it’s exactly the right one.
The Setup: Strong Mission, Invisible Nonprofit Operations
Rasheeda is the Executive Director of JWC Foundation, a Richmond, Virginia nonprofit on a mission to help Black entrepreneurs build operationally sustainable businesses. Coming up on their fifth anniversary, the org was thriving — but she had a nagging sense that the foundation underneath the work hadn’t been looked at in a while.
A corporate funder was doing a brand audit. She wanted a tech audit.
Not because everything was broken. Because she was smart enough to know you don’t scale what you haven’t stress-tested.
So she posted on Threads. Two people raised their hands. She picked the one who said: “I just need access. I don’t need you to walk me through it.”
That was me.
Phase One: The Backend Blueprint Begins
The first step of every Backend Blueprint engagement is a deep read of the existing nonprofit operations— without requiring the client to sit in long meetings. I asked for access to JWC’s website, CRM, and form software, then went in and started mapping.
This is where Puzzle earns its name. It’s not just a list of what software you’re using. It’s a visual picture of what jobs that software is doing, what data is being collected, and where the handoffs happen — or don’t.
When I brought the map back to Rasheeda, she looked at it and said, out loud: “I’m the problem. My bad, y’all.”
That’s not failure. That’s clarity.
A lean team of four — two full-time, two part-time — had been operating entirely from what lived in Rasheeda’s head. Processes that team members thought were happening weren’t documented anywhere. Things that had been paused were still technically “running.” The map made the invisible visible in one sitting.
Rasheeda went back to her team and apologized. She named it directly: “A lot of this has been in my head and that’s not fair.”
That’s what a good map does. It doesn’t blame people. It shows you the system — and then it gives you something to actually fix.
Phase Two: Building the Infrastructure
The audit revealed that JWC’s core need was an event management system — one that could handle data, automate follow-up, and let a distributed team work without depending on any single person being available.
We chose Airtable.
Rasheeda had tried Airtable before. Twice. It hadn’t clicked. That’s not unusual — Airtable without data structure is just a fancy spreadsheet that makes you feel bad. So we started by cleaning the member data, separating first and last names, standardizing fields, and building the base before we built anything visible.
Then came the interface.
Thirty minutes into a working session, Rasheeda had a live dashboard — dynamically pulling from clean, structured data. When a funder asked for metrics on short notice, a request would have meant hours of digging through spreadsheets a year ago, was now a 10 minute task.
That’s not a productivity hack. That’s operational resilience.
The Automations That Changed How the Team Works
The event attendance workflow became the clearest example of what’s possible when you build the right foundation first.
Staff mark attendance using an Airtable interface at events. That single action kicks off a chain: attended = welcome series. No show = automatically flagged the next morning and a “we missed you” email goes out. No manual follow-up. No one has to remember. The system handles it.
Rasheeda put it plainly: her second full-time staff member prefers to work late at night. Rasheeda’s a morning person. The system means neither of them has to be available at the same time for information to move. The org functions across schedules because the system carries what used to only live in one person’s head.
The Moment When the Client Schooled Me
One of my favorite moments from this engagement happened when Rasheeda was trying to solve a member directory problem. She wanted members to be able to update their own profiles without creating duplicate records — using their email to look up their existing record in a linked form.
I told her I didn’t think that was possible in Fillout.
She did it anyway.
I dug in, confirmed it worked, and immediately made a YouTube video about it.
Because it was brilliant, and I had genuinely never seen anyone pull it off. Credit where it’s due.
This is what happens when you work with ops-minded leaders who are ready to own their systems. They stop waiting for permission and start building.
What Changed at the Organizational Level
After the Backend Blueprint engagement, here’s where JWC Foundation landed:
Process visibility — Workflows that used to live in Rasheeda’s head are now documented in Puzzle. The team can see how work moves, who touches what, and where things hand off.
Tool clarity — The team had a real conversation about Asana: who liked it, who didn’t, and what it was actually for. The answer? Use it when multiple people are touching the same work. Don’t use it for individual tasks. That’s a policy decision that came directly from looking at the process map together.
Event management — Event are now ready to publish with six weeks of lead time, documented steps, and four team members coordinating without chaos. Before: day-of scrambles and “where is this?” After: it’s in the system.
Data on demand — A member dashboard that updates in real time, built from clean, structured data that the whole team can trust.
What Rasheeda Would Tell You
For anyone wondering whether this kind of engagement is for them — especially if they’re not particularly tech-forward — Rasheeda’s take is simple:
“Trust the process. And understand that the real value is that someone can tell you how things are actually working — not how you think they should work — and show you where the links are broken without judgment.”
She also added: knowing what things cost (Puzzle shows tool costs at the step level) has a way of focusing the mind. Nothing clarifies a process decision faster than seeing the price tag next to it.
The Bigger Point
JWC Foundation didn’t need to be rescued. They needed a mirror.
They needed someone to come in, look at the actual system, and hand back a clear picture of what was there — so the leadership team could make real decisions instead of operating on instinct and goodwill.
That’s what the Backend Blueprint is designed to do. And it works whether you’re systems-minded or not — because the goal isn’t to make you love tools. It’s to build an operation that doesn’t depend on any one person to hold it together.
Some of the stuff that I thought had been dropped was because it wasn’t documented anywhere. There was nothing to be picked up.
Now there is.
Ready to see how your organization actually works — before your next growth push? Learn more about the Backend Blueprint and book a sales call today.
