How a Denver commercial fit-out contractor tightened a 6-week proposal cycle to 12 days

The operator

Imagine an illustrative commercial fit-out shop in Denver — about 22 employees, including a director of operations, four project managers, an estimator-and-a-half, a marketing person, a controller, and a field team that swings between superintendents and skilled labor depending on the project. Annual revenue runs around $14M. Projects average $280,000 with a range from $40,000 punch-list remodels to $1.2M full medical office build-outs.

The firm’s pipeline came from three places: repeat property managers (about 55%), commercial brokers (about 30%), and direct tenant inquiries (the rest). The firm had no real marketing engine and didn’t need one — but every PM and broker contact they had was one bad project status update away from giving the next project to a competitor.

The problem

Three patterns kept showing up in lost projects and uncomfortable post-mortems:

• Proposal cycles measured in weeks. From RFP receipt to a signed proposal averaged 41 days. The estimator was a bottleneck. The PMs were a bottleneck for sub bids. The marketing person rebuilt every cover page from scratch.
• Sub coordination by email chain. Each project had a sub matrix in a Google Sheet that nobody outside the PM ever updated. Confirmations happened by phone. Schedules drifted. When a sub no-showed, it was discovered by the superintendent on site at 7 AM.
• Property manager update fatigue. Property managers were getting status updates inconsistently, sometimes by text, sometimes in a Friday email, sometimes not at all. One mid-sized property management group had quietly stopped bidding the firm because — in the words of their facilities lead — “we can never tell where things are.”

There was also a referral problem hiding in the data. The firm had done about 110 projects in the last three years and had never built a structured way to ask satisfied PMs for an intro to their portfolio peers.

What they installed

The fit-out shop installed the Construction Snapshot for GHL and prioritized four workflows in the first 60 days:

1. Estimate builder, rebuilt as a commercial proposal template. The estimator’s spreadsheet was migrated into a structured GHL estimate with reusable line-item libraries for common scope (demo, MEP coordination, drywall, flooring, finish carpentry, FF&E). Proposals went from custom-Word-doc-per-project to template-with-variations.
2. Subcontractor coordination workflow. Every sub the firm uses regularly now has a GHL contact, a sub-pipeline stage per project, and a two-way SMS channel. Schedule confirmations happen by tap-reply. Missed confirmations escalate to the PM 24 hours before scheduled arrival.
3. Project management portal for property managers and tenants. Every active project has a portal where the property manager can see schedule, current phase, change-order status, and the most recent five field photos. The portal replaces the old Friday email.
4. Referral program workflow. Two weeks after substantial completion, the property manager contact receives a structured ask: would they be willing to introduce the firm to one or two peers in their network? A small thank-you gift triggers automatically on a successful intro.

The other eight workflows were turned on and left at defaults to be tuned in the second quarter.

What changed

After 90 days, the picture had shifted considerably:

The proposal cycle was the most measurable change. Average turnaround from RFP to signed proposal dropped from 41 days to 12. The gain wasn’t the estimator working faster — it was line-item reuse and a standardized template removing about 70% of the rebuild work that used to happen on every proposal.

The sub coordination workflow took a chronic operational headache off the table. Sub confirmation rate — the share of scheduled sub appointments with an active confirmation more than 24 hours in advance — moved from the 60% range to 97%. PMs stopped finding out about no-shows at 7 AM, and superintendents got their week back for actual supervision.

Referral-sourced projects grew about 3.4× over a comparable prior-year window. The referral program workflow didn’t invent demand. It just made the ask, at the right moment, in a way that made it easy for a satisfied property manager to fire off a one-sentence intro.

The softest but maybe most important number: project status complaints dropped roughly 81%. The firm tracks these in a tagged folder, and the count went from a steady eight to twelve per quarter to two in the most recent 90 days.

Lessons

What this install reinforced:

• For commercial work, the portal is the product. Property managers are not buying construction. They are buying predictability. A status portal they can refresh on their own time is worth more than a perfect Friday update email.
• Template the proposal, not just the workflow. The 29-day drop in proposal cycle was almost entirely about reusable line items and a standardized cover layout. The estimator’s actual pricing logic didn’t change.
• The referral ask has to be a workflow, not a vibe. The firm always intended to ask for introductions. Until it was an automated step at a defined moment, it didn’t happen at scale.