Every GC I know has a graveyard of software they bought and stopped using. A field app that never got past the office. A scheduling platform that cost five figures and got used by exactly one person. A "collaboration hub" that became the place documents went to die. The problem is almost never the software itself — it's that the buying decision got made by someone who wasn't going to use it, based on a demo that was rigged to look easy, solving a problem nobody in the field actually had.
I've sat through more of these demos than I care to count, and I've been the guy who had to make a bad tool work after the check was already written. So this is the guide I wish someone had handed me: how to pick construction software that your crews will actually open on a Monday morning, without getting sold a bill of goods.
Start with the problem, not the feature list
The single biggest mistake is walking into this backwards — collecting a spreadsheet of features across five vendors and trying to find the one with the most checkmarks. Feature counts don't win jobs. Solved problems do.
Before you look at anything, write down the two or three things that are actually costing you money right now. Not vague ones. Specific ones. "My supers spend Friday afternoon rebuilding the same three-week look-ahead in a spreadsheet and it's stale by Tuesday." "I found out a sub no-showed because the change never made it out of the trailer." "I can't tell you which of my crews are overloaded next week without calling four foremen." Those are buying criteria. A tool either kills that pain or it doesn't.
Here's a test I use: if you can't explain in one sentence what a piece of software will let you stop doing, you're not ready to buy it. "It'll help us collaborate better" is not that sentence. "It'll let my foremen see next week's plan on their phone instead of me texting it out every night" is.
Separate the categories — most jobs need a few tools, not one
There is no single platform that does estimating, accounting, document control, daily reports, and short-interval scheduling equally well. Vendors will tell you theirs does. It doesn't. The all-in-one usually does one thing genuinely well, two things adequately, and the rest as afterthoughts bolted on to justify the price.
It helps to think in layers:
- System of record — accounting, contracts, buyout. This is your ERP or accounting package. It changes rarely and it's a big lift to replace.
- Document and project management — RFIs, submittals, drawings, daily logs. Where the paper trail lives.
- Planning and scheduling — the master CPM schedule lives in one tool; the weekly work plan and look-ahead live in another, closer to the field. These are not the same job, and forcing your CPM tool to run your weekly planning is why so many look-aheads end up back in Excel.
- Field execution — what the foreman actually touches: the schedule for this week, the daily report, photos, the punch list.
Decide which layer hurts most and solve that layer well. Don't let a shiny field app drag you into replacing your accounting system, and don't let an ERP salesman convince you his weak scheduling module means you don't need a real look-ahead tool.
Weight mobile and field usability above almost everything
Office software gets used because people are paid to sit at a desk and use it. Field software gets used only if it's easier than the alternative, which is a phone call or a marked-up print. That's a much higher bar, and it's the bar most software fails.
When you evaluate anything a foreman or crew leader will touch, test it under real conditions, not conference-room conditions:
- Can you read it outdoors in direct sun? A lot of interfaces are gorgeous on an office monitor and unreadable on a phone at 11 a.m. on a slab.
- Can you operate it with a gloved thumb, one-handed, standing up? If it needs precise taps on tiny targets, it's dead on arrival.
- What happens with no signal? Concrete, steel, and basements kill connectivity. If the app can't hold data offline and sync later, your daily reports won't get filled out.
- How many taps to do the one thing they'll do every day — see this week's plan, or file a daily log? If it's more than a few, they won't.
Put the app in an actual foreman's hands during evaluation and watch without helping. The silence when they can't find the button tells you more than any demo. A short-interval schedule your crews can pull up on the mobile app on the way to the gang box — the way a tool like LookAheadWall's crew-leader app is meant to work — beats a beautiful desktop planner nobody in the field ever opens.
Make the demo work for you, not the salesperson
A vendor demo is a performance. The rep has run that exact script two hundred times, on clean sample data, avoiding every rough edge. Your job is to break the script.
Send them a slice of your real world ahead of time — a real trade sequence, a real week with a conflict in it — and ask them to build it live. Then throw the curveballs that actually happen on a job:
- "The drywall sub just pushed two days. Show me right now what that does to paint and MEP trim, and how you'd notify the affected crews."
- "A crew got pulled to another job Wednesday. Reassign their work and show me who's now overloaded."
- "Show me last month's look-ahead versus what actually happened." (If the tool can't tell you what you planned versus what you did, it can't help you get better. That plan-vs-actual gap is where all the learning is.)
How the rep reacts to being knocked off script is itself data. "Great question, let me show you" is a good sign. Deflection, or "that's on the roadmap," tells you what you're really buying.
Run a real trial with real crews on a real job
Never buy on the demo alone. A pilot on a live project — one super, one or two crews, a few weeks — will teach you more than months of evaluation. Use actual project data, not the sandbox. Give it to your skeptics, not just your early adopters; the enthusiast will make anything work, but the grizzled foreman who hates new tech is your real test. If he'll use it, everyone will.
Watch what people do when they think the tool isn't looking. If your supers are quietly maintaining the old spreadsheet "just in case" three weeks into the trial, the tool has already lost. Adoption is the only metric that matters at this stage. A feature-rich platform at 20% adoption loses to a simpler tool at 90% every single time.
Check references — and ask the questions vendors hope you won't
Any vendor will hand you three happy customers. Talk to them, but steer past the marketing and get to the truth:
- "What did rollout actually feel like? How long until your field guys stopped complaining?"
- "What do you use it for that you didn't expect — and what did you buy it for that you never got working?"
- "When something breaks, how fast does support respond, and do they actually fix it?"
- "If you were buying again today, would you pick them?"
Reference a company your own size and type. A 400-person GC's experience with an enterprise platform tells you almost nothing about how it'll go for a 25-person outfit. Better yet, ask around at your association meetings and supplier lunches — the unfiltered opinion of a super who's used the thing for a year is worth more than any polished case study.
Understand the real total cost
The sticker price is the smallest number in the deal. What actually drains the budget:
- Per-seat math that surprises you. Some tools charge for every field user, which gets expensive fast when you want every foreman on it. Others charge per project or a flat rate. Model it against how you actually staff.
- Implementation and data migration. Getting your existing data in, configured, and clean is often a bigger cost than the first year of licenses.
- Training and lost productivity. Every hour a crew spends learning the tool is an hour not building. Budget for it honestly.
- Integrations. If it doesn't talk to your accounting or estimating system, someone is double-entering data forever — a hidden salary you'll pay every month.
And ask the unglamorous question early: can you get your data back out? Make sure your schedules, logs, and photos are exportable in a usable format. The day you want to leave a vendor is the day you find out whether you own your data or they do.
Plan the rollout like it's part of the job — because it is
Good software installed badly still fails. This is doubly true for anything that changes how you plan, not just what tool you plan in. Moving to disciplined weekly work planning and short-interval scheduling is a habit change first and a software change second. The tool supports the discipline; it doesn't create it. If your supers don't run a real weekly planning rhythm today, no app will make them — but the right app makes the rhythm a lot easier to keep.
So plan for it: pick a champion who owns adoption, start on one job before you go company-wide, and set a firm date when the old spreadsheet gets retired. Parallel-running the old and new systems forever is how tools die — people default to the familiar one. Force the switch, support it hard for a few weeks, and let it stick.
The short version
Buy for the problem, not the feature grid. Match the tool to the layer that's actually hurting. Weight field usability above office polish, because adoption is the whole game. Break the demo on purpose, pilot with your skeptics, and check references like you mean it. Count the true cost, confirm you can walk away with your data, and treat rollout as real work.
Do that and you'll skip the software graveyard. The right tool isn't the one with the longest feature list — it's the one your worst-tempered foreman quietly starts relying on without being told to. When that happens, you picked well.