APEX runs on business partnerships. Partners provide real-world projects, job shadows, guest speakers, and eventually hiring pipelines for student-associates. These relationships are what make APEX different from a regular class. But for years, the institutional memory of those relationships lived in individual instructors' inboxes, mental notes, and conversations — and it evaporated between semesters.
A partner would return in the fall and get re-introduced to APEX as if nothing had happened the previous spring. An instructor would walk into a meeting not knowing what a colleague had discussed with that company three months ago. When partners crossed between APEX and district-level contacts, nobody had the full picture. The history was there — it just wasn't anywhere.
The BPRM is built to fix that. It doesn't change how instructors manage relationships; it captures what they're already doing and makes it retrievable.
CRM systems fail when logging feels like a chore. The BPRM is designed around the opposite assumption: if logging takes more than 30 seconds, it won't happen consistently. Every logging method in the system is optimized for the situation where an instructor has just walked out of a meeting or off a phone call and has about 10 seconds before the next thing.
That's why Slack is the interface — instructors are already there. A plain-English message in a channel is the lowest possible barrier. The system reads the intent and does the structured data work on the other side. Instructors never fill out a form.
The most visible output of the BPRM is the pre-meeting brief — a 30-minute-before prompt that tells you what you need to know before you walk into the room. But that's a symptom, not the goal. The goal is that APEX as a program carries relationship history across semesters, across instructors, and across people who may have never met the partner in person.
This changes the professional dynamic considerably. A partner who returns for their third project doesn't have to re-establish context. An instructor who's newer to the program can walk into a meeting with a Core partner and already understand the relationship's history and current health. That's what a mature professional organization looks like — and the BPRM is the infrastructure that makes it possible for APEX to present that way.
Every project is logged against a partner, a course, a semester, and the student-associates involved. This builds a record that cuts both ways: when a partner asks "which students worked on our last project?", there's an answer. When a student-associate needs a reference or portfolio evidence of their business engagement, the record exists.
Over time, this data also connects back to the APEX Alumni LookBook and the broader story of what APEX-trained student-associates go on to do — a record that matters for the program's institutional credibility.
The BPRM could have been built on Salesforce or HubSpot. The decision not to use those tools was deliberate:
The stack is intentionally low-tech and low-cost. If Russ left Waukee tomorrow, another instructor with basic tech comfort could maintain this system. That's a feature.
APEX partners don't exist in isolation — some of them are also district-level business relationships managed by Lexi Shafer (District Business Relationship Manager) and Shane Scott (Director of Postsecondary Readiness). Before the BPRM, those two worlds had no shared record. A district contact might reach out to an APEX Core partner without knowing the depth of the existing relationship, which risked undermining trust the program had built over years.
The district expansion is designed to solve coordination without creating bureaucracy. The key concepts:
Lexi is an active logger — she manages her own portfolio of district relationships and the system works for her the same way it works for APEX instructors. Shane is primarily a reader and strategic querier — he uses the system to understand the employer landscape for postsecondary readiness planning, not to manage relationships day-to-day.
A partner who has worked with APEX across three semesters and two instructors sits down for a meeting. The instructor who scheduled it has never met them before. But she pulled a Brief beforehand, so she knows who their primary contact is, what the last project delivered, how the relationship is currently trending, and that there's an open follow-up item from March. The partner doesn't have to re-tell their APEX story. The instructor doesn't have to pretend she knows things she doesn't. The meeting moves faster and at a higher level — because the history is preserved and accessible.
That's the system working as intended.
The BPRM was designed by Russ Goerend, who manages the DWT course within APEX and has been building these business relationships for years. He built the system because he'd lived through the problem himself — watching institutional memory evaporate, re-introducing partners who deserved better, and knowing that the relationships APEX depends on require more care than anyone's inbox can provide. Like the student portfolio system, this is an educator solving a real operational problem with tools available to him, not a vendor product retrofitted to fit the program's needs.