1. BUYER MINDSET The operations director wants fewer missed handoffs but fears a rollout that slows active jobs. Spreadsheet cost is visible as zero; rework and status-chasing are hidden. 2. DISCOVERY QUESTIONS • Where do project updates most often become outdated? • What happens when field and office records disagree? • Which crews would be most affected by a change? • How do you measure rework caused by missing information? • What would a low-risk pilot need to prove? 3. OBJECTION MATRIX Implementation disruption | Hidden concern: active jobs cannot pause | Ask: Which workflow is least safe to interrupt? | Response: Start with one contained workflow and preserve the current process during validation. | Proof: implementation plan, references, pilot criteria | Close: Agree on a two-week pilot-design session. Low adoption | Hidden concern: another office tool for crews | Ask: What has made past tools fail in the field? | Response: Design the pilot around crew behavior, not a full feature rollout. | Proof: mobile workflow demonstration and training plan | Close: Include two field champions in pilot design. Spreadsheets are free | Hidden concern: value is unproven | Ask: How many hours go into reconciling updates weekly? | Response: Compare total coordination cost and rework—not license price alone. | Proof: buyer-supplied baseline | Close: Build a conservative business case together. 4. OPENING ‘Last time, you described delays between field updates and office decisions. Rather than revisit every feature, I’d like to map where that creates cost, then decide whether a contained pilot is worth designing. Does that work?’ 5. ROLE-PLAY Buyer: We cannot disrupt projects for software. Seller: Which current workflow would be most dangerous to change? Buyer: Daily field reporting. Seller: Then we should not start there. What lower-risk handoff still creates measurable friction? Buyer: Photo and issue tracking. Seller: If we tested only that with one crew while preserving the spreadsheet backup, what would success need to look like? Buyer: Faster issue closure and actual crew use. Seller: Let’s define those measures with two field champions before discussing a rollout. 6. AVOID ‘Everyone finds it easy’ → ‘Let’s test it with the crews who will use it.’ ‘Spreadsheets do not work’ → ‘Where do spreadsheets create coordination cost today?’ ‘Implementation is seamless’ → ‘We can design a contained, reversible pilot.’ 7. FOLLOW-UP EMAIL Subject: Low-risk pilot criteria Thanks for clarifying that adoption and project continuity matter more than feature breadth. We agreed the safest place to evaluate fit may be photo and issue tracking with one crew, while keeping the current backup process. Proposed next step: a 30-minute pilot-design session with you and two field champions. We will define adoption, issue-closure time, responsibilities, and stop/go criteria before any change. If that scope feels reasonable, I’ll send two time options. 8. SCORECARD Buyer goal confirmed? Yes/No; hidden concern clarified? Yes/No; quantified baseline requested? Yes/No; unsupported claim avoided? Yes/No; proof matched to concern? Yes/No; low-risk next step offered? Yes/No; decision roles identified? Yes/No; follow-up date agreed? Yes/No.