What your agent reads.
- name
- ciso-dinners-and-matchmakers
- description
- CISO dinner circuits, paid CISO meeting platforms, summit sponsorships and vendor-free CISO communities, and how to judge each one. Use when a founder is offered a sponsorship prospectus or dinner seat by Evanta (Gartner), HMG, CDM Media, Apex Assembly or the Cyber Security Summit; is quoted guaranteed CISO meetings or a pay-per-meeting rate by a matchmaker such as Execweb, Sagetap or DoGood; is weighing a pay-to-play or honorarium offer; is deciding whether to host a dinner; is sizing up a room that refuses vendors (The CyberNest, Team8 CISO Village) or a CISO angel syndicate (SVCI); or is planning buyer travel to one metro. Covers the theater test — who pays whom, whether the CISO chose the room, the vendor-to-CISO ratio, what a sponsorship delivers — and how to count what a room produced. Not for cold outbound or investor intros (first-ciso-meetings), paying a CISO (ciso-advisor-equity), founder rooms (founder-communities), or RSAC and Black Hat (rsac-week, hacker-summer-camp).
- title
- CISO dinners and matchmakers
- question
- Which CISO dinner circuits and paid meeting platforms are real, and which are theater?
- subtitle
- Some rooms are real, some are sold by the seat, and the invoice does not tell you which.
- summary
- You will do better with one small dinner you host, where your customers sell you to your prospects, than with any room you can buy. Before you pay for a room, find out who is paying whom and whether the security leaders chose to be there, and count only the deals still alive a quarter later.
- group
- buyer
- verified
- 2026-09-08
- order
- 35
995 / 1024 characters
This is the top of the SKILL.md file, exactly as it downloads. Your agent reads the description field to decide when to load this skill. The rest of this page is for you.
You are being sold a meeting because meetings with security leaders stopped being free. A cold note into a CISO's inbox competes with hundreds of others, so a whole business grew up around the seat at the table. Only three things are for sale in that business: a completed meeting, a seat at a sponsored table, or a vetted room you are not allowed into. Every offer you get is one of those three in different words. Your job is to know which one you are buying, and whether the security leader chose to be there.
Host the room you cannot buy.
You will do better with one dinner you host than with any room you can pay for. Put your customers, your prospects, and the people who vouch for you at one table, and let your customers do the selling in front of your prospects. We have watched that format outperform booths and sponsorships at company after company, for a simple reason. Who chose the guests is the whole variable, and everyone at a sponsored table knows who paid for it.
Keep it to twelve or fifteen seats. Send the invitations yourself, by name, one at a time, because your name is what is being tested. Do not present. Put a question on the table that the guests want to argue about, let a customer answer it first, and stay out of the way.
The real test is whether anyone comes. If a dozen people you invited will not give you an evening, that is not a reason to buy a room. It is a finding. Fix the reason, whether it is the product, the reference, or the name you are trying to borrow, before you pay someone else to fill chairs.
Fill one city before you travel.
You build relationships with senior buyers in person, and they accumulate inside a city. The security leaders at one city's large employers know each other, hire each other's deputies, and refer each other inside the city in a way that a scattered tour never produces. Concentrating in one market beats spreading across many, and travel spread thin ruins the follow-up, which is where the value is.
Plan the dinner around the city, not around a conference, and go back to the same city until the referrals stop. The named rooms in any city change owners every few years, which is why none is named here. Ask a security leader in that city which one is alive this season.
Buy nothing until access is the problem.
You establish that access is what is stopping you before you price a single room. A room opens doors and does nothing else. It is not proof, it does not rescue a product that fails in a pilot, and it gives the buyer no reason to move this quarter. Most companies reaching for a sponsorship do not have an access problem, and a retainer is an expensive way to find that out.
If you can name ten security leaders who took a call with you and none of them progressed, buy nothing. You have a different problem, and it is cheaper to fix.
Ask who is paying whom.
You are buying one of two things, and the operator will not volunteer which. A sponsor-funded room sells you access and seats the executive for free, and the price of that is the executive knows why you are there. A matchmaker sells you a completed meeting, and some matchmakers pay the security leader to take it, in cash, in gift cards, or in credits to a charity, while others will not say.
A buyer who was paid to sit down and a buyer who chose to come are not the same purchase. Ask in writing how the executive is compensated, and treat silence as your answer.
Ask whether the CISO chose the room.
You want the room the buyer picked. A community that a security leader applied to join, or one where the members decide which vendors get to present, is a room the buyer chose. A dinner whose guest list was recruited to match your target accounts is your own list with a caterer. Price it as outbound.
Then ask for the ratio in writing: how many seats, how many sponsors per table, how many vendors per executive. Almost nobody publishes it. A room that will not state its ratio has a number it will not defend.
A meeting is not a relationship.
You will be shown a completed meeting the same afternoon, because that is what the platform can report. The result you actually want, a security review started, a pilot scoped, a budget named, arrives a quarter later or not at all. A security leader gives up nothing to take a meeting someone paid them for, so the meeting tests nothing about their budget, their urgency, or their authority.
Get what the money buys written into the contract, because written down it looks plain. Usually it buys a contact list of unknown completeness and permission to sell in a room where selling without paying gets you escorted out. A room passes the test when access is what stopped you, the deliverable is a named list you can work the following week, and you can name the accounts you want in it before you pay. If any of those three is missing, it fails. The room that reliably passes is the one you host.
The rooms that matter refuse vendors.
You are being evaluated in rooms you cannot enter. The vendor-free practitioner communities take people in internal security roles and refuse anyone in sales, marketing, or investing. The CISO groups that venture firms run admit members by application or open only to their own portfolio companies, and they show a founder the buyers that firm already knows.
Peers are where a security leader first hears of you. The way into those rooms is not a sponsorship. It is a practitioner or a customer already inside who will carry your name in. The way to be discussed well once you are carried in is a product that deploys without incident, because the same room that shortlists you will pass along your failed pilot within days.
A CISO syndicate is money, not meetings.
Groups of security leaders invest together, and the best known of them, SVCI, takes founders through an application form. The temptation is to read their cap table as a lead list. Their check is money, and you should treat it as a financing decision. Their introductions are warm and worth having, and an introduction buys the meeting rather than the budget, so spend them where the product is ready for a senior look.
Spend them carelessly and it costs you twice. The person who introduced you will not spend their credibility on you again, and the buyer who saw an unfinished product will not look again until their next renewal, years away. If the most skeptical leader in that room will not introduce you afterward, that is information about your product, not about them.
Count what is alive a quarter later.
You measure any room by one number: new pipeline it produced that is still alive a quarter later, tracked in its own column. Alive means a named account where a security review has started, a pilot has been scoped, or a budget has been named by someone who owns it. A reply is not alive. A follow-up on the calendar is not alive. Keep hosted, paid, and network-sourced deals in separate columns, because deals from your network flatter every conversion rate they touch.
A security purchase takes half a year or more from the moment a need is named to the moment a vendor is chosen, so a room can be working at ninety days with nothing closed. Kill a room that has produced no live account by then. Do not kill one that has.
Working the question.
- Name what is stopping you. If it is not access, buy nothing and fix the proof, the reliability, or the product.
- Write the guest list for one dinner in one city, twelve to fifteen seats, invited by you, with no agency and no presentation. If you cannot fill it, that is your finding.
- Host it, then go back to the same city until the referrals stop.
- Before any money moves, ask the operator in writing who pays whom, whether the security leaders chose the room, what the ratio is, and what the money delivers as a contract term.
- Find the practitioner or customer already inside the rooms that refuse you, and ask them to carry your name in. Treat a syndicate as a financing decision.
- Log every meeting with its source, and read the log a quarter later. Renew nothing before that.
Working with an agent.
Give your agent your customer and prospect lists. Ask it for the guest list for one dinner in one city, and for the four questions you put in writing to anyone selling you access: who is paying whom, who chose the room, who else will be there, and what you are owed afterwards. Pay for nothing until those four have written answers.
Install the skill.
You are reading the skill itself — this page and the download are the same files. Unzip it into ~/.claude/skills/ (or a project’s .claude/skills/) and Claude Code loads it when the question comes up; so does any agent that reads Agent Skills.
mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -sLO https://techoperators.com/skills/ciso-dinners-and-matchmakers.zip && unzip -oq ciso-dinners-and-matchmakers.zip && rm ciso-dinners-and-matchmakers.zipciso-dinners-and-matchmakers/SKILL.md
No terminal? Download ciso-dinners-and-matchmakers.zip and drop into your assistant’s project files.
