A DevRel at Codeminer42 shares how their team went from a poor CFP acceptance rate to getting five proposals approved at RubyConf 2026. The core insight: writing a good CFP is a distinct skill from delivering a good talk, and most developers write abstracts like ingredient lists instead of pitches. The framework involves three steps — mapping features to audience benefits, identifying the specific pain the audience has before the talk starts, and writing a closing line that directly satisfies that named need. The post includes before/after CFP examples, notes on where AI helps (mechanical phrasing) versus where it hurts (naming the real need), and honest caveats about rejections that have nothing to do with writing quality.
Table of contents
A group with a boring nameTwo different skillsA CFP is a pitch, not a syllabusThe frameworkBefore and after2025: the loop closesRubyConf 2026Not every CFP fits every talk6.2K Impressions