DAYS 1–3001
Prove one useful signal
Baseline one school segment. Confirm Protech configuration, relationship permissions and one learning-engagement play.
Deliverable: working account view + agreed measures
What if every school relationship owner could see the right stakeholders, relevant learning opportunities and the next helpful conversation?
Jason Wickman · A 50-second point of view · Captions included
AACSB serves schools through membership, accreditation and learning. Our hypothesis: a shared school relationship plan can connect these touchpoints without confusing member engagement with independent accreditation decisions.
A digital foundation exists. Protech documents AACSB’s Dynamics-based AMS and move toward the SaaS Power Platform.
The school journey is changing. The 2026 Global Standards and six-year review cycle provide a timely reason to align relationship plans, learning and support.
See the research and assumptions ↓Explore three proposed plays. Each connects a relationship signal to an owner, an action and a measure.
| School stakeholder | 30-day interactions | Last interaction | Signal |
|---|---|---|---|
| Dean's office | 8 | 3 days ago | Active |
| Accreditation lead | 0 | Not yet | Review |
| Faculty champions | 4 | 5 days ago | Active |
The dean is engaged. The new accreditation lead has not attended an orientation.
Ask the relationship owner to offer a relevant standards briefing and confirm the school's preferred next step.
A mapped relationship becomes useful when the right person knows the next step.
Relevant learning participation
Suggested action requires seller review. No automated outreach.
Dean → accreditation lead → membership owner.
A relevant next step, owned by a person.
Learning participation, stakeholder coverage and handoffs.
Proposed relationship layer across membership and learning. Accreditation evidence, review decisions and authorized access remain in myAccreditation.
School · membership owner
Dean · accreditation lead
Learning · events · resources
Review milestone · human handoff
Value review · next-year plan
I would work alongside your membership, learning and accreditation teams, own the pilot and coach the behaviors that make it useful.
Baseline one school segment. Confirm Protech configuration, relationship permissions and one learning-engagement play.
Run weekly member-engagement reviews. Coach insight-led conversations and test human-reviewed school briefs alongside the existing Protech team.
Review progress against the baseline. Train an internal owner and decide what to scale, adapt or stop.
Targets follow the baseline. We would validate data access, licensing and feasibility before implementation.
I combine revenue leadership, Challenger selling and agents under human management and control to turn account insight into useful action.
I work with a handful of clients, own a focused outcome and leave your team able to sustain it. We establish the operating rhythm, measure progress and hand it over to your people.
15-minute call (free) → Revenue POV (free) → 30-Day Revenue Sprint (fixed fee) → Fractional CRO / Interim VP Sales (from $10K/month).
Dynamics 365 Sales, Dynamics 365 Customer Service, Dynamics 365 Customer Insights, Microsoft 365 Copilot, Copilot for Sales, Copilot Studio, and custom agents under human management and control. We validate the relevant products and existing licenses before proposing implementation.
Start with 15 minutes. If there is a clear fit, agree one focused outcome.
Protech documents AACSB’s Dynamics-based AMS and move toward the SaaS Power Platform. The standards update and six-year review cycle are verified on AACSB’s site. Our hypothesis is to use that foundation for more relevant member engagement. The partner case study does not establish current licenses or every installed module.
This concept proposes school stakeholder mapping, relevant learning engagement and a shared member-support review. Accreditation independence and confidential review materials must remain protected. It does not claim your current system lacks these capabilities. Installed modules, licensing, data availability and integration feasibility need validation. Agents operate under human management and control; their suggestions require review.
Research reviewed October 16, 2026. Company facts are sourced above; CRM design and recommended practices are Agilidy hypotheses. No performance uplift is promised.