Mark Stephen McCollum

Can you introduce your company, Automotive IntelliQence, and describe your role as founder and CEO?

I founded Automotive IntelliQence to solve operational problems inside dealership groups. After more than 35 years in auto retail, I saw the same inefficiencies repeat across stores, regardless of size. My role as CEO is focused on product direction, client alignment, and ensuring the software reflects how dealerships actually operate. I spend most of my time working with dealer principals, GMs, and operator teams to understand where margin is lost and where processes break down. Then we translate that into systems that are usable at the store level.

What is your core business model, and how do you structure your team and delivery?

We operate with a focused internal team supported by selective external development resources. The core product, data models, and client relationships stay in-house. That keeps accountability tight. We bring in outside specialists when needed for scale or speed, but we don’t outsource product ownership. The model is subscription-based software with implementation support. We stay close to the operator, not just the executive layer.

How do you differentiate Automotive IntelliQence in a crowded automotive software market?

Most software in this space is built by technologists. Ours is built by operators. I’ve run stores, managed multi-rooftop operations, and overseen more than $1.5 billion in revenue at AutoNation. The difference shows up in the details. We focus on workflow, not just reporting. We build tools that match how deals move, how inventory turns, and how managers actually make decisions day to day. If it doesn’t get used at the desk level, it doesn’t matter.

Who do you primarily serve, and how has that focus evolved over time?

We serve automotive dealers and dealer groups. That includes single-point operators and larger multi-rooftop organizations. Earlier in my career, my focus was strictly on store-level operations. Over time, that expanded into market-level and group-level performance. The software reflects that evolution. It connects store execution with broader operational oversight.

What are the most common problems clients come to you to solve?

Most clients come to us for visibility and control. They want to understand where they are losing gross, where processes are inconsistent, and where accountability breaks down. Common areas include inventory management, deal structure, and performance tracking across departments. They don’t need more data. They need usable information tied to action.

How do you stay ahead of industry shifts when the data is often delayed?

I rely more on direct operator feedback than delayed reports. I stay in regular contact with dealer principals and general managers. That gives me real-time insight into what is changing on the ground. The industry moves fast, but the core challenges stay consistent. Execution, discipline, and process still drive results.

Do you see a high percentage of repeat clients, and what drives that?

Yes. Retention is driven by relevance. If the system is part of daily operations, clients stay. We focus on adoption at the manager level. If a desk manager uses it every day, the store keeps it. We also maintain direct communication with clients, not just through support channels but through ongoing operational discussions.

How do you measure and ensure customer satisfaction?

We measure usage first. If the system is being used consistently, that’s a leading indicator. We also track client feedback in structured intervals and through direct conversations. Satisfaction comes from whether the tool improves performance, not just whether it runs without issues.

What kind of post-implementation support do you provide?

We stay engaged after implementation. That includes onboarding, training, and ongoing support. More importantly, we continue to refine how the system is used. Dealerships change. Processes evolve. The support model reflects that. It’s not a one-time setup.

How do you structure pricing and billing?

Our primary model is subscription-based. Pricing aligns with the size and complexity of the operation. Implementation may include an upfront component depending on scope. We avoid overly complex billing structures. The goal is alignment with long-term use.

What is the typical investment range for your clients, and how do you balance value?

Specific ranges vary based on group size and deployment scope, and I don’t generalize that publicly. What matters is the return. If the system helps improve gross, tighten processes, or increase accountability, the value is clear. We focus on measurable impact.

Have you turned down projects based on fit, budget, or scope?

Yes. If a client is not willing to commit to process change or adoption, it’s not a fit. The system requires engagement. We also look at operational readiness. If the basics are not in place, software alone won’t fix the problem.

What key challenges have you faced building this company?

One of the biggest challenges is bridging the gap between technology and real-world operations. Many tools look good in theory but fail in execution. We address that by staying close to operators and continuously refining the product. Another challenge is change management within dealerships. That requires discipline and leadership at the store level.

How do you foster innovation while staying practical?

Innovation has to be grounded in use. We don’t build features for the sake of it. We build based on observed problems. The process is iterative. We test, refine, and adjust. The goal is improvement, not novelty.

What role does culture play in your company?

Culture is built around accountability and clarity. Everyone on the team understands the end user. That keeps decisions focused. We avoid unnecessary complexity and stay aligned with the operator mindset.

Where do you see Automotive IntelliQence in the next 5 to 10 years?

The goal is to deepen integration into dealership operations. Not just as a reporting tool, but as a core system that supports decision-making across departments. Growth will come from expanding capabilities while maintaining operational focus.

How has your leadership style evolved over your career?

Early on, I was more focused on direct control. Over time, I’ve shifted toward clarity and alignment. You can’t scale by managing everything yourself. You need systems and people that can execute consistently.

What emerging technologies or trends are you watching closely?

Data integration and real-time visibility are key areas. There is also movement toward more predictive tools. The challenge is making those tools usable. Technology has to support decisions, not complicate them.

What advice would you give to other operators or founders building in this space?

Stay close to the problem. Don’t build in isolation. If you’re not talking to your end user regularly, you’re guessing. One lesson that stands out from my career is that execution always outweighs theory. The best plan doesn’t matter if it doesn’t work on the ground.