Prasanth Baskar
@bupd.xyz
January 21, 2026 at 10:10 PM
January 21, 2026 at 10:03 PM
Thanks for reading!
Go submit that CFP. 🚀
What's YOUR CFP tip? 👇
Go submit that CFP. 🚀
What's YOUR CFP tip? 👇
January 21, 2026 at 7:51 PM
Thanks for reading!
Go submit that CFP. 🚀
What's YOUR CFP tip? 👇
Go submit that CFP. 🚀
What's YOUR CFP tip? 👇
Want your CFPs to actually get accepted?
• Hook in first 3 lines
• Write for attendees
• Prove your expertise with links
• Use video introductions
• Draft thoroughly, edit ruthlessly
Your talks are good enough. Your CFPs just need work.
10/10
• Hook in first 3 lines
• Write for attendees
• Prove your expertise with links
• Use video introductions
• Draft thoroughly, edit ruthlessly
Your talks are good enough. Your CFPs just need work.
10/10
January 21, 2026 at 7:51 PM
Want your CFPs to actually get accepted?
• Hook in first 3 lines
• Write for attendees
• Prove your expertise with links
• Use video introductions
• Draft thoroughly, edit ruthlessly
Your talks are good enough. Your CFPs just need work.
10/10
• Hook in first 3 lines
• Write for attendees
• Prove your expertise with links
• Use video introductions
• Draft thoroughly, edit ruthlessly
Your talks are good enough. Your CFPs just need work.
10/10
Most CFP rejections aren't about your idea.
They're about:
• Weak hooks
• Vague abstracts
• No proof of expertise
• Writing for reviewers instead of attendees
Fix these. Your acceptance rate will skyrocket.
9/10
They're about:
• Weak hooks
• Vague abstracts
• No proof of expertise
• Writing for reviewers instead of attendees
Fix these. Your acceptance rate will skyrocket.
9/10
January 21, 2026 at 7:51 PM
Most CFP rejections aren't about your idea.
They're about:
• Weak hooks
• Vague abstracts
• No proof of expertise
• Writing for reviewers instead of attendees
Fix these. Your acceptance rate will skyrocket.
9/10
They're about:
• Weak hooks
• Vague abstracts
• No proof of expertise
• Writing for reviewers instead of attendees
Fix these. Your acceptance rate will skyrocket.
9/10
Your first draft should be THOROUGH.
Don't self-censor while writing.
Brain dump everything.
THEN edit ruthlessly.
Use the editing process to refine and shorten.
8/10
Don't self-censor while writing.
Brain dump everything.
THEN edit ruthlessly.
Use the editing process to refine and shorten.
8/10
January 21, 2026 at 7:51 PM
Your first draft should be THOROUGH.
Don't self-censor while writing.
Brain dump everything.
THEN edit ruthlessly.
Use the editing process to refine and shorten.
8/10
Don't self-censor while writing.
Brain dump everything.
THEN edit ruthlessly.
Use the editing process to refine and shorten.
8/10
Don't write talks solely about AI.
Everyone is. You'll blend into the noise.
Instead: Use AI as part of a broader technical story.
Stand out by being specific, not trendy.
7/10
Everyone is. You'll blend into the noise.
Instead: Use AI as part of a broader technical story.
Stand out by being specific, not trendy.
7/10
January 21, 2026 at 7:51 PM
Don't write talks solely about AI.
Everyone is. You'll blend into the noise.
Instead: Use AI as part of a broader technical story.
Stand out by being specific, not trendy.
7/10
Everyone is. You'll blend into the noise.
Instead: Use AI as part of a broader technical story.
Stand out by being specific, not trendy.
7/10
Secret weapon most speakers don't use
Record a 1-2 minute video.
Introduce yourself. Explain your talk.
Reviewers are human. Putting a face to your proposal makes you memorable.
6/10
Record a 1-2 minute video.
Introduce yourself. Explain your talk.
Reviewers are human. Putting a face to your proposal makes you memorable.
6/10
January 21, 2026 at 7:51 PM
Secret weapon most speakers don't use
Record a 1-2 minute video.
Introduce yourself. Explain your talk.
Reviewers are human. Putting a face to your proposal makes you memorable.
6/10
Record a 1-2 minute video.
Introduce yourself. Explain your talk.
Reviewers are human. Putting a face to your proposal makes you memorable.
6/10
Reviewers don't know you.
So show them:
• GitHub repos
• Blog posts
• Previous talks
• Projects you've built
Be DIRECT. Prove you know what you're talking about.
Links = credibility.
5/10
So show them:
• GitHub repos
• Blog posts
• Previous talks
• Projects you've built
Be DIRECT. Prove you know what you're talking about.
Links = credibility.
5/10
January 21, 2026 at 7:51 PM
Reviewers don't know you.
So show them:
• GitHub repos
• Blog posts
• Previous talks
• Projects you've built
Be DIRECT. Prove you know what you're talking about.
Links = credibility.
5/10
So show them:
• GitHub repos
• Blog posts
• Previous talks
• Projects you've built
Be DIRECT. Prove you know what you're talking about.
Links = credibility.
5/10
The winning formula for abstracts:
• Hook (grab attention immediately)
• Descriptive (explain what you'll cover)
• Final line hook (leave them wanting more)
This structure works. Every. Single. Time.
4/10
• Hook (grab attention immediately)
• Descriptive (explain what you'll cover)
• Final line hook (leave them wanting more)
This structure works. Every. Single. Time.
4/10
January 21, 2026 at 7:51 PM
The winning formula for abstracts:
• Hook (grab attention immediately)
• Descriptive (explain what you'll cover)
• Final line hook (leave them wanting more)
This structure works. Every. Single. Time.
4/10
• Hook (grab attention immediately)
• Descriptive (explain what you'll cover)
• Final line hook (leave them wanting more)
This structure works. Every. Single. Time.
4/10
Stop writing CFPs for reviewers.
Write for the AUDIENCE.
Reviewers know the tech. Attendees decide if your talk is worth their time.
Your abstract should make people think: "I NEED to attend this session."
3/10
Write for the AUDIENCE.
Reviewers know the tech. Attendees decide if your talk is worth their time.
Your abstract should make people think: "I NEED to attend this session."
3/10
January 21, 2026 at 7:51 PM
Stop writing CFPs for reviewers.
Write for the AUDIENCE.
Reviewers know the tech. Attendees decide if your talk is worth their time.
Your abstract should make people think: "I NEED to attend this session."
3/10
Write for the AUDIENCE.
Reviewers know the tech. Attendees decide if your talk is worth their time.
Your abstract should make people think: "I NEED to attend this session."
3/10
90% of reviewers don't read past line 3 of your abstract.
If you don't hook them in those first 3 lines, you've already lost.
Your brilliant idea? Doesn't matter if nobody reads it.
2/10
If you don't hook them in those first 3 lines, you've already lost.
Your brilliant idea? Doesn't matter if nobody reads it.
2/10
January 21, 2026 at 7:51 PM
90% of reviewers don't read past line 3 of your abstract.
If you don't hook them in those first 3 lines, you've already lost.
Your brilliant idea? Doesn't matter if nobody reads it.
2/10
If you don't hook them in those first 3 lines, you've already lost.
Your brilliant idea? Doesn't matter if nobody reads it.
2/10
will update with link once recording gets published
January 19, 2026 at 4:43 PM
will update with link once recording gets published
Not an orchestrator. Not claude-squad.
Just "hey, website-center-div needs you" with one-click jump.
github.com/bupd/ccn
Just "hey, website-center-div needs you" with one-click jump.
github.com/bupd/ccn
January 6, 2026 at 8:30 PM
Not an orchestrator. Not claude-squad.
Just "hey, website-center-div needs you" with one-click jump.
github.com/bupd/ccn
Just "hey, website-center-div needs you" with one-click jump.
github.com/bupd/ccn