A 12-week MVP path to a measured pilot, the India go-to-market plan, international scaling principles, and the risk register that gates production release.
Back to architecture & complianceInterviews, design partner, success baseline, data map, purpose register, threat/AI risk review.
Tenant, identity vault, import, catalogue, privacy evidence, roles and logs.
Item-item model, embeddings, rules, feedback, explanations, offline evaluation.
Rights, deletion, retention, incident runbook, restoration and contracts.
Faculty preview, small cohort, staged expansion, measurement and interviews.
Adoption
≥60%
Invited students who view recommendations
Relevance
≥65%
Positive feedback on shown recommendations
Cold start
≥80%
New opportunities exposed within 7 days
Validity
<1%
Invalid prerequisite/eligibility recommendations
Explanation
≥80%
Students finding reasons understandable
Privacy
Zero
Unauthorised personal data sent to model endpoint
Coverage
2×
Eligible catalogue reached vs. popularity baseline
Rights
100%
Valid rights tests completed within internal SLA
Begin with private engineering, management or vocational colleges with an active placement team, a digital student system, a defined catalogue and an executive sponsor.
| Offer | Indicative hypothesis | Scope |
|---|---|---|
| 12-week design-partner pilot | ₹2–5 lakh | One department, measured baseline, integration and outcome report |
| Annual institution licence | ₹4–12 lakh | Varies by active learners, modules, support and integrations |
| Per-active-student option | ₹300–₹900/year | Use only where procurement prefers usage pricing |
| Enterprise implementation | ₹3–15 lakh | Custom connectors, migration, SSO and deployment support |
These prices are hypotheses to validate, not market facts. Avoid a free pilot unless the institution provides executive sponsorship, approved data access, named users, a fixed timeline and a written purchase decision.
Diagnose placement outcomes & discovery problems
Quantify baseline & define pilot decision metric
Demo with synthetic students & public catalogue
Complete security/privacy review before student data
Sign pilot agreement, DPA and success scorecard
Deploy one department, publish evidence, convert to annual
Global expansion comes from a common privacy and product core plus country policy packs. Indian age, consent, retention or incident rules are never hard-coded into recommendation logic.
Expansion Rule
Do not claim worldwide, GDPR, FERPA or other jurisdictional compliance based only on the India design. Each country requires a legal and product gap assessment before launch — a global control plane holds tenant configuration and non-personal metadata, while separate regional data planes hold personal data.
Control: technical and contractual prohibition by default
Control: scoped tokens, service checks, tests, encryption, monitoring
Control: closed sources, structured extraction, deterministic validation
Control: hard rules, verified catalogue, human override
15.1 Production Release Gate — All Must Pass