Multi-Unit Mobile Modular: Lock the Spec, Compare Landed Cost, Then Talk Price

Multi-Unit Mobile Modular: Lock the Spec, Compare Landed Cost, Then Talk Price

If you're buying mobile modular units for a multi-unit project — portable project offices, relocatable classroom modules, volumetric units — here's the short version.

A price comparison only means something when two suppliers are quoting the same spec. On multi-unit work, they almost never are. The practical fix is to lock the written spec first, then compare total landed cost, and only then line up the quotes themselves.

I'm an office administrator, not an architect. I run facilities purchasing for a company of roughly 450 people. I manage about $1.4 million a year across twelve vendors, and I report to both operations and finance. I took over vendor relationships in 2021. I learned the multi-unit module thing the hard way in 2024.

Why my take on this is worth a few minutes

In early 2024, finance flagged three separate invoices for modular units from three sites. Why were three projects buying from three different suppliers? And why did the "same" portable project office cost different amounts on each invoice?

The job landed on me. My first move was the standard one: request factory quotes from mobile modular suppliers. Finding vendors wasn't the hard part. Getting three comparable quotes — that was the hard part.

Every factory catalog lists a portable project office. Every spec sheet looked like the same thing. It wasn't.

Here's something the spec sheets won't tell you: a "standard lead time" often includes buffer time the vendor uses to manage their production queue. It's not necessarily how long your order takes. For two units, that distinction doesn't matter. Across 18 unit orders spread over three sites — it decides whether site prep starts on time.

The 9-day decision I'd do differently

I had nine days to pick a supplier before a site-prep window closed. Normally I'd lock the spec, request equivalent quotes, and do a technical review. There was no time.

I picked based on price and verbal delivery promises. In hindsight, I should have held the line on equivalent quotes — even if it meant pushing the site-prep date back. But with operations waiting, I made the call on incomplete information. That's the honest version.

What I actually needed was three things, in this order: a locked spec sheet, a confirmed code path, and a delivery date in writing. Not three quotes on three different versions of the same product.

What "compare supplier options" actually requires

Most suppliers will send you a quote. Some will send you a comparable quote. The second group is the one you want.

Concrete example. One vendor's "standard electrical package" meant weatherproof outlets in a rain-tight enclosure. Another vendor's "standard electrical package" meant a hard-wired panel with breakers. The spec sheets read similarly. The quoted price differed by about 11%.

For two units, that gap is noise. For 18 units, it's a line item I have to explain to finance — and by then the spec mismatch is baked into the contract.

This is why I now compare total landed cost, not unit price. Break every quote into: unit price, freight, configuration fees, compliance review costs. In that order.

In my own 2024 comparison, pure unit prices varied 12%–18% across suppliers on paper. Once freight and configuration were folded in, total landed cost gaps narrowed noticeably. Freight alone accounted for roughly 7%–11% of landed cost across the three sites in my notes — which I recognize isn't a universal number, just what showed up in our case.

Comparing raw unit prices would have pointed us at the supplier with the highest downstream cost. I should have started with landed cost. I didn't. That's a lesson I paid for in a follow-up conversation with our controller.

The part that isn't about price at all

One thing I keep coming back to: the unit our operations lead receives is the first impression of how my team runs a project. If the electrical package is wrong, or delivery slips across five weeks instead of one drop, they don't blame the factory. They blame purchasing — meaning me.

So the money saved on a lower-spec electrical package gets spent back on internal credibility. In my experience, that trade almost never works out in your favor. The first impression lands on the admin buyer, not the supplier.

When this approach doesn't apply

Two cases where locking the spec and doing a full landed-cost comparison is overkill.

Small orders. If you're buying two or three units with standard specs, two or three quotes is enough. Don't build a full spec matrix for a purchase that fits in one email thread.

Site-specific constraints. If the site has unusual zoning, easements, or historic-district rules, the local supplier's familiarity may outweigh a factory-direct price advantage. The comparison criteria change entirely when code interpretation matters more than unit cost.

Also: if you need delivery faster than about eight weeks, price comparison stops being the main question. On a compressed timeline, delivery certainty is the variable that decides the outcome. Price becomes secondary.

What I'd tell someone starting this now

Multi-unit mobile modular isn't a mysterious category. It's ordinary purchasing where the spec gets multiplied by volume, and where the low purchase frequency means you don't have a baseline to tell what a fair quote looks like. An office administrator doing routine buying has the process and the vendor relationships. What they often don't have is a benchmark for what modular quotes should contain.

Having a sourcing partner that works factory-direct and does multi-supplier comparison — ArcSpan Sourcing is one example of that model — can shorten the gap. But the shortcut isn't the advice. The advice is this: lock the written spec, compare total landed cost, and get the delivery date in writing before you touch the price column.

The single unit that shows up wrong doesn't just cost money. It costs you the room where you had internal credibility. That's the number I'd like to have known going in.