- Customer Ticketing systems (Zendesk, helpscout, freshdesk)
- Bug/issue tracking systems (Pivotal, Jira, Github)
- Crms (Salesforce, Hubspot, Streak)
- And then theres even specialized customer facing and internal facing KnowledgeBase products (getguru, readme.io..)
Can you see the insanity? So many apps that are just different ways of abstracting and sorting knowledge, relationships, time and next steps.
A lot of progress has been made in enabling developers to integrate customer (event) data accross apps over the past 5 years (segment, mparticle with their data layers). But what about a standard data layer for the folder / project/tickets / tasks / notes hierarchies that exists in all these apps. So our information and knowledge isnt so siloed?
You can full-send into Notion (or any one of these systems) for a "jack of all trades, master of none." Obviously, not as good as a single-purpose system, but there really needs to be a space for unified data.
- Cloud document systems (Google docs, Dropbox paper, Notion)....
- Project management systems (Trello, Asana, Monday)
- Todo/task/notes management (Keep, Todoist, Evernote)
- Customer Ticketing systems (Zendesk, helpscout, freshdesk)
- Bug/issue tracking systems (Pivotal, Jira, Github)
- Crms (Salesforce, Hubspot, Streak)
- And then theres even specialized customer facing and internal facing KnowledgeBase products (getguru, readme.io..)
Can you see the insanity? So many apps that are just different ways of abstracting and sorting knowledge, relationships, time and next steps.
A lot of progress has been made in enabling developers to integrate customer (event) data accross apps over the past 5 years (segment, mparticle with their data layers). But what about a standard data layer for the folder / project/tickets / tasks / notes hierarchies that exists in all these apps. So our information and knowledge isnt so siloed?