Swell for Fireworks
Design Partnership Proposal
How it works:
Real-time coaching for stronger discovery calls
FAQ
How does it work?
Swell uses your sales framework as an internal map. It listens to both sides of the call separately, so something only counts as "covered" when the prospect actually confirms it.
Swell coaches in two ways:
In-the-moment nudges: When the AE is about to move past something worth digging into, Swell flashes a short cue, like "Find who the final sign-off is." Mostly silent. It only speaks up when it matters right now.
Periodic coverage checks: Every few minutes, it reviews the whole call against your framework and surfaces what's still open, like a manager saying "Before you wrap, we still don't know X."
Swell never tells the AE what to say, only what's missing, in plain language, so they keep their own voice.
Will Swell be distracting?
We designed Swell specifically to avoid this. The AE stays fully in control of the call. Swell's role is to catch points the AE might miss, not to tell them what to say or steer the conversation.
To keep it lightweight, suggestions are capped at one per minute, and AEs can dismiss anything that isn't relevant in the moment. Suggestions also disappear on their own after 20 seconds, so there's nothing lingering on screen competing for attention.
What happens to our customer call data?
Swell does not train or store on your customer call data. View our Security Portal for more info.
Does Swell plug into our internal tools for context?
The initial version of Swell does not use any data sources as context.
See Phase 2 of the proposed design partnership below for more information on connecting your internal data sources.
Has anyone used it yet?
Swell has been tested on more than 50 mock discovery calls but has yet to be used on a live call with a customer.
Design partnership proposal
Phase 1: Unpaid pilot with select AEs in Swell's current form (no connected data sources)
Phase 2: Paid design partnership connecting Fireworks' GTM stack to Swell for more context