Before you choose a system,
choose your direction.
Your next system will shape how your institution works. Make sure the decision begins with what your institution needs, what it must protect, and where it wants to go.
Your institution needs a strategy.
Urgency should move you forward.
With a direction you own.
Vendor timelines. Staffing constraints. Rising costs. Expectations for better service and AI-enabled operations. There are plenty of reasons to act.
But a deadline cannot tell you which problem to solve, which capabilities matter most, or which commitments your institution is ready to make.
Strategy turns pressure into a deliberate plan.
“Our vendor has a plan for us. Is it the right plan for our institution?”
“Leadership wants a recommendation, but we haven’t agreed on what must improve.”
“We need to modernize. Do we really need to replace everything?”
“What are we committing to, and which future choices could we lose?”
A product decision can become
an operating strategy by default.
When selection comes first, the institution can inherit commitments it has not fully examined.
A new system. The same friction.
Manual handoffs, unclear policies, and inconsistent data may survive a replacement. Diagnose what comes from the product, the process, and the way decisions are made.
The proposal is only the beginning.
Implementation, integration redesign, training, staffing, and running old and new systems together all shape the economics. So does the cost of changing direction later.
Today’s choice shapes tomorrow’s freedom.
Data access, integrations, identity, contracts, and operating responsibilities determine how easily you can adapt. Know what control you retain and what becomes harder to reclaim.
The right path starts
with your institutional context.
A sound strategy considers the alternatives and the order in which they make sense. Different parts of the institution may need different decisions at different times.
Improve what you have
Address process, configuration, and operational gaps.
Modernize in public cloud
Improve the operating foundation and create room to evolve.
Move selected functions
Change where the need and evidence justify it.
Adopt a SaaS platform
Test fit, maturity, readiness, and the operating model.
Replace the enterprise system
Plan the full transition when the institutional case supports it.
Each path faces the same test: priorities, readiness, risk, architecture, data, operating model, total cost, and future flexibility.
Four focused weeks.
A clearer institutional direction.
Separate institutional need from vendor urgency. Define what matters. Test viable paths. Give leadership a defensible position and concrete next steps.
Introductory fixed fee · Four-week engagement
Introductory pricing is available for a limited time. Pricing is confirmed in your engagement proposal.
Sponsor intake, structured workshops, guided stakeholder input, four decision deliverables, and an executive readout. Remote-first delivery unless otherwise scoped.
Align
Establish why the institution is considering change. Separate evidence, assumptions, and external pressure.
Define
Turn operational realities into priorities, required capabilities, and boundaries the institution must protect.
Evaluate
Test strategic paths for fit, cost, readiness, disruption, risk, and the evidence still needed.
Decide
Agree on what to do next, what to sequence, and which conditions should trigger future decisions.
A position you can explain.
A plan you can act on.
Leadership leaves with a shared account of why change is needed, which paths fit, and what should happen next.
- Priorities for the next 90 days
- Sequenced actions for the next 3–12 months
- Evidence gaps and future decision triggers
- Talking points to explain the institution’s position
The right answer may be to proceed, modernize first, phase decisions, or wait for specific conditions.
Illustrative example. Your roadmap reflects your institution.
Address immediate risks. Establish data ownership and integration requirements. Simplify priority processes.
Validate product capabilities, transition costs, staffing needs, and institutional readiness.
Make the larger commitment when agreed evidence, capacity, and fit conditions are met.
Start the conversation
before the commitment.
Bring the strategy discussion to your leadership team. The advisory overview explains the process, participation, deliverables, and fixed fee.
View the four-page brochure ↓PDF · Four-week Strategy Before Platform advisory
What is your institution weighing?
Use the Advisor to explore your questions and prepare for a more informed discussion.
Institutional priorities.
Practical experience.
David Kent Consulting brings higher education operational and technical experience to the same conversation. We help leaders examine how strategic choices will work in practice, from processes and staffing to integrations, data, and ongoing operations.
You define the criteria. Every path is measured against them.
Do we need to be planning an ERP or SIS replacement?
No. The engagement can help determine whether replacement, modernization, phased changes, or a deliberate decision to wait best fits your institution. The starting point is the institutional problem.
What if we have already started evaluating products?
The strategy discussion can still clarify your criteria, test assumptions, and identify evidence gaps before further commitments. During sponsor intake, we establish where you are in the decision and what the engagement must address.
Who needs to participate?
An executive sponsor and executive working group set direction. Selected functional and technical stakeholders contribute operational realities through guided input and workshops. Sponsor intake, an institutional fact package, and executive pre-work prepare the team before Week 1.
What can realistically be resolved in four weeks?
The engagement establishes decision drivers, requirements and guardrails, an analysis of viable strategic paths, and an executive roadmap. It identifies what is known and what still needs validation. Detailed procurement, implementation planning, and exhaustive product validation require their own scope.
Will the process steer us toward a particular product?
The engagement begins with institution-defined priorities and evaluates viable paths against the same criteria. The outcome can support modernization, a phased approach, formal product evaluation, or waiting for clearly defined conditions.
Own what comes next.
Your institution deserves a direction it can defend, a sequence it can execute, and the freedom to keep evolving.