We first heard about this project from a reader — a VP of operations at a mid-size general contractor we'll call Meridian Build Co. She had a problem that will sound familiar to anyone running multifamily work: a 140-unit, five-story build with 38 subcontractors, and a closeout process that had become a runaway train. Every project in their portfolio was bleeding weeks at the end, not because of field mistakes, but because of information. Drawings lived in one folder, RFIs in another, change orders in email threads, daily logs in a field app, and subcontractor payouts in accounting. Nothing talked to anything else.
We followed this project for 11 months. What follows is the timeline, the decision points, and the numbers — including how a construction management workspace called Stroyby helped them compress a closeout that historically ran 9 weeks down to 7.
The Setup: A Project With 38 Moving Parts
Meridian broke ground in early spring. By week 6, the cracks were already showing. The superintendent was filing daily logs, but the project manager couldn't see them without a phone call. The RFI log had 47 open items, and nobody could say with confidence which ones were blocking which subcontractor. A change order for an HVAC reroute had been approved verbally for three weeks before anyone put a number on it.
The VP put it bluntly: 'We weren't losing money on the work. We were losing it on the handoffs.'
The Decision Point: Standardize or Keep Patching
Meridian had two options. Option one: hire a project engineer whose full-time job would be chasing documents. That's a $70,000-plus salary plus benefits, and it doesn't fix the underlying problem — it just adds a human router. Option two: consolidate the workflows into a single workspace where drawings, RFIs, change orders, daily logs, and subcontractor payouts stayed in sync.
They chose option two. Not because they were sold on technology for its own sake, but because the math was simple. A 9-week closeout on a project this size was costing them roughly $18,000 per week in extended general conditions. If they could shave even a week, the tool paid for itself.
The Obstacles: Field Adoption and the 'We've Always Done It This Way' Problem
The first month was messy. Two of the older superintendents flat-out refused to log daily activity on a tablet. One subcontractor kept sending RFIs by text message. The PM had to rebuild the RFI log three times because the numbering scheme didn't match the old spreadsheet.
What turned it around was a small, unglamorous change: Meridian made the daily log the single entry point for everything. No log, no payout. Within two weeks, the holdouts fell in line — not because they loved the software, but because the alternative was not getting paid.
The Results: 22% Faster Closeouts and a Cleaner Punch List
By the time the project wrapped, the numbers were hard to argue with. Closeout ran 7 weeks instead of the historical 9 — a 22% reduction. The punch list had 61 items instead of the usual 90-plus, mostly because daily logs had caught small issues before they became punch-list line items. And the final subcontractor payout cycle, which used to take 12 days of back-and-forth, closed in 4.
The VP told us the biggest surprise wasn't the speed. It was the visibility. 'For the first time, I could open one screen and see every open RFI, every pending change order, and every payout status without calling anyone.'
What We Took Away
This isn't a story about a miracle tool. It's a story about what happens when you stop treating construction documents as separate artifacts and start treating them as one system. Meridian didn't change their subcontractors. They didn't change their project type. They changed where the information lived.
If you're running projects where closeout always seems to take longer than it should, the problem is probably not your field team. It's the gaps between your systems. You can see how Stroyby approaches that consolidation on their how-it-works page — and yes, the 22% faster closeout number is theirs, not ours.
- Closeout time: 9 weeks → 7 weeks (22% reduction)
- Punch list items: 90+ → 61
- Final subcontractor payout cycle: 12 days → 4 days
- Open RFIs at peak: 47, all visible in one log
None of this required a new hire. It required a decision to stop patching and start consolidating.