Strategic Technology Roadmap

Volentas University is a composite institution drawn from patterns we see repeatedly in mid-size research university advancement shops: a CRM transition that has been deferred past the point of comfort, AI adoption outpacing governance, and a technology team stretched well past capacity.

Engagement: 18 months, three phases Last updated August 2026

No institutional data, donor records, or proprietary information from any real engagement appears here. Volentas University is a composite drawn from common patterns across mid-size research university advancement operations.

Executive Summary

Volentas University raises $85M annually with a 140-person advancement operation. The technology supporting this work was built for a different era: a CRM approaching end-of-life, an alumni engagement platform procured independently by a different department, prospect research running on desktop spreadsheets, and three separate AI pilots that no one outside those teams knows about.

These problems are individually common in mid-size advancement shops. They converge here on a 22-month window: the CRM vendor has announced end-of-support, and that deadline compresses every other technology decision, from data cleanup to integration architecture to AI governance, into a timeline the current team cannot absorb at 2.5 FTE. The institution is mid-campaign, so every one of these changes has to happen without disrupting the work that funds the operation.

This roadmap does not assume unlimited budget or staffing increases. It sequences work so that early phases produce the evidence leadership needs to fund later phases, and structures decision gates where the institution can adjust scope as conditions change.

$85M Annual philanthropic revenue

2.5 Technology FTE for 140 users

22 mo Until CRM end-of-support

5 Systems holding constituent data

What We Found

Findings from 40+ hours of interviews, system walkthroughs, data sampling, and process observation across every functional area of the advancement operation.

Urgent

CRM End-of-Life

The vendor has announced end-of-support in 22 months, and the current contract includes vendor-assisted migration only if exercised within the first 12. Requirements gathering, evaluation criteria, and internal alignment on what the next platform needs to do have not started, and the window for vendor-assisted migration is already half gone.

Urgent

Fragmented Constituent Data

Constituent records live in five systems, and gift officers maintain parallel spreadsheets because they do not trust the CRM data. Alumni records and development records diverge on roughly a third of shared constituents, a gap that persists because no one owns the reconciliation process between the two offices.

Exposed

AI Running Ahead of Governance

Prospect research is using a wealth screening API, annual giving is testing generative content tools, and alumni relations is evaluating chatbot vendors. Each choice made operational sense in isolation, but there is no shared policy, no data sharing agreement between the tools, and no assessment of whether any of them meet FERPA requirements for the data they ingest.

Exposed

Technology Staffing Gap

The 2.5 FTE technology team can sustain day-to-day operations for 140 users, but the next 18 months add a platform migration, data cleanup, AI governance, and integration architecture to that baseline. Without additional capacity, the team triages by escalation rather than priority, and data quality and governance work stays at the bottom of the queue.

Functional

No Cross-Functional Pipeline View

Campaign reporting works well enough to produce board decks, but prospect pipeline metrics are department-level only, and no one has a cross-functional view of where the $85M comes from or where the gaps are forming. The reporting infrastructure will need a full rebuild to survive the platform change.

Functional

Compliance Gaps in AI and Vendor Security

FERPA training is current and CRM access controls are role-based, but there is no AI-specific policy, vendor security reviews are handled by central IT with no advancement-specific lens, and nobody has mapped which of the new AI tools process donor PII.

What Needs to Happen

Four workstreams, ordered by dependency: data work enables platform decisions, platform decisions constrain AI options, and none of it holds without the organizational capacity to sustain it.

Know What You Have

Before the institution can evaluate platforms, it needs to understand what the data looks like in practice, which is often different from what the schema describes: where the gaps are, where staff work around the system instead of inside it, and which integrations are formal versus someone's scheduled desktop export.

What this produces

Complete system inventory with actual data quality scores, not vendor-reported ones
Map of workarounds and shadow systems in active use
Data ownership assignments that survive staff turnover

Make the Platform Decision

The CRM transition is the hardest decision on this roadmap and the one with the least room for delay. The selection process should be built on documented requirements from operational reality, with a migration plan that protects campaign operations. Only 25% of CRM implementations hit their planned objectives, timeline, and budget simultaneously. This plan accounts for that.

What this produces

Requirements document built from operational reality, not aspirational features
Evaluation of 3–4 platforms scored against weighted criteria with peer institution reference checks
Migration plan with explicit timeline-vs-data-quality tradeoffs and rollback provisions

Govern AI Before Scaling It

Three teams adopted AI tools independently, each for reasonable operational reasons. But they're invisible to each other and to leadership, and nobody has mapped the data flows or regulatory exposure. This workstream audits what exists, builds a governance framework proportionate to actual risk, and identifies the use cases where AI creates measurable value given the data the institution has today.

What this produces

Inventory of all AI tools with risk classification and data flow mapping
Governance charter with acceptable use policy specific enough to enforce
Go/modify/retire recommendation for each existing pilot with explicit rationale

Build the Capacity to Own This

A technology engagement that leaves the institution dependent on the consultants who built it has failed. This workstream staffs to the actual workload, establishes governance that outlasts any individual, and transfers enough knowledge that the internal team can maintain and extend everything built here without outside help.

What this produces

Staffing model benchmarked to peer institutions with a realistic hiring sequence
Technology governance committee with defined decision authority, not just advisory input
Documentation and training sufficient for the internal team to operate independently

Phased Roadmap

Each phase ends with a decision gate where leadership reviews what was learned, confirms what changed since the plan was written, and decides whether to proceed, adjust scope, or redirect resources.

Phase 1

Diagnosis

Months 1–6

Every recommendation in Phase 2 depends on what this phase discovers, so the work here is diagnostic: interviews, data sampling, system walkthroughs, and process observation. The pressure to start fixing things before the assessment is complete will be significant, and premature action is the most common source of rework in these engagements.

Data

Constituent data audit Sample records across all five systems to score completeness, accuracy, and consistency, and map the workarounds. Every spreadsheet a gift officer maintains outside the CRM is a finding.

Data

Integration mapping Document every data flow between systems, both automated and manual, and identify which integrations are formal, which are someone's scheduled export, and which are copy-paste.

Platform

Operational requirements gathering Structured interviews with every functional area to separate what the CRM must do from what it happens to do, and flag requirements that are workarounds for missing features.

AI pilot audit Inventory every AI tool in use or under evaluation, map their data flows, and classify risk against institutional policy and regulatory exposure.

Org

Governance design Charter a cross-functional technology governance body with defined membership, meeting cadence, decision rights, and a clear boundary between committee authority and department-level decisions.

Org

Staffing and capacity assessment Benchmark the current team against peer institutions, quantify the gap between current capacity and what the next 18 months require, and build the case for the hires that Phase 2 needs.

Decision Gate 1 Leadership reviews findings, approves platform evaluation criteria, and confirms or adjusts Phase 2 scope based on what the diagnosis revealed.

Phase 2

Decision

Months 7–12

This phase acts on what Phase 1 found: platform selection, AI pilot disposition, staffing decisions, and migration planning all converge here.

Data

Data governance operationalization Assign data stewards, build quality monitoring that surfaces problems before they compound, and establish remediation workflows with clear ownership and defined escalation paths.

Data

Integration architecture Design an API-first, vendor-agnostic middleware layer so the institution does not have to rebuild its integrations the next time it changes a platform.

Platform

Platform evaluation Structured demos against the requirements matrix with weighted scoring, and reference checks with peer institutions who are 12+ months post-implementation, selected independently of the vendor.

Platform

Migration planning Data mapping and field-level transformation rules, with the binary choice between timeline and data quality made here explicitly, under leadership sign-off on the tradeoffs.

Governed pilot program Formalize two pilots with defined success criteria, monitoring, and a scheduled review date, and retire tools that do not meet governance requirements, a decision that will face resistance from the teams currently using them.

Org

First critical hire Data analyst or integration engineer, determined by whichever role the staffing assessment identified as the binding constraint. This hire needs to be in seat before Phase 3 begins.

Decision Gate 2 Platform selection ratified, migration timeline and data quality tradeoffs approved, AI pilot results reviewed, and critical hire confirmed. Phase 3 scope finalized; this is the last review before significant capital commitment.

Phase 3

Execution

Months 13–18

Begin the migration, scale what worked in AI, and transition from external guidance to internal ownership. Timeline includes contingency for the adjustments that always surface during implementation.

Data

Pre-migration data remediation Clean what can be cleaned before it migrates, because data quality problems compound during migration; establish the quality threshold below which records do not move.

Platform

Migration Phase A: core data Constituent records, giving history, and pledge schedules, with a parallel operation period alongside the legacy system. Historical giving data migrates in full because it underpins donor reporting, IRS compliance, and campaign counting.

Platform

Adoption and change management Training, feedback loops, early-adopter champions, and a staged rollout that accounts for different learning speeds across functional areas. Most CRM implementations that fail do so at adoption rather than migration.

Scale validated use cases Expand the pilots that proved value to full departmental deployment and integrate with the new platform where the data supports it; use cases that did not demonstrate clear value in Phase 2 are retired.

Org

Knowledge transfer Document every decision, configuration, and operational procedure so the internal team can maintain, adapt, and extend the systems independently by the end of this phase.

Org

Sustainability plan 24-month forward view covering staffing trajectory, contract renewals, technical debt budget, and AI governance review cadence.

Decision Gate 3 Engagement close-out: remaining work transitions to internal ownership with documented next steps, including items deferred or descoped during the engagement.

What Leadership Will Want to Know

The questions a VP of Advancement, a CFO, or a board committee will ask about this investment, and what this engagement is designed to answer.

Fundraiser return on investment: whether the technology enables gift officers to raise more with the capacity they have. Measured as dollars raised per FTE.

Gift officer time allocation: the percentage of frontline time that goes to relationship work versus administrative tasks, tracked over time to determine whether the technology investment shifts the ratio.

Platform adoption rate at 90 days: active usage by functional area, tracked against pre-migration baselines.

Pipeline visibility: a cross-functional view of prospect pipeline, solicitation activity, and close rates that leadership can access without requesting a custom report. This does not exist today and requires both the platform migration and the reporting rebuild to deliver.

Decision-to-action latency: elapsed time between a technology governance decision and its implementation. A governance structure where decisions sit for months is adding process cost without corresponding throughput.

Staff confidence in tools: surveyed at engagement start and end.

Assumptions & Constraints

This plan holds under these conditions. Where an assumption fails, the adjacent column describes the impact and the adjustment.

Assumes

Current budget authority is sufficient for Phase 1. No additional funding required until Decision Gate 1 produces the evidence to support it.

If not

Phase 1 scope narrows to the CRM end-of-life timeline and staffing assessment, the two items with external deadlines.

Assumes

The campaign remains active through the engagement. All technology changes must protect campaign operations and donor relationships.

If not

A campaign pause opens a migration window that doesn't exist otherwise. Phase 3 timeline compresses significantly.

Assumes

Executive sponsorship with decision authority is maintained for the duration of the engagement.

If not

The engagement pauses at the next decision gate until sponsorship is reestablished.

Assumes

Central IT partnership for security reviews, infrastructure, and vendor procurement. Advancement cannot do this alone.

If not

Add 2–3 months to Phase 2 for independent security assessment and procurement process.