Salesforce Workstream Overview

Center of Excellence + Salesforce — scope, sequence, funding, capacity and ownership for 2027–2028

Leadership Team briefing · Outward Bound USA · v7 · 28 September 2026 · updated for the revised leadership model, the August sales discovery survey and the CoE group sales roadmap

Executive Summary

What this document is

Outward Bound USA has several Salesforce efforts underway or proposed for 2027 and 2028. They have been discussed as separate projects with separate budget lines, which makes them look more expensive, more numerous and less connected than they are. This brief pulls them into a single view so the Leadership Team can see what each project is, how they depend on one another, what they cost, who owns them, and what changes for Schools as a result.

It is a decision document, not a status report. Section 18 lists the choices that need to be made.

The problem we are trying to solve

Each School runs its own Salesforce system, built and customized independently over roughly a decade. That independence is not the problem in itself. The problem is that the Schools and the national office cannot reliably answer shared questions — how many students come back for a second course, where group sales are stalling, how enrollment is tracking across the network — because the underlying data is structured differently in every system, and in some cases is not collected at all. We have also committed to funders, specifically through the Character Compass grant, that we will be able to report on repeat participation across the network.

The work breaks into three layers. Shared foundation is the plumbing: agreed data definitions, a governance agreement, and the Data Pipeline. Business capabilities is where value shows up: group sales automation, a shared enrollment capability, and recovering revenue lost to cancellations. Use and deployment is what happens inside Schools, including bringing every School to a workable minimum.

$560K
Identified funding across AAO and Lilly for 2027–28
11
Salesforce systems — nine Schools plus two national orgs
6 of 7
Surveyed Schools already hold group sales data in Salesforce
0 of 7
Surveyed Schools with a fully automated sales metrics process
3 of 9
Schools that cannot currently connect a student across programs
What changed in v7

1. The leadership model is set. Mike Pigg, COO, leads the first layer of the work: data governance, one unified project with shared expectations and timelines, and buy-in across stakeholders. Theresa Salus and the Center of Excellence, working with their AAO representatives, continue delivering group sales automation and, later, the group-facing portions of the Enrollment Platform. Ben Worden stays on as technical lead, working with vendors on the right output, implementation and strategy for the Data Pipeline and its downstream use in marketing and Lilly reporting. Section 01 sets this out.

2. The sales discovery survey is back. Seven Schools answered 18 questions on who sells, what lives in Salesforce, what is automated and how performance is tracked. Section 07 summarizes what it means for the portfolio.

3. The CoE roadmap now has dates. Five phases run from November 2026 to December 2027. Two of them overlap directly with Data Standards, Governance and the Enrollment Platform; this version reconciles them so there is one set of standards, not two.

The six things worth knowing before the discussion:

  1. These are not independent projects. Four of them need the same conversations with the same people at the same Schools. The unified project Mike leads is the mechanism that stops us asking School staff the same questions four times.
  2. Salesforce adoption is not the gap. Automation and consistency are. Six of seven surveyed Schools keep sales data in Salesforce, but two report no pipeline automation at all and most steps are manual everywhere. Contracting is the only automation pattern Schools share.
  3. The money is identified but split across two grants in ways that do not yet match the work. Resolving which grant pays for what is a decision, not a budget increase.
  4. Schools are not at a common starting point. OBCA has a near-complete group sales flow in Salesforce; NYCOBS runs sales in Google tools. Network reporting is only as good as the weakest inputs.
  5. The Data Pipeline is infrastructure, not a product. Judged on its own savings it looks modest. Judged on what it makes possible, including marketing tools and Lilly reporting, it has the widest reach here.
  6. Capacity is still the real risk, but it has moved. Splitting the work three ways removes the single-person overload on the CoE. The remaining pressure sits on the technical lead role, because the consultant agreement requires a Product Owner at half-time or more. Section 14 covers this.

If you have ten minutes: Section 01 shows who leads what. Section 07 shows where Schools are. Section 12 shows the money. Section 13 shows the order of work. Section 18 lists the decisions.

01 · Leadership Model

Three leads, one project

The work now runs through three clearly separated lanes. Process and governance, School-facing delivery, and technical build are different jobs, and each has a named lead. This replaces the v6 arrangement in which most of the portfolio defaulted to one Center of Excellence role.

Process, governance and stakeholder buy-in

Mike Pigg — COO

Runs the first layer of the work. Owns the data governance agreement, frames the portfolio as one unified project with one roadmap and one timeline, sets expectations with EDs and School staff, and builds buy-in across stakeholders. Holds the decision cadence and ratifies the shared standards once they are drafted and mapped.

Group sales automation and School-facing delivery

Theresa Salus and the Center of Excellence — with AAO representatives

Delivers the first set of deliverables: the five-phase group sales roadmap, School discovery and interviews, the business definitions of shared pipeline stages and metrics, School readiness assessments and the change management toolkit. Carries forward into the group-facing portions of the Enrollment Platform.

Technical lead and vendor strategy

Ben Worden — CMO, technical lead

Works with vendors to decide the best output, implementation and strategy for the overall vision: the Data Pipeline, the standard data model, and how pipeline data feeds marketing and, later, Lilly reporting. Scopes and manages DX Foundation, the network Salesforce engineer and any build consultant, and signs off technically on what the CoE specifies.

How the lanes hand work to one another

HandoffMike PiggTheresa Salus / CoEBen Worden
Shared stages, data and metricsRatifies through governance; takes to LT Drafts business definitions in roadmap Phase 2 (by Feb ’27)Maps them to the standard data model and pipeline
Automation and build requestsChecks timeline and School load Specifies the requirement from the mapped journeyScopes with DX Foundation or the network engineer
Build consultant for the gold-standard instanceApproves timing Identifies willing School(s) in Phase 4Routes through the existing vendor engagement so there is one, not two
School communicationSets network message with EDs Runs School conversationsKeeps vendors out of unstructured School conversations
Marketing and Lilly reporting outputsConfirms permitted use under governance Defines what Schools need to seeDesigns how pipeline data reaches Braze, dashboards and Lilly reports
What this resolves, and what it does not. It resolves the v6 question of whether the CoE lead should also be the Product Owner: the answer is no. It leaves two questions open. First, whether Ben carries the consultant’s half-time Product Owner commitment himself or delegates day-to-day backlog work. Second, the working cadence for the three leads — a short monthly steering check-in with Katie Dalbey for Lilly requirements is proposed.

02 · The Map

One portfolio with three layers

These efforts are usually listed side by side, as if they were equivalent. They are not. One layer is shared infrastructure, one is where revenue and mission value appear, and one is what happens inside Schools. Reading them as layers makes both the order of work and the budget questions clearer.

Layer 1 — Shared foundation (the plumbing)

Data Standards & Baseline

Agreement on the minimum fields, names and definitions every School uses, what moves between systems and what stays local. A standard model already exists as a starting point.

Prerequisite for everything else

Data Pipeline

The mechanism that moves course, application, contact and program data between School systems and the national system. Turned on one data type at a time. Replaces Nintex.

Restart · partly built already

Data Governance

A written agreement on how shared data may be used — reporting and operations now, no fundraising prospecting without a separate network decision.

Unresolved · affects School trust
▼   powers   ▼
Layer 2 — Business capabilities (where value appears)

Group Sales Automation

Common approach to handling inquiries and leads for group programs, so Schools can see where deals stall and compare performance meaningfully.

Underway · CoE-led

Enrollment Platform

A shared enrollment capability, starting with group programs. Open enrollment already runs on the same underlying mechanism. The name Schools and EDs will recognize.

Largest build · 2027

Waitlist & Cancellation Recovery

Recapturing open enrollment revenue currently lost when students cancel for reasons we can influence, and working waitlists more systematically.

Small · quick payback
▼   enables   ▼
Layer 3 — Use and deployment (what happens in Schools)

Repeat Participation (Lilly)

Being able to see when a student returns — a day program, then an expedition, then something longer. Mostly a reporting and data-completeness question once group data flows.

Grant commitment

School Baseline Parity

Bringing Schools without program tracking up to a workable minimum, and reusing what advanced Schools have already built instead of rebuilding it.

Gates the value of everything above

Development / Donor Data

Fundraising systems and donor records. Genuine demand from School development leaders, and the most sensitive subject in the portfolio.

Decision gate, not a 2027 build
Each project carries the same four fields: business outcome  ·  Salesforce deliverable  ·  School value measure  ·  estimated annual value
The portfolio in one sentence: a shared enrollment capability built on shared data plumbing, using group sales as the first real test case, which addresses the Lilly repeat-participation commitment and the sales enablement mandate at the same time — with donor data deliberately held behind a decision gate.

03 · The Projects, Defined

What each project is, what it is meant to achieve, and what changes when it is done

The short descriptions above are deliberately compressed. This section gives each project a fuller definition so there is no ambiguity about what is being proposed, what it excludes, and what a School would actually notice.

1 · Data Standards & Baseline

Layer 1 · Low complexity · Medium School effort
What it is
A negotiated agreement across the network on the minimum set of information every School records the same way: field names, stage definitions, how a lead is recorded, what a completed application looks like, and which pieces of information move between School and national systems. An existing standard model, developed over the last decade and tested across the network, is the starting point rather than a blank page.
What it is not
It does not require Schools to work the same way, use the same processes, or give up customization. It sets a floor, not a ceiling.
Goal
A documented minimum standard that every School has agreed to and can meet, so that data collected in nine places can be read as one picture.
Outcome when complete
  • Network reporting stops carrying caveats about non-comparable data
  • New Salesforce work at any School is built once, correctly, rather than reworked later
  • Schools currently building — and there are several — align now rather than after their systems harden

2 · Data Governance Agreement

Layer 1 · Medium complexity · Low School effort
What it is
A written agreement setting out how shared data may and may not be used. The operative distinction is between using data for reporting and operations, which is the current intent, and using it for fundraising prospecting, which would require a separate network decision. A data governance section was drafted for the National Operating Standards and subsequently removed, so a mechanism outside that process is needed.
What it is not
It does not reopen the National Operating Standards or the Charter.
Goal
An agreement Schools trust enough that sharing group program data no longer feels like a risk to their donor relationships.
Outcome when complete
  • The most common objection to data sharing has a written answer
  • Schools can participate without a standing concern that participants become national prospects
  • Later decisions about donor data start from an agreed framework rather than from scratch

3 · Data Pipeline

Layer 1 · High complexity · Medium School effort
What it is
The mechanism that moves agreed data between School Salesforce systems and the national system, in both directions. It already operates for open enrollment. The work is to restart a paused implementation, add group program data, build a repeatable template so it can be rolled out School by School, and connect the national system to the website and the Customer Engagement Platform (Segment, Snowflake and Braze).
What it is not
It is not a single switch that exposes everything. Data types are turned on one at a time, by decision. Donor data is not in scope.
Goal
Group program data moving reliably between Schools and the national office on a template that can be deployed repeatedly, with Nintex retired.
Outcome when complete
  • One connection point to network data instead of eleven separate ones
  • The $15,000 annual Nintex fee ends
  • Opens a later option to retire the CDP layer, currently around $50,000 a year, once the pipeline carries that function
  • Dashboards, marketing tools and future systems connect once rather than per School
  • Improvements built once can be deployed to other Schools rather than rebuilt

4 · Group Sales Automation

Layer 2 · Medium complexity · High School effort · Underway
What it is
Center of Excellence work, led by Theresa Salus with AAO representatives, to map how group program inquiries are handled today, define a common set of pipeline stages and practices, identify where automation genuinely helps, and give each School a roadmap. Five phases: journey discovery (by Nov ’26), shared stages and CRM practices (by Feb ’27), automation improvements (by May ’27), gold-standard platform design and deployment (by Aug ’27), and network reporting (by Dec ’27). The discovery survey in Phase 1 is complete. Group sales is the first use case for the wider enrollment approach: process first, technology second.
What it is not
It is not a simultaneous network-wide rollout, and it does not cover individual participant sales or multi-week programs.
Goal
Schools operating a common approach to group sales, adapted locally, with visible pipeline and conversion data.
Outcome when complete
  • Faster response to group inquiries, which is itself a conversion factor
  • Schools can see where prospects stall instead of guessing
  • Staff spend less time on manual tracking and follow-up
  • Directly serves the sales enablement mandate the AAO grant funds

5 · Enrollment Platform

Layer 2 · High complexity · High School effort · Largest build
What it is
A shared enrollment capability covering group programs, built on the pipeline and extending components that already exist from the open enrollment build. Rather than designing from theory, the approach is to identify the strongest existing School build, harden it, and make it deployable to others.
What it is not
It is not a new CRM, and it is not a replacement for School systems. It is a capability deployed into them.
Goal
A working model other Schools can adopt at a fraction of the cost of building their own.
Outcome when complete
  • Schools avoid the cost of independent builds — recent School estimates for comparable work have run $30,000–$40,000
  • A consistent enrollment experience for groups and partners
  • The infrastructure becomes something EDs can recognize and describe
  • Open enrollment and group enrollment eventually share one foundation

6 · Waitlist & Cancellation Recovery

Layer 2 · Low complexity · Low School effort
What it is
Capturing why students cancel, building a workflow to move waitlisted students into vacated places, and reducing attrition that falls within our control. This was already included in the prior pipeline scope of work rather than being a new idea.
What it is not
It does not address course inventory decisions or pricing.
Goal
A measurable reduction in cancellations we can influence, and faster backfill of places that do open up.
Outcome when complete
  • Revenue already won is retained rather than lost late in the cycle
  • Higher fill rates without additional marketing spend
  • Clear data on why students leave, which informs everything upstream

7 · Repeat Participation (Lilly)

Layer 3 · Medium complexity · Medium School effort · Grant commitment
What it is
The ability to see a student's full history with Outward Bound — a day program in the autumn, an expedition in the spring, a teacher program alongside it — and report on it. Schools increasingly design deliberate progressions, but the records are currently disconnected. Two evaluation questions sit under this, developed with RYTE at Montclair State: what helps or hinders building a good tracking system, and whether data quality improves as tracking improves.
What it is not
It is not new survey instruments or new evaluation methodology.
Goal
Reporting on repeat participation to Lilly without caveats about missing or incomparable data.
Outcome when complete
  • A grant commitment is met with evidence rather than estimates
  • Schools can see which progressions actually work
  • Alumni and re-engagement become addressable rather than theoretical
  • Future funders can be shown network-level outcome data

8 · School Baseline Parity

Layer 3 · Medium complexity · High School effort
What it is
Targeted help for Schools that cannot currently record program participation in Salesforce, so they reach a workable minimum. It also covers taking what advanced Schools have already built and making it portable, rather than commissioning the same work repeatedly.
What it is not
It is not rebuilding systems Schools already have, and it is not a uniform implementation.
Goal
Every School able to record and report program participation to a common minimum standard.
Outcome when complete
  • Network reporting stops inheriting the weakest inputs
  • The Schools furthest behind stop falling further behind
  • Investment already made by advanced Schools benefits the whole network
  • Every other project in this portfolio delivers its full value rather than a partial one

9 · Dashboards & Network Reporting

Layer 3 · Low complexity · Low School effort
What it is
Reporting drawn automatically from governed data rather than assembled by hand: open enrollment progress, group pipeline health, demographics, and potentially course outcome data. Includes response time to group inquiries, inquiry-to-booking conversion, and forecasting views.
What it is not
It does not add reporting burden for Schools; it draws on data already being captured.
Goal
Boards, the Leadership Team and School leadership able to see network performance without asking someone to build it.
Outcome when complete
  • Network data no longer depends on one person or team being available
  • Board and ED conversations start from shared numbers
  • Staff hours currently spent assembling reports are returned to other work

10 · Development / Donor Data

Layer 3 · High complexity · High School effort · Held
What it is
Fundraising systems, donor records, and the question of whether donor data is ever shared across the network. Demand is real: School development leaders have asked for support, and at least two Schools are actively moving fundraising data into Salesforce. It is also the subject most likely to generate resistance, and has been an open conversation for more than a decade.
What it is not
It is not proposed as a 2027 build, and no network donor data sharing is contemplated in this period.
Goal
A clear recommendation and a published decision point, so Schools know when and how the question will be addressed.
Outcome when complete
  • The most contentious topic is removed from the 2027 conversation without being hidden
  • Schools investing in fundraising systems now do so against known standards
  • A decision gate exists rather than an indefinite silence

04 · At a Glance

The same ten projects, compared side by side

Project Layer Complexity School effort Status Single-sentence goal
Data Standards & Baseline1LowMediumNot started Agree the minimum every School records the same way
Data Governance1MediumLowUnresolved Put permitted use of shared data in writing
Data Pipeline1HighMediumPaused, partly built Move group data between Schools and national on a repeatable template
Group Sales Automation2MediumHighUnderway Common group sales approach with visible pipeline
Enrollment Platform2HighHighScoping A shared enrollment capability Schools adopt rather than rebuild
Waitlist & Cancellation2LowLowIn prior scope Retain enrollment revenue currently lost to cancellation
Repeat Participation3MediumMediumNot started Report repeat participation to Lilly without caveats
School Baseline Parity3MediumHighNot started Bring every School to a workable minimum
Dashboards & Reporting3LowLowNot started Network performance visible without manual assembly
Development / Donor3HighHighHeld A recommendation and a decision gate, not a build

Complexity and School effort are planning estimates based on the August scoping session and prior platform experience, not figures stated in a source document.

05 · Where They Overlap

The overlap is the reason to sequence them together

Several projects need the same conversations, the same Schools, the same consultant and much of the same build. Budgeting them separately counts shared costs more than once and makes the total look larger than it is.

Shared elementProjects that depend on itWhat happens if built separately
School discovery conversations Group Sales Automation · Enrollment Platform · Data Pipeline · Repeat Participation · Parity Five separate requests reach the same one or two technical people at each School
Minimum field and stage definitions Group Sales Automation · Enrollment Platform · Data Pipeline · Reporting Rework, and data that cannot be combined across Schools
Group program data capture Repeat Participation · Enrollment Platform · Reporting · Parity Lilly reporting carries permanent caveats
The pipeline mechanism Enrollment Platform · Repeat Participation · Reporting · Dashboards · future Donor Continued Nintex spend on a tool that is not a long-term answer
Consultant and engineer availability All technical projects Scheduling collisions and paid-for capacity sitting idle
Change management with Schools Group Sales Automation · Enrollment Platform · Governance · Parity Change fatigue, and a sense that scope is expanding without consent
The practical consequence: one discovery process across Schools, run through the Center of Excellence and serving every project, replaces five parallel efforts. This is the single largest capacity protection available in the portfolio.

06 · Where Schools Actually Are

The starting points are further apart than generally assumed

The September 2026 Character Compass subgrant reports asked each School directly about tracking students across multiple program experiences. The answers fall into three groups. Network capabilities cannot produce felt impact until the lower group reaches a workable baseline, because combined reporting inherits the weakest inputs.

GroupSchoolStated positionWhat it means for the portfolio
AdvancedCSIOBS
Cathleen Stone Island
A Salesforce-based Participant Management Database tracks individual students across programs and years, including repeat participation and progression through pathways; focus is now on refining reporting Strongest candidate source model for progression tracking
AdvancedOBCA
Outward Bound California
Salesforce reporting tracks participation across OBCA programs and progressive touchpoints; explicitly lacks visibility beyond its own School and has asked for a shared tracking tool Clear demand signal for the network layer; extend rather than replace
BuildingNYCOBS
NYC Outward Bound Schools
Salesforce restructure underway and being integrated with sales process work; still using spreadsheets for multiple touchpoints; has asked to see models from other Schools Align now, while the build is still in progress
BuildingPOBS
Philadelphia
Working with RYTE and OBUSA on more efficient tracking; current process is a manual count Local instance that another School has already built upon
BuildingVOBS
Voyageur
Students identified in spreadsheets; no Salesforce tracking system yet; a task force is meeting monthly through year end to determine whether contract help is needed Remediation candidate with internal momentum already formed
BlockedCOBS
Colorado
Tracking students across their engagement journey is not currently possible; has deferred its own Salesforce and advertising investments pending clarity on Center of Excellence scope Our delay is directly suppressing School investment
BlockedNCOBS
North Carolina
No significant progress beyond returning cohorts; states the primary need is the ability to connect student experiences in Salesforce, which it does not have Direct dependency on the shared capability
BlockedHIOBS
Hurricane Island
No analysis performed to date; expresses confidence in tracking within its own programs, with work planned for the autumn Stated confidence may understate the work required
BlockedCBOBS
Chesapeake Bay
Subgrant response centred on a research partnership rather than CRM capability. The August sales survey now confirms Salesforce (alongside Asana) for group sales, with agreement and reminder automation Sales side now clear; participant tracking still needs discovery

Positions are drawn from the September 2026 subgrant reports covering all nine Schools. Group labels are an interpretive grouping for planning purposes. The two national Salesforce systems — OBUSA and OBSG — complete the count of eleven.

What has already been built and could be reused

Several Schools have constructed versions of what the network needs. Philadelphia built a local Salesforce instance that Outward Bound California subsequently built upon. Hurricane Island has built sales pipeline functionality with support from the network engineer. Cathleen Stone Island built participant tracking that already answers the progression question. The practical question for 2027 is not whether to build an enrollment capability from nothing, but which existing build to harden, template and deploy.

The Hurricane Island attribution derives from a meeting transcript and is worth confirming directly before it is presented externally.

07 · What the Sales Discovery Tells Us

Most Schools have Salesforce. Few have automated the sales process in it.

The August 2026 sales and partnership discovery survey asked 18 questions about who sells, where data lives, what is automated and how performance is tracked. Seven Schools responded: COBS, NYCOBS, NCOBS, CSIOBS, VOBS, OBCA and CBOBS. HIOBS and POBS are not in the returns and should be added before Phase 1 closes in November.

SchoolWhere sales data livesAutomated todayMetrics trackingReporting cadence
OBCAAll in SalesforceWeb lead alerts, lead conversion, stage updates, email templates, DocuSign contract that auto-marks Won, creates the course and alerts the PM; invoice status via BreadwinnerDashboards and report subscriptions, plus manualMonthly (1-day); quarterly (expeditions)
COBSSalesforce from proposal stage onward; SharePoint legacyDocuSign program agreements; stage updates to sent and closed-wonMostly manual; one Salesforce reportQuarterly revenue; annual
CBOBSSalesforce, with Asana alongsideProgram agreements, partner reminders, invoicing alert to accounting after signatureMixed; Excel work needed on Salesforce dataQuarterly OKRs
VOBSSalesforceGroups campaign in progress with KarenSalesforce plus manualWeekly and monthly
CSIOBSSalesforce, with Tripleseat for capacityTripleseat invoicing for OBP; roster portal; none for youth programsManualBi-weekly; quarterly board; year-end
NCOBSSalesforce, plus an Excel sales playbookNoneManual; wants Salesforce or TableauQuarterly to LT
NYCOBSGoogle Sheets, Sites and Docs; moving to SalesforceNoneMixed across six tools with manual reconciliationAd hoc

Rows are ordered roughly from most to least automated. CBOBS answers combine three staff responses that did not fully agree with each other.

What it means for the portfolio

Reviewer input on the CoE roadmap worth carrying forward

Comments from COBS on the detailed roadmap point to scope the network standard should cover:

08 · School Investment Already in Motion

Two Schools are spending their own money on overlapping work, and both have asked for help

This is the part of the picture least visible in budget conversations. While the network-level work has been in planning, individual Schools have moved ahead on their own, at their own cost, on work that overlaps directly with what is proposed here. Two have asked whether OBUSA can contribute. A third has done the opposite and paused its spending while waiting for us.

SchoolWhat they have done or are doingCost and funding positionWhat it means for this portfolio
CSIOBS Runs group programs only, with no open enrollment. Uses Raiser's Edge for donor data and has been evaluating a migration to Salesforce, partly driven by the network move to a common donation platform. New development leadership is motivated to move fundraising into Salesforce. Already operates advanced participant tracking on the program side. Estimated the migration at $30,000–$40,000 and formally asked whether OBUSA could assist with what it described as an unbudgeted expense An explicit, documented funding request already on record. Also the strongest existing progression-tracking model in the network.
NYCOBS Only overnight programming at one site is recorded in Salesforce today. Other outdoor programs collect course outcome surveys but the data is not entered; some climbing program forms are still on paper. Previously used Salesforce for both sales and fundraising before moving to separate tools. Has now contracted an external developer to upgrade Salesforce so programme and fundraising data sit in one architecture. Separately engaged an IT consultant on privacy and security. Identified a developer at approximately $30,000 and proceeded after OBUSA indicated the School would be responsible for costs Considerable further work is still needed on capturing all programme data, courses, enrollment and lead tracking. Alignment now avoids rework later.
COBS Deferred planned Salesforce enhancements and related advertising investment while awaiting clarity on Center of Excellence scope Spending withheld rather than committed Demonstrates the cost of ambiguity: our planning delay is suppressing School investment
Why the Leadership Team needs to address this deliberately. Funding sits in the Lilly budget that was originally conceived partly to help Schools make exactly these transitions. Internal correspondence has already raised the questions directly: how much is available to support Schools, how much is needed specifically for the two Schools furthest from the standard, and whether any could help those Schools move fundraising data into Salesforce. Those questions are unresolved. Meanwhile Schools are making decisions and spending money.
The choice is not whether to reimburse. It is whether we set a consistent, explainable position — before individual conversations set it for us. Options range from no retrospective support, to support conditional on alignment with network standards, to counting School spend as a contribution toward future fees. Each has different implications for fairness across the nine Schools, several of which have not spent anything and may reasonably ask why others were funded.

09 · Why the Data Pipeline Matters

Its biggest value is what it makes possible later, which is why it loses budget arguments

Judged as a standalone project, the pipeline produces a modest saving. Judged as infrastructure, it changes what the organisation can do next. Most of the capabilities below only become available once there is a single connection point to network data.

Connecting systems to each other today

55

Possible connections across 11 Salesforce systems — nine Schools plus two national orgs. Every new tool must be negotiated, built and maintained against each one separately. Processes become more error-prone and new technology gets slower to introduce.

Connecting through a hub

11

Each system connects once to the national system, which holds the shared view. The website and the Customer Engagement Platform connect to the hub rather than to every School individually.

Vendor documentation prepared before the Northwest school closed describes twelve Salesforce systems. Current planning should use eleven.

What it unlocksWhat becomes possibleWho benefits
One connection point for future technology New tools connect once to network data instead of being negotiated across every School. As technology changes, the cost of adopting or replacing a tool falls substantially. Some capabilities are only available to organisations that can offer a single connection point. OBUSA and Schools — cheaper, faster adoption of whatever comes next
Self-serve dashboards Enrollment, group, demographic and potentially course outcome reporting drawn from governed data rather than assembled by hand. Removes dependence on one person or team being available to produce network numbers. Boards, Leadership Team, School leadership
Marketing tools for non-marketers Salesforce flows and Campaign connections into Braze put basic marketing within reach of Schools that have no marketing staff, without specialist tooling at each location. Schools without dedicated marketing capacity
Richer School records A School's records can be enriched with network context — for example, a group student from one School who later enrolls in an open enrollment course elsewhere. Schools — better customer knowledge and re-engagement
Retiring legacy tooling Nintex is replaced rather than extended, ending its $15,000 annual fee. Once the pipeline is carrying data between systems directly, it also opens a path to retiring the CDP layer, currently around $50,000 a year. OBUSA — direct cost reduction, with a larger second step available later
Room to innovate in ways not yet defined Centralised, governed access is a precondition for capabilities the network has not yet identified. The value is real but cannot be estimated in advance. The network — future optionality
A second-order saving worth naming. Retiring Nintex is the immediate, contracted saving. The larger one sits behind it: once the pipeline is moving data between Salesforce systems directly, the CDP layer — roughly $50,000 a year — becomes a candidate for removal, because the pipeline would be performing much of the function we currently pay for. This is not a 2027 decision and it is not free: it would require re-instrumenting the Customer Engagement Platform, which carries its own cost and risk. It belongs in the picture as a future option rather than a budgeted saving.
How to weigh it: the pipeline should be assessed on what it enables, not on what it saves. Scored on its own savings it will always lose to a project with a visible revenue line. Scored on what it makes possible — including reducing what we spend to run the Customer Engagement Platform at network depth — it has the widest reach of anything in this portfolio.

10 · Technical Debt and a Single Source of Truth

Reducing accumulated technical debt has been an explicit goal since the first engagement

"Technical debt" here means the accumulated cost of systems that were built quickly, customized independently, and now have to be maintained separately. Retiring it was named in the original 2024 advisory objectives alongside consolidating and standardizing systems. Documentation from that work describes the architecture that addresses it, and records that substantial parts are already complete.

ComponentWhat it doesRecorded status
Centralized development Functionality used across School systems is managed from one central configuration rather than maintained separately in each Ready for deployment
Standard data model enforcement A shared data model held in place by configuration, requiring matching definitions while still letting Schools add their own customization above it Ready for deployment
Configurable collection and distribution The mechanism for gathering School data centrally and sending governed data back out Ready for deployment
Website integration with course data Course information surfaced through the public site Needs finalizing
CEP and Snowflake integration Braze connected through Snowflake rather than School by School Needs finalizing
Segment CDP receiving pipeline data Unified profile data flowing from the national system Needs finalizing

Why this matters for the 2027 decision

11 · Timeline

Discovery closes in 2026, building runs through 2027, the donor decision sits in 2028

ProjectQ4 2026Q1 2027Q2 2027Q3 2027Q4 20272028
Unified project & governance (Mike)
Unified School discovery
Data Standards & Baseline
Data Governance
School Baseline Parity
Group Sales Automation (CoE Ph. 1–5)
Data Pipeline restart
Enrollment Platform
Repeat Participation
Dashboards & Reporting
Waitlist & Cancellation
Development / Donor
Discovery and definition Build Deploy to Schools Operate and improve Held — conversation only, no build

Shaped by two anchors from the August scoping session: discovery completing through the end of 2026 with technical work sequenced across 2027, and an expectation that the group build takes roughly half the 14 months the original open enrollment platform required, because existing components are being extended rather than built from nothing. CoE roadmap milestones: Phase 1 discovery by Nov ’26; Phase 2 shared stages and practices by Feb ’27 (the group-sales half of Data Standards); Phase 3 automation by May ’27; Phase 4 gold-standard build with a willing School by Aug ’27; Phase 5 network reporting by Dec ’27. Mike’s governance agreement should land before Phase 2 closes so the standards have somewhere to be ratified.

12 · The Money

More is identified than the conversation assumes, held in four places

SourceAmountYearCurrently associated with
Salesforce Improvement Support$200,0002027 Salesforce and sales journey work — automation, change management, School roadmaps
Sales & Salesforce consultant$50,0002027 Consultant to drive the work
Lilly / Character Compass technology$275,000Unspent Data pipeline and related technology; none drawn to date
Group sales data & reporting$35,0002027 Dashboards, pipeline visibility, forecasting
Total identified$560,000 2027–28Across AAO and Lilly

A split already proposed internally for the Lilly technology funds

Earlier planning correspondence proposed moving pipeline implementation to 2027, reducing it to roughly $150,000, and reserving the remainder — about $125,000 — for supporting Schools directly. That split has not been confirmed, but it is the closest thing to an existing position on how much could go to School-level work, and it bears directly on the investment question in Section 08.

What vendor work has actually cost

EngagementAmountDurationNote
Strategic advisory: foundational assessment$28,0008 weeks Negotiated down from $36,400. System health scans, consolidation roadmap, technical debt strategy
System improvements$164,20015 weeks Negotiated down from $189,400. Split across two fiscal years
Data pipeline and student experience — initial$200,000— Original proposal
Data pipeline and student experience — revised $171,00018 weeks Reduced by shortening the timeline, with Nintex retirement added to scope. $9,500 per week

Approximately $30,000 was subsequently carved out of the pipeline scope to make room for the network Salesforce engineer's time within the same grant funding.

Two patterns worth noting. Every engagement so far has been negotiated below its opening estimate, and the most recent reduction came from compressing the timeline rather than cutting deliverables. The weekly rate gives a reliable unit for sizing 2027 work against available funds, rather than negotiating a total in the abstract.
What remains unresolved: which grant carries which project; whether unspent Lilly personnel budget can be moved to technology; how much is reserved for School support; and whether some scope moves to 2028. Views in the September leadership check-in ranged from an expectation that more will be needed, to an observation that the net budget effect is close to zero because expense and grant revenue release together.

13 · A Proposed Order of Work

Sequencing based on dependency, offered for the Leadership Team to accept, amend or replace

The order below follows dependency logic rather than preference. Projects that prevent rework elsewhere come first, infrastructure follows, and the most sensitive work is deliberately held. Figures are planning allocations against identified funding, not approved budget lines.

TierProjectIndicativeLikely sourceWhy here
1Data Standards & Baseline $25,000AAO consultant Lowest cost, shortest duration, prevents rework everywhere else. A standard model already exists to build from
1Data Governance Staff time— Precondition for Schools sharing group data. Without it every other project carries a trust cost
1Group Sales Automation $200,000AAO / SF Improvement Already underway, owned and budgeted; directly serves the sales enablement mandate
2Data Pipeline restart $175,000Lilly technology Infrastructure for group data, Lilly reporting, dashboards and Nintex retirement. Known scope, known vendor, partly complete
2School Baseline Parity $50,000Lilly technology Schools furthest behind cannot contribute usable data without help, which caps the value of everything above
2Enrollment Platform $75,000Lilly technology Makes the infrastructure legible to Schools and EDs. Extends existing builds rather than starting over
3Dashboards & Reporting $35,000Group sales line Low effort, high visibility. Produces the view that makes the whole portfolio legible to Boards and EDs
3Repeat Participation Within tier 2Lilly technology Rides on pipeline and parity work; remaining cost is fixing gaps at Schools with incomplete data
3Waitlist & Cancellation Within tier 2Lilly technology Already inside the prior pipeline scope; folding it in avoids a separate engagement
4Development / Donor $0 in 20272028 decision Highest complexity and sensitivity. Conversation continues, decision point is published, nothing is built

Indicative allocations total $560,000 against identified funding. They do not include any provision for the School investment question in Section 08, which would draw on the same pool.

14 · Capacity

The load is now split. Three pressure points remain.

v6 warned that one Center of Excellence role would absorb delivery, coordination, School engagement and vendor management while also owning sales enablement. The new model applies the highest-leverage options from v6 in substance: a Product Owner who is not the CoE lead, the consultant carrying project management, and ownership split by layer.

Rolev6 defaultv7 model
Mike Pigg, COOManager on a few itemsUnified project, governance, timelines and stakeholder buy-in
Center of ExcellenceProduct Owner, sales, enrollment, standards, reporting, School engagement, parityGroup sales automation, School-facing delivery, later Enrollment Platform portions
Ben Worden, technical leadExecutive sponsorVendor interface and Product Owner, data model, pipeline, marketing and reporting outputs
Learning & EvaluationConsultedOwns repeat participation and School parity
ConsultantBuild executionBuild plus project management, sequencing and decision capture

Remaining pressure points

1 · Technical lead time

The half-time Product Owner commitment

The consultant agreement requires a named internal lead at half-time or more. If Ben holds that alongside the CMO role, marketing and the Enrollment Platform timeline compete for the same hours. Options: Ben keeps decisions and delegates day-to-day backlog work to a named analyst or contractor, funded from grant personnel underspend.

2 · School staff load

The same few people answer every request

The survey shows sales, CRM and metrics often sit with one or two people per School. One unified discovery, run by the CoE under Mike’s project, remains the single largest protection. A School champion group can carry peer coaching.

3 · Sequencing

Only one active build touching Schools at a time

Standards and governance first, group capability next, parity alongside as School-facing work. Mike’s timeline is the place to hold this constraint.

15 · MOCHA Ownership

Mike manages the portfolio; ownership follows the three lanes

Manager Assigns, supports and reviews the owner
Owner One person accountable for the outcome
Consulted Input required before decisions land
Helper Does defined pieces of the work
Approver Signs off before it goes live
ProjectManagerOwnerConsultedHelperApprover
Unified project, roadmap & timelineLT (confirm)Mike PiggBen, Theresa, Katie, Meg, Mycah, EDsCoE working groupLT
Data GovernanceLT (confirm)Mike PiggBen, Theresa, Katie, EDs, Lach ZempOperations teamLT / Charter body
School investment positionMike PiggMycah BerrymanBen, Katie, Julia, EDsFinanceLT
Technical lead & vendor interfaceMike PiggBen WordenTheresa, Meg, KatieDX Foundation delivery lead, Karen ZelevinskyLT
Data Standards & BaselineMike PiggBen WordenTheresa, Meg, Katie, School CRM ownersCoE (Phase 2 definitions), Karen, DX FoundationMike Pigg → LT
Group Sales AutomationMike PiggTheresa SalusBen, Meg, Sales, MarketingCoE working group, AAO representatives, champion groupTheresa Salus (technical sign-off: Ben)
Data PipelineMike PiggBen WordenTheresa, Katie, School technical leadsDX Foundation, Karen ZelevinskyLT
Enrollment PlatformMike PiggTheresa Salus (group portions)Ben, Meg, KatieDX Foundation, Karen ZelevinskyBen Worden (technical design)
School Baseline ParityMike PiggKatie DalbeyBen, Theresa, Julia, School data leadsKaren Zelevinsky, RYTEKatie Dalbey
Repeat Participation (Lilly)Mike PiggKatie DalbeyBen, Theresa, RYTEDX Foundation, School data leadsKatie Dalbey
Dashboards & ReportingMike PiggBen WordenTheresa, Meg, Katie, FinanceMarketing analytics, Karen ZelevinskyLT
Waitlist & CancellationBen WordenMeg PetersonProgram Sales, customer success teamDX Foundation, Karen ZelevinskyMeg Peterson
Development / DonorMike PiggJulia FarmerBen, School development leadsKaren Zelevinsky, DonatelyLT

Changes from v6: Mike Pigg moves from Manager on selected items to Owner of the unified project and Data Governance, and Manager across the portfolio. Ben Worden moves from portfolio owner to technical lead and vendor interface. Who manages Mike’s own items is for the LT to confirm. This is a proposal for the Leadership Team to confirm or revise.

16 · Who Leads Which Side

Process, School insight, technical build and vendor delivery are different jobs

A lesson from the earlier engagement still applies: vendors should not enter School conversations before internal decisions are settled. Schools hear from OBUSA. The vendor receives a defined scope.

Unified project, governance and buy-in

Mike Pigg — COO

One project name, one roadmap, one timeline. Owns the governance agreement, including permitted use of shared data, a named CRM owner at each School, and how regional and national partnerships interface. Sets expectations with EDs and holds the decision cadence.

School feedback, insight and change management

Center of Excellence — Theresa Salus, with AAO representatives, the CoE working group and School champions

Owns the discovery questions, School conversations, journey mapping, business definitions of shared stages and metrics, readiness assessments, change management and School-specific roadmaps. The Phase 1 survey is complete; interviews and the capability matrix follow.

Technical lead and vendor strategy

Ben Worden — technical lead

Decides with vendors the best output, implementation and strategy for the Data Pipeline and standard data model, and how that data serves marketing and Lilly reporting. Scopes vendor work, keeps one engagement rather than parallel ones, and gives technical sign-off on what the CoE specifies.

Business process strategy and project management

DX Foundation — consultant

The translation layer between business need and system design. Runs the delivery cycle, maintains the decisions board and backlog, and hands suitable execution to the network engineer. Reports to the technical lead; requires a Product Owner at half-time or more.

Technical build

Karen Zelevinsky — fractional Salesforce engineer

Implements defined requirements across School systems and already holds access across most of the network. Already supporting VOBS on its groups campaign, per the survey.

Grant compliance and evaluation

Katie Dalbey — with RYTE (Montclair State University)

Owns the Character Compass evaluation questions and confirms the build meets Lilly commitments.

Risk, privacy and data protection

Lach Zemp — risk management counsel

Reviews the governance agreement and any third-party access arrangement, including School obligations to public school district partners.

Prior-build knowledge

Meg Peterson

Holds the earlier platform scope and discovery materials, so the network does not rediscover what it has already paid for.

17 · The Value Model

Every project needs a number an Executive Director would recognize

This is what moves the conversation from defending a budget line to weighing a portfolio against the revenue, capacity and savings it unlocks. The measures below are proposed methods; the baselines still need to be built.

ProjectHow value is createdHow to calculate itWhere it lands
Group Sales AutomationBetter group conversion Additional conversions × average group program valueSchool earned revenue
Enrollment Platform — groupsStaff time and conversion Hours saved × loaded staff cost, plus additional bookingsSchool capacity and revenue
Enrollment Platform — OEHigher fill rates Additional filled places × average net revenue per studentSchools and OBUSA
Repeat ParticipationStudents returning Additional repeat participants × average value of a subsequent enrollmentSchool revenue and grant compliance
Development / DonorDonor retention and reactivation Improvement in retention rate × average donor valueSchool contributed revenue
Data Pipeline — directTechnology and labour saving Retired licensing, starting with $15,000 annually for Nintex and potentially a further $50,000 for the CDP layer, less the cost of re-instrumenting, plus avoided integration and support hoursOBUSA and School technology cost
Data Pipeline — enablingCheaper future integration Cost of connecting a tool once versus across every system, multiplied by expected future integrationsNetwork technology capacity
Dashboards & ReportingLess manual reporting, less key-person risk Staff hours currently spent assembling network reporting × loaded costOBUSA, Boards, School leadership
Marketing for non-marketersCapability without headcount Campaign activity enabled at Schools with no marketing staffSchools with limited capacity
Data Standards & BaselineAvoided build cost Cost of independent School builds − cost of shared deployment. Recent School estimates for comparable work have run $30,000–$40,000School capital avoidance
School Baseline ParityUnlocks value elsewhere Share of network value currently unreachable because inputs are incompleteThe whole portfolio
Aligned programme and impact dataAccess to funding Grant dollars enabled or protected by shared reporting capabilityNetwork funding
Keep direct and enabling value separate. Direct value is created by the project itself. Enabling value is created elsewhere but depends on it. The pipeline has modest direct value and substantial enabling value, which is exactly why it is disadvantaged whenever it is judged in isolation against something with a visible revenue line.

18 · What the Leadership Team Needs to Decide

Nine decisions, each with a consequence

1

Do we confirm the three-lead model and run the portfolio as one project under Mike Pigg?

If yes: one roadmap, one discovery, one consultant engagement, one story for EDs.
If not: parallel requests reach the same School staff and shared costs keep being counted twice.
2

Do the CoE’s Phase 2 definitions become the network data standard?

If yes: the CoE drafts, Ben maps to the data model, Mike ratifies. One standard, due February 2027.
If not: group sales and the pipeline build to two different definitions and rework follows.
3

Which grant pays for which layer?

One option: AAO funds group sales automation and standards; Lilly funds pipeline, parity, Enrollment Platform and repeat participation. Any Phase 4 build consultant draws from the existing consultant line.
4

What is our position on Schools that have already invested, or expect us to?

If we set one now: we answer CSIOBS and NYCOBS consistently. NYCOBS already describes its Salesforce move as Lilly-supported.
If we do not: the position gets set case by case.
5

How is the technical lead’s time protected?

Options: Ben holds the half-time Product Owner role, or keeps decisions and delegates day-to-day backlog work to a named analyst or contractor.
6

What does the governance agreement cover, and by when?

Proposed scope: permitted use of shared data, a named CRM owner per School, lead capture as part of the minimum, and regional versus national partner ownership. Target: before Phase 2 closes in February 2027.
7

Do we fund School baseline parity as a named project?

If yes: the Schools furthest behind reach a usable standard.
If no: combined reporting inherits the weakest inputs.
8

Do we formally defer donor data to a 2028 decision point?

If yes: the hardest conversation leaves 2027, but governance still draws the boundary now, since program and development data already overlap at some Schools.
9

Do we require a quantified School value estimate before each project proceeds?

If yes: ED conversations shift from cost to return.
If no: we keep defending line items without evidence.