First To Fly
Back to Blog
aivertical-saasopinion

The Problem with AI CRMs

Adding AI to a generic CRM doesn't make it understand your industry. It just makes it faster at doing the wrong things.

KCKelvin Chng|March 14, 2026|5 min read
The Problem with AI CRMs

When AI automates without understanding, it just makes a bigger mess faster.

TL;DR: Adding AI to a generic CRM just automates the wrong workflows faster. The problem was never speed - it's that the tool doesn't understand your industry. Real impact comes from AI that's native to your domain, not bolted onto a generic shell.

At Carro, we tried every CRM on the market. Salesforce, HubSpot, you name it. And every single one had the same problem - they all assumed a "lead" was straightforward. In used car sales, it's not. A lead for the same car can come in from the wife and the husband separately. That same vehicle can get sold and then show up again months later through a completely different channel. The pipeline isn't "prospect to close." It's inspection, pricing, listing, matching, negotiation, financing, delivery, post-sale warranty - and the CRM needs to understand all of that.

We spent months trying to make these tools work. Configuring custom fields, adding widgets, installing plugins, bending the workflow to fit. The CRM providers all wanted their platform to be the centre of action, but sometimes CRM is just one part of a much larger operational flow. We were constantly fighting the tool.

So we built our own. From the ground up. Omnichannel communication that combined calls, SMS, emails, WhatsApp, and Telegram - something that wasn't available in CRMs at that time. Number masking to prevent data leakage. A single customer view where every ticket and interaction across every channel was visible in one place, so you could understand the full lifecycle with that customer. Escalation workflows for ticket closing. AI-powered summaries and sentiment analysis. Reminders and iceboxing - where leads could be frozen and automatically thawed after a set period.

It worked. Not because our engineers were better than Salesforce's, but because it started from how the business actually operated.

I think about this every time I see a new "AI-powered CRM" launch. There's a whole wave of them right now - AI chatbots, AI lead scoring, AI-generated emails. And I've watched this movie before. It's the same pitch enterprise software made ten years ago, except the magic word is "AI" instead of "cloud."

CRM WORKFLOW COMPARISON
Generic CRM pipeline vs what automotive actually needs
Generic CRM
Salesforce, HubSpot, etc.
1Capture lead
2Qualify contact
3Move through pipeline
4Close deal
5Post-sale handoff
Result: months of bending
Widgets, plugins, custom fields - constantly fighting the tool to fit the workflow.
Automotive Reality
What Carro actually needed
1Inspection & grading
2AI pricing & listing
3Buyer-seller matching
4Negotiation & financing
5Delivery & logistics
6Warranty & post-sale
7Vehicle re-entry cycle
Result: built from reality
Omnichannel, number masking, single customer view, iceboxing - features that didn't exist yet.

Faster at the Wrong Things

Here's what actually happens when you add AI to a horizontal CRM. The AI chatbot can answer generic questions, but it doesn't know that in your industry a "lead" can be the same asset showing up through three different people. The lead scoring predicts based on email opens and page views, but misses the industry-specific signals that your operations team reads instinctively. The AI-generated emails sound professional but miss the nuance of how your specific customers expect to be communicated with.

You're automating the wrong workflow faster. And that's not progress - it's expensive noise.

The fundamental problem was never that your CRM was too slow. The problem is that your CRM doesn't understand your business. Adding AI doesn't fix that. It amplifies it.

What Actually Works

The software that transforms an industry doesn't start from a generic framework and bolt AI on top. It starts from industry reality and builds AI into the specific problems that matter.

At Carro, we built AI that was native to the automotive domain. Credit scoring models that understood local market spending patterns. Pricing prediction using regression and random forests trained on our actual transaction data. Computer vision that could identify scratches and dents on vehicles. Acoustic models that could diagnose engine problems from sound. NLP bots for customer service that actually understood automotive terminology.

None of that came from wrapping a generic AI around a contact database. It came from understanding the domain deeply and then applying AI to the specific problems where it genuinely changed outcomes.

The AI has to be native to the domain, not wrapped around a generic shell.

The Moat Isn't the AI

Here's what most AI CRM companies don't want you to think about: their product is a commodity. If all you're doing is wrapping GPT around a contact database, there's nothing defensible about that. The API costs are dropping every month. Anyone with a weekend and a credit card can build it.

The real moat in industry software isn't the AI. It's the understanding of how the industry works - the edge cases, the workflows, the unspoken rules, the things that only someone who's operated in that space for years would know to build. That's why vertical SaaS keeps winning. Not better technology. Deeper understanding.

Ask the Right Question

Next time someone pitches you an AI-powered CRM, ask this: does this tool understand my industry, or does it just understand contacts and pipelines?

If it's the latter, you're buying a faster version of the same problem you already have. The tool will be impressive in the demo. It'll generate beautiful reports. And six months later, your team will still be running the actual business on spreadsheets and WhatsApp - because the CRM doesn't match how they work.

The software your industry needs isn't a better CRM with AI features. It's software built from the ground up for how your business actually operates, with AI embedded in the places where it genuinely changes outcomes.

That's what we build at First To Fly. Not generic tools with AI on top. Industry-specific software where the AI is native to the domain, built alongside the people who understand the work.

Things to remember

  • Generic CRMs understand contacts and pipelines - not your industry's actual workflow
  • At Carro we tried Salesforce, HubSpot, and others - none could handle how automotive leads actually work
  • We built a custom CRM with features that didn't exist yet: omnichannel, number masking, single customer view, AI summaries
  • AI on a horizontal tool amplifies the mismatch, it doesn't fix it
  • The moat in industry software is understanding, not technology - anyone can wrap GPT around a database
  • Real AI impact comes from domain-native models (credit scoring, computer vision, pricing prediction) not generic chatbots

Tell us what your industry needs.

Share
KC

Kelvin Chng

Founder & CEO

Co-founded Carro, Singapore's first automotive unicorn, scaling to 4,000+ staff across 6 countries. 15+ years building software systems. Now building First To Fly to make enterprise-grade software accessible for every industry.

Get posts like this in your inbox

Operator insights on AI, vertical SaaS, and building software for real industries. No spam, unsubscribe anytime.