We had only 300 responses, and said so loudly

We had only 300 responses, and said so loudly
Thin data usually means a dead campaign — or a dishonest one. The setup: a niche developer-tools client could only survey 300 engineers. Most teams would either pad it or quietly hope no one checked the sample size.
The angle was radical transparency. We led with the limitation: "A small but unusually specific sample — 300 senior engineers, here's exactly who they are." Specificity beat scale. A precise picture of a narrow group is more honest, and more interesting, than a vague picture of a vague crowd.
The pitch named the constraint upfront: "Small sample, but every respondent is a senior backend engineer at a company over 500 people — and the findings are pointed." Journalists trust a source that flags its own limits before they have to ask.
Result: 8 placements in serious tech outlets, 21 referring domains, and notably zero pushback in comments about methodology — because we'd disarmed it. Two writers specifically praised the honest framing in their pieces, which only added credibility.
A developer-publication editor said: "Refreshing to get a survey that tells me its weaknesses instead of hiding them."
Lesson: A small sample isn't fatal — pretending it's bigger than it is, is. Name the limitation, sharpen the specificity, and honest thinness beats inflated noise every time.