The institutions we've worked with, measured.
"We don't sell transformation. We project-manage it."
See our processThe Engagement Framework
Five phases. No surprises.
Every engagement follows this sequence. The deliverables below are not aspirational — they are contractual.
Phase 01
Audit
We read the room before we touch anything.
What Happens
A four-week structured discovery covering every system currently in production — SIS, LMS, CRM, payment gateways, authentication layers, and data warehouses. We interview twelve to twenty stakeholders across academic affairs, IT, and administration. We map every integration, document every workaround, and identify every compliance gap.
What You Receive
A 60-page Systems Audit Report: current-state architecture diagram, risk register with severity ratings, vendor contract expiration calendar, and a prioritized remediation backlog. This document becomes the project charter for everything that follows.
Sample Deliverable
Phase 02
Architecture
No vendor recommendations until the blueprint is done.
What Happens
Using the audit findings, we design the target-state architecture — the system your institution will run on in three years. We evaluate vendors against your specific constraints: enrollment size, budget cycles, IT staff capacity, and existing contractual obligations. We write the RFP if needed.
What You Receive
A Target Architecture Document with annotated system diagrams, a vendor evaluation scorecard with our recommendation and rationale, a data governance framework aligned to FERPA and applicable state regulations, and a realistic total cost of ownership projection.
Sample Deliverable
↑ Vendor recommendation: Canvas LMS (score: 87/100) over Blackboard Ultra (score: 62/100)
Phase 03
Migration
Data moves in phases, not all at once.
What Happens
We execute the migration against a published Gantt chart with weekly status reporting to your steering committee. Student records, historical transcripts, financial aid data, and HR systems each have their own migration lane with rollback procedures documented before a single record moves.
What You Receive
A live migration dashboard accessible to your project team, weekly written status reports, a data validation checklist signed off by your registrar and IT lead, and a post-migration audit confirming record integrity across all moved data sets.
Sample Deliverable
Phase 04
Training
Adoption is a project deliverable, not an afterthought.
What Happens
We build role-specific training curricula for administrators, faculty, and support staff — not generic vendor tutorials. Adjuncts who teach one section get a different onboarding path than department chairs managing curriculum workflows. Completion is tracked, and we don't close the training phase until 90% of target users are verified.
What You Receive
A Training Completion Dashboard showing adoption by role, department, and campus. Written SOPs for the fifteen most common workflows. A recorded library of institution-specific tutorials. A 30-day post-launch support window with a dedicated Slack channel for your team.
Sample Deliverable
Phase 05
Handoff
You leave with documentation, not dependency.
What Happens
The engagement ends when your internal team can operate, troubleshoot, and extend the system without us. We conduct a formal knowledge transfer over two weeks, document every custom configuration, and introduce your team to vendor support escalation paths. We are not interested in retainer relationships that substitute for institutional capability.
What You Receive
A complete System Operations Manual, an IT runbook for the twenty most common incident scenarios, vendor escalation contact sheets, a 90-day post-handoff check-in call, and a one-year anniversary review offer at no additional cost.
Sample Deliverable
Anonymized Case Results
What the work actually looks like.
All figures verified by client project sponsors. Institution names withheld by agreement.
Midwest, 14,000 students
The Situation
State compliance deadline for unified student data reporting — 9 months out, zero data governance framework in place.
Deployed compliant data warehouse, migrated 12 years of records, met deadline with 6 weeks to spare.
Southeast, 3 campuses
The Situation
Three campuses running three different LMS platforms. Faculty cross-teaching between campuses couldn't access each other's course shells.
Consolidated to single Canvas instance. Cross-campus course sharing went live in semester two of the engagement.
Northeast, R1 Institution
The Situation
CIO inherited a 15-year accumulation of shadow IT — 47 separate SaaS subscriptions, no SSO, no data dictionary.
Rationalized to 18 core systems, implemented SSO across all platforms, built first-ever institutional data dictionary.
Engagements spanning 2019–2025 · All outcomes independently verified by client steering committees
The 90-Day Migration Playbook
A practitioner's guide to planning, sequencing, and executing a campus-wide system migration — without losing data, faculty trust, or your job.
Contents (48 pages)
Free Download
Not ready to talk yet?
Start with the playbook.
48 pages. No fluff. The actual sequence we use with every client, packaged for you to run internally or bring to your next board presentation.
First Engagement
Request Your
Systems Audit.
We'll schedule a 30-minute scoping call, review what you share with us, and return a no-cost preliminary audit scope within five business days — a written document outlining what a full engagement would cover, and what it would cost.
What happens next
We confirm receipt within one business day.
A senior consultant reviews your submission before calling.
You receive a preliminary scope document, in writing, before any further commitment.