Shaping the class under a tuition cap
The fall class against a headcount and net-tuition target: pipeline by income band, aid levers, territories, and the family questions with a drafted reply that computes the tuition cap from stated income.
A sample of the app on simulated data. Book a call to click through it live, or to see it on your own exports.
One working session with the people in the seat: which decisions, which systems, what a good week looks like.
The app you see above, running on your own exports instead of the simulated world. Every screen, every decision, your numbers.
Wired to your systems with your permissions, agents proposing, people approving, the ledger recording who did what.
Overview
A college announces a commitment that caps tuition by family income. This app runs admissions and aid on a 53-object-type ontology built from vendor-shaped exports (admissions CRM, student information system, aid system), with agents drafting replies and proposing verifications that a counselor approves.
Decisions it produces
- Send a drafted family reply
- Verify income for a band
- Push a territory
- Adopt a plan
The world it runs on
A simulated residential liberal arts college of 2,400 students: 8,000 applicants, 30,000 alumni, twelve vendor-shaped source systems (student information, admissions CRM, LMS, HR and finance, advancement CRM, card system) and 2.1 million rows of mock data resolved into one ontology.
Every company, person and number in this demo is simulated; anchors are public facts or plausible for the segment. Substitute your own feeds and the same apps run on your operation, with your permissions.