What Responsible Innovation Looks Like in Nonprofit Technology

Why we’ve changed the way we think about our nonprofit technology roadmap—and why we’re excited to share that journey with our clients.

One of my favorite conversations with clients over the past several months hasn’t been about artificial intelligence. It hasn’t been about dashboards, data platforms, or even our products. It’s been about our roadmap.

We’ve started sharing our updated product roadmap during client business reviews, and I initially assumed it would be a fairly straightforward discussion. We’d walk through what was coming over the next year, answer a few questions, and move on to operational updates or strategic planning. Instead, it’s consistently become one of the most engaging parts of the meeting.

Of course, clients want to know what’s coming next. That’s expected. What surprised me was that they were even more interested in how we decide what belongs on the roadmap in the first place. They wanted to understand why some ideas move quickly while others take longer, how we evaluate emerging technologies like AI, and what influences our priorities. Those conversations made me realize something important: we hadn’t simply redesigned our roadmap. We’d quietly changed the way we think about innovation itself.

Looking back, that probably shouldn’t have been a surprise. Over the past year, many of the ideas we’ve explored in our thought leadership have been building toward this point. We’ve written about asking better questions before building dashboards, treating data as a strategic asset instead of a byproduct of applications, and using AI to enhance—not replace—human expertise. At first glance, those may seem like separate conversations, but they’ve all been leading toward the same conclusion.

Innovation isn’t about building more features. It’s about solving the right problems.

Innovation starts with better questions

The technology industry has always been fascinated by the next big thing. Today it’s AI. Before that it was predictive analytics, cloud computing, mobile apps, blockchain, and countless other technologies that promised to revolutionize the way organizations work. Some of those innovations genuinely changed our industry. Others generated far more excitement than long-term value.

The challenge for software companies isn’t deciding whether to innovate. The challenge is deciding how.

It’s remarkably easy to become a feature factory, reacting to every new trend by adding another capability, another dashboard, another automation, or another AI-powered widget. Before long, products become more complicated, users become overwhelmed, and innovation starts feeling like additional work instead of meaningful progress.

We’ve tried to resist that temptation. Every meaningful roadmap discussion starts with a deceptively simple question: What problem are we trying to solve? It’s all about the questions.

A fundraiser spending two hours preparing for a donor visit doesn’t need AI simply because AI exists. They need faster access to the information that helps them have a more meaningful conversation. A marketing team doesn’t necessarily need another segmentation tool; they need confidence that everyone is working from the same understanding of their audiences. An executive rarely wakes up wishing for another dashboard. They want trusted answers that help them make better decisions.

When we begin with the work our clients are trying to accomplish instead of the technology we want to showcase, the roadmap starts looking very different. To that end, we’re big believers in the Jobs to Be Done Framework, which we’ve written about before.

A roadmap should start conversations—not end them

That philosophy is also why we’ve changed the way we organize our roadmap. Rather than publishing a long list of promised delivery dates, we’ve adopted a Now, Next, and Later framework, along with a fourth horizon that simply asks, What’s Beyond? Instead of pretending we know exactly what the next eighteen months will bring, we’re organizing our thinking around priorities, learning, and outcomes.

That flexibility has actually made our client conversations much more concrete. Instead of debating whether a feature will arrive in October or November, we’re talking about the challenges nonprofits are facing today, the workflows that create unnecessary friction, and the opportunities where thoughtful technology can genuinely make a difference.

Just as importantly, this approach invites our clients into the process. Some of our best ideas have come directly from those roadmap conversations, and the roadmap itself has become less of a presentation and more of a collaborative discussion about where nonprofit technology should be headed.

Why we created ROI Solutions Labs

Of course, not every good idea belongs on a product roadmap. Some ideas deserve room to breathe before they’re ready for a release date, which is why we’ve begun referring to our experimental work as ROI Solutions Labs.

Labs isn’t another product. It’s a philosophy about how innovation should happen. It gives us a place to explore emerging technologies, validate ideas with clients, and learn what genuinely creates value before deciding whether something deserves to become part of the products nonprofits rely on every day.

Maria, our new AI assistant for Revolution CRM, is one of the first projects to emerge from ROI Solutions Labs. It didn’t begin with a mandate to build an AI chatbot. It began with a much simpler question: How can we make it easier for users to find answers without interrupting their work?

Instead of asking how we could add AI to Revolution CRM, we asked where AI could remove friction. Could it help users learn unfamiliar features? Could it answer “How do I…?” questions without requiring someone to search documentation or submit a support request? Could it make the software feel more approachable for new users?

Those questions led us to Maria. Other experiments may lead us somewhere entirely different. That’s exactly what Labs is designed to do: explore what’s possible before deciding what works.

Questions about how clients can more easily interact with their data have led to prototyping of natural language chat sessions with the database itself. It’s amazing, though still in development.

Four principles continue to shape our thinking

• Solve the problem before choosing the technology. Technology should begin with a client need, not a technical capability. Whether the answer is AI, automation, a redesigned workflow, or simply a better user experience, the goal is always the same: remove friction from the work nonprofit professionals do every day.
• Build trust before adding intelligence. AI is only as trustworthy as the foundation beneath it. Clean data, identity resolution, shared business definitions, and thoughtful governance may not be glamorous, but they’re what make intelligent systems reliable. Without trust, innovation simply creates faster confusion.
• Use technology to amplify people—not replace them. The best technology summarizes, recommends, explains, and accelerates. It gives fundraisers more time with donors, marketers more time to think strategically about audiences, and leaders more confidence in their decisions. Human judgment remains at the center.
• Measure success by the friction you remove. The most successful innovations often become almost invisible. They eliminate unnecessary clicks, simplify complicated workflows, and make trusted information easier to access. Eventually, people stop talking about the feature because they’re too busy enjoying the outcome.

Looking ahead

One of the unexpected benefits of sharing our roadmap has been the quality of the conversations it has created. Clients aren’t simply reacting to features—they’re helping shape them. Their questions challenge our assumptions. Their ideas influence our priorities. Their experiences help us decide what belongs in Now, what moves into Next, what remains in Later, and what deserves more time in ROI Solutions Labs before it’s ready for broader adoption.

That’s exactly how we think innovation should work.

If you’re already a ROI Solutions client and haven’t had an opportunity to see our updated roadmap, we’d love to walk through it during your next business review or strategy conversation. Not because we have every answer about the future, but because some of our best ideas have started with a client’s question.

Our roadmap isn’t a promise that we’ve already figured everything out. It’s an invitation to build the future together. We believe the best technology is created through partnership, curiosity, and a willingness to learn alongside the organizations we serve.

That’s what responsible innovation looks like to us. It’s not about chasing every trend or being first to announce the newest technology. It’s about listening carefully, experimenting thoughtfully, and delivering solutions that genuinely help nonprofits spend less time wrestling with software and more time advancing their missions.

ROI isn’t chasing the future—we’re building it thoughtfully, alongside our clients.

Want to learn more about our roadmap or claim ROI Solutions Labs swag? Let’s Talk!