How to Get Your Association's Board to Fund AI Initiatives

Picture the boardroom where the slides are polished and the executive team is ready to present their vision for the future of work. Within five minutes, the board members are asking about data privacy, system errors, and whether this is just a passing trend. The pitch is derailed before it even reaches the budget slide. This happens because association leaders often make a fundamental error when seeking funding for new technology: they pitch the technology itself. To secure buy-in, you have to stop pitching artificial intelligence. Instead, pitch the strategic goals the board has already approved, and position this new capability as the necessary vehicle to achieve them.

The pressure to modernize is real, and executives feel the urgency to adopt new tools before they fall behind. But bringing that urgency to the board without a strategic wrapper is a recipe for skepticism. Boards do not fund technology for the sake of technology; they fund solutions to organizational problems. That was the throughline of a panel of five association executives that Sofi Giglio, Account Director at Blue Cypress, moderated at digitalNow 2026.

The trap of the technology-first pitch

When a new capability dominates the news cycle, it is tempting to build a presentation around its features. Executives compile lists of potential time savings, industry benchmarks, and technical specifications. They explain the mechanics of the tools, hoping the board will see the same operational potential they do. But a board of directors is not a technology evaluation committee. Their primary mandate is strategic oversight and risk management.

When you walk into a room and present a standalone initiative focused on a moving target, you trigger their risk-management instincts. They see unknowns. They see a lack of predictability. They worry about data security, member privacy, and the reputation of the association. Securing AI board approval requires a complete shift in perspective. You should not explain this technology to your board any differently than you would explain a new marketing initiative, a membership drive, or a facility upgrade.

The focus must remain entirely on delivering member value. If the conversation drifts into the mechanics of how the models work or which vendor has the best parameters, you have lost the strategic high ground. The board needs to know what the organization will achieve, not the technical specifications of the software that will do the work. When you keep the focus on the member, the technology becomes a background detail in a larger story about organizational success.

Anchoring to your published strategic pillars

The most effective way to secure funding is to use the board's own work as the foundation of your request. Every association has a set of strategic pillars or long-term goals that the board has already debated, refined, and approved. These goals are usually public. They have budget attached to them. They represent the agreed-upon direction of the organization.

Tami Brehm, SVP of strategy, communications, and technology at the American College of Rheumatology, approaches this by starting with the strategy rather than the technology. She identifies the initiatives the board has already aligned on and works the new tools into that existing framework to accelerate the desired changes. This approach removes the friction of asking for permission to do something entirely new. You are not asking the board to approve a novel, untested direction for the association. You are asking them to fund a more efficient way to reach the destination they already mandated.

Consider the typical strategic goals of a membership organization. If one of your published goals is to improve member retention, your pitch is about member retention. The technology is simply the mechanism that will allow your team to personalize member communications at scale, thereby hitting the retention target. If the goal is to expand the association's advocacy impact, the pitch is about giving your advocacy team an edge. The conversation shifts from the risks of a new tool to the benefits of achieving an established goal.

Making the business case undeniable

When you frame your initiative as the "how" rather than the "what," the dynamic in the boardroom changes. The board has already agreed on the "what." They have already decided that expanding the certification program or improving the annual conference experience is a priority. By positioning your request as the operational execution of those priorities, you are speaking their language. You are focusing on outcomes, deliverables, and strategic advancement.

This framing also helps address the inevitable questions about cost and return on investment. If you pitch a standalone technology project, the board will want to see a direct financial return on that specific software. That can be difficult to project when the tools are constantly evolving and the initial implementation requires significant trial and error.

However, building a successful AI business case means tying the funding request directly to a strategic pillar. The budget is justified by the value of the strategic goal itself. You are tapping into the resources already earmarked for organizational advancement. The business case becomes undeniable because it is built on the board's own definition of success. You are simply showing them that the old methods of achieving that success are too slow or too resource-intensive, and that a new approach is required to meet their expectations.

Separating the builders from the operators

Once the board understands the strategic alignment, their next concern will be execution. They will want to know if the current staff has the capacity to implement these new tools without disrupting core operations. This is a valid concern, and addressing it proactively strengthens your overall association AI strategy.

Trevor Balough, senior director of AI at the American Chemistry Council, points to a clear division of labor when staffing these initiatives: run and drive. The IT team and core staff are responsible for the "run." Their job is to keep the organization functioning smoothly, maintain existing systems, and ensure members receive the services they expect. This work is foundational and cannot be compromised.

When organizations try to force their "run" team to also build new capabilities, the result is often burnout, delayed projects, and dropped balls in core services. To move the organization forward, you need a different subset of people focused on the "drive." This group is dedicated to innovation, testing new approaches, and building the systems that will execute the board's strategic vision.

Driving requires a completely different mindset and skill set than running daily operations. It requires comfort with ambiguity, the ability to pivot quickly, and a focus on future capabilities rather than current maintenance. By presenting this operational model to the board, you demonstrate that you have thought through the practical realities of implementation. You reassure them that the association's core functions are protected, while a dedicated effort focuses on accelerating the strategic goals.

Defusing common boardroom objections

Even with perfect strategic alignment and a clear operational plan, board members will ask questions. They will ask about the risks of adopting new technology too early. They will ask what happens if the tool makes a mistake in front of a member.

When you have pitched a technology, you have to defend the technology. You have to explain the vendor's security protocols or the technical safeguards you plan to implement. This puts you on the defensive. When you have pitched a strategic outcome, you defend the outcome. You acknowledge the risks, but you weigh them against the risk of failing to achieve the strategic goal.

If the board asks about the risk of a new communication tool, you remind them of the risk of stagnant member engagement. You explain that doing nothing is a choice that carries its own set of strategic vulnerabilities. This reframing allows you to have a mature conversation about risk tolerance rather than a defensive conversation about software features. You guide the board back to their primary responsibility, which is ensuring the long-term viability and relevance of the organization.

Keeping the focus on the destination

Securing funding for new capabilities does not require a masterclass in technology. It requires a deep understanding of organizational alignment. Boards want to see progress on the goals they have set. They want to know that the executive team is finding the most effective ways to deliver value to the membership.

When you stop pitching the tools and start pitching the outcomes, the friction disappears. You transform a conversation about risk and uncertainty into a conversation about execution and strategic acceleration. The most successful technology initiatives are the ones that disappear into the background, leaving only the achieved mission in plain sight. By anchoring your requests to the board's own strategic pillars, you ensure that the focus remains exactly where it belongs: on the future of the association and the members it serves.