1
Fit signals to look for Check these during research, before the first call.
How do technicians record inspections and repairs today? Listen for: paper forms, spreadsheets, or a shared desktop terminal Which system is your system of record for maintenance? Listen for: the back-office platform iMarq would connect to How long does it take a finished job to reach that system, and who re-keys it? Listen for: days of lag, office staff re-typing, lost forms Which compliance requirements drive your paperwork, and how long does audit prep take? Listen for: audit findings, weekend prep, binders How many technicians, locations, and assets would use this? Listen for: sizing for the proposal What does connectivity look like where your crews work? Listen for: dead zones that make offline a must What have you tried before, and how did the crew take to it? Listen for: adoption risk and a failed rollout to avoid repeating Who decides, who signs, and who approves on the IT side? Listen for: the economic buyer and the IT reviewer What triggered this conversation now, and when do you need a change in place? Listen for: an audit, growth, a contract ending Which FRA inspections and forms take the most crew time today? Rail only Listen for: the forms to digitize first Are you a Class I to III, short line, terminal, or rail service provider? Rail only Listen for: which rail playbook to use Are crews on track, mechanical, or both? Rail only Listen for: which workflows to show in the demo
Ask live: pain questions Push past the first answer. Ask what the problem costs in hours, downtime, or audit findings, who feels it most, and what happens if nothing changes this year.
3
Value props to establish 0 of 3 selected Pick the three this prospect confirmed. They become the spine of the proposal.
FRA-ready records generated automatically Works offline across track and yards Crew adoption over 90% at RELAM Connects to the ERP you already run iBot answers from your own maintenance data