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.