The TDX 2027 Call for Participation Is Now Open

The TDX 2027 Call for Participation (CFP) is officially open.

TDX is Salesforce’s developer conference where thousands of builders come together to explore the latest innovations in enterprise AI and development.Presenting is a powerful way to share your technical expertise, build your personal brand, and position yourself as a leader in the Salesforce ecosystem. Help us co-create the TDX session experience by submitting your proposals for compelling, high-quality content that will inspire and teach others by showcasing your expertise through deep technical dives, real-world implementations, and innovative solutions.

Whether you are an experienced speaker or new to the stage, we invite you to share your unique perspective and contribute to the community’s collective knowledge. In this post, we’ll share tips on putting together a standout CFP for TDX 2027 to increase your chances of being selected. The submission deadline is November 16, 2026.

Session topics that resonate with the developer community

We’ve reviewed the highest-performing sessions from TDX 2026 to understand what resonated most with our developer community and the biggest takeaway is: developers want authentic, hands-on, code-first, AI-native content.

The most successful sessions went beyond high-level concepts and dove deep into the technical details. They showcased real-world implementations, explored architectural trade-offs, and shared practical insights from debugging and solving complex challenges.

When submitting a developer session, show us the code (Apex, LWC, Python, Agent Script, etc.), dive into the architecture, and highlight practical, innovative solutions that attendees can learn from and put into practice.

Choose your TDX 2027 session format

When submitting your proposal, you can choose from the following session formats:

Theater Sessions (20 minutes): Fast-paced presentations in a high-energy, open theater space. Ideal for quick technical solutions, live demos, career lessons, or thought leadership. There’s no audience Q&A during the session, but speakers will have opportunities to engage with attendee questions in a separate space afterward. Maximum of two presenters
Breakout Sessions (40 minutes): Held in dedicated rooms, these longer sessions are ideal for deep technical dives and in-depth explorations of architecture or governance topics. We recommend allocating 35 minutes for the presentation and reserving the final 5 minutes for live audience Q&A. Maximum of three presenters.
Community Networking (45 minutes): Community-led networking and peer-learning sessions designed to foster meaningful connections and knowledge sharing. Through guided discussions, Trailblazers exchange ideas, tackle shared challenges, and learn from diverse perspectives across roles and career stages.

Note: You may share your preferred session format and length upon submitting, however, Salesforce reserves the right to incorporate more than one session proposal into a confirmed TDX 2027 session and change the session type/length.

How to craft a compelling submission

To maximize your chances of being selected for the TDX 2027 Developer Track, your proposal should clearly outline the technical lessons the audience will learn. Follow the below developer-focused best practices:

Craft a memorable title. Start with a strong verb and explicitly name the product or technology your session will cover (e.g., Build with Salesforce’s New Dev Plugin for Claude Code, Scale API Governance with Lessons from Salesforce, Automate Search and Retrieval Deployments via DataKits). Be specific about what attendees will learn.
- Tip: Be careful with AI-generated titles and abstracts as they often feel overly generic and inauthentic, especially when combined with excessive em dashes.
Write a clear, actionable abstract. Structure your abstract around three key questions: What technical challenge are you addressing? What specific solution will you demonstrate? What practical, actionable takeaways will attendees walk away with?
Be agent-native. Show an agent doing real work or agent development best practices. Cover evals, traces, guardrails, costs, and what happened when things went wrong.
Bring in the new stuff. Audiences love it when you pair what’s new in the industry with what’s new at Salesforce. For example, show how you build an app in Claude using Salesforce Skills, or how an MCP-connected agent takes action on Salesforce data.
Focus on depth over breadth. Don’t try to cover the entire Salesforce Platform in 40 minutes. Pick a specific topic and go deep (e.g., utilizing parallel subscriptions for Agent actions or optimizing Data 360 queries).
Share real-world experience. Features in Pilot and Beta are highly valued, as are innovative ways of using established technologies.
Use cross-cloud use cases. Showcase real-world solutions that span multiple Salesforce clouds and products, such as Salesforce Platform and Slack. Examples include: Integrate Slackbot with Agentforce via MCP and Automate Data 360 Pipelines via MuleSoft and Slack.
Show something you built. Focus on a solution you’ve personally built, sharing real-world lessons, technical decisions, and honest trade-offs. Practical, experience-driven sessions resonate more than feature tours. For example: Observe Agent Behavior with Traces, Evals, and Alerts.
Bring working proof. A repo, a skill, or an MCP tool that attendees can reuse makes your session more useful.

Best practices for your submission

Here are some best practices and guidelines for your TDX CFP proposal:

Write a one-line title (within 60 characters) that clearly states the session outcome.
Begin the abstract (within 120 characters) with a challenge, then state what attendees will learn.
List three takeaways and name the products, APIs, or tools you will use.
Add a short speaker bio with proof of experience, such as past talks, community work, or code.
Submit more than one idea (maximum of three). Different angles raise your odds of being accepted.
Ask for a peer review before you submit.

Common submission pitfalls to avoid

Based on what we’ve learned from past submissions, here are some things to avoid:

Generic marketing topics, sales pitches, and roadmap talk. Keep sessions technical and focused on what developers can build today.
Company or organization-specific product pitches. Showcase how you’ve used Salesforce technologies to build unique solutions and solve real-world challenges. Focus on the technical approach and practical takeaways, not just your employer’s story.
Broad titles like “Intro to Agentforce”. Name the specific outcome, tool, or skill.
Abstracts with no demo, code, or practical takeaways. Tell attendees what they will see, learn, and be able to do afterward.
Retired product names. Check the latest naming before you submit.

Access speaker support and resources

Once you submit your proposal, you’ll receive a confirmation email. All submissions will be reviewed after the CFP closes, and acceptance decisions will be communicated in December 2026.

If your proposal is accepted, you’ll become the content owner for your session and receive instructions for next steps. A Salesforce session owner will also be assigned to help you build your content and prepare for your TDX session(s).

If your proposal isn’t accepted, your submission will be kept on file for future event consideration. You can also explore opportunities to share your expertise at other Salesforce events, including Trailblazer Community conferences and Trailblazer Community group meetings.

Ready to submit your proposal?

Before submitting your session proposal, review the CFP FAQ and choose a preferred session format, prepare your title, abstract, three concrete takeaways, and a short speaker bio.

Submit your proposal here by November 16, 2026. We look forward to seeing the creativity and innovation you’ll bring to TDX 2027.

About the author

Akshata Sawant is a Lead Developer Advocate at Salesforce and co-author of a book titled “MuleSoft for Salesforce Developers,” published by Packt Publication. For a more in-depth look at Akshata’s accomplishments, visit her LinkedIn profile.

Alba Rivas works as a Principal Developer Advocate at Salesforce. You can follow her on Linkedin.