Direct Line:

(240) 441-5259

Get your Technology Strategy Audit and secure your church's digital future. Get Started

Technology

The Questions Your Board Should Ask Before Approving Any Technology Purchase

  • 10 Jun, 2026
  • 0 Comments
  • By Good Shepherd Insights
The Questions Your Board Should Ask Before Approving Any Technology Purchase
The Questions Your Board Should Ask Before Approving Any Technology Purchase

The Problem with Technology Purchases

We’ve watched church boards approve six-figure technology investments based on a 45-minute vendor presentation.

TL;DR: Church boards and nonprofit organizations often approve technology purchases without a consistent evaluation framework. This leads to vendor-driven decisions instead of mission-aligned investments. Implementing seven board-level questions before approval transforms technology decisions from reactive to strategic.

Answer Box

  • Create a one-page technology approval template with seven pre-determined questions
  • Require written answers before board votes to prevent vendor-driven decisions
  • Focus on mission capacity, implementation ownership, workflow changes, data portability, total cost, alternatives evaluated, and success metrics
  • Schedule 12-month success reviews at the time of purchase approval
  • Make the framework public to raise preparation standards for staff and vendors Sales teams show up with polished slides. They demonstrate features. They share success stories from similar organizations. The board asks a few questions about cost and timeline. Then they vote.

Three months later, staff struggles with a system that doesn’t match their workflow. The promised integrations don’t work. The vendor’s “similar organization” had twice the staff and completely different needs.

Most boards lack a framework for evaluating technology purchases. Without predetermined criteria, the decision defaults to whoever makes the most convincing presentation.

Research from Deloitte Consulting reveals the scope of this problem. Of 35 organizations surveyed, only one used a comprehensive approach to measuring and managing IT investments. Just 13% monitor the value of their technology decisions after implementation.

This isn’t a church problem. It’s a governance problem affecting organizations across sectors.

Key Point: Without evaluation frameworks, boards default to vendor-driven decisions instead of mission-aligned investments.

How Vendor Presentations Win Without a Framework

Vendor influence operates quietly. Polished, plausible, and reassuring.

The real risk comes from unexamined influence hardening into bias.

Without a framework, board members have no anchor point. They rely on vendor framing of the problem and solution.

The average technology purchase now involves 25 people: 13 from IT and 12 from business lines. That number has increased from 20 the previous year.

More voices should mean better decisions. Instead, it often means more confusion and longer sales cycles where the most persistent vendor wins.

Bottom Line: Without predetermined criteria, board members default to vendor framing instead of organizational needs.

What Strategic Misalignment Costs Organizations

When projects misalign with organizational strategy, they fail 52% of the time.

Organizations lose $109 million for every $1 billion invested in projects. That’s the price of approving initiatives without mission-aligned frameworks.

For churches and nonprofits, the stakes look different. A misaligned technology investment wastes money, consumes staff time, creates workflow friction, and pulls energy from ministry.

We’ve seen churches spend $30,000 on donor management systems that sit unused. The systems required data entry the team didn’t have capacity to maintain. The system worked perfectly but didn’t match operational reality.

The board approved it because the vendor presentation was compelling. No one asked the right questions beforehand.

The Reality: Misaligned technology purchases waste resources and create operational friction compounding over time.

Seven Board-Level Questions to Ask Before Any Technology Purchase

A well-designed governance framework gives every director clarity on responsibilities, decision-making processes, and standards.

This clarity creates focused meetings, faster decisions, and stronger oversight.

These seven questions should be answered before any board vote.

1. What Ministry Capacity Does This Create That Doesn’t Exist Today?

This question forces specificity. “Better communication” isn’t an answer. “The ability to send targeted messages to 500 small group leaders in under 10 minutes” is.

Frame the investment in terms of mission capacity. What becomes possible? What does operating without it cost the organization?

Quantify staff hours, reconciliation time, and missed opportunities. This gives the board a concrete basis for decisions.

Key Insight: Specific, quantifiable capacity gains prevent vague justifications from driving purchases.

2. Who on Our Team Will Own Implementation and Ongoing Management?

Technology purchases fail when organizations assume the system will run itself.

Someone needs to own implementation, maintain data integrity, train new staff, and troubleshoot problems.

If you don’t have a named person with confirmed capacity, you’re not ready to approve the purchase.

Key Insight: Systems without dedicated owners become abandoned investments within months.

3. What Workflows Will Change, and Have We Documented Current State?

Most technology implementations require workflow changes. Staff need to do things differently.

If you haven’t documented how work happens now, you’re buying based on vendor promises rather than operational reality.

Ask to see the current workflow map. Ask how it will change. Ask who will manage that transition.

Key Insight: Undocumented current workflows make evaluating system improvements impossible.

4. What Happens to Our Data If We Need to Leave This Platform in Three Years?

Vendor lock-in is real. Some platforms make it difficult or expensive to export data in usable formats.

Before you commit, understand the exit strategy. How do you get your data out? In what format? At what cost?

This question reveals whether the vendor views you as a long-term partner or a locked-in revenue stream.

Key Insight: Understanding data portability protects you from costly vendor lock-in situations.

5. What’s Our Total Cost of Ownership Over Three Years?

The purchase price is just the beginning. Add implementation costs, training, ongoing support, annual increases, and integration expenses.

Many vendors quote attractive year-one pricing with significant increases in years two and three. Get the full picture before you approve.

Include staff time in this calculation. A “cheaper” system that requires 10 extra hours of manual work each week isn’t cheaper.

Key Insight: True cost includes hidden expenses like staff time, training, and future price increases.

6. What Alternatives Did We Evaluate, and Why Is This the Best Fit?

This question prevents single-vendor presentations from dominating the decision.

If staff only evaluated one option, you’re rubber-stamping a vendor relationship, not making a strategic choice.

Ask to see the comparison matrix. Understand what alternatives were considered and why this option serves the mission best.

Key Insight: Comparing multiple options prevents vendor presentations from driving decisions.

7. What Does Success Look Like in 12 Months, and How Will We Measure It?

Only 13% of organizations monitor the value of their IT investments after implementation. This question puts you in that minority.

Define success metrics before you buy. Time saved. Engagement increased. Errors reduced. Revenue generated.

Schedule a 12-month review at the same meeting where you approve the purchase. Put it on the calendar now.

Key Insight: Pre-defined success metrics transform technology purchases from hopes into measurable investments.

How to Implement This Framework in Your Organization

Just over half of organizations use self-assessment tools to evaluate board efforts. Half don’t have systematic evaluation practices.

Implementing this framework doesn’t require a complete overhaul. Start with one change.

Create a One-Page Technology Approval Template

List these seven questions. Require staff to submit written answers before any technology purchase comes to the board for approval.

The template serves three purposes:

  • Forces staff to think through implementation before committing to a vendor
  • Gives board members consistent information to evaluate
  • Creates a record you reference when the 12-month review happens You’ll notice immediate changes in proposal quality. Staff will do more thorough evaluation upfront. Vendors will know they need to answer substantive questions, not deliver compelling presentations.

Make the Framework Public

Share it with your staff team. Send it to vendors before they present. Post it on your board portal.

Transparency raises the bar. When everyone knows evaluation criteria in advance, they prepare differently.

Review and Refine Annually

These seven questions work for most organizations, but your context might need modifications. Add questions reflecting your specific ministry challenges. Remove questions that don’t add value.

The goal isn’t perfection. The goal is consistency preventing vendor presentations from driving decisions.

Bottom Line: A simple one-page template changes how staff prepare proposals and how vendors approach your organization.

What Changes When You Implement This Framework

The first time you use this framework, you’ll feel the shift.

Vendors adjust their presentations. Instead of leading with features, they address mission capacity. Instead of glossing over implementation, they detail the support structure.

Board meetings get shorter. You spend less time asking clarifying questions because answers are already documented. You spend more time on governance, evaluating whether proposals serve the mission.

Staff proposals improve. When people know they need to answer these questions, they do more thorough evaluation work before bringing recommendations to the board. Weak proposals don’t make it to the agenda.

You make better decisions. Not perfect ones, but better ones. You approve technology fitting your operational reality instead of technology sounding impressive in presentations.

The framework doesn’t eliminate risk. It redirects your attention to risks that matter: mission alignment, implementation capacity, total cost of ownership, and measurable outcomes.

The Shift: From reactive, vendor-driven decisions to proactive, mission-aligned governance.

Applying This Framework Beyond Technology

This framework works for technology purchases. The principle extends to every major board decision.

Predetermined evaluation criteria transform facility decisions, staffing decisions, and program launches.

The pattern is the same. Without a framework, decisions default to whoever makes the most compelling case in the moment. With a framework, decisions align with strategy.

Research shows that 70% of organizations struggle with KPI alignment. The metrics problem stands out when examining misalignments between IT and business strategy.

You need to define before you measure. You need to frame before you evaluate.

These seven questions give you a frame. Use it. Adapt it. Make it yours.

Watch what happens when your board stops reacting to vendor presentations and starts governing technology decisions.

The Pattern: Predetermined evaluation criteria prevent compelling presentations from overriding strategic alignment.

Frequently Asked Questions

What if our board doesn’t have technology expertise?

These questions don’t require technical expertise. They focus on governance fundamentals: mission alignment, implementation capacity, cost transparency, and measurable outcomes. Board members without IT backgrounds ask these questions effectively because they address organizational strategy, not technical specs.

How long should staff spend answering these questions?

For most technology purchases, staff need 2-4 hours to document thorough answers. This upfront investment prevents costly misalignment. If staff struggle to answer these questions, you’re not ready to approve the purchase.

Do we need to use all seven questions for every technology purchase?

Yes. Each question addresses a different failure point. Mission capacity prevents vague justifications. Implementation ownership prevents abandoned systems. Workflow documentation prevents operational mismatches. Data portability prevents vendor lock-in. Total cost prevents budget surprises. Alternative evaluation prevents single-vendor bias. Success metrics prevent unmeasured investments.

What if vendors resist providing this information?

Vendors who resist answering these questions reveal their priorities. Quality vendors welcome the opportunity to demonstrate mission fit, implementation support, transparent pricing, and measurable outcomes. Resistance signals a relationship built on sales tactics rather than partnership.

How do we handle urgent technology needs?

Urgent needs still require answers to these questions. The framework shortens decision time by providing clear evaluation criteria. Urgency doesn’t eliminate the need for mission alignment, implementation planning, or cost transparency. It focuses the board on answering predetermined questions rather than starting from scratch.

Should we modify these questions for small purchases?

Small purchases still benefit from this framework. Lower dollar amounts don’t eliminate implementation requirements, workflow impacts, or the need for measurable outcomes. Scale the depth of answers to investment size, but maintain the structure.

What if our current vendor relationships don’t meet these standards?

Use the 12-month review question to evaluate existing systems. Schedule reviews for current technology investments. Document gaps between current performance and these standards. Use the framework for renewal decisions and competitive evaluations.

How do we build staff buy-in for this process?

Frame the template as a tool improving proposals, not a barrier. Staff who answer these questions upfront bring stronger recommendations to the board. The template prevents last-minute board questions and speeds approval for well-prepared proposals. Good staff work gets recognized faster. Weak proposals get identified earlier.

Key Takeaways

  • Church boards and nonprofits approve technology purchases without consistent evaluation frameworks, leading to vendor-driven decisions instead of mission-aligned investments
  • Only 13% of organizations monitor technology investment value after implementation, and projects misaligned with strategy fail 52% of the time
  • Seven board-level questions transform technology governance: ministry capacity created, implementation ownership, workflow documentation, data portability, total cost, alternatives evaluated, and success metrics
  • A one-page technology approval template requiring written answers before board votes prevents vendor presentations from driving decisions
  • Making the framework public raises preparation standards for both staff and vendors before presentations reach the board
  • The framework shifts boards from reactive, vendor-driven decisions to proactive, mission-aligned governance of technology investments
  • Predetermined evaluation criteria apply beyond technology to facility decisions, staffing, and program launches
Tags:
  • Strategy
  • Ministry
  • Leadership
Background Pattern

Get a Technology Strategy Audit

Wrong tools, underutilized software, vendor overcharges. Get a professional assessment of your current tech stack and a strategic roadmap forward.

Background Pattern
Good Shepherd Insights

Good Shepherd Insights

Fractional CTO

Fractional CTO providing strategic technology leadership for mid-sized churches.

Learn more about Good Shepherd Insights →