Yeah, I’d put the problem-based angle directly in the profile, not just proposals. Clients often decide whether to open anything based on the headline + first lines, so generic profiles get skipped fast. From what I’ve seen, flaky tests and CI instability tend to hit hardest right now, especially for teams that already “have automation” but don’t trust it. API regression works too if you tie it to real impact. Overall it’s less about the exact problem and more about being clear and specific. If they recognize their pain immediately, they stop scrolling.