The CRM Problem Isn't the CRM

I've used CRMs for most of my career. I've managed teams through them, built workflows around them, customized Salesforce, connected other systems into them and spent more hours staring at CRM dashboards than I'd care to calculate.

I still hate updating them.

Lately I've been thinking about why. I started building a fairly simple CRM for myself because I've been doing more networking, consulting and business development, and I reached the point where I couldn't reliably keep every conversation, introduction and follow-up in my head.

The irony wasn't lost on me. I hate documenting everything, so naturally I decided to build another place to document everything.

Once I started using it, though, I realized the CRM itself wasn't really the problem I was trying to solve.

Storing information is easy. Getting the information into the system consistently is where things start to fall apart.

The work usually happens before the CRM

Think about what happens after a normal business conversation. You finish the meeting, then you're supposed to open the CRM, add or update the contact, write some notes, change the opportunity status, create a follow-up and maybe update the company record.

None of those things are particularly difficult.

They're just one more thing to do.

Then someone calls. You walk into another meeting. You answer an email. You start working on the thing you were actually supposed to be working on. You tell yourself you'll update the CRM later.

Later has a pretty bad completion rate.

That matters because the quality of any CRM is eventually limited by the quality of the information inside it. A beautiful dashboard built on incomplete information still can't show you what's actually happening in the business.

This gets even more complicated when the work is relationship driven.

Not everyone you meet is a lead.

Someone might become a client. They could also become a referral source, collaborator, employee, advisor, connector or simply somebody you like and want to stay in touch with. Sometimes the most valuable relationships don't reveal what they are going to become for months or years.

Traditional CRM structures tend to want an answer sooner than that.

Lead. Qualified lead. Opportunity. Closed.

Real relationships don't always cooperate.

I don't need another place to enter information

That became one of the things I wanted my own system to handle differently. I wanted somewhere to keep people, companies, conversations, introductions, opportunities and follow-ups without pretending that every person I know belongs in a sales funnel.

But even after I built that structure, I still had the same basic issue.

It needed me to feed it.

That is the part I'm increasingly interested in solving.

After a meeting, I should be able to talk into my phone for thirty seconds and say something like:

"I met someone today through a mutual connection. They're involved with a healthcare company entering a new stage of growth. We talked about some commercial and operational issues they're working through, and there may be an opportunity for me to help. We're going to grab coffee next week."

That should be enough information for the system to do most of the administrative work.

It can identify the person. Connect the company. Save the context of the conversation. Recognize that there may be an opportunity. Add a follow-up for next week.

If I also say, "I met someone else who was great, but there's really nothing to follow up on right now," it should be able to remember that person without manufacturing a task just because the software needs something to do.

That distinction matters.

The goal isn't to create more CRM activity. The goal is to make sure the things that actually matter don't disappear.

The software should do more of the adapting

For a long time, we've asked people to adapt themselves to software.

Fill in the right fields. Pick the right status. Log the activity. Complete the task. Follow the process.

There are good reasons for structure. I've built plenty of it myself. Once a business has multiple people involved, you need reliable information. Otherwise you can't understand the pipeline, manage handoffs, forecast revenue or know when something important has been dropped.

I'm not arguing that structure should disappear.

I'm questioning who should have to create all of it.

Voice transcription, AI, email integration and automation are getting good enough that much more of the structure can be created from work that is already happening.

A conversation can become a note. A note can create a follow-up. An email can update the context around a relationship. A meeting can change the status of an opportunity without someone having to remember to change a dropdown afterward.

There should still be a human involved. I don't want a system deciding which of my relationships are valuable, and I definitely don't want every person I meet automatically dropped into some six-email nurture campaign.

Sometimes the right next action is to call someone.

Sometimes it's to send an email.

Sometimes it's to leave them alone.

The system should help me remember the difference.

That's where I think CRM automation and AI become genuinely useful. Not because we need an "AI CRM" stamped on another software product, but because the technology finally gives us a chance to remove some of the work that made people dislike CRMs in the first place.

Maybe the next meaningful improvement in customer relationship management isn't another feature.

Maybe it's requiring people to enter less information.

Let people talk to customers, meet people, send emails, make introductions and do their jobs.

Then let the technology do more of the remembering and organizing behind them.

The CRM isn't really the part I dislike.

Feeding it is.