Student information system modernization
The SIS is the spine of the institution. Replacing or re-platforming it is the highest-stakes IT decision a college makes — sequenced so enrolment never stops.
Fractional CIO and transformation leadership for universities, colleges, polytechnics and private post-secondary institutes modernising the systems that run enrolment, student records and administration. Where legacy student-information platforms, fragmented data, and multi-stakeholder governance make every system decision slower and higher-stakes than the vendor demo implies.
Sector-specific. Every higher education engagement is built around these levers, not a generic CFO playbook.
The SIS is the spine of the institution. Replacing or re-platforming it is the highest-stakes IT decision a college makes — sequenced so enrolment never stops.
Admissions, registrar, finance, advancement — each on its own system. One defensible student-and-revenue picture across all of them.
Faculty, administration, board, IT. The steering-committee discipline that gets a system decision made instead of studied for three years.
FIPPA, FERPA, PIPEDA — student-records privacy is non-negotiable. Built into every system rollout, not bolted on after an audit.
Failed ERP and SIS rollouts are common in higher ed. Recovering a stalled, over-budget implementation before it gets written off.
Eight-vendor RFPs, multi-year contracts, integration promises. The discipline to choose the platform that fits, not the one with the best demo.
We don't sell what we haven't run. Every engagement led by a partner who has been inside the function.
Universities, colleges, polytechnics and private post-secondary institutes modernising core administrative and student systems.
Marcin Samiec. Fifteen-plus years in IT strategy and transformation, with active higher-education engagements.
Yes — project rescue and turnaround on over-budget or stalled SIS/ERP rollouts is a core part of the work.
Yes — FIPPA, FERPA and PIPEDA compliance is built into every records-system rollout, alongside the broader privacy-and-security capability.
No — we lead strategy and the hardest decisions at the CIO level, then hand a steady-state operation back to your internal team.