5-day Senior CM placement on Oracle's hyperscale build in Fargo

Oracle called on a Monday. Their Senior CM seat on an active hyperscale data center build in Fargo had gone vacant. The schedule was already slipping. They needed boots on the ground, not a 60-day search.

Two specifics that mattered. The campus had passed initial concrete pour but the GC was running behind on submittal returns. And the owner's-rep team needed someone who could read a P6 baseline against actual progress on day one — not someone who would spend three weeks learning the program.

Within hours of the intake call we were on the phone with our pre-vetted bench. By Tuesday evening we had three candidates qualified to the specific scope. Interviews ran Wednesday through Thursday. Offer extended Friday. Accepted Friday afternoon.

That's 5 business days for a senior owner-rep seat on an active hyperscale campus.

During the final offer period, the candidate was already asking for P6 access to read the contractor's current baseline, supplier schedules, inventory and staffing levels by trade, and open RFI and submittal logs. That's the candidate. Not someone who shows up Monday and asks where the coffee machine is.

The runner-up was 95% there on paper — 18 years of construction management, two prior data center projects, the right software stack. The reason they didn't get the offer: they'd never run an OAC where the GC was openly behind. Their answer to "how do you handle a contractor who's missing RFI turn deadlines" was process language — "escalate per the contract." Not a story. And they couldn't articulate the OFCI ownership gap on equipment they'd actually managed. Could name the term. Couldn't tell us where it broke last time.

The placed candidate had survived two GMP overruns and could narrate exactly what he'd watch for in week one. That's the 5%.

The candidate was in the seat the following Monday. The project started pulling to the left inside two weeks.