> For the complete documentation index, see [llms.txt](https://docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-budget-archive/intersect-operational-services-overview/procurement-management.md). # Procurement Management {% hint style="danger" %} **ARCHIVED** This page has been archived. It's content might be outdated. {% endhint %} If a proposal has been approved by DReps, pushed through to successful treasury withdrawal and the vendor has selected Intersect to be the named administrator, then Intersect Operational Services team will oversee the entire procurement process. Intersect’s Procurement team will support from contract creation to contract initiation including any legal and financial requirements to consider. As the chosen Administrator, Intersect will complete all required procurement checks, including conducting the necessary KYB/KYC checks. Once this is done, the Intersect Procurement and Legal teams will work to establish a contract between the vendor and the Cardano Development Fund. The Procurement team will collaborate closely with the vendor to ensure delivery milestones are accurately captured and effectively documented, ensuring the smooth processing of smart contract payments. The team will also collaborate with the vendor to ensure that the contract is mutually agreed upon, with both parties in agreement on all content, clauses, and financial terms, before the contract is sent for signature. --- # 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.intersectmbo.org/intersect-knowledge-base/archive/cardano-budget-archive/intersect-operational-services-overview/procurement-management.md?ask=&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.