Templates / Sell Komo / Objection Handling

Objection Handling

Sell Komo

12 common objections with detailed rebuttals. Helps partners close deals confidently.

Template Content

~1113 words, 75 lines

# Objection Handling

The most common objections you'll hear when selling Komo -- and how to respond.

## "We want attendees to focus on the live experience, not digital distractions."

Komo doesn't compete with the live experience -- it **amplifies** it. Live polls during sessions make the audience part of the conversation. Scavenger hunts drive attendees to the show floor instead of keeping them on their phones in the hallway. Trivia about session content reinforces what speakers are presenting.

The alternative isn't "attendees engaging with the event" vs. "attendees on their phones." They're already on their phones -- the question is whether they're checking email or engaging with your event content. Komo redirects existing screen time toward event-relevant experiences.

## "Our team is already stretched thin; we can't handle more activations."

That's exactly why Komo works -- and why partners exist. The platform is no-code, so content can be built and scheduled in advance without developers. Everything goes live automatically based on the schedule. No one needs to be "running" Komo during the event.

As a partner, **you can handle the entire setup**. Build the hub, create the content, configure the schedule, and hand the client a link. Their team's involvement is minimal -- review and approve content, then watch the analytics come in.

## "Sponsors feel digital banners don't provide enough value."

They're right -- digital banners *don't* provide enough value. That's the point. Komo isn't banner ads. It's **interactive, sponsor-branded experiences** that attendees actively choose to engage with.

"The [Sponsor] Challenge" where attendees play a quiz about the sponsor's product for 2-3 minutes and voluntarily share their data is fundamentally different from a banner they scroll past. Sponsors get engagement time, qualified leads, and analytics -- not impressions.

## "Our team doesn't have time to learn new software."

Two answers here. First, the platform is designed to be no-code and intuitive -- most users are productive within an hour. It's drag-and-drop content creation, not enterprise software with a 6-week training program.

Second, **their team doesn't have to learn it at all**. As a partner, you can run Komo on their behalf as a managed service. You build the hubs, create the content, manage the campaigns, and deliver the reports. The client's team reviews and approves -- that's it.

## "Will the transition between our app and Komo be clunky?"

Komo is built for embedding. The SDK handles responsive sizing, theme matching, and seamless transitions. Users don't leave the host app -- Komo content loads inline. With SSO, there's no separate login.

For event apps specifically, Komo can embed as a tab, a section, or a full-screen overlay. The user experience feels native because it *is* native to the host app -- not a redirect to an external site. **Ask for a demo of the embed experience** to show them firsthand.

## "Our sales team says event leads are usually 'junk'."

They're probably right -- badge scans and business card drops are low-intent. Komo leads are different because they come with **context and intent signals**.

When someone completes a quiz about a sponsor's product, answers preference questions, and spends 3 minutes engaging with branded content, that's a fundamentally different lead than "walked past the booth." The data attached to each lead includes what they engaged with, how they answered, and how much time they spent. Sales teams can prioritize based on engagement depth, not just "attended the event."

## "It takes a year to onboard a new vendor."

Komo doesn't require a traditional vendor onboarding process. There's no on-premise installation, no IT infrastructure changes, and no multi-month integration project. It's a SaaS platform that works out of the box.

A basic hub can be live in **hours**. A fully branded, integrated implementation typically takes **2-4 weeks** depending on SSO and CRM requirements. As a partner, you handle the implementation -- the client's procurement and IT teams see a low-risk, fast-deployment tool, not an enterprise platform rollout.

## "We already use X and Y platforms with polls and Q&A."

Polls and Q&A are **two of 55+ content types** Komo offers. If that's all they need, those tools are fine. But if they want gamification (leaderboards, scavenger hunts, trivia competitions), sponsor-branded experiences with individual analytics, data capture, loyalty mechanics, and a persistent engagement hub -- that's where Komo lives.

The question to ask: "Are your current tools giving your sponsors measurable ROI? Are they capturing zero-party data? Can attendees accumulate points across experiences?" If the answer is no, Komo isn't replacing their poll tool -- it's adding an engagement layer they don't have.

## "Our event has 20,000+ attendees; can the platform handle it?"

Yes. Komo is built for high-concurrency environments. The platform handles large-scale events with thousands of simultaneous users. Infrastructure scales automatically -- there's no "turn on more servers" step for the client.

For events at this scale, Komo's team can provide a **load plan and performance review** in advance. Real-time leaderboards, live polls, and simultaneous gameplay have been tested and proven at scale. The architecture is cloud-native and built for exactly this use case.

## "Venue Wi-Fi is spotty."

Komo experiences are web-based and lightweight -- they work on cellular data, not just Wi-Fi. Most attendees at large events are on 4G/5G anyway because venue Wi-Fi is overloaded.

The platform is also optimized for **low-bandwidth environments**. Content loads progressively, interactions are designed to work on slow connections, and data submissions queue and retry if connectivity drops momentarily. It's built for real-world event conditions, not perfect lab environments.

## "We only need this for three days."

That's the current thinking -- and it's exactly the mindset Komo shifts. A 3-day event has a **6-8 week engagement window** when you include pre-event hype campaigns and post-event follow-up.

Pre-event: quizzes, polls, and early registration incentives build anticipation and capture data weeks before the doors open. Post-event: feedback surveys, session recaps, on-demand content, and automated follow-up sequences keep the audience engaged and push leads through the funnel. The 3-day event becomes a multi-week engagement program -- and that's a much bigger value proposition for sponsors too.

## "We don't have a creative agency."

They don't need one. Komo is designed for **non-designers to create polished experiences**. The platform includes templates, brand presets, and a drag-and-drop builder. Upload a logo, set the brand colors, and the content looks professional out of the box.

As a partner, this is also a service opportunity -- you can offer content creation and design as part of your implementation package. But make it clear to the client: this isn't a platform that requires a creative agency to use. If someone can create a PowerPoint, they can create a Komo experience.

Changes here will propagate to all partner hubs using this template. Switch to Preview to see how it renders.

What is Komo Pain Points by Persona

Partner Usage

Using template (2)

Eventbase auto-updates

WMT Sports auto-updates

Customised (1)

Fan 360 x Komo own version

Editing impacts 2 hubs

Changes to this template will be reflected in all partner hubs that haven't customised this section. Partners with their own version (1) will not be affected.

Customised Versions

These partners have their own version of this section. Click to compare.

Fan 360 x Komo

View version