Strategy
“We didn’t know how good we had it.”
A prominent university rolled out a new enterprise software system to replace an aging homegrown legacy system. By many conventional measures, the project was "successful."…
Tech Solutions
Traditional vendor enterprise software usually requires systematic compromise.
Choice is a beautiful freedom that helps shape our lives and day-to-day work.
Within higher education, innumerable choices have to be made in order for institutions to best serve their campus communities.
These decisions also impact the software applications utilized to support the institution’s strategic efforts. But this is where choice often becomes a false dichotomy.
We’ve observed that universities and colleges are, generally, only presented with two main paths for their software solutions: homegrown or vendor. And, whether it’s realized or not, institutions affirm three main statements when jumping from homegrown systems to vendor products:
There are so many other considerations tied up in those statements, but the market very much presents an either/or quandary that bundles these important factors into a packaged deal. This results in the institution needing to pick one path and compromise in certain areas – rarely does a one-size-fits-all solution address the above statements in a way that feels balanced and equitable.
It’s a shame. Colleges and universities should be able to toggle the switches of those statements independently of each other in order to make the best decision for their unique needs. Institutional leadership should have the right to forge a new path and plan of action for how to best tackle their software requirements.
A true freedom of choice should be back in the hands of the institution.
Follow along and join the discussion as we share our thoughts around the homegrown vs. vendor conundrum, and other insights on enterprise software within higher education.
A prominent university rolled out a new enterprise software system to replace an aging homegrown legacy system. By many conventional measures, the project was "successful."…
Building custom software is expensive. It generally involves at least several months of design and development effort, combined with extensive planning and input gathering throughout…
We all share the common objective of solving the technical aspects of these projects as seamlessly as possible, so that you can focus on changing…
The first step is often a zero-pressure phone call to answer questions and explore whether we both feel that there could be a fit.