Si tuvieras que hacer un crm que tenga la captura de leads, kanban de seguimiento por contacto/conversación IA para atender rápido a tus clientes que funcionalidad sería de mucho valor que debería tener.
Estoy construyendo un crm conversacional, me gustaría leer opiniones y funciones que consideran importantes tener dentro del crm.
Sales and customer teams spend their day on slack or teams....but the CRM is where they are expected to record everything that happened. As a result, updates get pushed to the end of the day...some never get entered at all and managers end up chasing people for pipeline updates. This gap is where a lot of CRM data starts losing context and eventually, accuracy. Do you think CRM should work more closely with the tools these teams already use every day instead of making them switch between systems? Where do you see the biggest gap between customer conversations and what actually gets recorded in the CRM?
I keep seeing the same pattern with growing businesses.
They buy a CRM to organize sales.
Then they add:
Six months later, they have more software than ever, but people are still asking:
“Did anyone follow up with this lead?”
“Did we send the quote?”
“Who owns this customer?”
“Is this order already in the ERP?”
The issue isn't necessarily that any individual system is bad.
The issue is the gaps between them.
A good business workflow should look something like:
Enquiry → Qualification → Next action → Quote → Follow-up → Order → Delivery → Customer history
At every step, the system should know:
What happened?
Who owns it?
What happens next?
When should it happen?
If your team has to remember the answer, copy information between systems, or check three different places to find it, you've created a workflow that depends on people instead of the system.
And this is where I think companies need to rethink how they buy software.
Don't start with:
“Which CRM has the most features?”
Start with:
“Which parts of our operation should require the least human effort?”
Then design the software around those workflows.
Sometimes an existing CRM is absolutely the right answer.
Sometimes integration is enough.
And sometimes the business has become different enough from the standard workflow that a custom system makes more sense.
The goal isn't to have more software.
The goal is to make the business easier to operate.
What is one workflow in your business that still depends heavily on spreadsheets, email, WhatsApp, or someone's memory?
I've been researching how RevOps/DataOps handle this.
In my experience and talking to people in similar roles like those, they are not even aware that revenue is leaking only if they see a dashboard once in a while and wonder, why, but still it's difficult to find out where and have to manually scrape the entire CRM, data warehouse or whatever, but by the time it's resolved, revenue has been lost.
- How do you even deal with this?
- Are you using a software that detects those issues or you just let revenue leak?
It would be more than lovely to reply if you have a same problem I just described or just discovered it.
I'm building Amfion for agencies and operators that want to offer an AI front desk under their own brand.
Each client gets an isolated workspace with their business knowledge, calendar, phone number, inbox and branding. The partner API provisions tenants, catalogs and usage, while per-tenant webhooks send bookings and leads back into the rest of the stack.
The part I'm working through is how much control partners need without turning onboarding into a configuration project. If you've built a multi-tenant or white-label product, which controls did customers actually care about?
Login