MISSION 01

Xavier International CRM

A CRM and a custom site built as one system. Every dynamic page and every enquiry runs through it.

CLIENTXavier International College
ENGAGEMENTCustom CRM, custom site, and the workflows joining them
STACKREACT · EXPRESS · AWS
LIVE ATxavier.edu.np
The Xavier International College website homepage
PLATE 01The public site, driven from the CRM
Xavier International brand cards for A-Level, +2, Bachelors and Masters, and School, each with its Kathmandu location
PLATE 02Xavier International across its programmes and campuses

THE PROBLEM

There were no workflows. Not bad ones, none. Nothing routed an enquiry to a person, nothing recorded that it had been answered, and nothing tied what the site said to whoever kept it true.

WHAT WE BUILT

  • A custom site with every dynamic section driven from the CRM, not edited as markup.
  • Enquiry capture, so a form submission becomes a record with one owner.
  • Content workflows for courses, news and events, and the public QA reports.
  • Reporting per intake, because that is how an academic year is actually shaped.

THE DECISION THAT MATTERED

Site and CRM are one system, not a CMS bolted to a CRM. A course page exists so somebody enquires about that course, and the person answering needs to know what the page says today. Splitting them would have invented an integration problem.

The harder half was designing a process for people who had none, then getting it used. A workflow imposed on a team that never had one gets abandoned quietly, so no step exists unless it removes work somewhere else.

ALL MISSIONSSTART SOMETHING LIKE THIS