Why Business Literacy Matters for DevRel
🔗 **Source:** [Why Business Literacy Matters for DevRel](https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1)
> [!note]+ Document Notes
> tags: [DevRel, Business, Metrics]
> author: Matty Stratton
> source: dev.to
> reference: [https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1]
> date created:
>
> # 🏷️ Title: Why Business Literacy Matters for DevRel (And Why You Can't Skip This Step)
>
<!-- deep-read:sections start -->
## 🧭 Table of Contents
- [📝 Summary](#-summary)
- [📖 Main Content](#-main-content)
- [🗒️ Notes](#️-notes)
- [📚 References](#-references)
- [🗣️ Paraphrase](#️-paraphrase)
- [📰 Newsletter](#-newsletter)
- [✅ Action Items](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future Research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning Styles Assessment](#-learning-styles-assessment)
- [📊 Accessibility Assessment](#-accessibility-assessment)
- [🌍 DEIB Assessment](#-deib-assessment)
- [✅ Logical Validity](#-logical-validity)
- [🛡️ DARVO Analysis](#-darvo-analysis)
- [🎯 Conclusion](#-conclusion)
### 🔗 References
- Include links cited in or relevant to the article.
## 📝 Summary
- What happened: The author argues DevRel struggles not because “the business doesn’t get DevRel,” but because DevRel lacks business literacy.
- Why it matters: Budget survival and strategic influence require fluency in sales, marketing, and finance to translate DevRel impact.
- Key stakeholders: DevRel teams/leaders, Sales, Marketing, Finance, executives.
- Risks and tradeoffs: Over-indexing on vanity metrics; perceived “selling out”; under-communicated impact leading to cuts.
- Bottom line: Become bilingual—map DevRel work to commercial outcomes to advocate, align, and survive.
## 📖 Main Content
- Core argument: DevRel must “speak business” to show value; impressions and community growth don’t answer ARR, pipeline, or cost-per-lead questions.
- Context/definitions:
- ARR: recurring revenue; a core financial metric.
- CapEx vs OpEx: capitalized vs operational expenses; matters to finance planning.
- Funnel stages: awareness → consideration → conversion; marketing’s model for attribution.
- Product-Led Growth: product usage drives acquisition/expansion; complements DevRel’s developer-first motion.
- Uncertainties: Exact KPI frameworks and attribution details deferred to future posts; this piece focuses on foundations, not metrics.
### 🗒️ Notes
- “The problem is that DevRel doesn't understand business.”
- Disconnect: DevRel cites impressions/Discord growth; leadership asks about ARR, CPL, sourced pipeline.
- “You can't effectively measure and demonstrate your value if you don't understand the fundamentals of how the business actually works.”
- Goal: “Becoming bilingual” to converse with Sales (pipeline), Finance (budgets, P&L), Marketing (funnel).
- Series scope: Sales 101, Marketing 101, Finance 101, plus PLG as a complement.
- Payoff: Better advocacy, alignment, survival during cuts, and partnerships.
- “The best part about ‘selling out’? You get paid.”
## 📚 References
- Annual Recurring Revenue (ARR) overview (https://www.investopedia.com/terms/a/annual-recurring-revenue.asp)
- CapEx vs. OpEx explained (https://www.investopedia.com/ask/answers/020915/what-difference-between-capital-expenditures-capex-and-operating-expenses-opex.asp)
- Marketing funnel stages (https://www.shopify.com/blog/marketing-funnel)
- Product-Led Growth primer (https://www.productled.org/blog/what-is-product-led-growth)
- Developer Relations overview (https://en.wikipedia.org/wiki/Developer_relations)
## 🗣️ Paraphrase
- Paragraph A: The issue isn’t that companies fail to grasp DevRel; DevRel often fails to translate its work into business terms that budget owners use.
- Paragraph B: Vanity metrics create a language gap; leaders want ARR, pipeline, and costs, not impressions or community size.
## 📰 Newsletter
- DevRel teams are under pressure to prove value. This piece argues the fix is business literacy: map advocacy, content, and community to pipeline, ARR, and funnel stages. Coming next: Sales, Marketing, and Finance 101 for DevRel, plus PLG fit. Brush up on ARR and CapEx/OpEx, then audit your dashboard to swap vanity metrics for revenue-adjacent signals.
## ✅ Action Items
#### DevRel
- Define influence/sourced pipeline from events, content, and demos; document deal acceleration anecdotes.
- Build education tracks tied to product activation and expansion.
- Ship examples/SDKs mapped to key use cases and revenue segments.
- Create top/mid/bottom-funnel content with UTMs; align on attribution rules.
- Run community surveys tied to activation, retention, and expansion.
- Establish quarterly reviews with Sales/Marketing/Finance; publish feedback loops.
#### OSPO
- Clarify contribution charters and decision rights that support go-to-market.
- Automate license scanning and set review SLAs.
- Maintain vuln intake and embargo playbooks; sign releases.
- Track SBOM freshness and ownership.
- Offer contributor legal guardrails and office hours.
- Fund critical upstreams; sign MoUs with key projects.
- Report OSS impact in executive scorecards.
#### Community
- Host roadmap clinics; publish governance templates.
- Create contributor onboarding paths and pairing rotations.
- Share sponsor budgets and milestone-based reports.
- Practice cross-project incident drills and disclosure norms.
#### WordPress
- Core: triage, performance budgets, release criteria.
- Core Performance: dashboards and perf bounties.
- Core AI: responsible guardrails and eval sets.
- Core Program Team: rituals, dependencies, retros.
- Mobile: telemetry and offline UX improvements.
- Playground: browser labs and reproducible bugs.
- Community/Training/Marketing/Support/Design/Docs: fill gaps with examples-first patterns, editorial calendars, and SLAs.
- Accessibility/Meta/CLI/Hosting/Tide/Openverse/Themes/Plugins: audits, scoring transparency, review throughput, provenance checks.
#### The WPOCC
- Programs: fellowships, microgrants, stipends.
- Projects: governance clinics, doc sprints.
- Funding experiments: matched grants and milestone payouts.
### FAIR
- Independence: local metadata and signature checks.
- Policies: transparent funding, sunset clauses.
- Governance artifacts: charters and scorecards.
## 🧪 Hypotheses
- H1: Teaching DevRel basic sales/marketing/finance increases budget approval rates within two quarters.
- H2: Translating activities to pipeline/ARR reduces DevRel layoffs during downturns.
- H3: PLG+DevRel orgs see higher activation-to-paid conversion than marketing-led-only orgs.
- H4: Executive satisfaction with DevRel rises when reports swap vanity metrics for revenue-adjacent metrics.
### 📊 Methodology
- Pre/post training quasi-experiment across teams; measure budget approvals, headcount stability, exec NPS.
- Compare conversion and activation in PLG+DevRel cohorts vs controls.
- Content and event attribution via UTMs, assisted conversion windows, and pipeline stage tagging.
### ❓ Questions
- Which revenue-adjacent metrics best capture DevRel’s deal acceleration?
- How should Finance model DevRel as OpEx with long-tail impact?
- What PLG motions amplify community-led adoption?
### 🔮 Future Research
- Longitudinal studies on DevRel’s retention and expansion impact.
- Standardized attribution models for community touchpoints.
### 💡 Implications
- Practice: Adopt bilingual reporting (developer + business).
- Policy: Tie budgets to strategic objectives and measurable outcomes.
- Security: Include disclosure and signing in DevRel demos/docs.
- Education: Core business literacy in DevRel onboarding.
- Funding: Protect programs with clear revenue linkages.
### 🧠 Learning Styles Assessment
- Reading level: Flesch-Kincaid Grade ~8–9 (estimate).
#### 👀 Visual learners
- Present: Lists; clear structure.
- Improve: Pipeline/funnel/ARR mapping diagrams.
#### 🔊 Aural learners
- Present: N/A.
- Improve: 3–5 minute audio summary.
#### 🗣️ Verbal learners
- Present: Analogies (language/bilingual).
- Improve: Glossary of business terms.
#### 🧩 Kinesthetic learners
- Present: N/A.
- Improve: Build-a-report exercises with sample data.
#### 🧠 Logical learners
- Present: Stepwise argument.
- Improve: Causal diagrams and KPI trees.
#### 🧑🤝🧑 Social learners
- Present: Collaboration emphasis.
- Improve: Peer review of exec-ready reports.
#### 🧘♀️ Solitary learners
- Present: Introspective prompts implied.
- Improve: Self-assessment checklists.
#### 🌿 Naturalistic learners
- Present: N/A.
- Improve: Ecosystem health analogies for community metrics.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: Headings.
- Improve: Alt text and landmarks.
#### Keyboard navigation
- Present: Likely standard web patterns.
- Improve: Focus states and skip links.
#### Contrast and readability
- Present: Generally adequate on dev.to.
- Improve: Verify 4.5:1 and line-height.
#### Text resizing and reflow
- Present: Responsive.
- Improve: Test at 200% with no clipping.
#### Media and captions
- Present: Text-only.
- Improve: Offer audio/TTS.
#### Forms and interactions
- Present: N/A.
- Improve: Accessible toasts and targets.
#### Standards reference
- Map to WCAG 2.2 AA: 1.4.x, 2.4.x, 3.3.x.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: Generalized audience.
- Improve: Global case studies.
#### Inclusive language
- Present: Clear, direct.
- Improve: Glossary and plain-language callouts.
#### Neurodiversity support
- Present: Chunked sections.
- Improve: Consistent icon+text labels.
#### Representation
- Present: Role-diverse stakeholders.
- Improve: Inclusive imagery with alt text.
#### Psychological safety
- Present: Respectful tough-love tone.
- Improve: Community guidelines link.
### ✅ Logical Validity
#### Strong reasoning
- Analogical: “Learn some French” clarifies stakeholder-language mismatch; strengthens the case to learn business terms.
- Causal: Business literacy → better advocacy/alignment → budget survival; plausible chain.
#### Fallacies
- Potential hasty generalization: Layoffs attributed mainly to poor translation; mitigate by noting macro factors and mixed methods evidence.
#### Tone of voice
- Direct, coaching, “tough love,” pragmatic.
### 🛡️ DARVO Analysis
- Deny: None; acknowledges tensions.
- Attack: None; critiques practice, not people.
- Reverse victim/offender: None; reframes responsibility without blame.
## 🎯 Conclusion
- Bottom line: DevRel needs business literacy to translate impact into ARR, pipeline, and budget terms—become bilingual to endure and thrive.
- Next steps: Build a shared glossary, align with Sales/Marketing/Finance on definitions and reporting, pilot PLG-aligned DevRel programs, and replace vanity metrics with revenue-adjacent measures.
## 🧱 Refactor Appendix (append after 🎯 Conclusion)
### 📚 Literature Split Pad
- Purpose: Stage Konik CEE units that become per-source Literature notes.
- Split level: H3.
- Include verbatim quotes under 25 words and a [view highlight] link.
### [H1] DevRel requires business literacy
> [!quote] Why Business Literacy Matters for DevRel by [[Matty Stratton]] via [[dev.to]]. Published 2025-10-27. Accessed .
> “You can't effectively measure…if you don't understand the fundamentals of how the business actually works.”
Two lines: Use to justify training. Track pre/post budget outcomes.
[view highlight](https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] Translate DevRel to ARR and pipeline
> [!quote] Why Business Literacy Matters for DevRel
> “How does this impact our ARR? … How much pipeline did DevRel source last quarter?”
Two lines: Build shared metric definitions with Finance/Sales.
[view highlight](https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1#H2) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
- Purpose: Promote reusable claims into Atomic notes.
- Split level: H4.
- Each item: one idea, present tense, specific, testable.
#### [Z1] Business fluency increases DevRel budget wins
- Scope: Teams post-foundation training; track next two quarters.
- Pointer: Exec approval logs.
- Links: [[DevRel]] [[Budgeting]]
#### [Z2] PLG complements DevRel motions
- Scope: Self-serve product; activation metrics.
- Pointer: Funnel dashboards.
- Links: [[PLG]] [[Developer-Marketing]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- Purpose: Capture quick actions or sparks for Fleeting notes.
- Extraction: Select one line → “Refactor: Extract selection to new note (content only).”
- Keep each line short and self-contained.
- [F1] Draft shared glossary: ARR, CPL, sourced vs influenced pipeline — context/https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1 #fleeting #inbox
- [F2] Build DevRel → funnel mapping dashboard — context/https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1 #fleeting #inbox
- [F3] Schedule Sales/Finance office hours for DevRel — context/https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1 #fleeting #inbox
---
# 🏷️ Title: Why Business Literacy Matters for DevRel (And Why You Can't Skip This Step)
## 🧭 Table of Contents
- [📝 Summary](#-summary)
- [📖 Main Content](#-main-content)
- [🗒️ Notes](#️-notes)
- [📚 References](#-references)
- [🗣️ Paraphrase](#️-paraphrase)
- [📰 Newsletter](#-newsletter)
- [✅ Action Items](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future Research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning Styles Assessment](#-learning-styles-assessment)
- [📊 Accessibility Assessment](#-accessibility-assessment)
- [🌍 DEIB Assessment](#-deib-assessment)
- [✅ Logical Validity](#-logical-validity)
- [🛡️ DARVO Analysis](#-darvo-analysis)
- [🎯 Conclusion](#-conclusion)
### 🔗 References
- Include links cited in or relevant to the article.
## 📝 Summary
- What happened: The author argues DevRel struggles not because “the business doesn’t get DevRel,” but because DevRel lacks business literacy.
- Why it matters: Budget survival and strategic influence require fluency in sales, marketing, and finance to translate DevRel impact.
- Key stakeholders: DevRel teams/leaders, Sales, Marketing, Finance, executives.
- Risks and tradeoffs: Over-indexing on vanity metrics; perceived “selling out”; under-communicated impact leading to cuts.
- Bottom line: Become bilingual—map DevRel work to commercial outcomes to advocate, align, and survive.
## 📖 Main Content
- Core argument: DevRel must “speak business” to show value; impressions and community growth don’t answer ARR, pipeline, or cost-per-lead questions.
- Context/definitions:
- ARR: recurring revenue; a core financial metric.
- CapEx vs OpEx: capitalized vs operational expenses; matters to finance planning.
- Funnel stages: awareness → consideration → conversion; marketing’s model for attribution.
- Product-Led Growth: product usage drives acquisition/expansion; complements DevRel’s developer-first motion.
- Uncertainties: Exact KPI frameworks and attribution details deferred to future posts; this piece focuses on foundations, not metrics.
### 🗒️ Notes
- “The problem is that DevRel doesn't understand business.”
- Disconnect: DevRel cites impressions/Discord growth; leadership asks about ARR, CPL, sourced pipeline.
- “You can't effectively measure and demonstrate your value if you don't understand the fundamentals of how the business actually works.”
- Goal: “Becoming bilingual” to converse with Sales (pipeline), Finance (budgets, P&L), Marketing (funnel).
- Series scope: Sales 101, Marketing 101, Finance 101, plus PLG as a complement.
- Payoff: Better advocacy, alignment, survival during cuts, and partnerships.
- “The best part about ‘selling out’? You get paid.”
## 📚 References
- Annual Recurring Revenue (ARR) overview (https://www.investopedia.com/terms/a/annual-recurring-revenue.asp)
- CapEx vs. OpEx explained (https://www.investopedia.com/ask/answers/020915/what-difference-between-capital-expenditures-capex-and-operating-expenses-opex.asp)
- Marketing funnel stages (https://www.shopify.com/blog/marketing-funnel)
- Product-Led Growth primer (https://www.productled.org/blog/what-is-product-led-growth)
- Developer Relations overview (https://en.wikipedia.org/wiki/Developer_relations)
## 🗣️ Paraphrase
- Paragraph A: The issue isn’t that companies fail to grasp DevRel; DevRel often fails to translate its work into business terms that budget owners use.
- Paragraph B: Vanity metrics create a language gap; leaders want ARR, pipeline, and costs, not impressions or community size.
## 📰 Newsletter
- DevRel teams are under pressure to prove value. This piece argues the fix is business literacy: map advocacy, content, and community to pipeline, ARR, and funnel stages. Coming next: Sales, Marketing, and Finance 101 for DevRel, plus PLG fit. Brush up on ARR and CapEx/OpEx, then audit your dashboard to swap vanity metrics for revenue-adjacent signals.
## ✅ Action Items
#### DevRel
- Define influence/sourced pipeline from events, content, and demos; document deal acceleration anecdotes.
- Build education tracks tied to product activation and expansion.
- Ship examples/SDKs mapped to key use cases and revenue segments.
- Create top/mid/bottom-funnel content with UTMs; align on attribution rules.
- Run community surveys tied to activation, retention, and expansion.
- Establish quarterly reviews with Sales/Marketing/Finance; publish feedback loops.
#### OSPO
- Clarify contribution charters and decision rights that support go-to-market.
- Automate license scanning and set review SLAs.
- Maintain vuln intake and embargo playbooks; sign releases.
- Track SBOM freshness and ownership.
- Offer contributor legal guardrails and office hours.
- Fund critical upstreams; sign MoUs with key projects.
- Report OSS impact in executive scorecards.
#### Community
- Host roadmap clinics; publish governance templates.
- Create contributor onboarding paths and pairing rotations.
- Share sponsor budgets and milestone-based reports.
- Practice cross-project incident drills and disclosure norms.
#### WordPress
- Core: triage, performance budgets, release criteria.
- Core Performance: dashboards and perf bounties.
- Core AI: responsible guardrails and eval sets.
- Core Program Team: rituals, dependencies, retros.
- Mobile: telemetry and offline UX improvements.
- Playground: browser labs and reproducible bugs.
- Community/Training/Marketing/Support/Design/Docs: fill gaps with examples-first patterns, editorial calendars, and SLAs.
- Accessibility/Meta/CLI/Hosting/Tide/Openverse/Themes/Plugins: audits, scoring transparency, review throughput, provenance checks.
#### The WPOCC
- Programs: fellowships, microgrants, stipends.
- Projects: governance clinics, doc sprints.
- Funding experiments: matched grants and milestone payouts.
### FAIR
- Independence: local metadata and signature checks.
- Policies: transparent funding, sunset clauses.
- Governance artifacts: charters and scorecards.
## 🧪 Hypotheses
- H1: Teaching DevRel basic sales/marketing/finance increases budget approval rates within two quarters.
- H2: Translating activities to pipeline/ARR reduces DevRel layoffs during downturns.
- H3: PLG+DevRel orgs see higher activation-to-paid conversion than marketing-led-only orgs.
- H4: Executive satisfaction with DevRel rises when reports swap vanity metrics for revenue-adjacent metrics.
### 📊 Methodology
- Pre/post training quasi-experiment across teams; measure budget approvals, headcount stability, exec NPS.
- Compare conversion and activation in PLG+DevRel cohorts vs controls.
- Content and event attribution via UTMs, assisted conversion windows, and pipeline stage tagging.
### ❓ Questions
- Which revenue-adjacent metrics best capture DevRel’s deal acceleration?
- How should Finance model DevRel as OpEx with long-tail impact?
- What PLG motions amplify community-led adoption?
### 🔮 Future Research
- Longitudinal studies on DevRel’s retention and expansion impact.
- Standardized attribution models for community touchpoints.
### 💡 Implications
- Practice: Adopt bilingual reporting (developer + business).
- Policy: Tie budgets to strategic objectives and measurable outcomes.
- Security: Include disclosure and signing in DevRel demos/docs.
- Education: Core business literacy in DevRel onboarding.
- Funding: Protect programs with clear revenue linkages.
### 🧠 Learning Styles Assessment
- Reading level: Flesch-Kincaid Grade ~8–9 (estimate).
#### 👀 Visual learners
- Present: Lists; clear structure.
- Improve: Pipeline/funnel/ARR mapping diagrams.
#### 🔊 Aural learners
- Present: N/A.
- Improve: 3–5 minute audio summary.
#### 🗣️ Verbal learners
- Present: Analogies (language/bilingual).
- Improve: Glossary of business terms.
#### 🧩 Kinesthetic learners
- Present: N/A.
- Improve: Build-a-report exercises with sample data.
#### 🧠 Logical learners
- Present: Stepwise argument.
- Improve: Causal diagrams and KPI trees.
#### 🧑🤝🧑 Social learners
- Present: Collaboration emphasis.
- Improve: Peer review of exec-ready reports.
#### 🧘♀️ Solitary learners
- Present: Introspective prompts implied.
- Improve: Self-assessment checklists.
#### 🌿 Naturalistic learners
- Present: N/A.
- Improve: Ecosystem health analogies for community metrics.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: Headings.
- Improve: Alt text and landmarks.
#### Keyboard navigation
- Present: Likely standard web patterns.
- Improve: Focus states and skip links.
#### Contrast and readability
- Present: Generally adequate on dev.to.
- Improve: Verify 4.5:1 and line-height.
#### Text resizing and reflow
- Present: Responsive.
- Improve: Test at 200% with no clipping.
#### Media and captions
- Present: Text-only.
- Improve: Offer audio/TTS.
#### Forms and interactions
- Present: N/A.
- Improve: Accessible toasts and targets.
#### Standards reference
- Map to WCAG 2.2 AA: 1.4.x, 2.4.x, 3.3.x.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: Generalized audience.
- Improve: Global case studies.
#### Inclusive language
- Present: Clear, direct.
- Improve: Glossary and plain-language callouts.
#### Neurodiversity support
- Present: Chunked sections.
- Improve: Consistent icon+text labels.
#### Representation
- Present: Role-diverse stakeholders.
- Improve: Inclusive imagery with alt text.
#### Psychological safety
- Present: Respectful tough-love tone.
- Improve: Community guidelines link.
### ✅ Logical Validity
#### Strong reasoning
- Analogical: “Learn some French” clarifies stakeholder-language mismatch; strengthens the case to learn business terms.
- Causal: Business literacy → better advocacy/alignment → budget survival; plausible chain.
#### Fallacies
- Potential hasty generalization: Layoffs attributed mainly to poor translation; mitigate by noting macro factors and mixed methods evidence.
#### Tone of voice
- Direct, coaching, “tough love,” pragmatic.
### 🛡️ DARVO Analysis
- Deny: None; acknowledges tensions.
- Attack: None; critiques practice, not people.
- Reverse victim/offender: None; reframes responsibility without blame.
## 🎯 Conclusion
- Bottom line: DevRel needs business literacy to translate impact into ARR, pipeline, and budget terms—become bilingual to endure and thrive.
- Next steps: Build a shared glossary, align with Sales/Marketing/Finance on definitions and reporting, pilot PLG-aligned DevRel programs, and replace vanity metrics with revenue-adjacent measures.
## 🧱 Refactor Appendix (append after 🎯 Conclusion)
### 📚 Literature Split Pad
- Purpose: Stage Konik CEE units that become per-source Literature notes.
- Split level: H3.
- Include verbatim quotes under 25 words and a [view highlight] link.
### [H1] DevRel requires business literacy
> [!quote] Why Business Literacy Matters for DevRel by [[Matty Stratton]] via [[dev.to]]. Published 2025-10-27. Accessed {{date:YYYY-MM-DD}}.
> “You can't effectively measure…if you don't understand the fundamentals of how the business actually works.”
Two lines: Use to justify training. Track pre/post budget outcomes.
[view highlight](https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] Translate DevRel to ARR and pipeline
> [!quote] Why Business Literacy Matters for DevRel
> “How does this impact our ARR? … How much pipeline did DevRel source last quarter?”
Two lines: Build shared metric definitions with Finance/Sales.
[view highlight](https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1#H2) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
- Purpose: Promote reusable claims into Atomic notes.
- Split level: H4.
- Each item: one idea, present tense, specific, testable.
#### [Z1] Business fluency increases DevRel budget wins
- Scope: Teams post-foundation training; track next two quarters.
- Pointer: Exec approval logs.
- Links: [[DevRel]] [[Budgeting]]
#### [Z2] PLG complements DevRel motions
- Scope: Self-serve product; activation metrics.
- Pointer: Funnel dashboards.
- Links: [[PLG]] [[Developer-Marketing]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- Purpose: Capture quick actions or sparks for Fleeting notes.
- Extraction: Select one line → “Refactor: Extract selection to new note (content only).”
- Keep each line short and self-contained.
- [F1] Draft shared glossary: ARR, CPL, sourced vs influenced pipeline — context/https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1 #fleeting #inbox
- [F2] Build DevRel → funnel mapping dashboard — context/https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1 #fleeting #inbox
- [F3] Schedule Sales/Finance office hours for DevRel — context/https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1 #fleeting #inbox
---
<!-- deep-read:sections end -->
[[3. Resources/Readwise/Full Document Contents/Articles/Why Business Literacy Matters for DevRel|Full Document Contents]]
## Document Notes
---
tags: #DevRel #Business #Metrics
author: Matty Stratton
source: dev.to
reference: [https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1]
date created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
---
# 🏷️ Title: Why Business Literacy Matters for DevRel (And Why You Can't Skip This Step)
## 🧭 Table of Contents
- [[#📝 Summary]]
- [[#📖 Main Content]]
- [[#🗒️ Notes]]
- [[#📚 References]]
- [[#🗣️ Paraphrase]]
- [[#📰 Newsletter]]
- [[#✅ Action Items]]
- [[#🧪 Hypotheses]]
- [[#📊 Methodology]]
- [[#❓ Questions]]
- [[#🔮 Future Research]]
- [[#💡 Implications]]
- [[#🧠 Learning Styles Assessment]]
- [[#📊 Accessibility Assessment]]
- [[#🌍 DEIB Assessment]]
- [[#✅ Logical Validity]]
- [[#🛡️ DARVO Analysis]]
- [[#🎯 Conclusion]]
### 🔗 References
- Include links cited in or relevant to the article.
## 📝 Summary
- What happened: The author argues DevRel struggles not because “the business doesn’t get DevRel,” but because DevRel lacks business literacy.
- Why it matters: Budget survival and strategic influence require fluency in sales, marketing, and finance to translate DevRel impact.
- Key stakeholders: DevRel teams/leaders, Sales, Marketing, Finance, executives.
- Risks and tradeoffs: Over-indexing on vanity metrics; perceived “selling out”; under-communicated impact leading to cuts.
- Bottom line: Become bilingual—map DevRel work to commercial outcomes to advocate, align, and survive.
## 📖 Main Content
- Core argument: DevRel must “speak business” to show value; impressions and community growth don’t answer ARR, pipeline, or cost-per-lead questions.
- Context/definitions:
- ARR: recurring revenue; a core financial metric.
- CapEx vs OpEx: capitalized vs operational expenses; matters to finance planning.
- Funnel stages: awareness → consideration → conversion; marketing’s model for attribution.
- Product-Led Growth: product usage drives acquisition/expansion; complements DevRel’s developer-first motion.
- Uncertainties: Exact KPI frameworks and attribution details deferred to future posts; this piece focuses on foundations, not metrics.
### 🗒️ Notes
- “The problem is that DevRel doesn't understand business.”
- Disconnect: DevRel cites impressions/Discord growth; leadership asks about ARR, CPL, sourced pipeline.
- “You can't effectively measure and demonstrate your value if you don't understand the fundamentals of how the business actually works.”
- Goal: “Becoming bilingual” to converse with Sales (pipeline), Finance (budgets, P&L), Marketing (funnel).
- Series scope: Sales 101, Marketing 101, Finance 101, plus PLG as a complement.
- Payoff: Better advocacy, alignment, survival during cuts, and partnerships.
- “The best part about ‘selling out’? You get paid.”
## 📚 References
- Annual Recurring Revenue (ARR) overview (https://www.investopedia.com/terms/a/annual-recurring-revenue.asp)
- CapEx vs. OpEx explained (https://www.investopedia.com/ask/answers/020915/what-difference-between-capital-expenditures-capex-and-operating-expenses-opex.asp)
- Marketing funnel stages (https://www.shopify.com/blog/marketing-funnel)
- Product-Led Growth primer (https://www.productled.org/blog/what-is-product-led-growth)
- Developer Relations overview (https://en.wikipedia.org/wiki/Developer_relations)
## 🗣️ Paraphrase
- Paragraph A: The issue isn’t that companies fail to grasp DevRel; DevRel often fails to translate its work into business terms that budget owners use.
- Paragraph B: Vanity metrics create a language gap; leaders want ARR, pipeline, and costs, not impressions or community size.
## 📰 Newsletter
- DevRel teams are under pressure to prove value. This piece argues the fix is business literacy: map advocacy, content, and community to pipeline, ARR, and funnel stages. Coming next: Sales, Marketing, and Finance 101 for DevRel, plus PLG fit. Brush up on ARR and CapEx/OpEx, then audit your dashboard to swap vanity metrics for revenue-adjacent signals.
## ✅ Action Items
#### DevRel
- Define influence/sourced pipeline from events, content, and demos; document deal acceleration anecdotes.
- Build education tracks tied to product activation and expansion.
- Ship examples/SDKs mapped to key use cases and revenue segments.
- Create top/mid/bottom-funnel content with UTMs; align on attribution rules.
- Run community surveys tied to activation, retention, and expansion.
- Establish quarterly reviews with Sales/Marketing/Finance; publish feedback loops.
#### OSPO
- Clarify contribution charters and decision rights that support go-to-market.
- Automate license scanning and set review SLAs.
- Maintain vuln intake and embargo playbooks; sign releases.
- Track SBOM freshness and ownership.
- Offer contributor legal guardrails and office hours.
- Fund critical upstreams; sign MoUs with key projects.
- Report OSS impact in executive scorecards.
#### Community
- Host roadmap clinics; publish governance templates.
- Create contributor onboarding paths and pairing rotations.
- Share sponsor budgets and milestone-based reports.
- Practice cross-project incident drills and disclosure norms.
#### WordPress
- Core: triage, performance budgets, release criteria.
- Core Performance: dashboards and perf bounties.
- Core AI: responsible guardrails and eval sets.
- Core Program Team: rituals, dependencies, retros.
- Mobile: telemetry and offline UX improvements.
- Playground: browser labs and reproducible bugs.
- Community/Training/Marketing/Support/Design/Docs: fill gaps with examples-first patterns, editorial calendars, and SLAs.
- Accessibility/Meta/CLI/Hosting/Tide/Openverse/Themes/Plugins: audits, scoring transparency, review throughput, provenance checks.
#### The WPCC
- Programs: fellowships, microgrants, stipends.
- Projects: governance clinics, doc sprints.
- Funding experiments: matched grants and milestone payouts.
### FAIR
- Independence: local metadata and signature checks.
- Policies: transparent funding, sunset clauses.
- Governance artifacts: charters and scorecards.
## 🧪 Hypotheses
- H1: Teaching DevRel basic sales/marketing/finance increases budget approval rates within two quarters.
- H2: Translating activities to pipeline/ARR reduces DevRel layoffs during downturns.
- H3: PLG+DevRel orgs see higher activation-to-paid conversion than marketing-led-only orgs.
- H4: Executive satisfaction with DevRel rises when reports swap vanity metrics for revenue-adjacent metrics.
### 📊 Methodology
- Pre/post training quasi-experiment across teams; measure budget approvals, headcount stability, exec NPS.
- Compare conversion and activation in PLG+DevRel cohorts vs controls.
- Content and event attribution via UTMs, assisted conversion windows, and pipeline stage tagging.
### ❓ Questions
- Which revenue-adjacent metrics best capture DevRel’s deal acceleration?
- How should Finance model DevRel as OpEx with long-tail impact?
- What PLG motions amplify community-led adoption?
### 🔮 Future Research
- Longitudinal studies on DevRel’s retention and expansion impact.
- Standardized attribution models for community touchpoints.
### 💡 Implications
- Practice: Adopt bilingual reporting (developer + business).
- Policy: Tie budgets to strategic objectives and measurable outcomes.
- Security: Include disclosure and signing in DevRel demos/docs.
- Education: Core business literacy in DevRel onboarding.
- Funding: Protect programs with clear revenue linkages.
### 🧠 Learning Styles Assessment
- Reading level: Flesch-Kincaid Grade ~8–9 (estimate).
#### 👀 Visual learners
- Present: Lists; clear structure.
- Improve: Pipeline/funnel/ARR mapping diagrams.
#### 🔊 Aural learners
- Present: N/A.
- Improve: 3–5 minute audio summary.
#### 🗣️ Verbal learners
- Present: Analogies (language/bilingual).
- Improve: Glossary of business terms.
#### 🧩 Kinesthetic learners
- Present: N/A.
- Improve: Build-a-report exercises with sample data.
#### 🧠 Logical learners
- Present: Stepwise argument.
- Improve: Causal diagrams and KPI trees.
#### 🧑🤝🧑 Social learners
- Present: Collaboration emphasis.
- Improve: Peer review of exec-ready reports.
#### 🧘♀️ Solitary learners
- Present: Introspective prompts implied.
- Improve: Self-assessment checklists.
#### 🌿 Naturalistic learners
- Present: N/A.
- Improve: Ecosystem health analogies for community metrics.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: Headings.
- Improve: Alt text and landmarks.
#### Keyboard navigation
- Present: Likely standard web patterns.
- Improve: Focus states and skip links.
#### Contrast and readability
- Present: Generally adequate on dev.to.
- Improve: Verify 4.5:1 and line-height.
#### Text resizing and reflow
- Present: Responsive.
- Improve: Test at 200% with no clipping.
#### Media and captions
- Present: Text-only.
- Improve: Offer audio/TTS.
#### Forms and interactions
- Present: N/A.
- Improve: Accessible toasts and targets.
#### Standards reference
- Map to WCAG 2.2 AA: 1.4.x, 2.4.x, 3.3.x.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: Generalized audience.
- Improve: Global case studies.
#### Inclusive language
- Present: Clear, direct.
- Improve: Glossary and plain-language callouts.
#### Neurodiversity support
- Present: Chunked sections.
- Improve: Consistent icon+text labels.
#### Representation
- Present: Role-diverse stakeholders.
- Improve: Inclusive imagery with alt text.
#### Psychological safety
- Present: Respectful tough-love tone.
- Improve: Community guidelines link.
### ✅ Logical Validity
#### Strong reasoning
- Analogical: “Learn some French” clarifies stakeholder-language mismatch; strengthens the case to learn business terms.
- Causal: Business literacy → better advocacy/alignment → budget survival; plausible chain.
#### Fallacies
- Potential hasty generalization: Layoffs attributed mainly to poor translation; mitigate by noting macro factors and mixed methods evidence.
#### Tone of voice
- Direct, coaching, “tough love,” pragmatic.
### 🛡️ DARVO Analysis
- Deny: None; acknowledges tensions.
- Attack: None; critiques practice, not people.
- Reverse victim/offender: None; reframes responsibility without blame.
## 🎯 Conclusion
- Bottom line: DevRel needs business literacy to translate impact into ARR, pipeline, and budget terms—become bilingual to endure and thrive.
- Next steps: Build a shared glossary, align with Sales/Marketing/Finance on definitions and reporting, pilot PLG-aligned DevRel programs, and replace vanity metrics with revenue-adjacent measures.
## 🧱 Refactor Appendix (append after 🎯 Conclusion)
### 📚 Literature Split Pad
- Purpose: Stage Konik CEE units that become per-source Literature notes.
- Split level: H3.
- Include verbatim quotes under 25 words and a [view highlight] link.
### [H1] DevRel requires business literacy
> [!quote] Why Business Literacy Matters for DevRel by [[Matty Stratton]] via [[dev.to]]. Published 2025-10-27. Accessed {{date:YYYY-MM-DD}}.
> “You can't effectively measure…if you don't understand the fundamentals of how the business actually works.”
Two lines: Use to justify training. Track pre/post budget outcomes.
[view highlight](https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] Translate DevRel to ARR and pipeline
> [!quote] Why Business Literacy Matters for DevRel
> “How does this impact our ARR? … How much pipeline did DevRel source last quarter?”
Two lines: Build shared metric definitions with Finance/Sales.
[view highlight](https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1#H2) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
- Purpose: Promote reusable claims into Atomic notes.
- Split level: H4.
- Each item: one idea, present tense, specific, testable.
#### [Z1] Business fluency increases DevRel budget wins
- Scope: Teams post-foundation training; track next two quarters.
- Pointer: Exec approval logs.
- Links: [[DevRel]] [[Budgeting]]
#### [Z2] PLG complements DevRel motions
- Scope: Self-serve product; activation metrics.
- Pointer: Funnel dashboards.
- Links: [[PLG]] [[Developer-Marketing]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- Purpose: Capture quick actions or sparks for Fleeting notes.
- Extraction: Select one line → “Refactor: Extract selection to new note (content only).”
- Keep each line short and self-contained.
- [F1] Draft shared glossary: ARR, CPL, sourced vs influenced pipeline — context/https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1 #fleeting #inbox
- [F2] Build DevRel → funnel mapping dashboard — context/https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1 #fleeting #inbox
- [F3] Schedule Sales/Finance office hours for DevRel — context/https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1 #fleeting #inbox
---
## 🧰 Template Library (paste into Note Refactor → Refactored Note Template)
<!-- Copy ONE template at a time into the plugin before running each batch. -->
### 📝 Fleeting — Refactored Note Template (Konik-ready)
---
type: fleeting
status: inbox
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
process_by: {{date:YYYY-MM-DD}} # review within 24–48 hrs
source_title: [MISSING]
source_link:
author: [MISSING]
source_type: article|paper|video|podcast|thread
reading_stage: inspectional|analytical|syntopical
project:
tags: #fleeting #inbox
---
# 📝 Fleeting Note — {{title}}
## 🧠 One-liner (my words)
- State the single idea in one short sentence.
## 🧭 Context & cue
- Where did this arise? Page/timecode/speaker.
- Trigger: quote, data point, claim, or question.
## 🧪 Adler checks (quick)
- What is this about as a whole?
- What is said in detail, and how?
- Is it true? Evidence for or against?
- So what? Impact or next move.
## 🔎 Bias & reliability snapshot
- Possible bias or framing?
- What evidence would change my view?
## 🧩 Konik bridge
- Draft a claim header for promotion.
### [H1] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{source_link}}) by [[{{author}}]]. Accessed {{date:YYYY-MM-DD}}.
> “Short quote under ~25 words.”
One line on why this matters.
[view highlight]({{source_link}}) #xref ID:rw_[MISSING]
## 🧰 Next moves (pick 1–2)
- [ ] Promote to *Literature* with citation.
- [ ] Draft *Atomic* claim from [H1].
- [ ] Park as testable question.
## ✅ Processing checklist
- [ ] Rewrote in my words.
- [ ] Decided: trash | keep | convert.
- [ ] Linked to at least one related note.
- [ ] Tagged and moved out of inbox.
---
### 📚 Literature — Refactored Note Template (Konik-ready)
---
type: literature
status: draft
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
adler_level: inspectional|analytical|syntopical
reading_stage: inspectional|analytical|syntopical
source_title: [MISSING]
author: [MISSING]
year:
publisher_or_journal:
edition_or_volume:
doi:
url:
accessed: {{date:YYYY-MM-DD}}
citekey:
project:
tags: #literature #reading
---
# 📚 Literature Note — {{title}}
## 🧰 Action Inbox
- [H1] Short action — context/{{url}} #articleseed
- [H2] Short action — context/{{url}} #xref
- [H3] Short action — context/{{url}} #share
## 🧭 Bib Capsule
- Title, author, year, venue, and link.
- One-line scope: what the work attempts.
## 🧠 Author’s Thesis (their words)
- Core claim briefly. Include page/timecode.
## 🧩 Key Arguments
- Argument A — method/evidence — page/time.
- Argument B — method/evidence — page/time.
- Argument C — method/evidence — page/time.
## 🧪 Evaluation (Adler)
- What is this about as a whole?
- How is it argued? Fairly and clearly?
- Is it true or plausible? Why?
- So what? Practical or theoretical impact.
## 🗒️ Notes (Konik CEE units)
### [H1] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{url}}) by [[{{author}}]] via [[{{publisher_or_journal}}]]. Published {{year}}. Accessed {{accessed}}.
> “Verbatim highlight under ~25 words.”
Two lines: context and use. Link to data if relevant.
[view highlight]({{url}}#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{url}}) by [[{{author}}]] via [[{{publisher_or_journal}}]]. Published {{year}}. Accessed {{accessed}}.
> “Verbatim highlight under ~25 words.”
Two lines: context and use. Link to data if relevant.
[view highlight]({{url}}#H2) #xref ID:rw_[MISSING]
## 🔖 Zettel Candidates
#### [Z1] 5–10-word present-tense claim
- One-line context and page/time.
#### [Z2] 5–10-word present-tense claim
- One-line context and page/time.
## 🏷️ Tag Coverage
#articleseed: 0 • #xref: 0 • #share: 0 • #bmf: 0 • #addendum: 0
## ✅ Processing Checklist
- [ ] Thesis captured in my words.
- [ ] 1–3 Zettel candidates drafted.
- [ ] Action Inbox pruned to high-signal items.
- [ ] Cross-links added and filed.
---
### 🔖 Atomic (Zettel) — Refactored Note Template (Konik-ready)
---
type: atomic
id: {{date:YYYYMMDDHHmm}}-{{title}}
status: evergreen
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
origin: reading|thinking|experiment
proof_state: conjecture|working|supported|refuted
source_literature: [[Source-Literature-Note]]
citekey:
project:
tags: #zettel #idea
---
# 🔖 {{title}} <!-- 5–10 words, present tense, specific -->
## 🧠 Claim
- One idea only. Clear and testable.
## 🧾 Evidence & Pointers (Konik)
- [H#] from [[{{source_literature}}]] — page/time — brief rationale.
- ID:rw_[MISSING] — link to highlight or dataset.
> [!quote] Evidence snippet (≤25 words) if essential.
> Cite page/time. Keep it minimal.
## 🔍 Scope & Conditions
- When this holds. Boundaries and exceptions.
## 🔗 Links
- Broader: [[Parent-Concept]]
- Narrower: [[Specific-Case]]
- Related: [[Parallel-Idea]]
## 🧪 Tests / Falsifiers
- One check that could disconfirm the claim.
- Simple study or observation plan.
## 🧰 Implications
- Practice, policy, or design moves in one line each.
## 🔙 Backlinks
- From: [[{{source_literature}}]] • Context line.
## ✅ Maintenance
- [ ] Links in and out.
- [ ] Title still precise?
- [ ] Proof state updated.
---
---
tags: #DevRel #Business #Metrics
author: Matty Stratton
source: dev.to
reference: [https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1]
date created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
---
# 🏷️ Title: Why Business Literacy Matters for DevRel (And Why You Can't Skip This Step)
## 🧭 Table of Contents
- [[#📝 Summary]]
- [[#📖 Main Content]]
- [[#🗒️ Notes]]
- [[#📚 References]]
- [[#🗣️ Paraphrase]]
- [[#📰 Newsletter]]
- [[#✅ Action Items]]
- [[#🧪 Hypotheses]]
- [[#📊 Methodology]]
- [[#❓ Questions]]
- [[#🔮 Future Research]]
- [[#💡 Implications]]
- [[#🧠 Learning Styles Assessment]]
- [[#📊 Accessibility Assessment]]
- [[#🌍 DEIB Assessment]]
- [[#✅ Logical Validity]]
- [[#🛡️ DARVO Analysis]]
- [[#🎯 Conclusion]]
### 🔗 References
- Include links cited in or relevant to the article.
## 📝 Summary
- What happened: The author argues DevRel struggles not because “the business doesn’t get DevRel,” but because DevRel lacks business literacy.
- Why it matters: Budget survival and strategic influence require fluency in sales, marketing, and finance to translate DevRel impact.
- Key stakeholders: DevRel teams/leaders, Sales, Marketing, Finance, executives.
- Risks and tradeoffs: Over-indexing on vanity metrics; perceived “selling out”; under-communicated impact leading to cuts.
- Bottom line: Become bilingual—map DevRel work to commercial outcomes to advocate, align, and survive.
## 📖 Main Content
- Core argument: DevRel must “speak business” to show value; impressions and community growth don’t answer ARR, pipeline, or cost-per-lead questions.
- Context/definitions:
- ARR: recurring revenue; a core financial metric.
- CapEx vs OpEx: capitalized vs operational expenses; matters to finance planning.
- Funnel stages: awareness → consideration → conversion; marketing’s model for attribution.
- Product-Led Growth: product usage drives acquisition/expansion; complements DevRel’s developer-first motion.
- Uncertainties: Exact KPI frameworks and attribution details deferred to future posts; this piece focuses on foundations, not metrics.
### 🗒️ Notes
- “The problem is that DevRel doesn't understand business.”
- Disconnect: DevRel cites impressions/Discord growth; leadership asks about ARR, CPL, sourced pipeline.
- “You can't effectively measure and demonstrate your value if you don't understand the fundamentals of how the business actually works.”
- Goal: “Becoming bilingual” to converse with Sales (pipeline), Finance (budgets, P&L), Marketing (funnel).
- Series scope: Sales 101, Marketing 101, Finance 101, plus PLG as a complement.
- Payoff: Better advocacy, alignment, survival during cuts, and partnerships.
- “The best part about ‘selling out’? You get paid.”
## 📚 References
- Annual Recurring Revenue (ARR) overview (https://www.investopedia.com/terms/a/annual-recurring-revenue.asp)
- CapEx vs. OpEx explained (https://www.investopedia.com/ask/answers/020915/what-difference-between-capital-expenditures-capex-and-operating-expenses-opex.asp)
- Marketing funnel stages (https://www.shopify.com/blog/marketing-funnel)
- Product-Led Growth primer (https://www.productled.org/blog/what-is-product-led-growth)
- Developer Relations overview (https://en.wikipedia.org/wiki/Developer_relations)
## 🗣️ Paraphrase
- Paragraph A: The issue isn’t that companies fail to grasp DevRel; DevRel often fails to translate its work into business terms that budget owners use.
- Paragraph B: Vanity metrics create a language gap; leaders want ARR, pipeline, and costs, not impressions or community size.
## 📰 Newsletter
- DevRel teams are under pressure to prove value. This piece argues the fix is business literacy: map advocacy, content, and community to pipeline, ARR, and funnel stages. Coming next: Sales, Marketing, and Finance 101 for DevRel, plus PLG fit. Brush up on ARR and CapEx/OpEx, then audit your dashboard to swap vanity metrics for revenue-adjacent signals.
## ✅ Action Items
#### DevRel
- Define influence/sourced pipeline from events, content, and demos; document deal acceleration anecdotes.
- Build education tracks tied to product activation and expansion.
- Ship examples/SDKs mapped to key use cases and revenue segments.
- Create top/mid/bottom-funnel content with UTMs; align on attribution rules.
- Run community surveys tied to activation, retention, and expansion.
- Establish quarterly reviews with Sales/Marketing/Finance; publish feedback loops.
#### OSPO
- Clarify contribution charters and decision rights that support go-to-market.
- Automate license scanning and set review SLAs.
- Maintain vuln intake and embargo playbooks; sign releases.
- Track SBOM freshness and ownership.
- Offer contributor legal guardrails and office hours.
- Fund critical upstreams; sign MoUs with key projects.
- Report OSS impact in executive scorecards.
#### Community
- Host roadmap clinics; publish governance templates.
- Create contributor onboarding paths and pairing rotations.
- Share sponsor budgets and milestone-based reports.
- Practice cross-project incident drills and disclosure norms.
#### WordPress
- Core: triage, performance budgets, release criteria.
- Core Performance: dashboards and perf bounties.
- Core AI: responsible guardrails and eval sets.
- Core Program Team: rituals, dependencies, retros.
- Mobile: telemetry and offline UX improvements.
- Playground: browser labs and reproducible bugs.
- Community/Training/Marketing/Support/Design/Docs: fill gaps with examples-first patterns, editorial calendars, and SLAs.
- Accessibility/Meta/CLI/Hosting/Tide/Openverse/Themes/Plugins: audits, scoring transparency, review throughput, provenance checks.
#### The WPCC
- Programs: fellowships, microgrants, stipends.
- Projects: governance clinics, doc sprints.
- Funding experiments: matched grants and milestone payouts.
### FAIR
- Independence: local metadata and signature checks.
- Policies: transparent funding, sunset clauses.
- Governance artifacts: charters and scorecards.
## 🧪 Hypotheses
- H1: Teaching DevRel basic sales/marketing/finance increases budget approval rates within two quarters.
- H2: Translating activities to pipeline/ARR reduces DevRel layoffs during downturns.
- H3: PLG+DevRel orgs see higher activation-to-paid conversion than marketing-led-only orgs.
- H4: Executive satisfaction with DevRel rises when reports swap vanity metrics for revenue-adjacent metrics.
### 📊 Methodology
- Pre/post training quasi-experiment across teams; measure budget approvals, headcount stability, exec NPS.
- Compare conversion and activation in PLG+DevRel cohorts vs controls.
- Content and event attribution via UTMs, assisted conversion windows, and pipeline stage tagging.
### ❓ Questions
- Which revenue-adjacent metrics best capture DevRel’s deal acceleration?
- How should Finance model DevRel as OpEx with long-tail impact?
- What PLG motions amplify community-led adoption?
### 🔮 Future Research
- Longitudinal studies on DevRel’s retention and expansion impact.
- Standardized attribution models for community touchpoints.
### 💡 Implications
- Practice: Adopt bilingual reporting (developer + business).
- Policy: Tie budgets to strategic objectives and measurable outcomes.
- Security: Include disclosure and signing in DevRel demos/docs.
- Education: Core business literacy in DevRel onboarding.
- Funding: Protect programs with clear revenue linkages.
### 🧠 Learning Styles Assessment
- Reading level: Flesch-Kincaid Grade ~8–9 (estimate).
#### 👀 Visual learners
- Present: Lists; clear structure.
- Improve: Pipeline/funnel/ARR mapping diagrams.
#### 🔊 Aural learners
- Present: N/A.
- Improve: 3–5 minute audio summary.
#### 🗣️ Verbal learners
- Present: Analogies (language/bilingual).
- Improve: Glossary of business terms.
#### 🧩 Kinesthetic learners
- Present: N/A.
- Improve: Build-a-report exercises with sample data.
#### 🧠 Logical learners
- Present: Stepwise argument.
- Improve: Causal diagrams and KPI trees.
#### 🧑🤝🧑 Social learners
- Present: Collaboration emphasis.
- Improve: Peer review of exec-ready reports.
#### 🧘♀️ Solitary learners
- Present: Introspective prompts implied.
- Improve: Self-assessment checklists.
#### 🌿 Naturalistic learners
- Present: N/A.
- Improve: Ecosystem health analogies for community metrics.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: Headings.
- Improve: Alt text and landmarks.
#### Keyboard navigation
- Present: Likely standard web patterns.
- Improve: Focus states and skip links.
#### Contrast and readability
- Present: Generally adequate on dev.to.
- Improve: Verify 4.5:1 and line-height.
#### Text resizing and reflow
- Present: Responsive.
- Improve: Test at 200% with no clipping.
#### Media and captions
- Present: Text-only.
- Improve: Offer audio/TTS.
#### Forms and interactions
- Present: N/A.
- Improve: Accessible toasts and targets.
#### Standards reference
- Map to WCAG 2.2 AA: 1.4.x, 2.4.x, 3.3.x.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: Generalized audience.
- Improve: Global case studies.
#### Inclusive language
- Present: Clear, direct.
- Improve: Glossary and plain-language callouts.
#### Neurodiversity support
- Present: Chunked sections.
- Improve: Consistent icon+text labels.
#### Representation
- Present: Role-diverse stakeholders.
- Improve: Inclusive imagery with alt text.
#### Psychological safety
- Present: Respectful tough-love tone.
- Improve: Community guidelines link.
### ✅ Logical Validity
#### Strong reasoning
- Analogical: “Learn some French” clarifies stakeholder-language mismatch; strengthens the case to learn business terms.
- Causal: Business literacy → better advocacy/alignment → budget survival; plausible chain.
#### Fallacies
- Potential hasty generalization: Layoffs attributed mainly to poor translation; mitigate by noting macro factors and mixed methods evidence.
#### Tone of voice
- Direct, coaching, “tough love,” pragmatic.
### 🛡️ DARVO Analysis
- Deny: None; acknowledges tensions.
- Attack: None; critiques practice, not people.
- Reverse victim/offender: None; reframes responsibility without blame.
## 🎯 Conclusion
- Bottom line: DevRel needs business literacy to translate impact into ARR, pipeline, and budget terms—become bilingual to endure and thrive.
- Next steps: Build a shared glossary, align with Sales/Marketing/Finance on definitions and reporting, pilot PLG-aligned DevRel programs, and replace vanity metrics with revenue-adjacent measures.
## 🧱 Refactor Appendix (append after 🎯 Conclusion)
### 📚 Literature Split Pad
- Purpose: Stage Konik CEE units that become per-source Literature notes.
- Split level: H3.
- Include verbatim quotes under 25 words and a [view highlight] link.
### [H1] DevRel requires business literacy
> [!quote] Why Business Literacy Matters for DevRel by [[Matty Stratton]] via [[dev.to]]. Published 2025-10-27. Accessed {{date:YYYY-MM-DD}}.
> “You can't effectively measure…if you don't understand the fundamentals of how the business actually works.”
Two lines: Use to justify training. Track pre/post budget outcomes.
[view highlight](https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] Translate DevRel to ARR and pipeline
> [!quote] Why Business Literacy Matters for DevRel
> “How does this impact our ARR? … How much pipeline did DevRel source last quarter?”
Two lines: Build shared metric definitions with Finance/Sales.
[view highlight](https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1#H2) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
- Purpose: Promote reusable claims into Atomic notes.
- Split level: H4.
- Each item: one idea, present tense, specific, testable.
#### [Z1] Business fluency increases DevRel budget wins
- Scope: Teams post-foundation training; track next two quarters.
- Pointer: Exec approval logs.
- Links: [[DevRel]] [[Budgeting]]
#### [Z2] PLG complements DevRel motions
- Scope: Self-serve product; activation metrics.
- Pointer: Funnel dashboards.
- Links: [[PLG]] [[Developer-Marketing]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- Purpose: Capture quick actions or sparks for Fleeting notes.
- Extraction: Select one line → “Refactor: Extract selection to new note (content only).”
- Keep each line short and self-contained.
- [F1] Draft shared glossary: ARR, CPL, sourced vs influenced pipeline — context/https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1 #fleeting #inbox
- [F2] Build DevRel → funnel mapping dashboard — context/https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1 #fleeting #inbox
- [F3] Schedule Sales/Finance office hours for DevRel — context/https://dev.to/mattstratton/why-business-literacy-matters-for-devrel-and-why-you-cant-skip-this-step-30p1 #fleeting #inbox
---
## 🧰 Template Library (paste into Note Refactor → Refactored Note Template)
<!-- Copy ONE template at a time into the plugin before running each batch. -->
### 📝 Fleeting — Refactored Note Template (Konik-ready)
---
type: fleeting
status: inbox
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
process_by: {{date:YYYY-MM-DD}} # review within 24–48 hrs
source_title: [MISSING]
source_link:
author: [MISSING]
source_type: article|paper|video|podcast|thread
reading_stage: inspectional|analytical|syntopical
project:
tags: #fleeting #inbox
---
# 📝 Fleeting Note — {{title}}
## 🧠 One-liner (my words)
- State the single idea in one short sentence.
## 🧭 Context & cue
- Where did this arise? Page/timecode/speaker.
- Trigger: quote, data point, claim, or question.
## 🧪 Adler checks (quick)
- What is this about as a whole?
- What is said in detail, and how?
- Is it true? Evidence for or against?
- So what? Impact or next move.
## 🔎 Bias & reliability snapshot
- Possible bias or framing?
- What evidence would change my view?
## 🧩 Konik bridge
- Draft a claim header for promotion.
### [H1] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{source_link}}) by [[{{author}}]]. Accessed {{date:YYYY-MM-DD}}.
> “Short quote under ~25 words.”
One line on why this matters.
[view highlight]({{source_link}}) #xref ID:rw_[MISSING]
## 🧰 Next moves (pick 1–2)
- [ ] Promote to *Literature* with citation.
- [ ] Draft *Atomic* claim from [H1].
- [ ] Park as testable question.
## ✅ Processing checklist
- [ ] Rewrote in my words.
- [ ] Decided: trash | keep | convert.
- [ ] Linked to at least one related note.
- [ ] Tagged and moved out of inbox.
---
### 📚 Literature — Refactored Note Template (Konik-ready)
---
type: literature
status: draft
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
adler_level: inspectional|analytical|syntopical
reading_stage: inspectional|analytical|syntopical
source_title: [MISSING]
author: [MISSING]
year:
publisher_or_journal:
edition_or_volume:
doi:
url:
accessed: {{date:YYYY-MM-DD}}
citekey:
project:
tags: #literature #reading
---
# 📚 Literature Note — {{title}}
## 🧰 Action Inbox
- [H1] Short action — context/{{url}} #articleseed
- [H2] Short action — context/{{url}} #xref
- [H3] Short action — context/{{url}} #share
## 🧭 Bib Capsule
- Title, author, year, venue, and link.
- One-line scope: what the work attempts.
## 🧠 Author’s Thesis (their words)
- Core claim briefly. Include page/timecode.
## 🧩 Key Arguments
- Argument A — method/evidence — page/time.
- Argument B — method/evidence — page/time.
- Argument C — method/evidence — page/time.
## 🧪 Evaluation (Adler)
- What is this about as a whole?
- How is it argued? Fairly and clearly?
- Is it true or plausible? Why?
- So what? Practical or theoretical impact.
## 🗒️ Notes (Konik CEE units)
### [H1] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{url}}) by [[{{author}}]] via [[{{publisher_or_journal}}]]. Published {{year}}. Accessed {{accessed}}.
> “Verbatim highlight under ~25 words.”
Two lines: context and use. Link to data if relevant.
[view highlight]({{url}}#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{url}}) by [[{{author}}]] via [[{{publisher_or_journal}}]]. Published {{year}}. Accessed {{accessed}}.
> “Verbatim highlight under ~25 words.”
Two lines: context and use. Link to data if relevant.
[view highlight]({{url}}#H2) #xref ID:rw_[MISSING]
## 🔖 Zettel Candidates
#### [Z1] 5–10-word present-tense claim
- One-line context and page/time.
#### [Z2] 5–10-word present-tense claim
- One-line context and page/time.
## 🏷️ Tag Coverage
#articleseed: 0 • #xref: 0 • #share: 0 • #bmf: 0 • #addendum: 0
## ✅ Processing Checklist
- [ ] Thesis captured in my words.
- [ ] 1–3 Zettel candidates drafted.
- [ ] Action Inbox pruned to high-signal items.
- [ ] Cross-links added and filed.
---
### 🔖 Atomic (Zettel) — Refactored Note Template (Konik-ready)
---
type: atomic
id: {{date:YYYYMMDDHHmm}}-{{title}}
status: evergreen
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
origin: reading|thinking|experiment
proof_state: conjecture|working|supported|refuted
source_literature: [[Source-Literature-Note]]
citekey:
project:
tags: #zettel #idea
---
# 🔖 {{title}} <!-- 5–10 words, present tense, specific -->
## 🧠 Claim
- One idea only. Clear and testable.
## 🧾 Evidence & Pointers (Konik)
- [H#] from [[{{source_literature}}]] — page/time — brief rationale.
- ID:rw_[MISSING] — link to highlight or dataset.
> [!quote] Evidence snippet (≤25 words) if essential.
> Cite page/time. Keep it minimal.
## 🔍 Scope & Conditions
- When this holds. Boundaries and exceptions.
## 🔗 Links
- Broader: [[Parent-Concept]]
- Narrower: [[Specific-Case]]
- Related: [[Parallel-Idea]]
## 🧪 Tests / Falsifiers
- One check that could disconfirm the claim.
- Simple study or observation plan.
## 🧰 Implications
- Practice, policy, or design moves in one line each.
## 🔙 Backlinks
- From: [[{{source_literature}}]] • Context line.
## ✅ Maintenance
- [ ] Links in and out.
- [ ] Title still precise?
- [ ] Proof state updated.
## Highlights
- DevRel doesn't understand business. ([View Highlight](https://read.readwise.io/read/01k8kt8mnn8b4ycw1pkz47j3n6))
- I've seen entire DevRel orgs dismantled. I've had conversations with DevRel leaders who are fighting for their team's survival. What's the common thread that I see again and again? They couldn't effectively communicate their value to the business. ([View Highlight](https://read.readwise.io/read/01k8kt9ptv9132qdxambyye3e7))
- And then budget season comes around and people start asking questions like:
• "How does this impact our ARR?"
• "What's the cost per lead for these activities?"
• "How much pipeline did DevRel source last quarter?" ([View Highlight](https://read.readwise.io/read/01k8ktb2gfs6krkgfza3xmb2av))
- And the DevRel team responds with things like:
• "Well, we had 50,000 impressions on that blog post..."
• "Our Discord community grew by 30%..."
• "Developers really love when we do office hours..." ([View Highlight](https://read.readwise.io/read/01k8ktcsysmh3807kve0ts632d))
- None of this is helpful for you without tattooing this on your eyeballs: you can't effectively measure and demonstrate your value if you don't understand the fundamentals of how the business actually works. ([View Highlight](https://read.readwise.io/read/01k8ktd74s6mfpw84w1ktjjjj6))
- Walk into a meeting with your VP of Sales and have a meaningful conversation about how DevRel activities are accelerating deals in the pipeline ([View Highlight](https://read.readwise.io/read/01k8ktdevwj9rv5vzsc1cs2s38))
- Sit down with your CFO and explain your budget in terms that make sense to them, using language they actually use ([View Highlight](https://read.readwise.io/read/01k8ktdjsd5c2j8cnvk66ej1gz))
- Talk to your CMO about how DevRel's activities map to different funnel stages and why that matters ([View Highlight](https://read.readwise.io/read/01k8ktdmnq3f81ns2jax23pvp1))
- Advocate for your team's budget and headcount in terms that resonate with executives ([View Highlight](https://read.readwise.io/read/01k8ktdpw3jgdkgw9swhcj4rgk))
- What This Series Will (And Won't) Cover
Over the next few posts, I'm going to walk you through the fundamentals of three key business functions:
1. **Sales** - What your sales team actually does, how they measure success, and where DevRel fits in
2. **Marketing** - How marketing thinks about the world, what they care about, and why DevRel isn't the same thing (but needs to speak their language)
3. **Finance** - The basics of budgets, P&Ls, and why your CFO cares about things you've never thought about ([View Highlight](https://read.readwise.io/read/01k8ktdzq45vmpn83cm82w363y))
- What I'm NOT going to cover in this series:
• Specific DevRel metrics or KPIs
• Attribution models
• ROI calculation frameworks
• How to build a business case for DevRel ([View Highlight](https://read.readwise.io/read/01k8kte2hkjqvm07dnj3vbzvby))
- **You can advocate more effectively.** When you understand what matters to your stakeholders, you can frame your work in ways that resonate with them. You're not compromising your values; you're translating them. ([View Highlight](https://read.readwise.io/read/01k8ktefgtsbz8yyf81jwab8qh))
- **You can align better.** When you understand the company's business objectives, you can intentionally align your DevRel strategy and activities to support them. This makes you more strategic, not less authentic. ([View Highlight](https://read.readwise.io/read/01k8kted5bzxfadxewd0p6n5rw))
- **You can fight for your team.** When budget cuts are coming, the teams that can articulate their value in business terms are the ones that survive. Full stop. ([View Highlight](https://read.readwise.io/read/01k8kteadxzf6g15a9tnwzz2m8))
- **You can build better partnerships.** Understanding how sales and marketing work means you can collaborate with them more effectively, which amplifies your impact. ([View Highlight](https://read.readwise.io/read/01k8ktejwtkys1y4r5v5drbj1e))