> For the complete documentation index, see [llms.txt](https://docs.mulearn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mulearn.org/partner-engagement/how-mlearn-connects-with-companies.md).

# How μLearn Connects with Companies

μLearn reaches out to companies through:

* **GTech consortium** - μLearn operates under GTech, a consortium of technology companies in Kerala. GTech member companies are the first point of engagement.
* **Campus activations** - companies are introduced to μLearn through campus events, challenges, and Launchpad hiring cycles.
* **Initiative partnerships** - companies are brought in as challenge sponsors, mentors, and hiring partners through flagship programs like In50Hours, Top 100, and Launchpad.
* **Direct outreach** - the μLearn core team maintains dedicated Points of Contact for company relationships, organised by geography in Trivandrum, Kochi, and Calicut.

## <mark style="color:$primary;">For Colleges and Institutions</mark>

If you are a college or institution your entry point is a Campus Node activation, not a standard partnership.

Go to **Campus Nodes** to understand how to activate a node and sign an MOU.

## <mark style="color:$primary;">For Government Bodies</mark>

If you are a government agency in your entry point is a skilling program co-design or GovTech challenge.

Go to **Section 11 - Replication and Expansion** to understand how μLearn scales with government support.

## <mark style="color:$primary;">How to Start</mark>

Every partnership begins with a conversation.

{% hint style="warning" %}
**Manual Intervention:** All partner engagements are initiated through partner inquiry form. Formal agreements require core team sign-off.
{% endhint %}

[**Start a partnership conversation →**](https://mulearn.org/contact)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mulearn.org/partner-engagement/how-mlearn-connects-with-companies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.