Hi Diane,
We work with electrical and industrial contractors on exactly this decision, so I'll share a recent story instead of a feature comparison.
One of our clients, a $60M industrial services contractor, bought Procore last year for project management. Six months in, they're pausing it. Not because Procore is a bad product. It's a good one. The problem was sequencing. They were also replacing their ERP, and it turned out Procore's cost code structure duplicated what the new ERP already handles, so the two systems wouldn't align when synced. In the meantime, with nothing connected, their team was entering the same data in multiple systems. And the people learning Procore this spring were going to have to relearn both systems this fall.
The lesson learned: the question usually isn't Project Sight vs Procore. It's what your financial system of record will be in three years, and which PM tool fits around it. Since you're on Viewpoint Team today, the answer changes a lot depending on whether you're staying put or thinking about a broader move.
A few questions worth answering before any demo:
- Which system owns cost codes, and will the PM tool sync to it or fight it?
- Where does double entry live today, and does the new tool actually remove it?
- If you change ERPs in the next few years, does this choice survive that?
We kept watching contractors buy good software in the wrong order, so we eventually built a structured way to work through it that we call StackBuilder. Happy to share more details anytime. Either way, when you do demo, insist they use your actual cost structure and one real job, not their sample data.
------------------------------
Brian Zielinski
Managing Director
ShapeConnect
brian.zielinski@shapeconnect.com(847) 322-4929
------------------------------