Start with one question.

Best for

A department with a documented source of truth, a named owner, and a queue of questions that repeat every term.

What happens

We index one live source — your academic calendar, handbook, or policy set — and stand CampusQ up against it. Then your team asks it the questions you actually get, and we measure what comes back.

You leave with

• A working CampusQ instance on your own content
• Citation accuracy measured on your questions, not ours
• A baseline of current advising volume and response time

Result

A grounded yes or no, on your own documents — not a demo built from someone else's content.

Best for

A pilot that answered correctly, with an owner ready to point a real cohort at it and a source they commit to keeping current.

What happens

We connect the remaining sources, set access, redaction, and retention rules with your team, and open CampusQ to a live cohort. Every question is logged and categorized from day one.

You leave with

• CampusQ live for a department or cohort
• Advising intelligence: volume, top topics, and coverage gaps
• Deflection figures measured on your own traffic

Result

Usage evidence from your own students, and a documented list of the questions your sources do not yet answer.

Best for

An approved rollout with a business owner, a completed security review, and each source under someone who maintains it.

What happens

We extend CampusQ across departments, integrate with your identity provider and student systems, complete security and accessibility review, and transfer the operating runbook to your team.

You leave with

• CampusQ across departments, with SSO and role-based access
• Audit log, retention policy, and security documentation
• Runbooks, admin training, and a named support path

Result

A system your institution can operate, answer for in a review, and keep current as policy changes.