Contractor Problem Interview Script (Copy + Adapt)

Contractors respond better to short, concrete, jobsite-friendly questions than to a lengthy, abstract discovery script designed for a desk-based professional — this template covers four sections (recent job walkthrough, money leaks, past tool experience, and wrap-up) built specifically for the shorter attention windows and more concrete conversational style this population typically brings to an interview, whether it happens over a full scheduled call or a brief exchange at a supply house.

Quick Answer: This script covers four sections: a walkthrough of a specific recent job to anchor the conversation in something real, direct questions about where money or time was lost on that job, questions about any software or tools they've tried and abandoned, and a brief wrap-up. Keep each section short and concrete, following Mom Test discipline — ask about specific past behavior, not hypothetical future interest — and expect the whole interview to run considerably shorter than a typical desk-based discovery call.

The Template

Opening (30 seconds): "Thanks for talking with me. I'm trying to understand how [trade/role] handles [specific workflow area] — not selling anything, just learning. Mind if I ask about a recent job?"

Section 1 — Recent job walkthrough:

1. "Tell me about the last job where [specific workflow area] came up — what happened?"
2. "Walk me through what you did, step by step, from start to finish on that."

Section 2 — Money and time leaks: 3. "Was there a point in that job where things got delayed or cost more than expected because of this?" 4. "How much time or money would you guess that cost you, roughly?" 5. "How often does something like that happen — that job, or most jobs?"

Section 3 — Past tools and workarounds: 6. "Have you tried any app or software for this before? What happened?" 7. "What do you currently use instead — paper, a spreadsheet, texting, something else?"

Section 4 — Wrap-up: 8. "Is there anyone else dealing with this same thing you think I should talk to?" 9. "Can I follow up if I build something and want your take?"

Question-by-Question Rationale: Intent Table

Filled Example: 20-Minute Interview With a Drywall Sub

Opening: "Thanks for talking with me — trying to understand how drywall subs handle scheduling with GCs, not selling anything yet."

Q1-2: "Last job, GC pushed our start date twice without much notice — first time I found out was showing up to a site that wasn't ready for us. Cost us two wasted trips and we had to shuffle another job to cover the gap."

Q3-5: "Probably cost us a full day's crew pay across both trips, maybe $1,200-1,500 in wasted labor, plus the headache of rescheduling the other job. Happens maybe once every four or five jobs — not every time, but often enough it's a real pattern."

Q6-7: "Tried one of those scheduling apps a GC wanted us to use two years back — never really stuck because half the GCs we work with don't use it, so we ended up tracking things two different ways. Mostly it's just texting the GC's site super directly now, and a paper calendar in the truck."

Q8-9: "Yeah, talk to [name], he runs a bigger drywall crew than me, deals with this even more. Sure, follow up whenever."

Adaptation Notes for GCs, Subs, and PMs

For GC-side project managers, adjust the recent-job walkthrough to focus on coordination across multiple subs rather than a single sub's own scheduling experience, and expect a somewhat longer, more structured conversation given this population's typically more office-based, desk-adjacent schedule compared to a sub's more field-driven day. For individual subcontractor owner-operators, keep the script as close to the template above as possible, and be prepared for shorter, more concrete answers — this population responds best to concrete, recent-job framing exactly as demonstrated in the filled example. For office-based safety managers or EHS staff, shift the money-leak questions toward liability and compliance framing specifically ("was there a moment this created real regulatory or liability exposure") rather than pure cost framing, since this population's real pain concentrates differently than a field-focused trade contractor's does.

A Closer Look: Why the Script Should Feel Like a Conversation, Not an Interrogation

A script written out on a page, followed too literally in a real interview, can come across as stiff or interrogation-like — reading questions verbatim in exact numbered order, without adapting to what the contractor is actually saying, tends to produce shorter, more guarded answers than a conversation that uses the script as a guide while genuinely following up on whatever the contractor's own answer opens up. If a contractor's answer to the recent-job walkthrough question naturally surfaces a money-leak detail before you've formally asked Section 2's questions, follow that thread directly rather than redirecting back to the script's original order — the goal is covering the same underlying ground the template maps out, not executing the questions in the exact printed sequence regardless of where the conversation naturally wants to go.

This distinction matters more with contractors specifically than with some other interview populations, since this population responds especially well to a conversation that feels genuine and specifically curious about their actual situation, and especially poorly to anything that feels like a checklist being read at them — a dynamic covered more generally in interviewing general contractors, where the shorter, more concrete conversational style this population brings rewards genuine, responsive listening over rigid script adherence. Practice running through this template a few times with early interviews specifically to build comfort holding its structure loosely in mind while still letting the conversation breathe naturally — the filled example above reads smoothly precisely because the founder let the drywall sub's own specific numbers and details drive the conversation's natural pacing, rather than mechanically working through each numbered question in isolation regardless of what had already been covered a moment earlier in the contractor's own prior answer.

Key Takeaways

• Anchor every conversation in a specific, recent, real job, not general or hypothetical questions about workflow challenges.
• Keep the script short and concrete. This population responds better to a focused ten-minute conversation than a lengthy, exploratory one.
• Always ask about past tools tried and abandoned. This context is frequently the most useful and most commonly skipped part of a contractor discovery interview.
• Always ask for a referral. It's the single highest-quality recruitment channel once your interview pipeline gets started.
• Adapt the money-leak framing to the specific stakeholder — cost and time for field-focused trades, liability and compliance for safety-focused roles.

Frequently Asked Questions

How long should I expect this interview to actually take?

Ten to twenty minutes for most field-based contractors, sometimes shorter for a brief on-site or supply-house exchange — expect considerably less time than a typical thirty-to-forty-five-minute desk-based professional discovery interview, and don't treat a shorter conversation as lower-quality signal, since the worked example above shows real, usable signal emerging from a genuinely brief, concrete exchange.

Can I use this same script for a phone or video call instead of in-person?

Yes, the questions themselves transfer directly to a phone or video format — the main adjustment is scheduling, since interviewing general contractors covers the flexible, off-hours scheduling this population typically requires regardless of whether the actual conversation happens in person or remotely.

What if a contractor gives vague, non-specific answers even with these questions?

If a specific-job-anchored question still produces a vague answer, gently redirect back to specifics — "can you think of one particular time that happened, even roughly when it was" — rather than accepting a general answer and moving on, since vague answers are usually a sign the question needs one more specific redirect rather than a signal that no real, concrete example exists; most contractors, once redirected toward a specific recent memory rather than a general pattern, can recall a concrete example, and that concrete example is considerably more valuable validation evidence than a general, abstract statement about their typical experience, precisely because a specific real event is harder to unconsciously exaggerate or minimize than a vague generalization tends to be, giving you more reliable signal to build product and pricing decisions on.

Should I record these interviews, or rely on notes taken during the conversation?

A brief voice recording, with the contractor's explicit permission asked up front, captures specific numbers and phrasing more reliably than in-the-moment notes alone, especially for a fast-moving, concrete conversation like the filled example above — but always ask permission explicitly before recording, and be prepared to proceed with notes only if a contractor prefers not to be recorded, since pushing on this point risks losing an otherwise willing and useful interview subject over a secondary process preference rather than the substance of the conversation itself.