Feel-Felt-Found Technique: Modern Examples by Industry

The classic structure still works: Feel (validate) → Felt (show they're not alone) → Found (show what was discovered). What's dated is the delivery — "I understand how you feel, others have felt the same way, and what they found was..." said in that sing-song script voice. Below is the same structure rebuilt as something a real person would actually say, with modern, industry-specific proof points.

The rule for all of these: replace "others" with a specific, credible peer reference whenever you can, and replace "found" with a mechanism, not a platitude.

---

SaaS & Technology

Common objection: "We already have a tool that does something similar."

"Makes sense — a lot of teams already have something in place. I worked with a RevOps lead at a similar-sized company last year who was in the exact same spot, running [category] through a tool they'd had for three years. What she found, once we dug into it together, was the tool covered maybe 60% of what her team actually needed day-to-day — the rest was happening in spreadsheets nobody wanted to admit to. That's usually the gap worth checking for before ruling this out."

Common objection: "Your pricing is higher than [competitor]."

"Fair — and price comparisons matter. A platform engineering lead I spoke with recently had the same reaction initially, went with the cheaper option, and came back to us eight months later because the lower sticker price didn't include the implementation support that ended up costing more in internal engineering time than the price difference. Worth factoring the total cost in, not just the license line."

---

Financial Services & Insurance

Common objection: "We're not comfortable changing providers mid-cycle."

"That's a completely reasonable instinct — a lot of finance teams feel that way about mid-cycle changes, especially given how much scrutiny switching gets internally. One CFO I worked with felt exactly that risk-aversion, and what her team found was structuring the transition to run parallel with the existing provider for one full cycle before cutting over meant zero disruption risk — and gave the board a clean before/after comparison to justify the switch."

Common objection: "Compliance will slow this down for months."

"Understood — compliance timelines are real, not a stalling tactic on your end. A compliance officer at a mid-size firm felt the same concern going in. What his team found was bringing compliance into the conversation in week one, rather than after the commercial terms were set, actually cut the review cycle roughly in half because there were no surprises late in the process."

---

Healthcare & MedTech

Common objection: "Clinical staff won't adopt another new system."

"That concern is well-earned — clinical teams are stretched thin and rightly protective of their time. A director of nursing I worked with felt exactly that resistance before rollout. What her hospital found was that adoption wasn't really about the system — it was about whether it added a step to an existing workflow or removed one. Once it was framed and configured as removing documentation time, adoption wasn't the fight she expected."

Common objection: "We need this to be airtight on compliance/HIPAA before we even consider it."

"That's the right instinct, and I'd be concerned if you weren't asking. A health system CIO felt the same non-negotiable requirement. What came out of that process was a joint security review with their compliance team before any pilot started, not after — which is the same approach I'd suggest here."

---

Manufacturing & Industrial

Common objection: "We can't afford downtime to implement something new."

"That's a real constraint, not an excuse — downtime on a production line has a hard cost attached. A plant operations manager felt exactly that risk before a rollout last year. What his team found was scheduling implementation across a planned maintenance window instead of a live shift meant zero unplanned downtime — the constraint didn't go away, it just got planned around."

Common objection: "Our team has been doing it this way for 20 years."

"That kind of institutional knowledge is genuinely valuable — I wouldn't want to dismiss two decades of what works. A production supervisor felt the same protectiveness of his team's process. What he found was the change wasn't about replacing the process, it was about removing the manual parts of it his team already complained about — the tenure and the improvement weren't actually in conflict."

---

Professional Services & Agencies

Common objection: "We've been burned by consultants before who overpromised."

"That's a fair scar to have, honestly — a lot of the market has earned that reputation. A COO I worked with felt that exact skepticism, having been through two consulting engagements that delivered a deck and not much else. What made the difference for her team was tying the engagement to a specific, measurable outcome upfront instead of a scope of hours — so success wasn't a matter of opinion at the end."

Common objection: "We don't have internal bandwidth to manage another vendor relationship."

"That's worth taking seriously — a vendor that creates more management overhead than it saves isn't worth it. An operations director felt that exact hesitation. What her team found was the engagement worked better with a single point of contact and a fixed weekly touchpoint, rather than the sprawling stakeholder management she'd dealt with before — bandwidth cost went down, not up."

---

Building Your Own — The Modern FFF Formula

1. Feel: Name the specific concern in one sentence, with genuine respect (not "I understand," which reads as scripted — instead, "that's a reasonable/fair/well-earned concern").
2. Felt: Reference one specific, credible peer (role + situation, not "many customers") who had that exact concern.
3. Found: Name the actual mechanism or structural change that resolved it — never end on a vague "it worked out great."
4. Always end with a check-back question, not a statement: "Does that address the concern, or is there a piece I'm missing?"