What This Course Is (and Isn't): A Map of the Major Platforms

Welcome

Hello, and welcome. This is Super Structures General Contractors — a national general contractor headquartered in Powhatan, Virginia — here to help you and your clients build something that lasts. We're glad you're with us, and we look forward to connecting with you.

Alright, What This Course Is (and Isn't): A Map of the Major Platforms. Don't let the plain title fool you. Here's the part that actually matters on the job: You do not need to master eleven platforms; you need to know what each one is for, who it fits, and how it talks to the others, so you can choose well and ask good questions. Learn it well and the next software demo will be you interviewing the vendor instead of the other way around.

A superintendent at a mid-size GC got handed three logins in one week: Procore from the owner, P6 from the scheduling consultant, and a Bluebeam Studio Session from the architect. Nobody explained what each one was for, so for a month he used all three badly and his own phone for everything that mattered. By the time someone sat him down for an hour and drew the map, he had already been blamed for a missed RFI that was sitting in a tool he did not know he owned. That hour is this course.

A note before we start: this is a high-level overview, not the training you will need to run the product. Super Structures is not affiliated with, sponsored by, or paid by any company named in this course, we do not sell or support these products, and nothing here is legal, financial, or purchasing advice. This is for learning and education only. Features, editions, and pricing change often. Each lesson lists the vendor's own website, which is where to go for current details, demos, and training.

Where we stand

We teach these products because you will meet them on the job, not because we sell them. Super Structures has no legal, sales, support, or financial relationship with any company in this course and receives no money from any of them. We are not telling you to buy anything. Every platform lesson ends with the vendor's own website, which is where to go for current details, demos, pricing, and real training. This course is for learning only.

What this course covers

Eleven platforms you will hear about on nearly every commercial or residential job, grouped by what they do:

• Project management and field: Procore, Buildertrend, Autodesk Construction Cloud, Bluebeam Revu.
• Scheduling: Primavera P6, Microsoft Project.
• Accounting and ERP: QuickBooks for contractors, Foundation, Sage Construction, Acumatica Construction Edition, CMiC. Then two lessons that matter more than any single product: how they integrate with each other, and how a CRM helps your company.

What this course is not

• It is not product training. Each vendor has its own courses, and most of the big ones have free certification tracks. Take those when you have chosen.
• It is not a ranking. The right tool depends on your size, your trade, your owners, and what you already run. A product that is perfect for a $300 million GC is a burden for a twelve-person remodeler, and the reverse.
• It is not a price list. Pricing models change constantly. We describe how each one tends to charge (by user, by volume, by module, by computing resources) so you know what to ask, and we never quote a number.
• It is not an endorsement. Super Structures is not affiliated with any of these vendors. We describe what each product is known for and where users report it being thin.

How to read each overview

Every platform lesson answers the same six questions, so you can compare across lessons:

• What it is: the category and the core job it does.
• Who it fits: company size, trade, and the kind of owner that asks for it.
• What it does well and where it is thin.
• How it is sold: per user, per project volume, per module, cloud or on-premise.
• How it connects: the integrations that matter most.
• What it takes to run it: the training, the admin time, and the data discipline.

The five layers of a contractor's stack

It helps to picture the software as layers, each holding a kind of job data:

• Pursuit: the CRM, where owners, architects, leads, and bids live before there is a job.
• Preconstruction: takeoff and estimating, where quantities become a price.
• Project management and field: documents, RFIs, submittals, daily logs, change management, where the job is run.
• Scheduling: the logic and dates the field works to.
• Accounting and ERP: job cost, billing, payroll, and the general ledger, where the money is recorded. A small company covers all five with three tools and some spreadsheets. A large one may have a product in every layer. The layers are the same.

The one idea underneath all of it

Every tool here holds some of your job data: the estimate, the budget, the schedule, the drawings, the RFIs, the costs, the people. The value comes from that data flowing between tools without being re-keyed. When you evaluate any product, the question is never "does it have feature X." It is "where does this data come from, where does it go next, and who is responsible for keeping it right."

How contractors actually choose

Most software decisions in construction are made one of four ways: the owner or the GC above you requires it; a new controller or PM brings the tool they already know; a salesperson shows up at the right moment; or a crisis (a lost bid, a surety problem, a blown job) forces a change. None of those is a method. The method is the one this course builds toward: know the categories, know your own data flow, define the problem, evaluate on your own data, pilot, then train.

Going Deeper (Intermediate)

Build your current-state map before you watch another demo. One page: every tool your company uses, what data lives in it, who owns it, and every place a person re-types data from one tool into another. Those re-typing arrows are your integration opportunities and your error sources. Most contractors who draw this map for the first time find five to ten of them, and at least one that explains a recurring mistake.

Then write the problem statement in one sentence before naming any product: "Our PMs cannot see committed cost until the controller closes the month" is a problem. "We need Procore" is a conclusion. Half the software purchases in this industry started with the conclusion.

Advanced / Pro-Level

Pros evaluate platforms against their own job data, not the vendor's demo project. They bring a real estimate, a real schedule, a real month of costs, and ask the vendor to load it. They talk to three reference customers of their own size and trade, and ask what the second year was like, not the first. They budget the people cost: a system owner with hours in their week, training for every user, and three to six months of lower productivity. They pilot on one job before they roll anything out company-wide. And they write data portability into every contract, because the job history they build over a decade is worth more than any product.

They also know the difference between a platform decision and a tool decision. The accounting system and the PM platform are platform decisions: they shape everything around them and take a year to change. A takeoff tool or a time-clock app is a tool decision: pick one, try it for a quarter, switch if it does not work.

Practice Challenge

List every software tool your company touches in a week, including spreadsheets, text messages, and email used for job data. Next to each, write what data lives there and who owns it. Circle every place someone re-types data from one into another. Then write one sentence describing the biggest problem the circles reveal. (Answer: there is no single right list; the point is the circles, and most companies find five or more; each one is a candidate for integration or for picking one system of record, and the sentence is your problem statement for the rest of this course.)

In Practice

The superintendent who knows the map opens Procore for the RFI, checks P6 for the look-ahead, and marks up the drawing in Bluebeam, in ten minutes. The one without the map uses his phone and gets blamed for the RFI he never saw.

Common Mistakes to Avoid

• Treating a high-level overview as training, then blaming the product when it is misused
• Buying on features instead of on data flow and fit
• Starting with the product name instead of the problem statement
• Letting each department pick its own tool with no shared cost codes or job numbers
• Skipping the current-state map and evaluating against the vendor's demo data

Takeaway: You do not need to master eleven platforms; you need to know what each one is for, who it fits, and how it talks to the others, so you can choose well and ask good questions.

Educational content, for learning only. This is a vendor-neutral, high-level overview, not product training, support, or a recommendation. Super Structures General Contractors and Super Structures Learning are not affiliated with, endorsed by, sponsored by, or compensated by any company or product named here, and we receive no money from them. Product names are trademarks of their owners. Features, editions, integrations, and pricing change; verify current details on the vendor's own website before you buy.