# Sales-driving features, low-hanging fruit **URL:** \ **Category:** Ideas & Features\ **Created:** [September 27, 2022, 10:51pm UTC](https://community.fibery.io/t/sales-driving-features-low-hanging-fruit/3341 "2022-09-27T22:51:03Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [September 27, 2022, 10:51pm UTC](https://community.fibery.io/t/sales-driving-features-low-hanging-fruit/3341/1 "2022-09-27T22:51:03Z")
This topic may not be appropriate here, but I wanted to try to curate a list of what I think are some important missing features that might be _relatively_ easy to implement and would, in my view, have a disproportionately high positive impact on sales and retention. I’ll mostly be linking to existing feature requests here, and will try to categorize it. I’m also making this a wiki so others can add to it. Just be aware I may remove or annotate your changes if I disagree, as I think it’s important that this be a really focused list that ideally would be reasonably actionable for the team. # Import and Migration Almost everyone coming to Fibery will have existing data. Getting them into the tool with their data reasonably intact is key to giving them a good experience, especially if you can “enrich” their data with Fibery-specific benefits (e.g. Fields, References, etc.). Fibery already has good sync with a number of tools, but could use a couple key improvements that may have higher impact. - [Easy import of markdown docs to wiki](https://community.fibery.io/t/easy-import-of-markdown-docs-to-wiki/307), i.e. _bulk_ import of markdown, which is broadly supported for export from a variety of tools - [📅 VOTE here for _Calendar_ Integration Prioritization](https://community.fibery.io/t/vote-here-for-calendar-integration-prioritization/958), i.e. Google Calendar sync - [Add “Page”/Document sync to Notion Integration](https://community.fibery.io/t/add-page-document-sync-to-notion-integration/3216) - Deduplication as a core feature - Make import an optional part of workspace creation (i.e. make it more discoverable) # Work Management and Notifications Although Fibery is extremely powerful and can manage a wide variety of processes, those are almost inevitably more complicated to implement and get used to in Fibery vs. e.g. simple work management. And the largest common denominator for most Fibery users will probably be projects + tasks or some variation of. Thus it makes sense to really prioritize the user experience here as it’s the first thing many users will encounter, and rough edges in this area will likely turn people off quickly, especially vs. other, more purpose-built tools they may be coming from. - [Simpler reminder functionality in addition to automation-based approach](https://community.fibery.io/t/simpler-reminder-functionality-in-addition-to-automation-based-approach/2378) and I will be posting a more specific proposal around this soon - [Lack of Work Management features in Fibery (Reminders, Dependencies, Notifications, My Work, etc.) - #12 by Oshyan](https://community.fibery.io/t/lack-of-work-management-features-in-fibery-reminders-dependencies-notifications-my-work-etc/3319/12) here I outline what I think is a fairly low-effort, high impact short-list of potential changes to Notifications to make them far more usable - [[APPROVED] Mention notification UI improvement](https://community.fibery.io/t/approved-mention-notification-ui-improvement/796) - [[PLANNED] “Watcher” of an Entity - use the Assignment Extension?](https://community.fibery.io/t/planned-watcher-of-an-entity-use-the-assignment-extension/563) - [Turn “Notifications” into “Inbox”](https://community.fibery.io/t/turn-notifications-into-inbox/2251) or [Viewing sent Notifications and responses](https://community.fibery.io/t/viewing-sent-notifications-and-responses/2014) - [Small element of Notifications - “I’ve read it” functionality](https://community.fibery.io/t/small-element-of-notifications-i-ve-read-it-functionality/1179) and/or comment reactions # Comments, etc. - [In-line comments should open in “gutter” (like Google Docs)](https://community.fibery.io/t/in-line-comments-should-open-in-gutter-like-google-docs/1289) - [Unread indicator on in-line comment threads](https://community.fibery.io/t/unread-indicator-on-in-line-comment-threads/1288) # Polish and User Experience - [Opportunities for “polish”](https://community.fibery.io/t/opportunities-for-polish/3338) # Other Perspectives on the Same Topic This is essentially another user’s suggestions for similar goal: > [@Features to ease the Fibery learning curve – MRR opportunity smiley](https://community.fibery.io/t/features-to-ease-the-fibery-learning-curve-mrr-opportunity/2910): > > I’ve started introducing Fibery to some of my key teammates, preparing to pitch it as a replacement for our current Asana-and-Google-Workspace based system that we use to coordinate and manage all of our our department activities (designing, building and updating websites and brochures, SEO work, and running weekly client meetings). We have about 20 people in our department, and successful adoption of Fibery here would mean the possibility of extending it to the rest of the company (~200 people … --- _[View the full topic](https://community.fibery.io/t/sales-driving-features-low-hanging-fruit/3341)._