While Microsoft Copilot Studio can create documents and add information, it does not do so accurately, and this is an area that needs improvement. The complexity of the licensing is another concern. Understanding how credits are spent based on different types of messages is unclear and complicated, particularly when explaining to non-technical customers unfamiliar with Copilot.
The user interface of Microsoft Copilot Studio has to be better—much better. I still need a front end on top of whatever I am creating, so I cannot say that it is a complete no-code or low-code development environment. The more we use it, the more we will get to know. Once it has gone into production, I will get to know more. Pricing is another cumbersome thing because we do not want it to be very expensive. There are solutions that are open source and freely available, and people are using them. When we build with the hope that enterprises will like the enterprise-grade solution, they have to be ready to pay. The pricing should be friendly. Currently, I feel it is not all that friendly. I feel that the pricing and licensing methods of Microsoft Copilot Studio are not very conducive. Enterprises who already have licenses may benefit from it, but new customers, SMB customers, and mid-market customers without licenses will find it difficult to absorb the cost because it becomes expensive based on usage. I do not have a solution to this, but I feel there is good scope where pricing can be better. The rationale behind my statement is that most Microsoft tools were primarily driven for enterprises, especially those that are not a must-have. Many applications, like Power Apps, were only used by enterprises or mid-sized companies. However, with AI coming in, everybody wants to use it, so there is a huge market available. If we do not price ourselves to that, we will miss the bus.
For analytics, I prefer using the Power BI platform instead of Microsoft Copilot Studio. When it comes to analytics, though it gives the right insight, the visuals are not of great quality, or sometimes they don't appear at all. For instance, when creating charts of sales on a quarter-on-quarter basis or month-on-month basis in a bar graph or pie chart, Microsoft Copilot Studio doesn't perform adequately. Anything requiring image creation or graphs and plots is not optimal. The graphing features are missing in Microsoft Copilot Studio. Although image creation is available, it lags at times, similar to any other LLM module. When creating content based on graphs or CIO presentations, these features are not developed to a great extent.
Microsoft Copilot Studio is an advanced AI-powered assistant designed to streamline processes and enhance productivity for tech-savvy professionals.
Focusing on intuitive integration and seamless workflow improvement, Microsoft Copilot Studio leverages AI to automate and facilitate complex tasks. It adapts to user needs, promoting efficiency and accuracy across diverse professional environments. By incorporating intelligent analysis and collaborative tools, it stands as a vital addition for...
While Microsoft Copilot Studio can create documents and add information, it does not do so accurately, and this is an area that needs improvement. The complexity of the licensing is another concern. Understanding how credits are spent based on different types of messages is unclear and complicated, particularly when explaining to non-technical customers unfamiliar with Copilot.
The user interface of Microsoft Copilot Studio has to be better—much better. I still need a front end on top of whatever I am creating, so I cannot say that it is a complete no-code or low-code development environment. The more we use it, the more we will get to know. Once it has gone into production, I will get to know more. Pricing is another cumbersome thing because we do not want it to be very expensive. There are solutions that are open source and freely available, and people are using them. When we build with the hope that enterprises will like the enterprise-grade solution, they have to be ready to pay. The pricing should be friendly. Currently, I feel it is not all that friendly. I feel that the pricing and licensing methods of Microsoft Copilot Studio are not very conducive. Enterprises who already have licenses may benefit from it, but new customers, SMB customers, and mid-market customers without licenses will find it difficult to absorb the cost because it becomes expensive based on usage. I do not have a solution to this, but I feel there is good scope where pricing can be better. The rationale behind my statement is that most Microsoft tools were primarily driven for enterprises, especially those that are not a must-have. Many applications, like Power Apps, were only used by enterprises or mid-sized companies. However, with AI coming in, everybody wants to use it, so there is a huge market available. If we do not price ourselves to that, we will miss the bus.
For analytics, I prefer using the Power BI platform instead of Microsoft Copilot Studio. When it comes to analytics, though it gives the right insight, the visuals are not of great quality, or sometimes they don't appear at all. For instance, when creating charts of sales on a quarter-on-quarter basis or month-on-month basis in a bar graph or pie chart, Microsoft Copilot Studio doesn't perform adequately. Anything requiring image creation or graphs and plots is not optimal. The graphing features are missing in Microsoft Copilot Studio. Although image creation is available, it lags at times, similar to any other LLM module. When creating content based on graphs or CIO presentations, these features are not developed to a great extent.
The user was asked about satisfaction with functionality and potential suggestions for additional features.