# Content Progression Does Not Create Consent for Sales Contact A developer choosing progressively more product-specific content signals interest in that content, not automatic permission for identity tracking or sales outreach. A developer-first funnel preserves trust only when every stage offers independent value and commercial contact requires a separate, explicit choice. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions This applies to DevRel, product marketing, demand-generation, and sales handoffs. It doesn't reject coordinated journeys; it separates content relevance from contact consent. ## Evidence > “By virtue of their click, the reader has bought into the idea that THIS blog (compared to the last one) is going to talk about a product, feature, or module.” The source presents voluntary progression as permission for product specificity. The boundary in this note is narrower: that click supports the next content context but doesn't, by itself, authorize tracking or human outreach. ## Links - [[3. Resources/Permanent Notes/DevRel Should Never Carry a Sales Quota]] — extends: preserving a separate consent boundary prevents DevRel education from becoming disguised quota work. - [[3. Resources/Permanent Notes/Education Is the Only Marketing That Works With Developers]] — applies-in: educational trust survives only when the lesson remains useful without conversion. - [[3. Resources/Permanent Notes/The Four Objectives Framework Replaces Vanity Metrics in DevRel]] — applies-in: engagement and revenue are separate outcomes and need separate measures. - [[3. Resources/MOCs/DevRel MOC]] — applies-in: the MOC lists this note under Synthesis additions (2026-08-11). ## Source - [[3. Resources/Readwise/Articles/A DevRel-Led Funnel That Puts Developers First]] — source framework and verbatim evidence.