# DevRel Should Never Carry a Sales Quota The moment a Developer Relations team carries a lead generation quota, it stops being Developer Relations and becomes sales with a conference badge. The primary goal of DevRel is not lead generation. It's building trust, providing education, and creating genuine relationships with a technical community. These goals are incompatible with quota pressure. The reason is structural, not ideological. Developers detect sales intent faster than any other audience. A DevRel professional who needs to generate 50 leads from a conference will make different choices than one who needs to help 50 developers succeed. The first optimizes for badge scans and follow-up emails. The second optimizes for real conversations and useful answers. Developers can feel the difference in the first thirty seconds. This doesn't mean DevRel has no business value -- it means the value is indirect. DevRel sits at both the top and bottom of the funnel: brand awareness at entry, developer satisfaction at retention. Measuring it requires metrics like community growth, documentation quality, time-to-first-success, and developer satisfaction scores. These are harder to track than lead counts, which is why organizations under pressure default to quotas. But the shortcut destroys the thing it's trying to measure. The measurement paradox is real: DevRel's ROI is genuinely hard to quantify, which makes teams perpetually vulnerable to budget cuts. But solving that problem by attaching sales metrics doesn't measure DevRel -- it kills it. <!-- atomicity: 1 idea ✓ --> ## Why This Matters This is a structural argument, not a preference. Organizations that put quotas on DevRel teams don't get "DevRel that also sells." They get sales teams that burned their community's trust. The damage compounds because trust, once lost with developers, rarely returns. ## Links - [[3. Resources/Permanent Notes/Education Is the Only Marketing That Works With Developers]] — evidence-for: developer trust grows through useful teaching, while quota pressure turns education into a disguised conversion tactic. - [[3. Resources/Permanent Notes/DevRel Burnout Is Structural Not Personal]] — evidence-for: assigning a short-term sales target to long-horizon relational work creates incompatible demands at the role level. - [[3. Resources/Permanent Notes/DevRel as Railroad Infrastructure]] — contrasts: connective infrastructure supports the whole developer journey but should not inherit the sales department's closing target - [[3. Resources/Literature Notes/The Developer Journey - Awareness to Advocacy - Literature Note]] — applies-in: advocacy emerges from a long trust journey rather than a quota-driven lead handoff - [[3. Resources/Permanent Notes/DevRel Programs Take Three to Five Years to Show Results]] — contrasts: a short sales quota mismeasures relationship and adoption work whose business effects develop over several years - [[3. Resources/Permanent Notes/The Four Objectives Framework Replaces Vanity Metrics in DevRel]] — extends: explicit awareness, activation, engagement, and retention objectives measure DevRel without assigning it a closing quota. - [[3. Resources/MOCs/DevRel MOC]] — applies-in: the MOC lists this note under Should DevRel carry revenue responsibility?. ## Source - [[3. Resources/Literature Notes/The Developer Journey - Awareness to Advocacy - Literature Note]] - [[3. Resources/Readwise/Books/The Business Value of Developer Relations]] - [[3. Resources/Readwise/Books/Developer, Advocate!|Developer, Advocate!]]