Small Satellite Conference 2026 TL;DR
- SmallSat 2026 runs August 23–26 at the Salt Palace Convention Center in Salt Lake City.
- The commercial exhibit hall is open Monday–Wednesday, 9:00 AM–5:00 PM.
- The official exhibit kit lists lead retrieval at $150 per device, ordered by email.
- Technical session context should shape booth questions and follow-up.
- Capture mission context, stakeholder role, timeline, and next step—not only badge data.
- Use the final day to merge multiple conversations from the same account before teardown.
Everything You Need to Know Before You Arrive in Salt Lake City
Dates and venue: Small Satellite Conference 2026 runs August 23–26 at the Salt Palace Convention Center in Salt Lake City, Utah. The 40th annual conference theme is The Clouds Above the Clouds, focused on the technologies behind successful satellite constellations.
Exhibit hours: The commercial exhibit hall is scheduled Monday, August 24 through Wednesday, August 26, 9:00 AM–5:00 PM each day. Exhibitor setup must be complete by Sunday at 6:00 PM, and teardown begins after the floor closes Wednesday.
Exhibit model: SmallSat publishes booth options from tabletop through 20 x 20 quad booths, with full-access booth staff passes included by booth size. That matters: booth staff can attend technical sessions, not just stand on the floor, so your best reps should listen for mission, payload, ground, and constellation themes before follow-up conversations.
Field Marketing Tip
Turn technical-session attendance into booth intelligence. SmallSat is unusually technical. Do not staff the booth as if every conversation starts cold. Assign one rep to Research & Academia sessions, one to Enterprise sessions, and one to poster and flash-talk themes. Each day, convert those observations into three questions your booth team can ask: What mission constraint are you solving? What part of the constellation stack is blocking scale? What decision has to happen after the conference?
Know the Buyer Before They Walk Up
Commercial constellation and payload leaders
These buyers care about scale, reliability, supplier readiness, and integration timelines. Capture the program stage, constellation size, mission profile, and next technical review.
Government and defense program stakeholders
They may not buy on the booth floor, but they shape requirements and partner shortlists. Capture mission context, contracting path, security constraints, and stakeholder names.
University and research teams
Research groups can be influential partners, future commercial buyers, and talent magnets. Separate near-term procurement conversations from collaboration and recruiting conversations.
Component, launch, ground, software, and services vendors
Some traffic will be partner-led rather than buyer-led. Qualify quickly, then route partner opportunities separately from sales opportunities.
Day-by-Day Floor Strategy
Sunday — Prepare around the program
Setup is not only booth logistics. Use Sunday to review the schedule, identify the talks your target accounts will attend, and assign session coverage. Your strongest opening lines should come from the conference agenda, not a generic product sheet.
Monday — Capture high-intent first conversations
The exhibit hall opens with fresh traffic after the morning keynote. Ask short discovery questions, preserve mission context, and book longer follow-up meetings for Tuesday or Wednesday while calendars are still open.
Tuesday — Convert technical interest into next steps
Use mid-show resets to identify accounts with multiple visitors, missing economic buyers, and partner mentions. If two people from the same company visited separately, merge the context before follow-up.
Wednesday — Close the loop before teardown
Final-day conversations often include attendees who waited until they had seen enough of the market. Keep senior coverage active until 5:00 PM and send every promised note before leaving the Salt Palace.
Zones and Themes to Track
Constellation operations and space networking
Ask how the buyer handles data latency, ground infrastructure, and operations at scale.
Edge processing, payloads, and mission software
Capture the technical constraint in plain language so sales follow-up does not flatten the conversation into a badge scan.
Launch, integration, and supply-chain readiness
For hardware and services vendors, the buying question is often timing. Record launch window, qualification requirement, and procurement path.
Lead Retrieval at Small Satellite Conference 2026
SmallSat’s 2026 exhibit kit lists Lead Retrieval at $150 per lead device, with exhibitors instructed to order by emailing register@smallsat.org; the page says more information is coming soon. The public kit does not name a software provider, app brand, package tiers, CRM/API options, or add-on pricing, so exhibitors should confirm current device details and delivery rules directly with the SmallSat registration team.
That official device is useful for the baseline job: capturing badge/contact data on the floor. B2Brain is designed to go further by helping the booth team preserve the reason the conversation mattered: mission context, technical need, buying role, qualification notes, and the exact next step. Instead of ending the show with a device export that still needs cleanup, exhibitors can use B2Brain to capture voice notes, turn them into CRM-ready records, trigger contextual follow-up, and report which conversations became meetings and pipeline.
For first time customers, B2Brain is available for free at SmallSat for up to 2 users - book a demo to discuss.
Build Your ROI and Pipeline Math
Illustrative assumption block: tabletop booth $2,000 or single booth $3,500 from the public exhibit kit; booth build/services/travel assumed at $8,000–$14,000; lead device $150; average contract value assumed at $75,000. Replace these with your actual booth size, travel plan, ACV, and historical conversion rates.
Formula: total event investment = booth + build + services + travel + lead capture. Meaningful conversations = booth-team capacity × show days × utilization. Qualified conversations = meaningful conversations × qualified-account rate. Meetings booked = qualified conversations × lead-to-meeting rate. Opportunities = meetings booked × meeting-to-opportunity rate. Expected pipeline = opportunities × average contract value. Pipeline multiple = expected pipeline ÷ total investment.
Worked example: a single-booth team spends $3,500 on space + $11,000 assumed build/services/travel + $150 lead retrieval = $14,650. If the team captures 90 meaningful conversations, qualifies 35% of them, converts 30% of qualified conversations to meetings, and 50% of meetings to opportunities, that is 90 × 35% = 31 qualified conversations; 31 × 30% = 9 meetings; 9 × 50% = 4 opportunities. At a $75,000 assumed ACV, modeled pipeline is $300,000, or 20.5× event spend. This is a planning model, not a guarantee.
- Conservative: 60 conversations × 25% qualified × 20% meeting rate × 40% opportunity rate × $75,000 ACV = about $75,000 modeled pipeline.
- Target: 90 conversations × 35% qualified × 30% meeting rate × 50% opportunity rate × $75,000 ACV = about $300,000 modeled pipeline.
- Strong execution: 120 conversations × 45% qualified × 40% meeting rate × 55% opportunity rate × $75,000 ACV = about $900,000 modeled pipeline.
The lever is not the scanner count. It is the number of qualified conversations that leave Salt Lake City with context, ownership, and a scheduled next step. If you haven't already done so, the Event ROI Calculator (free tool) will give you great direction on how to make your $$ go the extra mile.
After the Show
By Thursday morning, every meaningful conversation should be in CRM with program context, qualification, next action, and owner. Prioritize booked meetings first, active mission or procurement projects second, and partner/research conversations third. SmallSat rewards teams that remember technical nuance; generic “great meeting you” emails are easy to ignore.
Turn mission conversations into CRM-ready next steps
B2Brain helps booth teams prepare account briefs, capture voice notes after technical conversations, turn them into structured CRM-ready records, and route follow-up by account, mission need, and next action.