Tim Lockie's Blog

Buy outcomes, not software! How a nonprofit flipped a crisis into proof of culture

Written by Tim Lockie | May 28, 2026 5:50:08 PM

What happens when a vendor relationship is built on rhythms, trust, and behavior—not features and billable hours

When Furniture Bank's payment processor collapsed, tens of thousands of dollars were frozen overnight. They had days—not months—to rebuild how they took payments. What saved them wasn't a new platform or an emergency consultant. It was a rhythm they'd already built within a trust-based partnership that turned ordinary habits into crisis infrastructure.

When the floor fell out
Buying rhythms, not software
You get what you pay for
Same tools, different behavior
Build the rhythm before you need it

 

When the floor fell out

This wasn't an IT problem—it was a mission threat

At 6:12 a.m., Sam sent a Slack message: "Ran six payments. Half failed. Something's off."

Three went through. Three didn't. No errors. Just silence.

Furniture Bank's payment processor had collapsed behind the scenes. Not deprecated. Not sunset. Shut down by court order. The processor's confidence that everything would resolve before the deadline turned out to be words, not action.

Between $60,000 and $80,000 sat frozen in digital limbo: money meant to fund the mission. Every day without payment capability was a day Furniture Bank said "no" to the people who needed them most.

Because Sam had been documenting small failures for weeks, the team wasn't starting from zero when the crisis hit. Her Looms and receipts became the playbook. The friction she'd made visible gave the team a head start most organizations don't get in crisis.

The same Digital Guidance® rhythm used for routine friction became the decision stack for crisis response. The questions were already in place:

  • What problem are we actually solving? Not "payment processing" in general. A shutdown. Frozen funds. A short fuse.

  • Who owns the decision? Sam as the Guide, working shoulder to shoulder with Matt at Ascendably.

  • What needs to happen to get a yes? Stripe had to match workflow, stay PCI-compliant, and allow secure customer-side payments.

  • What's the safe experiment? Start with new customers. Migrate the rest gradually. Communicate early, before panic sets in.

     

Dan Kershaw, Furniture Bank's Executive Director, knew when to hit the fire alarm—and when to get out of the way. His role wasn't to solve the problem. It was to clear blockers so the people who owned the work could move.

Scope creep was caught immediately. Someone tried to fold in a tax receipting problem. That was shut down. The team stayed focused.

Within days, the team migrated to Stripe. Same people. Same tools. Different behavior.

Matt researched Stripe and Salesforce integration and handed them a working path forward. Bobby provided a Stripe Payments Accelerator that let Furniture Bank manage their own flows. Sam coordinated sales, documented edge cases, and guided the migration with her coach supporting the process in the background.

Within a week, Stripe was live. The process was operational. The system was moving. The community Furniture Bank supports remained unaffected.

Buying rhythms, not software

Furniture Bank didn't upgrade its tech stack—they upgraded how they used it

Most nonprofits buy tools and end up with frustration. They invest in platforms that promise efficiency, only to watch adoption stall and workarounds multiply. The software works fine. The people struggle to use it consistently. Leadership blames the tool. The cycle repeats.

Furniture Bank bought something different: a rhythm. A decision stack that turned friction into action.

The Human Stack®'s Digital Guidance® methodology is a philosophy that centers on the musicians, not the instruments. People and behaviors matter more than platforms. Technology is neutral infrastructure. Culture determines whether that infrastructure becomes a liability or an asset. Ascendably, as an authorized The Human Stack® partner, operationalizes this philosophy through a model called Managed Success.SM

Managed SuccessSM isn't consulting. It's not implementation support or training. It's a simple, systematic approach—a weekly rhythm with clear roles and a system for surfacing and resolving friction before it calcifies into dysfunction. The nonprofit designates a Guide who owns the work. The vendor provides a coach who supports the Guide's decisions. Leadership governs by clearing blockers and protecting scope.

For two months before the payment processor collapsed, Furniture Bank had been practicing this rhythm. Weekly meetings. Clear ownership. A shared board where staff could document friction without waiting for permission to escalate. Sam Bernardo, the Sales Manager, recorded Looms showing failed transactions. She dropped receipts into the Guidance request board. She documented delays and manual reconciliations piling up.

Most organizations treat persistent low-level issues as background noise until they become catastrophic. Sam's documentation wasn't dramatic. It was methodical. Week after week, she made friction visible. The team treated it as something to prioritize—annoying, but manageable.

She was pointing at a fault line.

Building culture infrastructure before crisis is what made resilience possible. When the processor shut down, the team didn't start from zero. They had context. They had a system in place. They had someone who owned the process.

 

 

You get what you pay for

If you wanted outcomes but paid for hours. You get disappointment.

Ascendably and The Human Stack® didn't sell hours or deliverables. They didn't sell a roadmap or a set of features to implement. They co-authored a contract for success rooted in shared behaviors, boundaries, and trust.

Traditional vendor relationships optimize for the wrong thing. Nonprofits pay for hours. Vendors deliver tasks. Success is measured by completion, not capability. The nonprofit gets a finished project but remains dependent. When the next crisis hits, they call the vendor again. The cycle perpetuates dependency, not capacity.

Managed SuccessSM flips that model. It defines who leads (the nonprofit Guide), who supports (the vendor coach), and who governs (leadership). The nonprofit owns the decisions. The vendor teaches them to make better ones. The relationship builds capacity, not reliance.

Trust was built through rhythm, so when crisis hit Dan didn't have to double-check his vendor. He'd watched Matt work for two months. He'd seen The Human Stack® protect scope. He'd watched the rhythm absorb friction and turn it into action. When Matt said, "We can do this," Dan's job was to say 'yes' and let him run.

This is what buying outcomes looks like. Not advice. Not a roadmap. A rhythm that can absorb shock.

The contract didn't specify deliverables—it specified behaviors. Weekly meetings happen regardless of urgency. Friction gets documented, not ignored. Scope gets protected, not expanded. The Guide makes decisions with support, not permission. Leadership clears blockers, it doesn't micromanage.

When the payment processor collapsed, those behaviors held. The contract wasn't renegotiated. The rhythm didn't pause. The team executed because the infrastructure was already there.

This model replaces dependency with capacity. The vendor teaches the nonprofit to own its systems. When the engagement ends, the nonprofit doesn't lose capability—it retains the behaviors that made success possible. The rhythms outlast the contract.

Most nonprofits hire vendors to solve problems. Furniture Bank hired a partner to build the system that solves problems. The difference is structural, not semantic.

Same tools, different behavior

Furniture Bank didn't need new instruments—it needed to learn to play together better

The transformation wasn't about smarter staff or new software. It was about consistent practice and role clarity. Sam didn't become a better technologist. She became a better Guide. Dan didn't learn Salesforce. He learned when to step back. Matt didn't write custom code. He taught the team to make decisions faster.

Sam Bernardo, the Sales Manager, recorded Looms showing failed transactions. She dropped receipts into the Guidance board. created habits. Documenting friction became routine, not exceptional. Protecting scope became automatic, not debated. Empowering Guides like Sam to act decisively became culture, not policy.

A well-framed request is an asset. Sam's Looms and documentation weren't complaints—they were intelligence. Her weeks of persistence handed the team a playbook before they knew they needed one. When the floor fell out, they had something solid to stand on.

Most organizations have a Sam: someone who sees the mess before everyone else. The difference is whether that person has somewhere to go with it, and agency to act on it. Managed SuccessSM gave Sam both. She didn't wait for permission. She kept friction visible, built the case, and was ready when it mattered.

Success looks like a system that lets people show up at their best when it matters most. Not heroics. Not scrambling. Just people executing because the infrastructure supports execution.

Managed SuccessSM is the practice space. You do it long enough for new behaviors to become culture. The weekly rhythm isn't dramatic. It's boring. It's the same questions every week. The same roles. The same documentation process. But boring is what holds when everything else breaks.

Furniture Bank didn't use Managed SuccessSM for emergencies. They used it to deal with the boring stuff: failed transactions, manual reconciliations, scope creep. The infrastructure they built for routine friction turned out to be exactly what they needed when it all went to hell.

Guides earn their title in moments like this. Sam didn't become a hero because she solved the crisis alone. She became a Guide because she kept the system working for herself, her team, and all the departments the crisis impacted.

 

Build the rhythm before you need it

Resilience isn't built in the fire—it's built in the rehearsal

If your organization is still deciding who makes calls during a crisis, you're already behind. The time to clarify roles is not when the payment processor shuts down. The time to build trust with your vendor is not when you need them to work a weekend. The time to practice documentation is not when you're trying to migrate platforms in 72 hours.

Rhythms built for everyday friction become the infrastructure that holds under pressure. The questions Furniture Bank used to resolve a failed transaction were the same questions they used to migrate payment processors. The roles that worked for routine Managed SuccessSM meetings were the roles that worked during crisis response. The trust built through two months of weekly rhythm was the trust that let Dan say 'yes' without hesitation.

Without this type of partnership, the cost of disruption is mission-stopping. With it, crisis becomes proof of culture. Furniture Bank's story isn't about avoiding disaster—it's about having the infrastructure to absorb disaster without breaking.

The next evolution of nonprofit digital transformation isn't smarter tools. It's smarter rhythms of trust. Most organizations optimize for technology when they should optimize for behavior. They buy platforms when they should buy practices. They hire consultants when they should build partnerships.

Culture is your real crisis infrastructure. Technology fails. Vendors disappoint. Platforms shut down. But rhythms—clear roles, documented friction, protected scope, empowered Guides—those hold. They hold because they're built on human behavior, not software features.

Buying outcomes means investing in relationships and rhythms that let people perform at their best. It means treating your vendor like a partner who teaches you to own your systems, not a contractor who does work you'll never understand. It means building the boring infrastructure of weekly meetings and documentation practices before you need them to save you.

Furniture Bank made a bet on rhythm over reaction. They built culture infrastructure when things were stable. When the floor fell out, the rhythm held. The sales team kept moving. The community remained supported. The mission continued.

Trust and culture are the real infrastructure that keeps missions alive when systems fail. You can't buy that in a crisis. You have to build it before you need it.

Consider your own vendor relationships: Are you buying outcomes or hours? Are you building rhythms or waiting for the next fire? Start building the rhythm before you need it—because culture is your real crisis infrastructure.