The UK Space Power Conference runs September 23-24, 2026 in London. It's owned by UK Space Command, which makes it a defence procurement event wearing a conference badge. Keynotes include Minister Luke Pollard MP and Air Chief Marshal Sir Harv Smyth. Tickets are £495+VAT, or £695+VAT for VIP.
If you sell into defence, aerospace, or government-adjacent SaaS, this is one of the few 2026 events where the buyer and the budget holder are in the same room. If you don't, skip it.
What this conference actually is
Most space conferences are trade shows with a defence panel bolted on. This one is the inverse. UK Space Command owns it, which means the agenda is built around capability gaps the MoD is trying to close, not around exhibitor floor space.
That distinction shapes who shows up and why. At a commercially owned event, the exhibitor list is the signal — vendors buy floor space to be seen by buyers. At a command-owned event, the speaker list is the signal. The MoD isn't renting a hall to attract suppliers; it's convening them to communicate requirements it has already scoped internally. The programme is closer to a market engagement notice than a marketing exercise.
That matters for pipeline. When a conference is owned by the buyer, the speakers aren't there to sell. They're there to signal what they need. Read the keynote list as a procurement document.
Pollard sits in the MoD. Smyth runs the Royal Air Force's space portfolio. Both are the kind of names that appear on a conference programme six to twelve months before a contract notice hits Find a Tender. That lag is the useful part. By the time a requirement is formally tendered, the framing has already been set — the language used in the notice, the way the problem is scoped, the capabilities treated as table stakes versus differentiators. Suppliers who heard the keynote are bidding against a brief they already understand. Suppliers who didn't are reverse-engineering intent from a PDF.
There's a second layer worth noting. UK Space Command sits inside a procurement ecosystem governed by the Defence and Security Industrial Strategy and the single-source contracting regime, which means not every requirement runs a full competitive tender. Some capabilities are directed to specific suppliers under national security exemptions. For everyone else, the competitive window is real but narrow, and it opens earlier than the tender date suggests.
For founders and small teams, the practical read is this: the value of an event like this isn't the badge scan or the booth. It's the twenty minutes of a keynote where a requirement gets described in plain language before it becomes a formal document. That's the earliest public signal you'll get.
The ticket price tells you who's in the room
£495+VAT is not a founder-friendly price. It's a filter. At that number, you're not competing with students and job-seekers for attention. You're in a room with people whose companies paid for them to be there.
VIP at £695+VAT is the tier that matters if you're selling. The extra £200 buys you access to the sessions where the actual conversations happen. If you're going to spend the money, spend the extra. A £495 ticket that gets you a lanyard and a coffee is worse value than a £695 ticket that gets you three introductions.
There's a second filter at work here, and it's the one most founders miss. Defence procurement runs on process: capability statements, framework agreements, security clearances, and the slow machinery of prime contractors subcontracting down to SMEs. A conference badge doesn't shortcut any of that. What it does is put you in the same room as the people who decide which suppliers enter the pipeline in the first place — programme leads, commercial officers, and the primes scouting for credible small players. That's a qualification problem, not a marketing problem, and it's why the room composition matters more than the agenda.
Compare that to what you'd pay for a B2B lead gen agency in a month and the maths gets uncomfortable. We broke down what those retainers actually buy you at each price point, and a single conference ticket often beats a month of outsourced prospecting for the same spend.
Who you should be targeting before you book
Don't buy a ticket and figure out the target list on the train down. Build the list first, then decide if the ticket is worth it.
Three buckets worth building:
- Prime contractors and their subs. The primes send business development leads, not engineers. Those people have budget authority for tooling and services. Note the tier structure: a sub-tier supplier chasing the same MoD requirement as you is a competitor, but a sub-tier supplier two levels down from your buyer is often a warm introduction. Map the supply chain before you map the floor plan.
- UK Space Command and adjacent MoD desks. Civil servants attend these events. They're not buyers in the traditional sense, but they shape requirements. The distinction matters: requirements drafted in a capability document eighteen months before a contract notice are where positioning actually happens. A conversation at a conference can influence a specification; it cannot influence an award. Treat these contacts as intelligence sources, not pipeline.
- Space-adjacent SaaS and services firms. Companies selling into the same buyer you are. Some are competitors. Some are channel partners. You won't know which until you talk to them. The tell is usually the buyer, not the product: if they sell to the same budget line, they're competing for it; if they sell to an adjacent line, they may be able to carry you in.
Build the list from the speaker roster, the sponsor list, and last year's attendee LinkedIn activity. If the conference is inaugural, lean harder on the sponsor list. Sponsors send their best people. Cross-reference against your existing CRM before you book — a conference is a poor substitute for a warm introduction you already have sitting in your pipeline.
What we'd do with the attendee list
We've written before about extracting attendee lists from Australian conferences before competitors do. The same playbook applies here, with one difference: defence buyers are harder to reach cold than most.
Generic cold email to a MoD email address gets ignored. Personalised email that references a specific session, a specific capability gap, and a specific reason you're relevant gets read. The bar is higher, but so is the payoff.
What we'd do:
- Pull the speaker and sponsor lists into a spreadsheet. Score each name against your ICP.
- For the top twenty, write a one-paragraph email that references something they said or something their organisation is publicly working on.
- No pitch in the first email. Just a question about whether they're attending and whether they'd have fifteen minutes.
That's it. Twenty emails, hand-written, sent two weeks before the event. The reply rate on that approach beats any automated sequence we've run against this audience.
Two process notes matter more here than at a commercial conference. First, defence procurement runs on formal channels, so your email is not a sales motion — it is a request for a conversation that may take months to convert. Treat the first touch as intelligence gathering, not pipeline. Second, attribution and consent rules bite harder when the recipient sits inside government. Under UK GDPR, legitimate interest can cover B2B outreach, but a public-sector address invites scrutiny that a private inbox does not. Keep your lawful basis documented, honour opt-outs immediately, and never infer attendance from a scraped list alone.
If you're running outbound at any volume, check your DMARC setup first. Google and Microsoft closed the volume loophole in 2026, and a misconfigured p=none policy will land your carefully written email in spam before a human ever sees it.
What doesn't work at defence conferences
Standing at the coffee station handing out branded pens. Nobody at a £495 ticket event wants a pen. The same logic applies to the branded tote bag, the stress ball, and the lanyard nobody asked for. Swag signals that you've optimised for volume rather than relevance, and in a room this small, that reads as a tell.
Pitching on the first conversation. Defence sales cycles run eighteen months minimum, and the procurement path is rarely linear. A requirement has to survive capability-gap assessment, internal stakeholder review, and budget alignment before it ever reaches a formal competition. The first conversation is about establishing that you understand the problem, not about booking a demo. Founders who lead with a pitch are effectively asking a stranger to skip four internal approvals on your behalf.
Assuming the person you're talking to is the buyer. At this event, half the room is there to gather intelligence for someone else. Programme officers, technical advisers, and primes scouting subcontractors all look identical on a name badge. Ask what they're working on before you ask what they need. The answer tells you whether you're speaking to a decision-maker, an influencer, or a gatekeeper — and each requires a different follow-up.
And don't skip the sessions. The talks are where you learn what the buyer is worried about. When a keynote frames a capability gap or a timeline pressure, that's not background noise — it's the vocabulary your prospect will use internally when they argue for budget. Mirror it. That's the raw material for every follow-up email you'll send for the next six months.
If you want to try this
Build the list before you buy the ticket. If the list is thin, the ticket isn't worth it. If the list is strong, the £695 VIP ticket pays for itself with one good conversation. That sequencing matters more at a conference like this than at a general industry expo, because the attendee mix is narrow by design. A space power event draws programme officers, capability leads, primes, and a small layer of adjacent suppliers — not a broad cross-section of commerce. The value of the room is concentrated, which means the value of your list is concentrated too. Twenty well-chosen names will outperform two hundred scraped badges.
Practically, that means working the list in tiers before the agenda drops. Tier one: organisations already named in the conference's own materials, since their presence is confirmed rather than assumed. Tier two: the primes and integrators whose programme offices sit downstream of the keynote themes — resilience, domain awareness, launch access. Tier three: the smaller firms whose attendance is likely but unconfirmed, and who are therefore worth a low-cost, low-commitment first touch. Score each tier by how directly your offer maps to a stated priority, not by how senior the title sounds. A capability lead with a live requirement beats a director with none.
Then draft the outreach in the same register the room uses. Reference the agenda, not your product. Ask a question that a programme officer can answer in one line. The goal of the pre-conference email is not to sell — it is to convert an unknown name into a recognised face before you reach the coffee queue.
If you want help building and scoring that list, give MiraReach a try. It finds prospects, scores inboxes, and drafts the emails. You still press send.
— Mira