Electricity is wonderfully theatrical at the wall switch and stubbornly administrative everywhere else. Before a lamp answers a finger, an immense stack of maps, models, customer records, field decisions, phone calls, and software has already agreed to cooperate. Brian Carr has built his career in that stack. He is CEO of Marketing at Milsoft Utility Solutions, the Abilene, Texas company whose systems help electric utilities model distribution networks, manage outages, map assets, support field engineering, bill customers, and communicate when a quiet evening becomes a very busy one.
Carr did not arrive through electrical engineering. His route ran through management jobs in banking and electronic retail after attending the University of Texas at Arlington. That background placed him close to the small dramas of customer service: the account that must reconcile, the product that must be explained, the question that arrives with no patience for an organizational chart. He carried that practical education into Milsoft, where his responsibilities came to include sales, marketing, training, and business development.
It is an unusual apprenticeship for infrastructure technology, and a useful one. A utility buys software in a technical language, operates it in an institutional language, and is judged by customers in very plain language. Is the power on? When will it return? Why is the bill wrong? Carr's work lives in the translation among those questions.
From the counter to the control room
Public career records place Carr in a Bank of America banking-center management role in the middle of the 2000s. At roughly the same time, his Milsoft chapter began. He moved into sales and marketing leadership, served in a co-CEO role for those functions, and became CEO of Marketing in 2014. Milsoft's own account says he has led its sales and marketing team since 2011 and has been instrumental across four linked disciplines: sales, marketing, training, and business development.
The sequence matters more than the job-title arithmetic. Banking and retail train a manager to watch the moment where a system meets a person. Utility software enlarges that moment. The “customer” might be an engineer building a circuit model, a dispatcher assigning work, a crew checking an outage in the field, a billing specialist correcting an account, or a resident listening to an automated update. One platform can touch all of them without any one of them caring much about the platform itself. They care whether the answer is right.
The useful pitch is not “software.” It is a shared picture when the map, the phone, the crew, and the customer all need the same answer.The operating logic of integrated utility systems
A grid is also an information problem
Milsoft began in the 1980s with Wayne Carr writing distribution-analysis software at Milford Engineering. The company was formed in 1989, initially around the demanding mathematics of electric-distribution circuits. It later expanded into outage management, interactive voice response, geographic information systems, and field engineering. The 2019 acquisition of Daffron and Associates added customer information, work management, and financial management systems.
That history gave Brian Carr something more complicated than a catalog to take to market. The products describe a chain of work. A geographic model shows what is connected. Engineering analysis tests how the network behaves. An outage system turns calls and device information into a view of trouble. Field tools carry that view outside the office. Communications software answers customers. Billing and work-management systems keep the institutional memory. Each module has a name; the commercial argument lies in their ability to converse.
One outage, five views of the same event
model
picture
response
calls
data
billing
The executive task is to make the connections legible before a utility ever needs them under pressure.
This is where Carr's broad remit makes sense. Training is not a decorative cousin of sales in enterprise software. It is part of the promise. Business development is not merely finding a name and an email address. It means understanding how a utility's existing systems, vendors, workflows, and people might fit together. Marketing has to survive contact with a control room.
Trust has a longer sales cycle
Consumer software can acquire a user between breakfast and lunch. Utility software enters an organization with history, regulation, legacy data, and consequences. A new system may need to integrate with mapping, metering, telecommunications, financial records, and field practices that have accumulated over years. The sale is partly a product decision and partly a vote of confidence in the people who will answer after installation.
Carr's longevity is therefore part of the story. Milsoft's profile places him at the company for more than a decade; other public career records trace his tenure back to 2005. He is not only the marketing executive. He is treasurer of the board, a role that puts market-facing work beside the sober obligations of governance. The board itself divides leadership among business operations, product, marketing, and directors with deep company experience. Carr's title, “CEO of Marketing,” sounds idiosyncratic because it is. It also declares that reaching the market is treated as an executive domain rather than an afterthought.
Carr is listed as Milsoft's international sales contact, even as the company's center of gravity remains Abilene. That pairing tells its own story. Specialized software does not require a glamorous postal code. It requires enough domain knowledge to be useful across local conditions, and enough consistency to support customers far from headquarters. The office can stay in West Texas while the conversations cross borders.
In infrastructure, marketing earns its keep when the promise still makes sense at 2 a.m., in bad weather, with the call queue growing.A standard more useful than applause
Selling coherence, one conversation at a time
Carr's public biography is spare. It offers no grand manifesto, no shelf of personal anecdotes, and no theater of disruption. The absence suits the market. His documented ambition is practical: deliver software that meets the changing needs of utilities and municipalities seeking better operational efficiency and customer support. Those phrases can sound bloodless until a storm arrives. Then efficiency becomes the difference between a clear dispatch and a duplicate trip. Customer support becomes the difference between useful information and another unanswered call.
His career also complicates the familiar idea that technical industries must be explained by people who began as technologists. Carr came from the customer side. The useful skill was not pretending to be the engineer in the room. It was learning enough about the work to connect an engineer's requirements with an operator's constraints and a customer's expectation. Sales, training, and business development converge there: each asks a different version of “What has to be understood before this can work?”
Milsoft's own growth gives that question scale. What began with pencil, paper, a calculator, and distribution-analysis code expanded into a suite used by more than 1,000 utilities, municipalities, consulting firms, and universities worldwide. Carr did not found that first product, and the company's history rightly credits Wayne Carr, Leon Giesecke, Luis Malavé, and the teams that built it. Brian Carr's contribution sits in the next act: carrying an increasingly broad technical story into the market and keeping customers close enough to influence what comes next.
There is a decent lesson in that for anyone selling serious software. Complexity is not a license to be obscure. A product can contain circuit models, geospatial data, automated calls, field updates, and financial workflows; a buyer still needs a clear reason to trust it. The work of explanation is neither cosmetic nor separate from the product. Done honestly, it is a form of systems thinking.
And so Carr's path, from bank branch to utility platform, looks less like a detour than it first appears. Both worlds run on records, reliability, and human confidence. Both become visible when something is wrong. Both punish a gap between what a system knows and what a customer is told. He changed industries, then spent years working on the same durable problem: helping an organization make a complicated promise and keep it.
That work rarely produces a cinematic ending. A successful day may look like a training session that prevents a mistake, an integration question answered before a contract, or a utility team discovering that two departments can finally see the same information. These are modest victories with compound interest. Carr's record at Milsoft is built from their repetition. The point is not to make the electrical grid sound glamorous. The point is to make its software understandable to the people charged with choosing it, learning it, and depending on it when ordinary routines give way to urgent decisions.