Buying construction software can feel a little like buying a car. You know you need something reliable. You have a list of must-haves. You watch a few demos, compare features, maybe even kick the tires a little. Note – I do not recommend kicking your monitor during a software demo. It scares the consultants and makes things super awkward.
But unlike buying a car, construction technology isn’t something you drive off the lot and magically know how to use.
It becomes part of how your business handles projects in every aspect, from early design to preconstruction, team collaboration, document management, subcontractor management, and ultimately, delivering the work. That’s a pretty big deal.
So, what should you actually expect during the technology selection process? Spoiler: it’s about a whole lot more than the demo.
It Starts with Discovery, Not a Sales Pitch
I’ll let you in on a little secret. When I kick off a discovery call, I’m not thinking, “How quickly can I show them Autodesk or IMAGINiT products?” I’m thinking, “Help me understand how you work.” That means I’m probably going to ask a lot of questions. Maybe more than you’re expecting. (Don’t worry – there isn’t a quiz at the end).
Questions we may ask:
- Walk me through how you handle the (fill in the blank here) process today?
- Where does information typically get stuck?
- Talk to me about what happens the moment an opportunity lands on your desk.
- Who touches the project and when?
- If you could wave a magic wand and fix one process tomorrow, what would it be?
I promise that I’m not trying to win a game of Twenty Questions. I’m trying to understand your business before recommending any type of solution, because here’s the truth: the coolest solution in the world won’t solve the wrong problem.
The best demos aren’t generic
I’ll admit it. I cringe a little when I hear someone say, “Just show us everything.”
Everything? We’d be here until next Thursday, and somewhere around hour six we’d both be pretending not to check the time.
A good demo shouldn’t feel like a technology commercial. It should feel like someone saying, “Here’s how this could work for your team.”
That’s why we tailor demos around your specific workflows, your pain points, and your goals. If document control is your biggest headache, let’s spend time there. If estimating is where you’re losing hours every week, we’ll focus our conversation there.
No two companies work the same way, so no two demos should either.
The part nobody puts in the brochure
Let’s say you’ve selected your solution. Congratulations! Take a moment. Celebrate, maybe grab a coffee. Then it’s time to buckle up, because this is where the real work begins.
This is the part that’s going to determine whether your investment succeeds or struggles. <Cue music of possible impending doom>
Implementation.
This is where I usually hear one of two things:
“We just need a little training.”
Or…
“We’ll figure the rest out ourselves.”
Sometimes, that’s absolutely the right approach, but other times it’s a little like buying a fully furnished kitchen, skipping the plumbing, and then wondering why the sink doesn’t work.
Training teaches you the buttons; configuration teaches the software your business
Yes, training is important. It teaches users where to click, how features work, and how to navigate the platform.
Configuration is different. Configuration answers questions like:
- Should approval workflows match your current process?
- How should project templates be structured?
- What document standards should every project follow?
- What permissions should different teams have?
- Which reports will leadership actually use?
Those aren’t software questions, they’re business questions. They’re the kinds of conversations that determine whether your tools fit your business or whether your business spends the next year trying to fit the solutions.
Getting these types of questions right from the beginning can save countless hours (and A LOT of headaches) down the road. Quality hurts once, and it’s a smart way to protect your software investment.
Why services matter
This is the part where people sometimes assume consultants are just trying to sell extra services. I get it! Nobody wakes up hoping to buy consulting services, but here’s another confession: my goal isn’t to recommend the biggest services package – it’s to right-size it for your organization.
Some firms are ready to hit the ground running with minimal support. Others are juggling multiple offices, dozens of users, existing workflows, integrations, or years of project data.
Those organizations usually benefit from taking a little more time upfront to configure the system around how they work.
Think of it this way: would you rather spend a few extra days setting up the foundation or months trying to work around decisions that could have been made correctly the first time?
Technology is only half the story
One of the biggest surprises for many companies is realizing that platform implementation isn’t really about software.
It’s about people.
It’s about helping teams adopt new processes, creating consistency, and building trust in the data. Making sure everyone understands not just how to use the platform, but why they’re using it. The most expensive systems you’ll ever buy aren’t the ones with the highest price tag.
They’re the ones nobody uses.
A great software evaluation shouldn’t leave you thinking, “That was a really impressive demo.” (Although I’ll never shy away from applause/cheers/compliments.) It should leave you thinking, “I can actually picture our teams using this.”
The best platform decisions and rollouts don’t happen because someone bought terrific technology. They happen because people invested the time to understand their processes, prepare their teams, and build a solution that supports the way they work.
Software is an investment.
People are the return.
That’s the difference between a successful software selection with implementation/training and another solution that quietly collects digital dust.
