One of the things we try to improve with Atlas CRM is the way you manage your sales process. The sales functionality we are building, makes it possible to use the benefits of Atlassian products in your sales workflow. Many of you have tested the sales functionality and you have massively provided us with feedback for improvement and questions about our approach.
There is one question I would like to answer in this blog-post, because we get it on a regular basis:
Why don't you use issues for Sales in Atlas CRM?
A sale in Atlas CRM
To understand this question, you need to know something about sales in Atlas CRM. To help you manage your sales, Atlas CRM allows you to capture specific information about each sale:
- Who is working on the sale
- What customer is involved with the sale
- How much revenue the sale could bring in
- What work needs to be done to win the sale (Jira issues)
- And more..
All of this information is available in a new object, which we call a sale. The sale object gives you an overview of all of this information and allows you to easily add- or update information.
The question above is about this object. Why have we built our own sale object? Why didn't we just use Jira issues to capture all of this information?
The answer to this question is in our vision.
Atlas CRM is available for Jira and Confluence, which we both use every single day. We do not prefer one product over the other and want to offer the same experience inside both products. This is why we strive to provide you with the same Atlas CRM functionality in Jira and in Confluence.
When we started building the sales functionality in Atlas CRM, we decided to build it in Jira. We had to choose between Jira or Confluence, simply because we can't build it in both products at the same time. But from the start, our goal has been to bring the same functionality to Atlas CRM for Confluence.
Issues are not available outside of Jira. Our choice to not rely on issues allows us to bring the sales functionality to other Atlassian products such as Confluence. And that is exactly what we plan to do.
Companies and contacts
Atlas CRM companies and contacts are similar to sales. We could've used issues to document companies and contacts. But this would have made it impossible for us to bring Atlas CRM to Confluence. Not with the same functionality, at least.
Building our own objects costs more time and effort, but we have decided to go down this path to offer you the best solution. If we look back at this part of our history, it only makes sense to make the same decision today for the sales feature. But we did have more reasons for our decision.
Another reason for us to choose not to rely on issues is that issues are somewhat limiting. Issues limit us in how much information we can store, how we store it and and how fast we can retrieve that information.
We have big plans for the sales functionality and Atlas CRM in general. If we would rely on issues, it would not be possible for us to make sales as powerful as we plan to do and provide you with best possible user experience.
I hope this gave you some insight in our vision and the choices we have made. Keep your feedback and questions coming, we love to read everything you have to say. Your question might end up in a blog-post like this one.