Software students actually use, on top of systems IT can’t replace.
Universities and training organizations operate at the intersection of complex administration, learner-facing software, and research data. The internal systems are old; the expectations are not. Procurement cycles are long, accessibility is non-negotiable, and the firm has to be there in five years. We’ve been building software for institutions for over 25 years.
What we build
Three layers, one institution.
We build the digital products students and faculty actually use, the administrative tools behind them, and the AI capabilities that let staff handle volume without losing the human judgment the work requires.
The internal systems most institutions run (Banner, Workday, PeopleSoft, Drupal, Sitecore, custom .NET) aren’t going anywhere quickly. We don’t argue with that. We build the modern layer on top: the integrations, the workflows, and the experiences that get the institution where it needs to be without forcing a migration nobody asked for.
Accessibility in practice
WCAG 2.1 AA is the target from the first design review.
We design and test for WCAG 2.1 AA, the level ADA Title II holds public institutions to. Accessibility shapes the design system, the component library, and the QA pipeline, so it is part of how the work gets built rather than a remediation pass at the end. We test with axe-core as we go, and a person reviews what automated testing cannot catch, like text baked into an image.
We’ve worked with UW-Madison, UW-Parkside, Special Olympics Wisconsin, and others where accessibility, usability, and longevity matter more than novelty.
What we’ve solved
Two patterns we’ve built for institutions.
Student-facing applications that have to integrate with the SIS, the LMS, and identity, and have to be accessible from day one.
- What we built
- Custom student- and athlete-facing applications integrated with institutional identity providers and content systems, designed and tested to WCAG 2.1 AA.
- Outcome
- Applications that students, athletes, and faculty actually use, and that pass institutional accessibility review without remediation rounds bolted on at the end.
Administrative tooling on top of legacy systems (Banner / Workday / PeopleSoft) where replacement isn’t on the table for years.
- What we built
- Custom administrative applications and integrations that sit on top of existing institutional systems of record, governed by Master Services Agreements with project-specific Statements of Work.
- Outcome
- Staff workflows automated against the data already in the legacy systems, without forcing a migration that the institution isn’t ready to undertake. The legacy systems keep doing what they do; the new tooling absorbs the workflows that no longer fit them.
Where leverage compounds
The opportunities we see most often.
- Student- and athlete-facing applications integrated with the SIS, LMS, and SSO.
- Administrative workflows on top of Banner, Workday, PeopleSoft, and other systems of record.
- AI assistants for staff handling student services, advising, and high-volume inboxes.
- Internal-search and knowledge-base systems that index policy, handbooks, and prior cases.
- Reporting and analytics layers that pull from the institutional warehouse without re-architecting it.
- Accessibility audits and remediation for applications already in production.
How we work with institutions
Built for procurement, not around it.
Engagements are governed by Master Services Agreements with project-specific Statements of Work, the structure institutional procurement is designed for. We’re comfortable with long evaluation cycles, vendor security reviews, accessibility documentation, and the multi-stakeholder approval paths the work actually requires.
We’ve been doing this since 1999, which means the firm has been around as long as the systems most of these projects integrate with. We expect to be around for the renewal.
Tell us where the institution gets stuck.
Identity? Accessibility? An advising backlog? A decade-old internal tool nobody wants to own? Bring the unpolished version. We’ll help you scope an engagement procurement can approve.