Chanakya B-School

Chanakya School of Modern Management is a postgraduate business school in Hyderabad. We built its admissions website and the content system behind it, so families can compare programmes and the school's team can change anything on the site without a developer.

What was the problem?

The school offers seven programmes, from an MBA and a PGDM to a doctoral route, across three Hyderabad campuses, with a one-year programme in Dubai as well. The brief asked us to merge two earlier design options, the look of one and the content depth of the other, and to include what an established management institute is expected to show: faculty, advisors, governance and student resources.

A school site has two readers who want different things. A parent wants fees, approvals and campus details stated plainly. The admissions team wants every enquiry in one place and wants to edit the copy itself, without waiting on anyone.

What did we do?

This is web design and development and application development, with search, analytics and hosting handled by the same team.

• Programme pages made for enquiries. Each programme has a landing page with a short answer, who it is for, curriculum, careers, fees, admission steps, FAQs and a call-back form. A programme finder filters by level and interest.
• Fees stated openly. The fees page shows what the school has published, and lists what has not been published yet instead of guessing.
• India and abroad side by side. A global pathways page compares the routes, and a separate Dubai page carries the one-year programme and its January 2027 intake.
• Campus and institutional pages. Each campus has its address, hours, phone and a map link. Faculty, advisors, leadership, governance, disclosures and student resources each have a page, and the official handbook and policies are published as PDFs, so the site quotes the school's own documents.
• Neeti, the school's articles section. Writers add articles, photos and diagrams in the CMS.

Where a fact did not exist, the site says so on the page. We would rather show a gap than invent a number.

How does the school's team edit the site?

The CMS sits inside the same application at its own admin address. Staff manage programmes, intake dates, fees tables, pages, FAQs, faculty, campuses, documents and images. Saving a change refreshes the affected pages, the sitemap and the machine-readable summary of the site straight away, with no redeploy. Admins manage logins. Editors change content and follow up enquiries.

What happens when someone sends an enquiry?

The enquiry form and the popup both post to one endpoint. Each enquiry is checked, rate limited, saved in the CMS, and stored a second time in a flat file as a backup. Email to the admissions team, a thank-you email to the family and a row in a Google Sheet run afterwards as background jobs, which retry if email or Google is down. Each enquiry shows whether it was delivered, so none is lost quietly.

The popup is polite. It opens only after a visitor has spent time on a page and scrolled a third of the way, or moves to leave on desktop. Once closed it stays quiet for a while, and it never returns after someone has enquired. On phones it is replaced by a call and counselling bar. The analytics events it sends carry no personal data. Admissions can move an enquiry from new through to enrolled.

How is the site made easy to find?

Every page has its own title, description and canonical address, with structured data for the school, courses, articles, events, FAQs and breadcrumbs. FAQ answers are written so the first sentence makes sense on its own when an AI assistant quotes it, which is the idea behind AEO: being the answer AI assistants give. The site also publishes an llms.txt file that states its known gaps and lists figures an assistant should not state, such as placement percentages. More on this in search and answer visibility.

Google Analytics, Tag Manager and Microsoft Clarity are in place, and enquiry events are tracked for analytics.

How is it run?

The site runs on a dedicated server behind Cloudflare, and we never build on the live copy. Each release is built in a clean folder, checked on a separate port, then swapped in, with the previous two versions kept so we can roll back. A staging copy, hidden from search engines, takes changes first, and the CMS database is backed up on a schedule. This is part of our digital infrastructure work, and the school can add ongoing care on top.

What changed?

• The site and CMS are live, with the January 2027 intake and the Dubai page published. The school's team now edits programmes, fees and dates itself.
• Every enquiry is saved twice and shows whether it reached admissions.
• Search and enquiry results: [RESULT TO CONFIRM]. We will add numbers once the school has approved them.
• Still to come from the school: team logins, the enquiry email addresses, the Google Sheet to connect, Search Console access, fees for the specialised programmes, and real campus photographs. Most campus images are still stock photos.

If you run a school or college and want a site your staff can edit and your families can trust, tell us what you need.