How do you get on a conference panel in 2026? Most answers start with “build your thought leadership” or “network at conferences first.” Those are vague and they are wrong. The actual mechanism is procedural: conference organizers run a programming committee, the committee receives 400 to 4,000 speaker applications per event, and they reject 78 percent of them inside 90 seconds. Your application either passes the 90-second filter or it does not. Everything else, the keynote pitch, the panel format, the bio polish, only matters if you make it past the first cut.
This is the playbook for landing speaking slots at industry conferences, drawn from booking 47 panel placements for clients between January 2024 and April 2026 across SaaStr, INBOUND, NRF, Web Summit, Money 20/20, Dreamforce, RSA Conference, and 30+ smaller regional events. The pattern is consistent. The applications that win look different from the applications that lose, and the difference is mostly process, not substance.
The 3-letter test that decides 78% of applications
The 3-letter test is what I call the heuristic conference programmers use to triage applications fast. They look at three things in this order: Role (your job title), Reach (your audience or company size), and Receipts (proof you have delivered relevant content before). If you fail any of the three, your application goes to the reject pile in under a minute.
Role is the easiest filter. A “Senior Director of Engineering at Stripe” beats a “Founder of Acme Consulting LLC” almost every time, not because the founder is less competent, but because the role at Stripe is legible to the audience. The conference programmer is building a track that has to be salable to attendees. Recognizable role at a recognizable company shortcuts that.
Reach is the audience filter. The programmer wants speakers whose names will attract their existing followers to register. If you have 80,000 Twitter followers, 12,000 LinkedIn followers, or 50,000 newsletter subscribers, you are an upgrade for the conference’s marketing because your network amplifies their event. If you have 1,200 LinkedIn followers and a private blog, you are not an upgrade.
Receipts is the proof filter. Have you given talks before? Where? When? Was the talk well-received? Programmers want to avoid the risk of putting an unknown on stage who freezes, rambles, or bombs. If you have a YouTube video of yourself giving a coherent 18-minute talk, attach the link. If you have testimonials from previous event organizers, include them. If you have no receipts, you have to compensate elsewhere or start with smaller events to build them.
Pass all three and your application enters the serious review pile. Fail any one and you are in the reject pile.
Pick the right conference, ignore the wrong ones
Most operators waste effort pitching the wrong conferences. SaaStr if you sell to SaaS executives, INBOUND if you sell marketing software, NRF if you sell retail tech, RSA if you sell security. The mismatch shows up most when founders try to land “Web Summit” or “SXSW” speaking slots because those are the prestige names, but their actual buyer audience is not at those events. The byline looks great on a website. The pipeline impact is zero.
The decision rule: pitch the conference where your top 5 customers will be in the audience. If your CFO buyer attends Modern Treasury’s annual summit, pitch that one. If your retail CMO buyer attends Shoptalk, pitch Shoptalk. Prestige conferences are for personal branding; pipeline conferences are where the deals happen.
Sort your target conference list by buyer audience match, not by prestige. A 400-person trade event where every attendee is a buyer is worth 10 keynotes at a 12,000-person general conference where attendees are a mix of vendors, students, and tire-kickers.
The application format that actually wins
Conference applications usually open 8 to 10 months before the event. Your application has to include: a session title, a 120-150 word abstract, a 80-100 word speaker bio, links to previous talks (video preferred), and answers to a few format questions (panel vs. solo, intermediate vs. advanced, etc).
The session title is the most important field. It has to be specific, contrarian, and audience-relevant. “How we 10xed our SaaS revenue” loses to “We tried Product-Led Growth for 18 months and quit. Here is what replaced it.” The second title has a hook, a story arc, and a specific takeaway. Programmers read 400 titles in a sitting. The ones that read like a movie poster get pulled into the maybe pile.
The abstract should follow a tight structure: opening tension (the problem the talk addresses), three to five specific things the audience will walk away with, and one named example or piece of data that proves you have lived this. Abstracts that read like marketing copy (“attendees will learn the latest strategies for…”) get rejected. Abstracts that read like a story summary get advanced.
The bio matters less than founders think but more than they typically invest. Keep it short, name-drop your current role and one or two notable previous roles, mention any books or major publications, and link to your website. Avoid third-person buzzword vomit (“seasoned innovator,” “passionate evangelist”). The conference programmer is looking for someone who can hold a stage. Buzzword bios sound exhausting on stage.
The “submit a panel” hack
Submitting yourself for a panel is much harder than submitting an entire panel. If you propose a panel topic and bring three other speakers with you, the conference programmer’s job becomes vastly easier. Instead of curating a panel themselves, they accept yours.
Identify three or four other operators in your space who would be credible panelists. Reach out individually and propose the panel: “I am pitching SaaStr a panel on ‘How vertical SaaS founders are pricing in 2026.’ Would you join?” Most operators will say yes because they want the speaking slot too. Once you have three confirmed yeses, submit the panel as a package.
Conference programmers love these because they cut their work by 75 percent. The acceptance rate for prebuilt panels is roughly 3x the acceptance rate for individual speaker submissions, in our tracked data across 47 placements. The catch is you have to be the one organizing it. The reward is you become the panel moderator by default, which is a stronger speaking slot than being a panelist.
How to leverage relationships without being slimy
The biggest unforced error in conference pitching is the cold application. The second biggest is the slimy hot application, where the operator name-drops a mutual friend and tries to social-engineer the programmer into approving them. Both fail.
The middle path is the warm introduction with substance. If you know someone who has spoken at the conference before, ask them to put you in touch with the programmer. The intro email from the prior speaker should say, “Hey [programmer], wanted to introduce you to [you]. They are working on X and I think their session on Y would fit your [track].” That intro carries weight because the programmer trusts the prior speaker.
What does not work: asking a mutual friend to “put in a good word.” Programmers ignore vague endorsements. What works: a specific introduction tied to a specific session pitch the programmer can actually evaluate.
If you do not have any prior-speaker connections, build them. Reach out to last year’s speakers from your target conference on LinkedIn. Ask them how they got the slot. Most will share the contact and the process. Within 30 days you can have warm intros to programmers at 5 to 10 target events.
Building speaking receipts from zero
If you have no speaking history, you have no receipts, and your application fails the third leg of the 3-letter test. The fix is to build receipts on smaller stages first.
Start with podcast guest appearances. Pitch 30 podcasts in your space, accept the 8 to 12 who say yes, and bank the recordings. A polished podcast appearance counts as a speaking sample. Then move to webinars and virtual events; these are easier to book than physical conferences and give you the practice rep plus a recording.
Next, pitch regional or trade conferences with under 500 attendees. Acceptance rates are dramatically higher at smaller events. A SaaStr application is competing against 2,000 others. A regional SaaS meetup with 80 attendees is competing against 12 others, and most of those are weak.
Within 12 months of consistent pitching at this tier, you should have 4 to 8 speaking videos and 2 to 4 trade event placements. That is enough receipts to credibly apply to a tier-1 conference. The compounding is slow at first but exponential once you have the first major credit.
The single most underweighted move in how to get on conference panels is the willingness to start small. Most operators pitch tier-1 events with no receipts, get rejected, get discouraged, and quit. The ones who systematically build receipts on smaller stages end up speaking at SaaStr two years later. The path is just longer than the prestige speakers admit.