> For the complete documentation index, see [llms.txt](https://release.consumr.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://release.consumr.ai/process-for-product-release.md).

# Process for Product Release

1. A monthly development plan is finalized by the product team (plan is based on a combination of suggestions, R\&D results, bugs, enhancements, client requests etc) – **Responsible: Danish & Gautam**
2. A concept note is created an published on <https://release.consumr.ai> (This domain can only be accessed by Profit Wheelers). Each release will be under the month it is scheduled for. The month page will carry a release calendar that will have a date of release on test and a date of release on App. Read more about the structure of the release notes on the home page of <https://release.consumr.ai> - **Responsible: Danish & Gautam**
3. Once the concept note is ready, a notification will be sent to all by mail and on the teams group (that I have created just today) called, “**Product Updates**” - **Responsible: Danish & Gautam**
4. All key members of ProfitWheel will/should/must go through the updates and revert with questions, suggestions, doubts etc. The Objective will be to ensure that everyone is on the same page. **If there are no questions, it will be expected to get a reaction to the post from each member that they have gone through the notes and are fine with it.** This we need to achieve within a week from the date and time the concept note is released.  – **Responsible: Vivek, Aman, Sweta, Rahul, Poonam, Jason N, Abhinay, Sarabjeet & any other addition to sales, customer success and operations team.**
5. The **Product team** will start to work on the product beyond PoC to make it test ready **Responsible: Danish & Gautam**
6. In the meantime, **Customer Success** & **Product Marketing team** will create a release plan that will include external communication, client communication and support portal upload plan based on all the features the Product Development team is working on and share it with all the stakeholders involved – **Responsible: Aman, Jason, Rahul, Abhinay, Sweta, Poonam**
7. **Sales team** should decide a narrative around it (depending on whether they decide to sell the feature or not) – Either way it should be communicated to all the stakeholders – **Responsible: Vivek, Aman, Jason, Sarabjeet**
8. **Product team**, after completing the internal testing on development environment, will **push the features on test environment** either as they are finished and will intimate everyone through an email and notification on teams group. Reconfirming the date of product release and converting the concept notes to release notes based on any changes that were made during development of the product.  **Responsible: Danish & Gautam**
9. Customer Success, Sales and Operations team will start using and **testing the product** as a process of UAT (User acceptance Test) and follow the bug reporting process to report any bug they encounter. This has to happen way before the release date - **Responsible: Vivek, Aman, Sweta, Rahul, Poonam, Jason N, Abhinay, Sarabjeet & any other addition to sales, customer success and operations team.**
10. Weekly connect call with be schedule to check on the status of the release where all the teams will give their update of the release. – **Responsible: Danish**
11. All release related activities will happen as planned by respective team as per the dates committed – **Responsible: Customer Success, Sales, Operation and Product Team**


---

# 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://release.consumr.ai/process-for-product-release.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.