Skip to content
Thinkclub Logo
Consult Us

Zero to Live — Companion Guide to the MITCAT Case Study

The operational playbook behind MITCAT’s transformation: what we did in which order, which tools we chose, and what a new college should copy versus customise.

12 min read

Read the case study first

The MITCAT story on our Work page is the outcome narrative — 590 accounts, .ac.in live, social presence established. This companion is the sequencing document: the order of operations when a greenfield agriculture college has accreditation momentum but zero digital identity.

Use it as a checklist for your own steering committee. Swap crop science for your discipline; keep the layer order.

Month 0 — Legal name, ERNET paperwork, board resolution

Before design or demos, align the legal name on AICTE/UGC letters with the ERNET registrant form. Pass a board resolution authorising domain request and institutional email policy.

Parallel track: inventory every Gmail and WhatsApp group already in informal use — you will migrate or retire them.

Month 1–2 — Domain, site skeleton, identity system

ERNET delegation and DNS handoff come first. Ship a credible single-page site on the .ac.in host while the full information architecture is drafted.

Lock logo, colour, and typography before departments print orientation kits. MITCAT’s crest appears on everything from lab coats to Instagram — because we froze master brand early.

Month 2–3 — Google Workspace and role-based provisioning

Verify domain, provision leadership and registrar, then roll waves by department. Student accounts follow a naming convention published before day one.

Enable shared drives for accreditation evidence and marketing assets — not personal My Drives.

Month 3+ — Social, events, and capacity

Stand up five platform presences with one content calendar owner. Train two faculty on livestream basics before the first founders’ day.

Open a micro design lab so students ship posters under brand guardrails — capacity outlasts vendor contracts.

What we deliberately did not buy

No monolithic ERP in semester one. No paid LMS before courses stabilised. No custom mobile app. Low-cost, institutional-grade tools first; licensed complexity only when data models are clear.

Related

Infrastructure

Put this into practice on your campus

ERNET edu domains, email, DNS, and low-cost institutional stacks.