Somebody in your office signs the check for scheduling software, and that person almost never carries a level. So when you bring them a tool to run the Last Planner System, "it'll make us more collaborative" gets you a polite nod and no budget. You need a number. The good news is the number is real, and the sources of it are boring and specific enough that a controller will believe them. This is how to build that case honestly — what it costs, where the return actually comes from, and where people fool themselves.
Get honest about the total cost first
Nothing kills a business case faster than a number that grows after approval. So price the whole thing, not just the license.
The subscription is the easy part — usually a per-seat or per-project monthly fee, and for a look-ahead tool it's small relative to the labor it touches. The costs people forget are the ones that come out of field time. You'll spend real hours standing up the first project: setting up your locations and areas, loading the trade sequence, getting foremen logged in and past the "why do I have to do this" phase. Budget a few sessions of your own time and a superintendent's to get one job humming. Then there's the weekly cost that never goes away — the planning meeting itself. If a look-ahead and weekly work plan session runs 45 minutes with six trades in the room, that's real money every week, and you should put it in the cost column even though you were arguably already spending it (badly) in hallway conversations and reactive phone calls.
Add it up over a realistic horizon — a year, or the length of the job. A number that includes the ugly parts is more credible than a rosy one, and it protects you when the invoice comes.
Where the money actually comes from
Here's the part most ROI pitches botch: they list twelve benefits and quantify none of them. You don't need twelve. You need two or three that you can defend with your own numbers. On nearly every job, the return concentrates in a short list.
Crew idle time and the half-day nobody logs
This is the big one and it's the one nobody writes down. A drywall crew shows up to a room that isn't ready — the electrician didn't get his rough-in inspected, or the framing inspection is still open, or the material's on the wrong floor. They mill around, they "find something to do," they leave early. That hour or two never shows up on a report as a delay. It shows up as lower productivity that everyone shrugs at.
The whole point of running work through a make-ready process — screening next week's tasks for constraints before you commit to them — is to stop putting crews in front of work that can't be done. When you only promise work that's genuinely ready, the trade shows up and produces. Put a number on it: take your average crew size, your loaded labor rate, and estimate the hours per week your trades currently lose to showing up on unready work. Even a conservative guess here usually dwarfs the software cost, because you're multiplying a wage by a lot of bodies across a lot of weeks.
Rework and out-of-sequence work
When trades stack up out of order because the schedule slipped, quality goes down. The classic is closing a wall before the runs are tested. You skip the megger check to make up a day, drywall goes up, and now you're cutting inspection holes and chasing a fault behind finished gyp. Reliable weekly planning doesn't magically produce good work, but it keeps trades in sequence and gives inspections room to happen before the next trade buries them. Rework is expensive and it's traceable — pull a few real examples from your last job and price them. Two or three documented tear-outs make the abstraction concrete for the person holding the checkbook.
Crisis overtime and acceleration
Reactive scheduling runs on Saturdays. When you find out Thursday that Monday's work can't happen, you scramble, and scrambling costs premium time. Steadier planning flattens those spikes. You won't eliminate overtime — weather and change orders are real — but you can point to the recurring crisis weekends that came from foreseeable, preventable pileups and argue that a disciplined look-ahead catches most of those a week or two out, while there's still time to fix the constraint instead of buying your way out of it.
The one metric that ties it all together
If you measure only one thing, measure Percent Plan Complete — the share of the tasks you committed to this week that actually got done. It's simple: promised twenty, finished sixteen, that's 80%. Most crews that have never run this discipline start somewhere around 50%, which means half of what the schedule "said" was fiction. Teams that stick with weekly make-ready and honest commitment tracking climb into the 80s over a couple of months.
PPC matters for the business case because it's the leading indicator of everything above. Low PPC is idle time, rework, and overtime, just measured before it turns into cost. When you track the reasons tasks fail to complete — waiting on the trade ahead, missing material, no inspection, unclear direction — you get a ranked list of what's actually breaking your schedule. That list is worth more than any generic ROI figure, because it tells you exactly which constraint to kill next. A look-ahead tool like LookAheadWall earns its keep here by making the plan visual and location-based so the misses are obvious, and by keeping the trade-flow sequence in front of everyone so nobody commits to work the crew ahead of them hasn't cleared.
Run a pilot instead of arguing about benchmarks
You'll find industry figures floating around — single-digit productivity gains, a few points of schedule variance, big PPC jumps. Fine as ballpark. But your controller trusts your numbers more than a study, so generate your own. Pick one project, ideally one with a superintendent who's actually willing.
- Measure a baseline before you change anything. Even a rough sense of current PPC and the recurring late-work fire drills gives you a "before."
- Run the make-ready and weekly work plan discipline for six to eight weeks. That's long enough for the team to get past the awkward phase and for PPC to move.
- Track PPC weekly and log every reason for a missed commitment.
- Compare the crisis weekends, the tear-outs, and the crew-standing-around days against the "before."
Now your business case reads: "On the Belmont job we went from 55% to 82% PPC in seven weeks, cut two of our usual Saturday recoveries, and the software cost less than one of those Saturdays." That sentence gets funded. Vague promises about collaboration do not.
Don't oversell the timeline
Be straight about when the money shows up, because if you promise week-one savings you'll lose credibility in week two. Some things improve immediately — the plan gets clearer, the Monday meeting gets shorter and less of a shouting match. PPC and constraint resolution move in the first month or two. The schedule and productivity gains that actually hit the P&L show up over three to six months, once the discipline is a habit and not a chore. The deepest return — a field culture where foremen surface problems a week ahead instead of hiding them until they explode — takes longer and is the one worth the most.
The caveat that makes you credible
Here's the thing most pitches leave out, and including it will do more for your credibility than any spreadsheet: the return depends almost entirely on whether you actually run the process. The software is a tool for a habit. If the weekly plan gets built and then ignored, if foremen don't commit honestly, if nobody tracks why tasks missed, you'll get a fraction of the return or none of it. I've watched crews buy a good tool and keep running the job off a dry-erase board and a group text, and the tool became a very expensive way to not change anything.
So bake the honest condition into your case. The investment pays when the superintendent owns the weekly work plan, when trades make real commitments in the room, and when misses get logged and chased instead of buried. Present it that way and you're not selling software — you're proposing a change in how the field plans work, with a tool that makes the change stick. That's a case a working superintendent believes, and it's a case that survives contact with the jobsite.
Putting the case on one page
Boil it down to something a decision-maker reads in two minutes:
- Current state. Roughly what's your PPC now, and what does unreliable planning cost you — idle crews, rework, crisis weekends? Use real examples from the last job.
- Total investment. License plus setup plus the weekly meeting time, over the year or the job. Don't hide the meeting cost.
- Expected return. Pilot numbers if you have them, conservative estimates if you don't, concentrated in the two or three sources that dominate — idle time, rework, overtime.
- The condition. Returns depend on running the discipline weekly. Say so.
Do that and the math almost always lands the same way: the recovered field hours from even a modest improvement in plan reliability outweigh the cost of the tool by a wide margin, usually inside the first project. The look-ahead schedule isn't the expensive part of your job. The half-days your crews lose to work that was never ready — those are the expensive part. The case for the software is really just the case for stopping that bleed, and putting a number on it is how you get someone with a checkbook to care as much as you do.