Reminds of one more thing:
Integrations when scripting. I think this has to do with packages in scripts, but Iâm not sure. For example: the ability press a button: âCallâ and it integrates with a calling service and opens in new tab (or within the fibery extention). Same thing for sending WhatsApp messages using WhatsApp api. I tried to set this up and wasnât able to. (Without their sdk is much harder). Not sure if it was a skill issue or a feature issue, but I would say thatâs a roadblock for what pdudin was saying (if I understood correctly)
From memory, sending emails would need to be signed by the domain - postmark integration might be handy.
Agree with this 100%. Need to support more records, not just for CRM use cases either.
Other concerns (off the top of my head):
Notifications. Lack of âeasy-to-useâ notification features make it tricker for average users to implement Fibery since the need for reminders (e.g. call, email, contact ending) are crucial. We can build this but new users looking to replace current CRMs will likely find it more cumbersome. Maybe it would be helpful if Fibery implemented a shortcut to create rules from date field at entity level (e.g toggle that says âEnable reminderâ). Then you can see all rules that the date field triggers from the entity view.
User analytics. Many platforms (e.g. Attio, Hubspot, Salesforce) allow you to track user metrics (visited site page, signed up, made payment, etc) and integrate with your site through native SDK or something like Segment. This can help with updating contract or lifetime value as well vs manual input.
Emailing. Lack of âtightly-integratedâ emailing processes (you must build out via rules, subject formulas and buttons vs having dedicated emailing components. Messages come in rich text fields and is slightly messy when it comes to responding to recipients) and other points @pdudin expressed.
Integrations. Zoom integration or similar (create zoom link from Fibery). Hightouch or Census for database syncing (syncing customers from your platform and building deals or other processes around them), though this area has not been a priority for Fibery and led us to build our own integration with Postgres.
1 Like
I have been using Planfix for 10 years and they had the email integration right from the start.
I do not use Gmail interface at all these days. All funneled to the CRM/task mgmt system.
Yes, you have to authenticate via your gmail/outlook account.
I have been calling @mdubakov and @Chr1sG to go look at how Planfix does it. Just copy that into the Fibery and grow grow grow.
Product priorities and trick you into doing something for your current customer base. Growth, though, comes from completely different niches and types of clients. Hard to quantify, as SW-engineers tend to trust the numbers. So they sit in the âAtlassian alternative bubbleâ, which turned out to be a great product⌠just to replace Jira and Confluence. How do I get to use it on a company level (not the R&D dept)? Answer: I donât use it, because it has no justified use cases outside of ideation and documentationâŚ
So we keed discussing blows and whistles here (color palettes, buttons, layouts), while a leap is required for Fibery to become a usable CRM.
I know this is a thread for ideation and expressing specific needs for CRM, so I apologize for being negative but⌠frankly Iâm pretty skeptical of Fiberyâs ability to significantly appeal to serious CRM users, or to earn many additional customers via this route. Existing, entrenched solutions are numerous, and many of them are actually good and well-liked. The main advantage Fibery provides is integration with other data but A: Fiberyâs integrations with other CRMs (like Hubspot) give arguably enough such connective functionality (not to say itâs perfect, but itâs like an 80% solution), B: the number and scale of features people want here seems significant and C: most of what I think is being discussed here are things that would merely strengthen/increase use by existing customers, rather than attract new ones.
So much of what CRMs do in serious use is antithetical to Fiberyâs lego-like approach, itâd be bolting on a lot of custom stuff, or doing things in a clunkier way than a more focused tool like Planfix, etc. And even if such things were implemented it takes a lot of benefit to convince someone to switch from an existing âworks well enoughâ tool.
Aiming for low-hanging CRM fruit, so to speak, i.e. quick/easy wins that make the CRM case more appealing for existing and new users, that sounds great. But a lot of the above sounds much bigger and more time-consuming. Not that it should not have been suggested, that is after all what this thread is about, but as far as the value of such features to Fiberyâs success I am skeptical.
5 Likes
Sadly, even my CRM has all these features and Fibery still does not.
Dates and notifications would be necessary for sure. Deals have timelines, dependencies, reminders, etc etc
2 Likes
Thank you for all the feedback, so many things to think about!
It is interesting that Notion and Monday are relatively popular CRMs (source).
CRM use cases are so different. For example, Attio lacks many things mentioned above, but they still growing fast (the do have great enrichment and OK email integration, but you canât ditch your email client in Attio still).
2 Likes
My experience from customers related to available CRM options are that customers think they provide too many features that are not required and will not be used. The general feedback is that the CRM needs to be simple to use. This is always where it starts, but we know, it always lies in the detail. So, it starts simple and grows into the detail and always ends up more involved than what the customer envisaged.
The strength of Fibery for me has always been the lack of barriers that result in product or application silos. For me a CRM is just one piece of the puzzle of a Company Operational Management System.
A useful CRM system will grow over time to eventually end up addressing the following :
The natural evolution will then be the integration of the CRM workspace with the other company functional workspaces that will grow according to the requirements.
In the past this was only possible using many software developers, time and money. With Fibery it is now possible for small and medium sized company to afford a âbespokeâ expert system that previously was only available to larger corporations.
I assume all the massive CRM systems out there started small at some stage and grew to what it is today.
TargetProcess was unique and perfect for our software development, but it was closed and confined to software development. Its full potential was/is Fibery. However, the world is different now with an overload of options to choose from often resulting that the perceived safe option of the known is chosen.
For me the Fibery paradox is what is it aspiring to become? Trying to be all things which it definitely could become over time, competing with everybody out there? I do not know.
My two cents worth of philosophical rambling.
3 Likes
Closest things to Fibery now are ClickUp and Monday. Notion and Airtable are also quite close, but Notion is still more wiki+PKM and Airtable is moved to more no-codish solution with UI Builder.
1 Like
Iâm not sure this is true. With Notions event in October and their calendar acquisition and release in 2024, things are changing.
- Notion announced Notion Mail in October
- Notion AI works with external services (Slack, Google Drive, etc)
It feels like Notion wants to be the company OS, and even ClickUp is moving there too:
- They bought Hypercal and now have a Meeting Agent (which is really cool)
- They have connected search
Everyone wants to be âthe one appâ
3 Likes
ClickUp always positioned itself as one-app for all. Notion competes with Microsoft and google more, it is like Docs + Email + Calendar + Tasks, but more complex processes are hard to support in Notion. I bet someday they will move to more complex processes as well, but not right now
This might be a bit random - going for it anyway. Looking at the CRM chart, you have to think that in the next two years, 90% of those seat licences are going to come under threat from AI. I heard a voice demo of an AI Call Centre agent on Friday and it was already better than 80% of calls I heard in many centres.
Training AI on voice calls is already in progress. CRM is going to morph into something else, a service to agents. Auto capture of email and voice data is not an option, itâs the whole point.
It reminded me of the post - reproducing below. AI Agents have no memory to speak of, they need to be highly focused on one thing, so they will need to work together to achieve the digitisation of sales and marketing into operations - onboarding and service delivery.
I heard of Orchestration in this post below by the Crew AI guy, Iâm not exactly sure why it feels so relevant to this conversation, but reproducing it here.
JoĂŁo (Joe) Moura
CEO at crewAI - Product Strategy | Leadership | Builder and Engineer
I bet my entire career on one crazy prediction:
AI Agents will transform enterprise operations more than cloud computing did.
Today, IBM, NVIDIA, and PwC are our partners. Hereâs how I spotted what others missed:
I was Director of AI Engineering at Clearbit, leading their enterprise AI products through acquisition. But I walked away from it all - including a massive retention bonus.
Why? The signs were impossible to ignore.
Large language models were reaching unprecedented capabilities, while computing costs plummeted.
Traditional automation was failing enterprises spectacularly.
Their systems were rigid, brittle, and couldnât adapt to change. (Does he mean Salesforce and Hubspot?)
Thatâs when it hit me: AI Agents could bridge the gap between basic automation and true intelligence. They understand context, make decisions, and adapt on the fly.
But the real opportunity? Enterprises would soon need thousands of these AI Agents.
And theyâd need a way to orchestrate them all.
Thatâs why we built CrewAI - to help companies deploy and manage AI Agents at scale.
The response has been mind-blowing:
⢠50M+ agents executed in January alone
⢠90,000+ waitlist signups
⢠Major partnerships with tech giants
Hereâs what I learned about spotting massive opportunities:
-
Look for multiple trends converging
⢠Advanced AI capabilities
⢠Falling computing costs
⢠Enterprise automation needs
⢠API accessibility -
Find markets desperate for transformation
⢠Current solutions failing
⢠Clear pain points
⢠Massive potential impact -
Timing is everything
⢠Too early = market not ready
⢠Too late = missed opportunity
⢠Perfect timing = exponential growth
The next wave of billion-dollar enterprises wonât just use AI.
Theyâll be built on autonomous AI Agents that think, decide, and act.
If youâre a decision-maker, you have two choices:
- Watch others pioneer AI Agent adoption
- Lead the charge and gain massive competitive advantage
The cost of waiting? Potentially billions.
Follow me for insights on:
⢠AI Agent implementation
⢠Enterprise automation
⢠Future of work
⢠Real-world case studies
The future belongs to those who see it coming. And something massive is happening right now.
Want to stay ahead? Follow me more on AI agents and enterprise tech.
==
Great pitch I thought.
The API thing struck a chord - multiple connections between individual systems - or a centralised data exchange with a great UI.
3 Likes
What about Coda? 
I would encourage you to think very in-depth about why this might be the case in this particular survey, and who might be using it for this. This quote for example might be illuminating:
We hypothesize that participants in this survey skew toward earlier-stage companies. Slack is a must, and Zendesk or Intercom are expensive and complicated, especially if you donât have a customer support (or success) team.
And
- ~45% work in 1-to-100-employee companies
I would really have liked to see that lower range be subdivided, something like 1-10 and 11-100, at least. Because this leaves a vast range of very different kind and scale of companies. In other words I have concerns about bias in the sample here and thus about what exactly the data is telling us about âCRMâ usage patterns.
2 Likes
A CRM in Fibery is most likely to directly compete with Coda. But Coda is an integration-first platform, theyâre not actually trying to replace dedicated tools for their target (enterprise) customers. Just make it easier to bring data together across the portfolio of apps.
Codaâs packs and automations builders make the time to deploy much shorter. Buttons and formulas in Coda are also more powerful and email integration is different - better in some ways, worse in others.
Fibery has much better reports and a more polished user interface. Itâs not as flexible as Coda out of the box, but scripting actions and a stable API make it a better platform for developing company-specific integrations. Iâd say Fibery requires an in-house dev or support company to maintain.
1 Like
I afraid Coda is dead
Wow that is interesting. When I was looking around for a tool with better tables than Notion I considered Coda. Looking promising. Big funding, interesting features. Chose to go with Fibery for various reasons. Apparently a good choice to not go with the big and mighty one, but the smaller one - the one with a better soul and visionl.
Theyâve stated the acquisition doesnât kill Coda and that Coda will be getting integrated with Grammarly âŚ
Iâm planning to share more detailed thoughts in the future, but I wanted to provide some initial feedback on our experience.
Fibery has been working exceptionally well as a CRM solution for my small team. The most significant benefit has been finally achieving a single source of truth for all our business information: leads, clients, companies, deals, customer support inquiries, product feedback, contracts, and legal processes.
This unified approach has eliminated the information silos we previously struggled with and has streamlined our workflow considerably. The flexibility to customize Fibery to our specific needs has been invaluable.
If Fibery evolve with more Process Driven features like Pipefy, it will probably be even more useful as CRM and to run other processes â Related: Invitation to users wanting improved workflows - #10 by Renato_Carvalho
2 more things that would help create more controlled workflows:
- Conditionally Visible Buttons
- Required Fields by State
Conditionally visible buttons:
Buttons should only appear under certain conditions. When pushed a button might disappear and be replaced by another button (thatâs condition is now true). This will make it so that only the actions that are relevant to a user can be taken
Required Fields By State
When creating an entity or moving it from one state to the next it is sometimes important to have certain information to advance. i.e. I canât email a contract to be signed without the email address.
Adding these required conditions will help ensure workflows and automations do not break and that employees arenât able to make mistakes as easily. Any place where the user could create a new entity that has required fields can pull up the same UI that is used when automations ask the user for field inputs. If the user fails to answer the required fields then the workflow should prevent the update to the next state.
5 Likes
I read the community posts, checked latest releases, etc. Vibes are not good to me. Maybe it will survive, but my extremely biased gut feelings are telling me that it will be in turbulent mode and outcome is totally unclear. I have little faith in such weird merges.
2 Likes