What Does It Feel Like to Be Customer 1468A?

A few weeks ago, we were discussing customer support, software vendors, and implementation experiences when CPS Partner Claude Schott made a comment that immediately changed the direction of the conversation.

"Sometimes you're customer 1468A."

Everyone laughed because they instantly knew what he meant.

It wasn't a criticism of any particular software company. In fact, most successful software companies eventually face the same challenge. As they grow, they add customers, employees, products, and processes. Growth is the goal.

But growth changes relationships.

When a software company has hundreds or thousands of customers, individual organizations inevitably become part of a larger system. Support requests are routed. Escalations follow defined paths. Customer success becomes structured and standardized.

Again, none of that is inherently bad.

The question is what happens to the customer experience along the way.

As systems integrators, we often see a different side of the relationship. While software vendors focus on building and improving the platform, agencies still need someone who understands how that platform fits into their specific environment.

They need someone who remembers why Records chose one retention approach over another.

They need someone who understands why Public Works structured a workflow differently than Human Resources.

They need someone who knows which department championed the original project and which retired employee built half the repository fifteen years ago.

Those details rarely exist inside a ticketing system.

They exist inside relationships.

Claude put it this way:

"The software company has to think about thousands of customers. We get to think about ours one at a time."

That distinction is one of the reasons systems integrators exist in the first place.

Software vendors are responsible for developing products, maintaining security, delivering innovation, and supporting a broad customer base. They have to think strategically across an entire market.

Systems integrators are responsible for helping individual organizations succeed with those products.

Those are very different jobs.

An agency may be one of thousands of customers to a software vendor.

To their implementation partner, they are often one of a few hundred relationships built over decades.

That changes the conversation.

When a customer calls CPS, they are not starting from the beginning. In many cases, we know the repository. We know the departments involved. We know the project's history. We know the people.

We are not trying to figure out who customer 1468A is.

We already know.

Claude often reminds our team that growth creates a responsibility. Every new customer makes it slightly easier for someone to become customer 1468A.

That reality has shaped many of the decisions we've made over the years.

Programs like VIP Support were not created to provide special treatment.

They were created because agencies told us they valued continuity, familiarity, and direct access to people who already understood their environment.

The challenge isn't avoiding growth.

The challenge is growing without making customers feel anonymous.

One of the hidden realities of technology projects is that software is only part of the equation. Long-term success depends on governance, process design, training, adoption, change management, and institutional knowledge.

The software vendor provides the platform.

T

The systems integrator helps the organization turn that platform into a solution.

Over time, that relationship becomes valuable in ways that are difficult to measure.

When a department reorganizes.

When regulations change.

When leadership turns over.

When a major migration begins.

When the person who built everything retires.

Those moments are when organizations discover whether they are a number of customers or a relationship with customers.

As Claude observed later in the discussion:

"The software company has to scale. That's their job. Our job is making sure our customers don't feel like they're being scaled."

Perhaps that's the real value of a strong implementation partner.

No matter how large the software company becomes, someone still knows your name.

The irony is that customer 1468A usually isn't looking for special treatment.

They simply want to avoid feeling like customer 1468A.