Anthology Student consulting
Hands-on help with Anthology Student (formerly CampusNexus and CampusVue) from someone who has worked in it since 2007, first as a user and then building on it.
I put AI agents to work, under controls I build, on real student systems with real compliance stakes. Not a chatbot bolted on, and not a pilot that never leaves the lab.
Many schools are being told to “do something with AI” and are right to be wary. The risks are specific: an agent that changes a record it should not, a confident answer that is wrong, student data sent somewhere it should not go, and no way to show an auditor what happened.
Those risks are manageable. They are engineering problems, and they have engineering answers.
Pick a task that is tedious, frequent and easy to check. A reconciliation. A pre-flight check before a deployment. A weekly exception report. I will tell you honestly if a task is a poor fit, including when plain code would do the job better than AI.
It will not make decisions about students. It will not change production data: a person approves and runs every change. It will not be given data we have not agreed to in writing. Those limits are in the design from the first day.
Common questions
AI agents speed up the reading, comparing and checking around the work: studying your systems, drafting code and reports for review, and running the same checks on every record. Whether an AI tool sees your records at all, and which ones, is your decision, made in writing before work starts. Where the answer is no, the agent works on structure, rules, code and counts, and the record-by-record work is ordinary code inside your environment. More on the approach page.
Not directly. Where you have agreed to it, an agent reads a live system, and the tools it is given there are read tools. Changes are rehearsed in test and applied by a person. The full method is on the approach page.
Every handoff includes a walkthrough for your team along with the documentation and runbooks, and I build reports and validator checks that your staff run for themselves rather than tools only I can use. For technical staff, I can set them up with the same agent tooling I use for my own work. If your team needs more than a walkthrough, say so on the first call. See applied AI.
Hands-on help with Anthology Student (formerly CampusNexus and CampusVue) from someone who has worked in it since 2007, first as a user and then building on it.
Connect your student system to everything around it, as changes happen, with a record of every change.
SSRS reports and Power BI dashboards your staff trust, including Crystal Reports rebuilt for the web client, by someone who has used those reports.
Move student and financial aid data between systems with a rehearsal first and proof for every record.
Automation around financial aid data, built by a former aid administrator, with the evidence an auditor asks for.
Take the manual steps out of admissions, registrar, aid and finance work with Workflow Composer and FormsBuilder, inside the system your staff already use.
Nowhere to run an integration? I host and maintain it on Azure, in your subscription or a dedicated one.
The full list, and the three ways an engagement can run.
Tell me what you run and where it hurts. The first call is 30 minutes, free, and you will leave with a clear next step whether or not we work together.