Nothing going wrong is a difficult thing to sell. There is no dramatic photograph of the breakdown that never happened. A building remains comfortable, the equipment carries on, and the customer has the luxury of thinking about something else. Billy Marshall has spent a substantial part of his working life explaining why that uneventful day deserves a price.
His route to the argument ran through enterprise software. It eventually brought him to commercial contractors: the people responsible for sprinkler systems, mechanical equipment, and the work that makes a building usable long after the ribbon has been cut. An invoice can record their hours. It is a rather poor narrator of everything those hours prevented.
Marshall’s company, ServiceTrade, gives that work a digital record and a route back to the customer. His books give the idea a vocabulary. His career gives it some friction: an early place at Red Hat, an unsuccessful turn at another startup, and years spent building a business in a market that did not initially attract much investor attention.
Free software, expensive lessons
Marshall joined Red Hat in November 1998, after IBM. Software that customers could obtain free online presented a pleasingly awkward commercial puzzle. What, precisely, should the company charge for? The answer he describes in his account of that period emerged from listening to users who cared deeply about keeping systems working.
The value lay in dependable maintenance and access to updates. In Marshall’s telling, he helped shape the subscription offering, negotiated a seven-figure Cisco agreement, and went on to lead sales. He recalls resisting customers who wanted to buy only help after something broke. That arrangement rewarded the wrong event. His preferred promise was reliability over time.
“a predictable outcome for a predictable price”
Billy Marshall, describing the Red Hat proposition
It is an idea with a useful life outside computing. A contractor who helps equipment keep working has something to sell between emergencies. The difficulty is persuading a buyer to recognise that value while enjoying the very absence of trouble that makes it easy to overlook. A well-maintained system rarely sends a thank-you note.
Marshall’s next company supplied a less comfortable education. He founded rPath with Red Hat veterans, pursuing software delivery in the emerging world of virtualization and cloud computing. At a 2022 entrepreneurship event, he recalled being asked to leave despite the company still having money in the bank. He spoke about crying when he understood what was happening.
That detail matters because it puts some weight behind the advice he later offered other founders. He described two failures before ServiceTrade and cautioned against treating success as an orderly progression. The practical measures he recommended were modest and recurring: look at the direction of deal sizes and the number of customers signing up.
“Don’t believe that every success is a straight line.”
Billy Marshall, 2022
The contractor was already in the room
ServiceTrade began with a working problem inside DunnWell, a national service business. Technology developed there appeared useful beyond its original home. On September 26, 2012, Marshall and Brian Smithwick founded a company around it. The product had roots in the work it was meant to organise, with Smithwick bringing the experience of building software for contracting operations.
That origin gave the venture a specific audience. These were businesses managing service relationships, equipment histories, repeat visits, field teams, and the uncertain business of repairs. The customer was not simply shopping for another piece of office software. The application had to fit a company whose most important work happened somewhere other than the office.
The early social calendar was appropriately small. ServiceTrade’s first customer appreciation event and fishing tournament, held at the Outer Banks in 2014, drew eleven people. By the fifth anniversary, the business had more than 300 customers spread across 45 states and four Canadian provinces. It had 21 full-time employees.
A photograph from that anniversary retrospective showed colleagues at one of Marshall’s Low Country boils. The scene fits the interests described in his professional biographies: offshore fishing, outdoor activities, and time at the smoker. There is room in this particular software story for a pot large enough to feed the team.
By December 2021, when ServiceTrade announced an $85 million growth investment led by JMI Equity, it reported more than 800 customers. Frontier Growth and Bull City Venture Partners also participated. Nine years separated the founding from that announcement. Capital arrived behind a business that had already spent considerable time learning its customers’ habits.
At a January 2022 interview, Marshall discussed the discipline of keeping a startup focused rather than trying to serve everybody. He also reunited with Joe Colopy, whose time at Red Hat had overlapped with his own. The conversation placed ServiceTrade inside a longer local network of people who had been building software businesses for years.
A truck wrap for the work you cannot see
Marshall’s phrase “digital wrap” begins with a familiar sight: the contractor’s branded van. Its lettering advertises the company while a technician goes about the job. The online equivalent extends the service experience through useful information. A customer can see what happened, understand the equipment’s history, and return to the record after the vehicle has disappeared.
He developed the argument in The Digital Wrap, published in 2016. Money for Nothing, co-authored with Shawn Mims, followed in 2018. The titles have a salesman’s appetite for attention, but the underlying subject is patient relationship building: help customers understand why an apparently uneventful service relationship has value.
His writing borrows examples from familiar digital services, including Amazon’s customer communication. Buyers become accustomed to information being available when they need it. A service business that leaves them guessing makes the purchase harder to appreciate. The technician’s work may be accomplished; the customer’s experience of it still needs attention.
In a 2019 essay, he challenged contractors who directed their management energy toward making the back office more efficient while giving less attention to customer experience. It is a telling emphasis for someone selling operational software. The paperwork matters because of the relationship it supports. A neater internal process has limited persuasive power if the customer remains puzzled.
There is also a sharp sense of audience in his practical guide to buying software. Earlier in his career, he observed, the people buying from him often bought software professionally. Contractors generally had other jobs to do. Explaining a product clearly, and helping a buyer judge whether it would work over time, became part of the responsibility.
Give the calendar some manners
Marshall’s operating advice gets down to the working month. In his “anchor jobs” approach, substantial recurring assignments go into the first two weeks. Smaller nearby jobs fill the gaps. Less predictable repairs occupy the later part of the month. The design gives known work a place before uncertainty takes its usual liberties.
He also urges contractors to protect skilled technicians from tasks that other people can handle. Truck preparation, administrative work, and repair quoting can consume time that is expensive to replace. His wider point is that a shortage makes the quality of the work accepted, and the way it is organised, especially consequential.
The same customer-facing argument appears in his 2025 writing: can buyers see service summaries, quotations, invoices, and history online? Can the record help them understand future equipment needs? Those are ordinary questions. They expose how much of a service relationship can be made easier through clear information rather than another telephone call.
For Marshall, technology has to earn its place in that routine. A technician needs useful context. An office needs information it can act on. A customer needs an explanation. The elegance of the software is only part of the transaction; the rest takes place in the working habits of people who have a full day already.
Back to the unfinished work
His interest in the trades extends beyond the current workforce. In 2025, ServiceTrade sponsored the Heavy Metal Summer Experience, which introduces students to hands-on careers. Marshall endorsed the opportunity those careers offer. He later joined students for meals and conversations about the value of maintenance and the importance of showing customers what service accomplishes.
His own education was technical: aerospace engineering at Georgia Tech, followed by graduate degrees in engineering and management at MIT. His public argument leaves room for other routes into useful, well-paid work. The connection is concrete. Better tools can help today’s technicians, while exposure to the work can help someone decide to become one.
In July 2024, Marshall moved from CEO to strategic advisor as William Chaney took the helm. On October 12, 2026, ServiceTrade announced his return. The company said it served more than 1,300 contractors. The founder was coming back to lead a business considerably larger than the one that had taken eleven people fishing.
His return message committed to more investment in AI and a flatter organisation with customer support teams reporting directly to him. He named billing, sales, and customer service among the work where the technology could expand. These are promises for the next chapter, with measurable usefulness as the stated test.
The continuity is easier to see than the new vocabulary might suggest. Marshall is still concerned with the information surrounding a service, the time of the person delivering it, and the trust of the person paying. The desired ending remains wonderfully uneventful: the equipment works, the customer understands why, and somebody gets paid for keeping it that way.