> For the complete documentation index, see [llms.txt](https://docs.global-entertainment-token.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.global-entertainment-token.org/8.-use-cases-and-deployment-scenarios/8.3-implementation-process-deployment-model-for-companies-and-organizations.md).

# 8.3 Implementation process: deployment model for companies and organizations

<figure><img src="/files/54Y38X1ieiWi2MNm4lnD" alt=""><figcaption></figcaption></figure>

GET offers a three-stage model for corporate and organizational adoption:

Step 1: Light collaboration (non-technical collaboration)

* Introduction of GET Pay (QR code payment / participation bonus distribution)
* NFT sales agent / issuance support
* Limited use of DAO voting function (Google Form + GET collaboration)

Step 2: Platform collaboration (medium-scale collaboration)

* Project page installation on GET Platform
* Voting/support/NFT sales/operation of exclusive content
* Marketing collaboration (SNS campaigns, events)

Step 3: API/SDK level collaboration (full-scale implementation)

* GET token integration within own services
* External ID/ Integration of external ID/Wallet, display in GET Wallet
* Automatic logic for reward distribution and mileage linkage
* On-chain by node linkage or smart contract


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.global-entertainment-token.org/8.-use-cases-and-deployment-scenarios/8.3-implementation-process-deployment-model-for-companies-and-organizations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.