01
Rollout Training
New platform going in? I train the people who have to use it on Monday. Role-based sessions for PMs, supers, foremen and field crews, built around your actual workflows, not a vendor's demo data.
Construction Technology Training Specialist
Construction technology that actually gets used in the field.
Most construction software doesn't fail in procurement. It fails on the jobsite, three weeks after rollout, when nobody remembers why it mattered. I train the crews who have to live with it.
01
The gap is never the licence. It is the handover.
Nobody ever went back to paper because the software was too good. They went back because the handover was too fast.
Field-based training for construction teams
On-site nationwide, remote available
Construction software rarely fails because it was the wrong product. It fails because it arrived on a Tuesday with a two-hour vendor demo, and by the following month the crew had gone back to paper, phone photos and a group chat. The gap is never the licence. It is the handover.
This practice exists to close that gap. Training is built around your actual workflows and your live projects rather than a vendor's sample data, delivered in blocks short enough that crews stay with it, and followed up at the three-to-six week mark where adoption usually quietly dies. The aim is to leave you with people who can train the next crew without calling anyone.
Role-based
PMs, supers, foremen and field crews trained separately, not together
On-site
Trailer, conference room or tailgate, or remote if that suits better
Defined end
Short engagements with a finish line, not an open retainer
02
What I do
Four ways in, depending on where the rollout actually is.
02
Adoption Recovery
Already bought the software and nobody's using it. I find where it broke down, retrain around the real objections, and get usage back up without restarting the whole implementation.
03
Train-the-Trainer
Build internal capability so you stop paying outside help. I develop your superusers into people who can onboard the next crew, the next project and the next hire without me.
04
Curriculum & Documentation
Job-aids, quick-reference cards and short-form video your field teams will actually open. Written at the level the work happens, not the level the software was sold at.
Training that happens where the work happens.
Trailer, conference room or tailgate. In blocks short enough that crews stay with it, using your projects and your data rather than a vendor's demo.
03
How it works
Short engagements with a defined end. You should not need me permanently, and the last step exists to make sure you don't.
01
Assess
A short discovery on-site or remote. What you bought, what's actually being used, and where the drop-off is. You get a straight read even if the answer is that you don't need me.
02
Build
Training built to your workflows and your projects, using your data. Role-based, so a foreman isn't sat through a project engineer's session.
03
Deliver
On-site or remote, in blocks short enough that crews stay engaged. Trailer, conference room or tailgate, whatever fits the schedule.
04
Reinforce
Follow-up at the point adoption usually dies, three to six weeks out. Job-aids in hand, superusers identified, and a usage check so you know it stuck.
Tell me what you rolled out and how it's going.
If the honest answer is that you don't need training, I'll tell you that too.