If you’ve been sitting on a session idea—something you’ve tested in the real world, something you’ve learned the hard way, or something you believe the industry is still getting wrong—today is the day to put it in front of TechCrunch Disrupt 2026.
TechCrunch Events has opened (and is now closing) the window for submissions to speak at Disrupt 2026, with organizers urging prospective speakers to submit their session topics before the deadline ends. The call is straightforward: share your insight, help shape the conversations that will define the next wave of tech, and give the Disrupt audience a reason to show up early, stay late, and argue about what they heard long after the lights come up.
But there’s more going on here than a simple “apply before time runs out.” The timing matters, the format matters, and—most importantly—the kind of sessions that tend to land at Disrupt are changing as the industry itself changes. In other words: this isn’t just a last-day reminder. It’s a signal about what TechCrunch believes the market needs to talk about next.
Why this submission window feels unusually urgent
Tech conferences don’t just compete for attention; they compete for relevance. And relevance is increasingly tied to specificity. In the early days of startup events, broad themes like “AI” or “fintech innovation” were enough to draw crowds. Now, audiences have seen too many panels that recycle the same talking points: the same definitions, the same hype cycles, the same “we’re building” slides.
Disrupt’s speaker call reflects a different expectation. Organizers aren’t only looking for people who can speak confidently about a topic—they’re looking for people who can add new information to the conversation. That means sessions that are grounded in outcomes: what worked, what failed, what changed after the first deployment, what surprised the team, and what the data actually says.
The urgency of “today is the last day” is partly logistical, but it’s also editorial. Once the submission deadline passes, the program planning shifts from open intake to selection, scheduling, and final shaping. That transition is where ideas either become part of the event’s narrative—or get left behind.
So if you’re thinking, “I’ll apply later,” the more accurate framing might be: “I’ll miss the chance to influence what Disrupt chooses to emphasize.”
What makes a session topic worth selecting
A strong submission usually does three things at once: it clarifies the problem, it demonstrates credibility, and it promises value that can’t be found in a generic keynote.
First, clarity. A session topic should make it obvious what the audience will walk away with. Not just “AI governance,” but “how teams operationalize AI risk controls without slowing product shipping.” Not just “robotics,” but “what breaks when you scale autonomy from demos to warehouses.” Not just “climate tech,” but “how to measure impact credibly when carbon accounting is still messy.”
Second, credibility. Disrupt audiences are smart and skeptical. They can tell when a speaker is repeating industry folklore. Credibility doesn’t require a perfect track record, but it does require honesty about constraints. If you’re a founder, show what you built and why. If you’re an operator, show what you changed internally and what happened afterward. If you’re a researcher or policy expert, show how your work translates into decisions people can make.
Third, value. The best sessions feel like a shortcut through someone else’s learning curve. They include frameworks, checklists, decision trees, or case studies that attendees can adapt immediately. Even when the topic is forward-looking, the session should still offer practical takeaways.
This is where the Disrupt audience differs from many other conference audiences. Disrupt tends to attract founders, investors, builders, and operators who want actionable insight—not just inspiration. That doesn’t mean the sessions can’t be visionary. It means the vision has to connect to execution.
A unique angle: Disrupt is increasingly about “how” not “what”
One of the most interesting shifts in tech discourse over the past year has been the move from “what are we building?” to “how do we build it responsibly, profitably, and at scale?”
That shift shows up in the categories TechCrunch covers and in the kinds of conversations that keep resurfacing across startups and enterprises. The call for session topics is broad—spanning areas like AI, enterprise, startups, transportation, hardware, climate, fintech, biotech & health, government & policy, robotics, fundraising, media & entertainment, crypto, and more—but the underlying theme is consistent: the industry is moving from experimentation to implementation.
When you’re experimenting, almost anything can sound plausible. When you’re implementing, the details matter: data quality, model drift, compliance timelines, procurement realities, unit economics, supply chain constraints, integration complexity, security posture, and user trust.
That’s why a “unique take” can be more valuable than a flashy one. A session that explains the hidden bottleneck—what slows teams down, what causes adoption to stall, what creates regulatory friction, what makes scaling fail—often lands better than a session that simply announces a new capability.
In other words, the best submissions often don’t just describe the future. They diagnose the present.
The Disrupt audience is also changing—and so should your pitch
Disrupt has always been a meeting point between startups and the broader ecosystem. But the ecosystem itself is evolving. More enterprise leaders attend. More technical operators show up. More investors want to understand not only market potential but also operational feasibility.
That means your session topic should consider who will be in the room. A founder might want to know how to validate a go-to-market strategy. An investor might want to understand whether the business model can survive real-world constraints. An engineer might want to know how to implement something safely. A policy-minded attendee might want to understand what regulators will ask next.
A session that speaks to only one of these groups risks feeling incomplete. A session that bridges them—without becoming vague—tends to stand out.
For example, a panel on AI could be framed around model performance, but the stronger version might connect performance to deployment risk, then to customer trust, then to compliance and procurement. That’s a lot of ground, but it can be done in a structured way: “Here’s the pipeline, here’s where failures occur, here’s how teams mitigate them, and here’s what buyers need to see.”
That kind of structure is exactly what makes a session feel like it belongs at Disrupt.
What “help shape the conversations” really implies
The phrase “help shape the conversations defining the tech industry” can sound like marketing language. But in practice, it’s about agenda-setting.
TechCrunch Disrupt doesn’t just reflect trends; it amplifies them. When a topic gets a prime slot, it becomes a reference point for the rest of the year. People build strategies around what they expect to be discussed. Teams align hiring priorities around what they think will be validated publicly. Investors look for signals in what gets spotlighted.
So when organizers invite session topics, they’re not only collecting content—they’re curating a narrative. Your submission is a chance to influence that narrative.
And because today is the last day, the selection process is likely already in motion. That means the submissions that arrive at the end of the window may be competing against a smaller set of final candidates. If you’re going to apply, don’t treat it like a formality. Treat it like a pitch.
How to think about your session topic if you want it to stand out
Even without seeing the exact submission form, you can improve your odds by designing your topic around a clear promise. Here are a few ways to sharpen a session idea into something Disrupt-ready:
1) Lead with a tension, not a theme
Instead of “Fintech and regulation,” try “Why fintech teams keep underestimating compliance timelines—and how to plan for them from day one.”
2) Offer a framework
Audiences love models they can reuse. “A 5-step approach to X,” “a maturity model for Y,” “a checklist for Z,” or “a decision tree for choosing between A and B.”
3) Include evidence
Even a small amount of evidence beats none. Metrics, anonymized case studies, lessons learned from deployments, or results from experiments.
4) Make the audience part of the story
Sessions that invite reflection—“If you’re building X, ask yourself these questions”—tend to feel more engaging than lectures.
5) Don’t hide the trade-offs
The most compelling sessions acknowledge constraints: cost, latency, adoption friction, security, governance, or operational overhead.
6) Choose a specific audience outcome
What should attendees be able to do differently after the session? Write that down. Then build the session around it.
A last-day opportunity is also a last-day filter
There’s a psychological trap people fall into with deadlines: they assume the deadline is only about time. But deadlines also act as filters. They separate ideas that are ready to be articulated from ideas that are still vague.
If you’re serious about speaking, today is a forcing function. You’ll need to decide what your session is truly about, what you’ll teach, and why it matters now. That clarity is useful even if you aren’t selected—because it helps you refine your message for customers, partners, and future opportunities.
And if you are selected, that clarity becomes the foundation of a session that can actually deliver value in a limited time slot.
What happens after you submit
Once you submit your session topic, the process moves into review and selection. That typically involves evaluating relevance, speaker fit, session format, and how well the topic contributes to the overall program. Because Disrupt spans many categories, the goal isn’t just to fill seats—it’s to create a coherent experience where sessions complement each other rather than repeat each other.
That’s another reason specificity matters. A vague topic can be hard to place in a schedule without duplicating something else