> For the complete documentation index, see [llms.txt](https://docs.hesh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hesh.app/introduction/before-start.md). # Before start Every manufacturing company has its own unique way of running its production process. Different companies utilize various CRM, ERP, and MRP systems, and each has its own distinct organisational structure with unique skill sets. This makes preparation an absolutely crucial phase before implementing Hesh. While Hesh can revolutionise your production processes, it's important to assess your company's readiness to ensure a smooth and successful transition. ### **Tips:** * **Team Buy-in:** Successful implementation requires strong team buy-in. We suggest you communicate clearly with all stakeholders the benefits they will get after Hesh implementation. * **Responsible Person:** Designate a single responsible person for managing the Hesh implementation. This person will be your primary point of contact with Hesh support and Customer Success Manager. Consider providing additional motivation to this individual to ensure their commitment to the process. * **Employees Loyalty:** To foster employee buy-in, ask your Customer Success Manager to provide additional materials to present the Hesh solution to your employees and help them understand its benefits. * **Consider Expertise:** Consider utilizing Hesh affiliate partners or integrators to assist with the implementation process. Alternatively, hiring a business analyst can help manage a smooth transition. * **Prepare Thoroughly:** Run through the guidelines related to preparation in this documentation. They will teach you how to prepare a bill of operations for all your products and how to design your organisational structure for seamless integration with Hesh. --- # 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.hesh.app/introduction/before-start.md?ask=&goal= ``` `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.