If you’ve ever thought about speaking at a Salesforce event, I have good news for you: the TDX 2027 Call for Participation is now open. This is your invitation to get on stage, share something you’ve built, and teach the community what you’ve figured out along the way.
TDX is Salesforce’s developer and technical conference, where thousands of builders show up to dig into enterprise AI and what’s next for the Platform. And the sessions aren’t decided behind closed doors. A big chunk of the technical content comes straight from the CFP, which means proposals from people doing the actual work: admins, developers, architects, consultants, and anyone building, configuring, or extending solutions across the Salesforce ecosystem.
A few things to know before we go further. The CFP opened on October 28, 2026, and closes at 5:00 p.m. PT on November 16, 2026. You can submit up to three ideas. Salesforce will announce acceptance decisions in December 2026. If you’ve never presented before, that’s not a problem here; first-time speakers are genuinely encouraged to apply.
One thing worth saying up front: a strong idea isn’t enough on its own. How you frame it in the proposal is what gets you picked. So below, I’ll walk through how to choose your format, write a title and abstract reviewers actually stop on, and avoid the mistakes that quietly sink good sessions.
Table of Contents
What TDX 2027 Is Looking For This Year
If I had to sum it up in one line, I would say this is not the year for high-level overviews. It is a year for revealing how things actually work.
The content that gets picked comes from real work. Something you built, broke, and fixed, or figured out the hard way on a project. Reviewers want hands-on, code-first, AI-native material, not a tour of a product’s feature list. Think about the moment you muttered, “I wish someone had shown me this sooner.” That’s usually the session.
Below are the topic areas getting the most attention this cycle:
- Agent configuration, testing, and governance
- MCP servers, tools, and integration patterns
- Data 360
- Cross-cloud use cases that connect Agentforce, Slack, MuleSoft, and the Platform
- Headless and AIforce experiences
- Agent Script and Agentforce Vibes
- Salesforce APIs and the Agent API
- Agentic identity, permissions, security, and trust
The real test a reviewer applies is simple. Can they tell, right away, what problem you solved and what someone gets out of sitting in your room? If that’s not clear, the proposal does not move forward – no matter how good the underlying work is.
Which Track (and Audience) Are You Writing For?
TDX content spans admins, developers, and architects, and each group listens for something slightly different. Knowing who you’re talking to changes how you pitch. Here’s how I’d think about it.
The Admin Track
The admin role is shifting under everyone’s feet. The old responsibilities still matter (clean data, sensible permissions, automation that doesn’t break down), and they matter even more once an agent can act on that information. On top of that, the job now includes new skills: configuring agents, writing clear instructions and prompts, and testing agent behavior before go-live. Admin sessions land best when they’re practical enough that someone can walk back to their desk on Monday and try them in their own org.
The Developer Track
This is the most code-forward track, full stop. Show the code: Apex, LWC, Python, Agent Script, whatever you actually used. Go agent-native and get specific about evals, traces, guardrails, and cost, including what happened when things went sideways. One thing that sets strong dev proposals apart is working proof: a repo, a skill, or an MCP tool attendees can grab and reuse. That’s the difference between a talk people enjoy and a talk people bookmark.
The Architect Track
Architect sessions go past what agents do and into how you design, connect, and govern them. The good ones get into the trade-offs: balancing deterministic and probabilistic workflows, orchestrating multiple agents, applying guardrails and observability, keeping autonomy bounded so an agent can’t wander off and do something it shouldn’t. If you present here, lean interactive. The Architect Vista uses live lightboard diagramming, and watching a design take shape in real time tends to stick with people far longer than a static slide.
Choosing Your TDX 2027 Session Format
You’ve got three formats to pick from, and the right one depends on how much depth your idea actually needs. Here’s a side-by-side look.
| Format | Length | Best for | Q&A | Presenters |
|---|---|---|---|---|
| Breakout | 40 min | Deep dives, architecture, governance | ~5–10 min live Q&A | Up to 3 |
| Theater | 20 min | A focused demo or single technique | No formal Q&A (chat after on the floor) | Up to 2 |
| Community Networking | 45 min | Guided peer discussion, not a presentation | Discussion-based | — |
A quick note worth keeping in mind: Salesforce reserves the right to combine more than one proposal into a single confirmed session, and to adjust the session type or length. So submit the format you’d prefer, but don’t be surprised if your 40-minute idea comes back shaped a little differently.
And if you’re sitting on more than one idea, submit each as its own proposal. You can put forward up to three. Different angles genuinely raise your odds.
How to Write a Proposal Reviewers Won’t Skim Past
Reviewers read a lot of these. The ones that stick are the ones where the value is obvious in the first few seconds. Let’s go field by field.
The Title
Keep it to 60 characters or fewer. Start with a strong verb, name the actual product or technology, and make the outcome unmistakable. A clear title beats a clever one every time.
- Weak: Intro to Agentforce
- Strong: Observe Agent Behavior with Traces, Evals, and Alerts
The second one tells me exactly what I’ll be able to do when I walk away. One more thing: be careful with titles generated entirely by AI. They tend to read as generic and interchangeable, and a title stuffed with em dashes is a tell reviewers have learned to spot. Write it yourself, then tighten.
The Abstract
This is the public description people read when deciding whether to attend, so make every word pull weight.
A heads-up on length, because the guidance isn’t perfectly consistent depending on which track you’re submitting under. Some materials reference a 200-character abstract; others reference 120. Write toward ~120 characters to stay safe, then confirm the exact limit in the submission form before you lock it in. That one check saves you a rewrite.
Structure it around three things, in this order:
- The challenge you’re tackling
- What you’ll actually demo or build
- The concrete takeaway attendees leave with
Don’t just narrate your slide deck. Tell people what’s in it for them.
The “Why Should This Be Presented?” Field
This is the most important one, and you get about 1,000 characters. Treat it as an open letter to the review team. What’s the problem, who keeps running into it, what’s different about how you solved it, and why does it matter right now? “Admins should know about this” won’t move the needle. The specifics will.
Mistakes That Get Proposals Rejected
Most rejections aren’t about weak work. They’re about how the idea was framed. Watch for these:
- Pitching a topic instead of an outcome. This is the single most common miss. “We’ll talk about agent testing” is a topic. “You’ll learn how to test agent behavior before go-live” is an outcome.
- High-level overviews, product pitches, and roadmap talk. Keep it technical and focused on what people can build today.
- Company-specific sales stories. Share the architecture and lessons others can reuse, not your employer’s origin story.
- Vague or broad titles. Name the specific tool, pattern, or result.
- Abstracts without a demo, code, or real experience behind them. If there’s nothing to show, then there’s nothing to accept.
- Retired product names. Naming moves fast in this ecosystem. Double-check current terminology before you submit.
Why It’s Worth Submitting (Even If You’re New to the Stage)
If you’ve never presented before, submit anyway. First-time speakers are genuinely welcome, and the payoff goes well past the 20 or 40 minutes you’re on stage.
Teaching something forces you to understand it more completely than you did before. Your story can save another builder weeks of trial and error. And TDX is a place where solid technical work actually gets noticed, which can open doors later.
Accepted speakers get a complimentary pass (if you already bought one, you can request a refund or transfer it), an assigned session owner to help you prep, and access to a speakers-only Slack channel with deck templates and presentation support. You won’t be figuring it out alone.
And if your proposal isn’t selected? It stays on file for future events, and there are Trailblazer Community Conferences and Community Group meetings throughout the year where strong content finds a home. One pass isn’t the end of the road.
Key Dates and How to Submit
Here’s everything time-sensitive in one place:
- CFP opens: October 28, 2026
- CFP closes: 5:00 p.m. PT on November 16, 2026
- Notifications: accept or decline decisions go out in December 2026
Submissions enter review after the CFP closes. Due to the volume, individual feedback isn’t provided. Submitting early doesn’t hurt your odds, so there’s no reason to hold off on a finished proposal.
Before you start, read the CFP FAQ so you know what each field expects, then submit your session here.
Your next step is small and specific: open a blank note and write down one problem you solved this year that made you think someone else is definitely stuck on this too. That sentence is the seed of your abstract. Build out from there, and you’re already ahead of most of the pile.
Frequently Asked Questions
The CFP closes at 5:00 p.m. PT on November 16, 2026. It opened on October 28, 2026, and submissions are reviewed after it closes.
Keep it tight. Aim for around 120 characters and confirm the exact limit in the submission form, since the stated cap can vary. Lead with the challenge, name what you’ll demo, and end with the takeaway.
A breakout runs 40 minutes with time for live Q&A and suits deep technical dives. A theater session is a focused 20-minute demo or single technique with no formal Q&A, though speakers usually stay on the show floor afterward.
Up to three. Submitting multiple ideas from different angles improves your chances, and each one should be its own separate proposal.
Yes. Every accepted presenter receives a complimentary speaker pass. If you already purchased one, you can request a refund or transfer it to someone else.
Your submission is kept on file for future events. You can also present at Trailblazer Community Conferences and Community Group meetings held throughout the year.
Mayank Sahu
I’m a Salesforce enthusiast passionate about CRM solutions, automation, and integrations. As a continuous learner, I stay updated with the latest Salesforce trends, tools, and innovations to share valuable insights and best practices. My goal is to help businesses and professionals maximize their Salesforce potential through actionable tips, industry updates, and strategic guidance.
Follow me for expert insights and the latest updates from the Salesforce ecosystem!
- Mayank Sahu
- Mayank Sahu
- Mayank Sahu
- Mayank Sahu
