In your conversation with MWS a year ago, you framed upfits as strategic investments and walked through best practices at a high level. Since, what have you been hearing from fleet managers that tells you standardization is the next problem worth solving?
Alexa Rubin: The dialogues with fleet managers has shifted toward a search for order. The post-COVID landscape left many fleets with highly fragmented specifications, and the need to “get whatever was available” led to a sacrifice of standardization in favor of immediate uptime.
Now that these vehicles are reaching the end of their cycles, managers are facing high costs and long lead times associated with maintaining a heterogeneous fleet. We are hearing that standardization is the primary lever for compressing order-to-delivery timelines and reducing TCO. The emphasis is now on leveraging vendor networks and fleet management partners to create repeatable, core specifications to regain procurement discipline without sacrificing the functional utility required for field operations.
MWS: When you walk into a fleet operation that has lost control of its upfits, what do you see? Talk us through the patterns that keep showing up across clients.
RUBIN: When a fleet has lost control of its upfits, the first thing you feel is frustration due to vehicles that aren’t configured for the work at hand. Technicians are forced to improvise around missing functionality, and managers are constantly firefighting instead of planning. That frustration manifests in predictable operational patterns.
For example: frequent rework and retrofits due to undocumented or mismatched specs; prolonged downtime while parts or the “right” chassis are sourced; and wildly inconsistent installs from region to region or vendor to vendor, creating maintenance headaches and safety risks. You also see crews using the wrong vehicle for the job or adapting tools to fit a vehicle, broken vendor relationships, a tolerance for mediocre builds just to keep assets moving, and BOM mismatches that bloat inventory and slow repairs. All these symptoms point directly to weak specification of governance, and a pressing need to standardize upfits.
MWS: Spec creep is one of those phrases that fleet managers nod at without always defining it the same way. How would you describe it? Where does it usually come from within an organization, and what is the real cost when no one keeps it in check?
RUBIN: Spec creep is the gradual, unofficial accretion of one‑off requirements and local modifications into a fleet’s baseline specs. It starts when there’s no formal, disciplined process for evaluating, prioritizing, and applying field feedback. It often originates in the front lines with technicians and drivers who identify real problems, but it can also come from regional managers or procurement trying to placate internal stakeholders, salespeople asking for customer‑specific tweaks, or well‑meaning engineers pushing incremental changes.
Left unchecked, spec creep multiplies complexity. Your procurement department struggles to compare bids and parts. As a result, BOMs fragment and inventory costs rise; maintenance and training become inconsistent, lead times lengthen, and safety and resale values suffer.
That doesn’t mean field innovation should be ignored. I once met a former HVAC tech who patented a tamper-proof hinge. His employer declined to pursue his idea, and now his solution is a standard option offered by several manufacturers. Fleets should create a clear feedback channel for frontline ideas but couple it with a governance process so beneficial innovations scale without turning your fleet into a mosaic of incompatible builds.
MWS: Is the best approach to base spec with controlled modifications?
RUBIN: A rigid base spec often fails to meet the needs of most businesses because the small, functional tweaks that drive on-the-ground efficiency are exactly what differentiates a fleet and creates value for its clients. The goal isn’t to strip the vehicle down to a bare-bones build, but rather to ensure that necessary modifications are standardized across the entire organization. While some argue that technicians work differently and require individual customization, allowing that level of variability can tie a vehicle to a specific person, making it difficult to reassign if that employee leaves.
In addition, a technician’s personal preference for efficiency doesn’t always align with the safest or most sustainable way to complete a task. Allowing “carte blanche” builds at the technician or location level creates a confusing litany of specs that are impossible to manage. Therefore, the goal is to provide a functional build that fully supports the job requirements out of the box so that workers aren’t tempted to make their own “custom” modifications in the field, while maintaining strict organizational control over those specifications to ensure every vehicle remains safe, transferable, and easy to maintain.
MWS: Adopting the framework is one thing; protecting for three+ years in is another. Who should own the spec inside a fleet organization, and what does a healthy change-control process look like when a region or a technician asks for an exception?
RUBIN: Protecting the framework over time comes down to ownership and discipline, and that starts with a clearly defined fleet playbook. The specs should be centrally owned, typically by the fleet manager or a small governance group and fully documented so they outlive any individual and allow the team to focus on improvements rather than constantly reinventing processes. That playbook should cover everything from OEM selection and total vehicle budget down to incident procedures, creating a clear set of parameters for decision-making.
When it comes to change control, the key is that requests don’t get decided in the moment. Rather, they get evaluated against the playbook. If a region or technician requests an exception, it should follow a defined path. Does it align with safety standards? Does it improve efficiency in a measurable way? And can it be applied consistently across the fleet? If it meets those criteria, it can be incorporated in a controlled way. If not, it should be declined without ambiguity.
Just as important is setting expectations up front by having drivers and stakeholders understand and acknowledge the playbook. That way, they know how to submit ideas and, more importantly, that approvals are based on a consistent framework, allowing you to say “yes” where it makes sense without unraveling the broader strategy.
MWS: Tell us about the Ford Transit your team converted into a mobile key-making center. What was the customer trying to solve, what were the design constraints around integrated storage and onboard power, and how did the build come together?
RUBIN: This upfit was a finalist for the 2026 Upfit of the Year recognition. My colleague, Todd Mattingly, an upfit manager led the project, here’s what he said.
The Ford Transit Key Van upfit started with a clear operational problem: the customer needed a way to produce keys on demand across multiple vehicle dealership and auction locations without being tied to a fixed shop. From a design standpoint, three things drove almost every decision: reliable onboard power, a usable workspace, and organized storage for a wide variety of parts and tools.
Locksmithing equipment is sensitive to power quality, and the machines need to run consistently throughout the day, so power stability was a must-have. At the same time, technicians needed a well-lit interior to handle detailed work, and enough integrated storage to keep hundreds of key blanks, fobs, and tools organized and accessible without wasting time digging around for them.
The first iteration of the van used a more traditional setup—an inverter paired with house batteries that charged off the chassis alternator or shore power. It worked, but it introduced some inefficiencies and added system complexity. Based on feedback from the field, the second iteration moved to a 3072Wh battery bank with shore power integration. This simplified the system by eliminating the need for both the inverter and separate house batteries, while still delivering consistent, reliable power for the lighting and key machines. It also reduced maintenance concerns and made the system more predictable for daily use.
Inside, the layout was built around the workflow. The key-cutting and programming machines were positioned to create a natural work sequence, minimizing unnecessary movement. Work surfaces were sized to support both the equipment and in-progress jobs, while still leaving room to maneuver inside the van. Storage was customized to handle a high volume of small, varied parts, so technicians could quickly find what they needed. Lighting was upgraded to ensure even bright coverage across the workspace, which is critical for precision tasks.
What made the build successful was the collaborative process. The customer, their field technicians, and the upfit team worked closely through each iteration. Feedback from real-world use directly informed improvements, and the upfit team translated those insights into practical design changes. The result is a mobile key-making center that’s not just functional but optimized for how technicians work.
MWS: That Transit is a good example of a non-standard use case. What did the build reinforce about the playbook itself? Where did modular thinking pay off, and were there moments that pushed you to refine how Mike Albert approaches similar specialty conversions?
RUBIN: The Transit build is less a showcase of modularity and more a validation of the playbook in action, specifically how well it governs collaboration. What stood out was the tight feedback loop between the client, their technicians, the upfit design team, and the installation team. It was a technically complex build that opened meaningful revenue opportunities, and because the use case was so new, there wasn’t a pre-existing modular solution to rely on. Instead, the strength of the process carried it. Utilizing clear communication, defined expectations, and a shared commitment to getting it right.
Where the playbook really proved its value was in iteration. The first build was treated as a true pilot, tested in the field, and then refined based on real-world use. The improvements in the second iteration didn’t happen by chance; they were the result of disciplined feedback and a willingness to adjust within a structured framework. It reinforced that, for specialty conversions, modularity may not always be the starting point, but a strong playbook ensures that even one-off builds can evolve into repeatable, functional solutions over time.
MWS: How should fleets think about the upfit itself throughout the vehicle’s lifecycle? Where can fleets recapture value at decommissioning that they are leaving on the table today?
RUBIN: While fleets have historically treated the chassis as the asset and the upfit as a sunk cost, that mindset leaves real value on the table. The better approach is to manage the upfit as its own lifecycle asset, as one that should be inspected, maintained, and evaluated independently at each stage of the vehicle’s life.
While many organizations automatically cycle the upfit with the chassis, there are cases where investing in a higher-quality build upfront, or even redeploying an upfit, can create savings, reduce lead times, and limit material waste.
The challenge is that there’s no universal solution. Some upfits are built to last beyond a typical five to seven year vehicle lifecycle, but many are not, especially in fleets where equipment is used heavily every day. By the time the chassis is ready for replacement, the upfit may be at its end of life as well, and attempting to transfer it can introduce fitment issues, safety concerns, and additional labor costs that erode any expected savings.
A strong lifecycle approach starts with consistent inspection protocols, not just at decommissioning, but throughout the vehicle’s life. That way, fleets understand the true condition of the upfit before making a redeployment decision. From there, refurbishment must be practical and repeatable. Can the upfit be removed, reinstalled, and warrantied without introducing risk? Do you have the right partners to do that work reliably? Warranty terms also play a major role, and they’re often overlooked. A longer-life upfit only creates value if the warranty meaningfully supports that extended use, which is not always the case.
Where fleets can recapture value is in being more intentional. That might mean selectively redeploying higher end upfits where condition, compatibility, and labor economics make sense, or it could mean improving decommissioning practices by harvesting reusable components, standardizing parts, or negotiating better residual value with vendors. The key is shifting from an automatic replacement mindset to disciplined evaluation by understanding when an upfit still has life left and, just as importantly, when trying to extend it will create more cost and complexity than it saves.
MWS: Once a fleet has the framework in place, how do they prove it is working?
RUBIN: Upfit success shows up less as a spike in one metric and more as the absence of noise. The most immediate signal is that the fleet stops generating complaints. Vehicles are fit for purpose, maintenance is predictable, and operations run without constant intervention. From there, you can look at more concrete indicators. Technician retention is a strong one. When crews work from consistent, well-designed, and well-maintained vehicles, they take more pride in their work and are far less likely to push back on assignments. On the other side, if you’re still hearing, “Don’t put me in that truck!,” it’s a clear sign something isn’t working.
TCO is another critical lens. OEMs and fleet management partners can provide benchmarks, and comparing your actuals against those projections helps surface where things may be off. That’s often where latent issues reveal themselves. For example, rising tire spend could indicate a build that’s too heavy for the chassis, or it could point to driver behavior, but without that data, you wouldn’t know for sure. Safety metrics matter as well. A sustained reduction in workers’ compensation claims tied to vehicle use is a strong indicator that your specs, training, and processes are aligned. Those outcomes don’t just validate the framework internally; they become a meaningful part of how you attract and retain talent, reinforcing a cycle where better vehicles and safer conditions lead to stronger teams and more efficient operations.
MWS: For fleet managers recognizing that their upfit program is messier than it should be, what is a realistic first move in the next 30 to 60 days?
RUBIN: The first move should not be a wholesale redesign; it should be getting grounded. Fleet management is often underestimated and is sometimes a part-time responsibility, so the key is to break the problem down into manageable pieces rather than trying to fix everything at once.
Start by identifying the most painful, visible issues in the fleet and gathering the data needed to understand them, such as downtime, rework, maintenance spikes, or recurring technician complaints. From there, focus on small, high-impact changes that are fully within your control and document those decisions as the foundation of a playbook. Early wins matter because they build internal credibility and can help unlock broader support, whether that’s executive buy-in or additional budget for future pilot builds.
At the same time, involve your technicians early. They’re closest to the work, so showing that their input leads to tangible improvements helps create alignment before larger changes are introduced. What you want to avoid is the instinct to overcorrect by jumping straight into a full spec overhaul or chasing a “perfect” future-state design without the data or organizational support to sustain it. That approach often creates more disruption than progress. Instead, prove that incremental improvements can stabilize operations, then use that momentum to scale more meaningful changes over time.
about the author
Alexa Rubin is Manager of Truck Upfit at Mike Albert Fleet Solutions, where she helps clients design vehicle upfits that balance functionality, driver satisfaction, and total cost of ownership. She works closely with a broad network of upfit manufacturers and fabrication partners across North America.
