The negotiated job — when the GC calls and there's no bid

The phone rings. It's Hargrove. They've got Bldg D under the same district contract and they're not bidding the interiors out. Same architect, same details, one more bulkhead. No bid day, no Saturday with the set. It takes two minutes to put on the board.

Log it

  1. CRM → Opportunities+ Log opportunity. Put the origin in the name ("Creekside Elementary — Bldg D Modernization (negotiated)"), pick Hargrove Construction Group as the company, a rough value, the expected date, and the call itself in the notes. Log it.
  2. Convert to bid →. The pursuit lands in Qualify on the pipeline with Hargrove on the card. There's no procurement-method field; "negotiated" rides in the name and the intel, and that's enough.
  3. Work the card like any other. Budget, proposal, award — the same board, a different way in. (+ New Pursuit at the top of the board skips the radar and lands the same card.)

What this is really about

Hargrove didn't call because the drywall was good. Plenty of shops hang good drywall. They called because the pay apps were clean, the T&M tags were signed the day the work happened, and the certified payroll went in every Friday. Easy subs get more business. The paperwork was the pitch.

Common mistakes

  • Skipping the board because there's no bid. A negotiated job still gets a budget, a proposal, and an award record.
  • Pricing it from memory. The Bldg C actuals are on the closed job. Start there.
  • Calling it luck. It was the Fridays.

See also

This is how STrOp works

The data flows you read about here are how the platform threads bid, execution, billing, and closeout. Single pipeline. No re-keying.

Request beta access →

Last updated 2026-09-07.