Experts of Experience - Why Customer Experience is Your Best Competitive Advantage
Episode Date: January 15, 2025Can a focus on customer experience really drive business success? On this episode, Steve Martocci, the visionary behind SUPCO and Splice, shares why he believes prioritizing user needs leads to ground...breaking innovations and a loyal customer base. Plus, he describes the process to capture attention, build interest, and drive action by truly understanding your users.Tune in to learn:(0:00) Intro(1:37) Customer Experience as a Competitive Differentiator(3:01) Building Products for Yourself(6:35) Balancing User Experience for Different Segments(8:09) Inspiring New Users Through Experts(9:57) Creating a Diverse Set of Opinions(11:45) Navigating Customer Feedback and Intuition(13:08) Learning from User Feedback(14:50) Prioritizing Features Based on User Needs(16:22) The Importance of Team Collaboration(18:34) Building and Leading Teams(21:04) Creating an Environment for Innovation(25:31) Maintaining Customer Connection as You Grow(41:41) Building Trust with Customers(45:29) Recent Impressive Brand Experiences(49:35) Advice for Customer Experience Leaders –Are your teams facing growing demands? Join CX leaders transforming their strategies with Agentforce. Start achieving your ambitious goals. Visit salesforce.com/agentforce Mission.org is a media studio producing content alongside world-class clients. Learn more at mission.org
Transcript
Discussion (0)
Inspiration goes a long way.
Keep your team inspired.
Keep them excited and inspired
about what their impact is in the world.
Don't overbuild in the beginning.
Get enough in the market so that you can start listening.
Feedback can be really helpful
in showing you what to prioritize,
but it's so important not to lose that intuition
and that intuitive sense of people don't know they want this.
And that might be something that just blows their mind and makes them want this product even more.
But they didn't ask for it.
Hello everyone and welcome to Experts of Experience.
I'm your host, Lauren Wood.
Today, I am so excited to have my dear friend,
Steve Martosi on the show. Steve is a serial entrepreneur with many successful businesses
under his belt. GroupMe, a group messaging app that was sold to Skype.
Blade, the helicopter company you may have heard of. Splice, a royalty-free music platform for
creators. And now, Supco, a companion app for your supplement routine.
We are going to dive into creating businesses
with the customer in mind and really dive into Steve's genius
around business building.
And I will say that I have had a front row seat
as he's been doing this on his latest venture
because his co-founder and CEO of
Supco is actually my partner, Nick.
So I have definitely gotten to learn a little bit more about Steve's leadership style and
how he builds businesses.
And today we are going to dive into all of that.
Steve, so great to have you on the show.
I'm excited to be here.
And I'm also really curious to what, you know to what Nick gets to say behind the scenes on this
because you got the unfiltered Steve feedback
so you know exactly where to go with your question.
Perfect.
We'll spill the tea for everyone here.
Yeah.
So Steve, you've built many successful products
across various industries, social networking,
music production, transportation, now health tech.
And I'm really curious to know how you think of customer experience as a competitive
differentiator for you. I don't think about it as a differentiator first. I first think about the
product that I want to exist, right? Usually I'm the first user of the product or at least, you
know, want to have something come into existence, I generally don't like to build things
that already exist in the world.
So I don't usually even have something
to kind of look at as a comp.
So for me, I think it really just starts
as what's the experience that I want.
And then I think once you've kind of nailed that,
you start thinking about what's the experience for others
and the other kind of, you know, different segments of a market.
Yep.
I mean, you being the original user,
I can imagine gives you a major step up
because you are, you were building this for yourself.
Like I know with SUPCO, for example,
both you and Nick are those like extreme supplement nerds
where you have spreadsheets,
spreadsheets of all the supplements
you're taking and the nutrients and you really were solving a problem for yourself.
And so I'm curious to know how you've kind of been translated that into a business because
it's one thing to say, Hey, I have a problem, but it's another thing to go out and actually
build the thing.
Yeah.
And look, I think in all the business, if you go all the way back to GroupMe, right,
GroupMe was made in 24 hours at a hackathon
to go to a concert with our friends.
And it was just something we needed, you know?
And then, you know, the same weekend
I was using it for the concert,
my co-founder was using it for his family,
kind of like, who was having a baby, you know,
delivered and keeping them updated.
This was before group text messaging existed.
So I think that the real thing is to start
with our core problem, start with the thing
that Nick and I need, and then really just kind of like,
start seeing where it falls apart, right?
You give it to your mom and she doesn't understand
what the word stack is, and you're like,
oh, okay, well, maybe we have to tailor that down.
Or, you know, you kind of say,
I just want to get biohackers right now,
or I'm just going to focus the initial release
on this core market and then think about them
educating the world about these things
like terminology and stuff as you go.
So, you know, in every company it's been a bit different.
In Splice's example, I wasn't really the first customer
because I am not the kind of hardcore musician.
And that was, I had to do a two hour research session
with a music producer to understand their workflow,
to validate a hypothesis I had.
So it's a little different every time,
but you go with your gut at first and you kind of,
even if it's not pretty, it's got to be functional.
And then, and then you can kind of, you know, spice it up and adapt from there.
It's actually interesting.
The concept of like, what's the group that you go after?
Because I think a lot of businesses struggle with this.
It's like, do you go for the super users and the super users only in the beginning?
Or like you said, are you trying to educate people and open it up to a wider net?
How do you think about that? And like, how do you make that decision?
Look, I think one of the principles for me,
that's really important is I like to build tools that are extremely powerful yet
extremely easy, right? Like there's like,
there's something that you can do,
especially when you're not just trying to recreate something that exists,
you're not just trying to make something 10% better that existed before you're trying to create a whole new category.
And so, you know, that gives you the kind of opportunity to, you know, kind of build these elegant user experiences
that can progressively reveal themselves to the newbie.
But then when the hardcore user wants to click in and see, oh, you do that, you do that, oh, okay, you're there.
And there's kind of this secret sauce, I would say,
of toeing that line.
And look, I get a lot of shit sometimes
for people being like, well, what's your target market?
Like, why are you not just focused on this group?
And I'm like, because I actually believe I can build stuff
that appeals to the entire sector.
And that has happened with Splice particularly, I believe I can build stuff that appeals to the entire sector.
And that has happened with Splice particularly, you know,
we're such a tool for the brand new music creator
and half a top 40 music.
And that's hard.
Yeah.
I mean, you have like Splice as an example,
you have both the experts as well as the people
who are just exploring music as a hobby.
And it's such a, there must be a fine balance there
between speaking to the experts
and then speaking to someone who's just learning.
How do you approach that as you're building the business
and especially the features that you offer
because that simplicity piece gets really complicated
when you're trying to serve multiple different groups?
Yeah, look, I think that it's a great question, right?
And you see that with...
So for Splice, and I actually think for Sepco
in a lot of ways, if you appeal to the pros,
if you appeal to the most respected people in the industry,
you start to realize that the newbies
and the people getting used to the space,
they want to learn from their heroes, particularly in music.
And they're kind of willing to jump over hoops
to be like, I wanna be like that person, right?
It's kind of where like, yes, a lot of people
have GarageBand installed and mess around with GarageBand,
but you'll actually see people jumping ahead to tools
like Logic and Ableton and these more complicated systems
because they wanna learn what their heroes do.
So if you kind of give away to speak to them
and let them do some of the marketing and messaging,
and you realize like, oh, wait a second,
I have the same sounds that, you know,
that producer is using to make top 40 songs,
like, okay, and you kind of inspire them
so that even if there is some learning to do along the way,
they realize it's the right learning to do.
It's the learning that like the absolute best in this industry can also go down this path. That's not going to be a waste of their time.
Yeah. It's kind of like they can see their journey in front of them.
Yeah. You know, we used to say our biggest, we had two things that were our biggest
competition, but, but once we had you, our biggest competition in, in, in supplies,
as people given up on themselves.
Right. So you just didn't want to let someone get frustrated with the process
and you never want to have someone get stuck along the way yeah so if you can
kind of cater to them and even if they have some learning to do they just don't
feel alone in their journey it really helps them stick around that's really
interesting actually because that's inspiring like when you can see what
others are doing you can see what others are doing,
you can see that, oh, this person,
in the case of Splice, put out this song
and they found that sample on Splice.
Like, I can do that too.
And with Supco, I think you guys have really nailed this
in the fact of having influencers share their stacks
where you can go and find what people
that you're looking up to are taking
and what they recommend,
and then you can go and do the same thing.
So even someone like me, who despite having lived with Nick
for almost five years now,
I do not know that much about supplements.
I can go and learn and see,
oh, here's what an expert is doing,
and I can be like that as well.
Yeah, and look, I think that's exactly right.
And in music, it was important to have
a wide variety of genres and a wide variety of producers
at all different levels, you know, just because, you know,
yes, the Sabrina Carpenter's Espresso song,
Song of the Summer, was made from three splice loops.
And that's like super inspiring to some people.
They're like, wow, like I can do that?
That's nuts.
But then there's other people who are like,
well, no, I'm like a deep underground techno artist
doing this and that.
And like, when you realize they can use it too,
you're like, oh, I can appeal.
And I think in SUFCO, it's similar, right?
Some people are, the supplement space
is extremely opinionated.
And the opinions range from like
the hardcore research institutions and doctors
to influencers that are just talking about what they do.
So finding a way to help you easily absorb all that
to figure out kind of what path you wanna go down
to make your own decisions.
That's how we give you agency over your health
and that's how we kind of empower you.
And so it's a big piece of figuring out
how to kind of expose people to a diverse set of opinions
and then easily make them be able to make a choice.
Yeah, I think it's actually really special though
to not just say, here's the opinion you should have,
but here's all these different opinions.
So then you can decide your own path within that.
Cause that gives people so much agency.
And oh, I have choice in what I believe here
or how I do things.
And I can see the variation
of how others are doing the same.
Yeah, and look, that's the goal, right?
But then to make an experience easy,
you could, if you're like,
hey, I just trust everything this doctor says,
you click a button and go, right?
You don't need to, I'm not gonna get in the way
and make you do all this research.
You can trust, make the experience simple.
But to know that you don't have to take anyone's
just word for it and you can incorporate your own thinking
or things that are more specific to your demographics
or health conditions,
that's super interesting. That really unlocks the ability to make you feel like you've got
control of your health. That's awesome. I want to talk a little bit about the balance between
customer feedback and intuition. As you've built businesses,
I'm sure you get a lot of feedback from not only users,
but teammates, investors,
and then there's this like innate intuition
that you have as a builder.
And I'm curious how you navigate that.
Usually for what I do is in the beginning,
I have an initial thought of where I think things are,
I have my gut based on my experience
and what I wanna see exist in the world.
And it's pretty important for me to like get that out,
that first version out,
and then start listening to the feedback.
And like sometimes that might have a little bit
of an overbuild in one area or underserved in another area,
but like, if I don't get that core hypothesis out sometimes,
I sit around being like, well, what,
but what about, you know, this?
And what about that?
Like, I never got a chance to explore it this way.
And so for me, I think usually,
I try to keep it pretty tight,
but keep it kind of driven from the gut,
maybe some user research.
But sometimes also in the beginning,
I've gotten some user research that has been,
set me away from a certain path.
Like some of the social features on Subco,
we did some initial testing and people weren't that interested
in it in the cohort we did.
But like now all of a sudden we get a lot of demand
and people wanting to see these things.
So you have to kind of be careful
in some of those early hypotheses.
I think it's, I think it's don't overbuild in the beginning,
get enough in the market so that you can start listening.
And then I love to just work down the list
until someone says like, oh, it's just too expensive.
Or I didn't have enough money this month,
but you got through all the other complaints.
That was a big splice thing was like, okay,
the backlog for year one after launch was just like,
what are they saying?
And we just worked through it.
And most of the time, the good news is it's aligning
with what we were, what our hypothesis was.
Like right now at Sepco, a lot of it's around scheduling
and people wanting to take things.
Like they're hardcore, right?
They're hardcore users who are like,
I don't just take something every day.
I take something for once a week.
And we intentionally knew that that was gonna be
a limitation, but we said, let's go let the users ask for it before we over complicate you
know the workflow with introducing all these extra variables and taking more
time to build it so that's a great one that's like okay top of the backlog
let's work through it but then you know some things that people might not even
know they need or want like some of our community features that are coming and
things that you just kind of have to see it. So it's a mix, right?
It's a fine line and you only have so many resources.
Prioritization is always your biggest problem in a startup.
And so it's a dance for us.
Yeah, I think feedback can be really helpful
in showing you what to prioritize,
but it's so important not to lose that intuition
and that intuitive sense of people don't know they want this.
And that might be, you know,
something that just blows their mind
and makes them want this product even more,
but they didn't ask for it.
And I think we really need to balance that.
And I speak to a lot of leaders
and I facilitate workshops where we're prioritizing products.
And this is the conversation that always comes up of like,
well, what are we intuiting?
And then we need to validate it and listen.
But there was always some magic in what we think is right
in the beginning as well that needs to be considered.
Yeah, and look, I think that sometimes they also
don't get to see where you're going, right?
So you might roll something out and, you know,
maybe the users are okay with it,
but they're not like super happy.
Even like, so one of the things we did at Splice with this
was we had to make sure we were faster than the file system.
Meaning like when you go to listen to a sound,
it's gotta load even faster than if you were listening to it
on your, going through sounds on your local hard drive.
And we did that and that was amazing.
But some people were still like,
oh, well I want it to just show up in my hard drive view
because that's where I'm used to going through things.
But if we did that, you'd miss out on these features
that we have now where you can like find
AI based similar sounds and automatically
find compatible sounds and all these things.
And like, you have to understand why we kind of hold
the line on something for a while
because we know what can come if we change this experience.
This stuff always comes up.
And look, at some point, users love things.
If we had a bunch of people give feedback
in early subco of what they wanted,
but they never really quantified it on like,
how much they would be willing to pay for that
You know if you're like, oh, you know Well, I want you know everything to be personalized to me exactly based on my blood work and sent to me and pill packs and done
To be like this and you know all this up great awesome
What do you want to spend for that and like, you know, it's like oh, oh right, right? There's a cost with that totally
Mm-hmm. Yeah hypothetical feedback is very different than Real life experience, right, right, there's a cost with that. Totally. Yeah, hypothetical feedback is very different
than real life experience.
That's right, yeah.
And I think hypothetical feedback or saying,
what would you want is helpful to see,
okay, what's the mindset of the customer?
What are they thinking about?
But it isn't until you actually show them
or even if they're a paying customer
and they have skin in the game,
that you're really gonna be able to understand
how they're responding to something.
Yeah, yeah, I agree.
Have there been any examples where you intuited a feature
that didn't end up working out?
Oh, I'm sure there are tons of them.
The key to that though is making sure you find out fast
and didn't over invest in them, right?
Like we had a product come in, Nathan at Subco
and he saw a couple of the features we had built
and he's like, guys, like what?
You built this already?
You were like, well, we were gonna use it for this thing
and like, and we never even used it, right?
So it happens all the time.
I think the key is to learn from every one of them.
And it's also, it's an interesting,
like even working with Nick, right?
And working with people who are not necessarily
as experienced rolling certain things out.
Like your business team wants something for a reason,
but you're like, yo, you really gotta use it for that.
You know, like, are you gonna?
And sometimes there's this back and forth between external requirements that are coming in
and the like, all right, but that's another piece of code
that we got to maintain.
And you know, I've actually really enjoyed my relationship
with Nick watching my, because like, you know,
at some point as a product leader and CEO like myself,
you know, you can't do it all yourself.
You have to do it with a team.
You have to really grow a team and build a great culture.
And sometimes you want to,
you really want to enable the team to take their ideas,
run with them and build great things.
And we've just developed this great relationship
and Nick has taken the lead on so many things
like our trust score that is absolutely loved by the users.
And he had all the insight to getting that built,
which has been great.
And then something like I was talking about
with the first implementation of lists
and maybe some other things, he's like,
oh, he learns and then he hears my opinion about it.
And trying to foster an environment
where people can test these ideas and your team,
you have a system for helping people understand prioritization
and like the cost that comes with things
and build a healthy product development culture out of it.
I wanted to ask you about building and leading teams,
especially in the early days where you have people coming
from all these different expertise
and just in seeing the team you've built with SUPCO,
it's like a world-class team,
you've brought exceptional people together, but they
also have different opinions. And how do you create an environment where, like you
said, people can test and they can learn and, you know, maybe there's some healthy
friction but you're able to still move forward. That's the art, right? That's the
that's the secret sauce. And for us, what it is is really short feedback loops
and a lot of like in collaboration, design and by team.
And it works right now while we're small, right?
So, you know, every six weeks we're getting together
for an onsite or offsite, like we get together in person
and that's when we tackle some of the bigger stuff.
And that stuff's nice to do in the room together.
You have a high amount of empathy kind of
when you're together, working through like,
sometimes I get heated and people have opinions,
but you kind of like want people to be heard and understood.
We do a team-wide kind of show and tell every day right now.
And so, I've never built the startup completely remote.
I usually have done remote engineering and things like that,
but having an environment that feels
like we're really in it together remote engineering and things like that, but having an environment that feels like
we're really in it together has been
the fast feedback loop process.
And look, people have really good ideas
and it's sometimes really hard to have to be the one
that's like, I hear you, we're going to ship something
that kinda sucks a little bit, we're gonna get feedback,
and then we're going to evolve to that next point.
Or I see when we get stuck on something where there's no good answer, like we could talk in theory for days about like, you know,
an opinion on something, but it really just, in that sense,
it feels like we don't have enough data. Um,
and that's why we should ship something or, you know, talk to, talk to, uh,
do an interview or something because we're just circling on, okay, it's your opinion versus my opinion.
Like great.
Yeah.
And I try my best to not have to, to kind of step in and play any kind of card on like,
well, I'm the CEO or I'm the, you know, or like in my experience, like I, there's just
so many lines I don't like say anyone's saying on the team and have to, to kind of justify
their, their kind of position.
Say goodbye to chat bots and say hello to the first AI agent. Agent Force Service Agent makes self-service an actual joy for your customers with its conversational language anytime on any channel.
To learn more visit salesforce.com slash agent force.
Now I've thought it has been really cool to see the cadence
at which you meet this every six weeks on site,
team gets together, and then the daily connection
of feedback, I mean, you've been building really quickly
because of that, and I initially, I'll be totally honest,
when Nick was like, oh, we meet every day, I'm like, really?
Like, that feels like kind of a waste of time.
Do you really need to do that?
Like, yes, it's early stage, yes,
it's a small number of people,
but now you're like, what, 10 people?
Yeah, about that.
A little more than that.
That's like, you know, it's a lot of time.
It's an expensive meeting,
and especially when resources are tight,
and I've kind of questioned it,
but then I've seen the results of that type of touch point
and just the fast iteration that you're able to do
as a result.
But then how does that scale?
Like what are you gonna do now that you're,
like what did you do at Splice, for example,
just in terms of bringing people together?
These are all great questions.
So I think that when I think about, you know,
how does this scale, I really want this to,
it may be a move to like departmental show and tells.
There's something amazing about these fast feedback loops and look, people get blocked
on stuff and they sometimes rabbit hole for days where if they just talked to another
engineer, if they just talked to the product owner about something, if they just talked
to the designer about something, they would like unblock.
And you know, yes, you can kind of talk about it in
a quick stand up in the morning, but kind of showing people where they are and kind
of where they're stuck. And if you kind of are sensing someone's kind of like, not moving
at the pace, you know, they are capable of moving at, we like kind of address it like
fast. So, you know, and context gets heavily shared amongst the team, right? You're in
the remote environment, you miss out on the lunch together
where you're just like talking about something
or going over, there's so much like water cooler
conversation that you miss out on
that this works for us right now
and I'd love to see it work at scale kind of departmentally
where, you know, like if we form into teams
that they can meet and do a similar thing,
even if the whole company can't do it.
And even the last offsite we did,
I think it was more of a timing issue,
which was right after our launch
and we were still all scrambling,
that going right into that was,
it might not have been the best timing,
I don't know if we got the best use of time out of it,
but in-person time in general,
I think is so important to building empathy,
and building great products, you need to have the connection amongst the different people on your
team. And so we always just make sure we get that even if it's not the most productive session.
That in-person time goes so far in building trust and allowing you to actually speed up
as a result of it. If people have human connections with their peers,
you can ask those questions.
You can be vulnerable.
I'm not really sure how to do this.
Or like I've been rabbit holeing,
can you help me get out of the rabbit hole?
And if you don't have that connection,
which remote work has, I think that's been the biggest hit
as a result of remote work is that human to human connection
that we have with our peers.
So finding the time to just be together, even if it's not about work is that human to human connection that we have with our peers. So finding the time to just be together,
even if it's not about work.
It helps. And then the unscripted lunches and stuff during those things,
like there's something about the meetings that make people feel like they need
to perform, stick to a topic.
And then just having that kind of unstructured time too of like hearing what's
on someone's mind,
where they don't feel like they have to be on stage either.
They're just talking to someone.
Yeah, completely.
I mean, empathy inside and out is what I always say
is so important inside the organization,
having empathy for ourselves.
And then we can also apply that to our customers,
of course, to understand their points of view.
Yeah, and I mean, on that front too,
like I'm a very much someone who came up
in the world of paired programming, which is literally when you're coding two people are working
on the same project together.
And it's extremely intimidating at first, people are seeing typos, people are seeing
you think through things in real time.
But it is deeply, deeply liberating once you've kind of like allowed yourself to be that vulnerable
with another coworker. And like, you don't get blocked you think things you
learn you absorb like so much moves fast and so we actually end up doing a lot of
like live design sessions you know like you kind of need to be okay with being
pretty exposed I would say and it was very like that a group me and then you
know splice got got bigger and bigger
to the point where that got harder to do.
And I think one of the things I think a lot about at Subco
as we scale is making sure that that kind of culturally
is established early enough.
I remember this day at Splice where I was interviewing,
like, I don't know, like two or three PM roles
at the same time. And it was a day that I realized I kind interviewing like, I don't know, like two or three PM roles at the same time.
And it was a day that I realized I kind of like lost
something a little culturally because I hadn't codified
enough about like how we build software
and how we kind of build together
was a kind of rapid growth period.
And you know, you let the culture get away a little bit.
I mean, I think it's really difficult to do that
the bigger you get, but in my opinion,
those small groups, like creating your little pod
where you can open up and there's vulnerability
and the leader is expressing that and showcasing that,
then you can kind of continue it on,
but it's really, really difficult to create
that level of openness when you're dealing
with like 200 people.
Yeah, I mean, at least at scale,
being open enough to be honest about metrics,
be honest about user feedback, you know,
like use the product, things like that,
that if you get to disconnect,
so there's the whole like disconnects your internal team
and then there's a disconnect from the actual user base,
right, if we're coming back to customer experience.
And like that is I think a recipe of a disaster
for a company on a disconnect.
And they're not, they're heads in the sand on so much,
either from a telemetry perspective, from just a,
from like, you know, our support channel right now,
it's just like everybody sees every piece of feedback
that kind of comes in and it's like, it really helps drive home where we're
falling short, where we have more work to do.
Yeah. How do you keep that customer connection though, as you grow? How do you
make sure that everyone is really staying in the mindset of the customer
and staying connected to the customer's needs?
There's like these really process processy ways of doing it,
which is like, oh, have a user research team
and make sure you're in the field gaining your knowledge.
And like those things are all true.
Those things are all kind of helpful.
But I think there's also, you know,
there's a potential like even once a month
to just like make half the day or a full day of like,
we did this thing at this place called Beat Relay,
which was a simple thing, musicians, non-musicians,
everyone in the company signed up for a team
and that team made music together, right?
And Beat Relay, as much as it was just a fun thing
and cool, was also a nice forced dog food session
of like trying to work on music collaboratively,
you know,
across location with people.
Can you define dog food for us?
Cause you guys say this all the time.
Yeah, it's just using your own product, right?
Like particularly like it's kind of like, maybe it comes from like eat your own dog
food or make sure, make sure your food tastes good, you know, use your product.
Um, it's funny. I, I realize, I don't know why I think that term is just so common, but maybe it's Make sure your food tastes good. Use your product.
It's funny, I don't know why I think that term is just so common, but maybe it's not.
We've had many employees come in and just be like,
what are you talking about here?
But yeah, so using the product I think is one,
create fun experiences for people to use the product.
And then also, we used to have a really good
hackathon culture at GroupMe, where we would do, we used to have a really good hackathon culture
at GroupMe where we would do like,
I think it was a quarterly hackathon,
which was kind of like, just like,
what do you want to have exist?
And I think that that always yielded really amazing features
and insights from people's just personal struggles
with our own software.
Yeah, using the product is so, so key.
And it's definitely difficult if you're in like
a SaaS based business and you can't necessarily
use the product, at least as in depth as your customers are.
But I've also at times had teams like actually go
and be with the customer.
I was gonna say, watching those like customer feedback
sessions and you're just like, oh, oh, man.
Wow. This is really difficult.
Isn't it?
Oh, I know that sucks.
You're like, oh, we haven't worked on that page for so long.
You know, like, yeah, like, yeah, those things are just,
those are brutal.
It's brutal, but it's such important information.
Another thing that I did when I was running customer
experience at Too Good to Go, especially
when we had a big backlog of tickets, and I guess AI is somewhat solving this, but what
we did as a result was great.
We would do care parties where every single person in the company would have a two-hour
block and we would give them a little rundown of here's how you answer tickets, here's
all the easy tickets that you can answer.
And we would essentially have like a race,
like who can answer the most tickets in this amount of time.
And then we had prizes and we would have like breaks with like fun things
that we would do and just like make it exciting because it can be really draining
to do this, like to answer tickets and just the same type of thing over
and over and over again.
But it does a couple of things.
It one, creates a deep understanding of what the customer is dealing with.
And it also creates deep empathy for what the care team is dealing with.
And it really just does wonders for anyone out there who's listening to this.
If you don't have your team answering customer support tickets, I highly recommend that you do. Just getting everyone to jump on board for a period of
time goes so far in really developing that customer and that employee understanding.
Yeah. And like, look, successful organizations I've been at, you know, have done that. I
think it was a guild group. They did rotations through support. Maybe even done a week through support, which was nuts.
It was a lot.
And we did some of that too.
And then, you know what was super annoying
that would happen in this is, you know,
customer support would be dealing with something
all the time that wasn't getting prioritized.
But then like, I'd go talk to some musician,
some famous musician, and they'd be like,
well, so and so doesn't work.
And then you'd be like, guys, we gotta fix this. And they'd be like, well, so and so doesn't work. And then you'd be like, guys, we gotta fix this.
And they'd be like, I know,
we've been saying this for months.
And you're like, aw, crap.
So kind of making sure that you listen to your CX people
because just because they're at the front lines, right?
They're getting that feedback.
And you know, make sure you have a really easy way to give.
I think one of the things that AI potentially
is taking away too is, you know,
so many of these issues are getting solved with AI,
like the actual issues, but where's the feedback coming in?
You know, not so much like, oh, I don't know how to do
this thing or this is, but like, actually the suggestion,
like we are getting the most insane suggestions
from our user base right now.
Insane in a good way, insane in a like,
oh my God, I can't believe you spent the time
to write six paragraphs on what we need to do
around improving your supplement routine, this is amazing.
And so like, having it, but you know, that only works
because at the top of every page
in our app is a feedback button that doesn't ask you
a million questions to get it through,
just lets you dump it in.
People do it, and that's great, and we answer them.
You have to make it easy for people to give you feedback,
and feedback is absolute gold, as you are saying.
If someone is going to take that time,
one, that's like
there's so much juice to squeeze out of that message that you can then bring back to your
team. And we should make it easy for people to share their thoughts first and foremost.
One of the quick things we would do on that, so we've always done like a weekly town hall,
which again, for some people is way too often,
but we would do it an hour every Friday.
And a section that we used to have in all of them
was like, you know, we had splice rules, splice sucks,
and then splice, which would be like
the highlight support tickets of the week, right?
And like some of them would be, you know,
listen to the good stuff too, because the good stuff's inspiring, right? Then you can totally miss the good stuff, right? And like some of them would be, listen to the good stuff too,
cause the good stuff's inspiring, right?
Then you can totally miss the good stuff, right?
Some of those deep inspiring stories,
like share them with your team
because what you really, really want
is an inspired team building a great customer experience.
And like, a team that doesn't feel that,
they just don't put in the effort to go the extra mile.
And so inspire your team is like really, really important.
So show the good stuff.
Don't hide the bad stuff, you know,
like bring it to the top.
And then, you know, and then, you know,
for us there's just a lot of levity, I think too.
We make a lot of jokes as a team and,
and the, the, the Splay Shr shrugs I think we called it would be the
support tickets that we just like I don't know what you're talking about like I don't even think
of using our product right now does anyone understand this totally totally well totally
well I think what you're highlighting is something that I really beat a drum on is that customer
experience leaders need to focus on being more influential.
And being more influential means drawing people in.
Like you want the rest of the team to be interested in what the customers are saying, not just,
oh, we're getting this complaint, fix it.
We're getting this complaint, fix it.
We're getting this complaint, fix it.
That's not inspiring.
No one wants to act on that.
And like you're saying, if you go and speak to a musician and they tell you that feedback,
then you're like, I'm inspired to make a change
where we got 50 tickets that asked for this feature, do it.
It's not inspiring.
And I think that CX leaders are in a difficult position
because they are at the intersection of these two parties,
but they're also in such a powerful position
because they're at the intersection of these two parties, but they're also in such a powerful position because they're at the intersection of these two parties,
the company and their team and the customer.
And through effective communication,
we can really inspire change within our organizations.
And so I think it's something I know for myself,
that was a KPI at one point I set for myself.
I'm like, I need to be more influential.
This quarter, that is my focus. I'm making friends with everybody.
I am positioning every message that I send
as what's in it for them, what's in it for the sales team,
what's in it for marketing, what's in it for product
to help me fix this issue.
And little changes went a really, really long way
for me getting some projects that I had been complaining
about for years to get the green light finally,
just by changing how I approached it.
I think that's a great point.
And I think that, look, I think I've had a real luxury
doing really cool businesses where you can be like,
JJ Abrams says he needs this feature,
and you're like, oh, wow, we gotta build that.
It's inspiring.
I definitely, how to do it in some enterprise
SaaS companies, I'm not exactly sure,
but maybe it's, you know, everything you were just saying
there, just like, you know, raising that kind of,
both that empathy bar and just the friendliness
of the relationship between both the coworkers
and the customers.
So I wanna shift gears a little bit
and talk about revenue streams, because I know at Splice you had a
pretty unique approach to what I mean the business itself you were
enabling people you are enabling people to purchase royalty-free music and use it in their creations
but tell us a little bit about how you structured
the subscription model and how you did that in the best interest of your customers.
Yeah, all right. So, you know, there's three different examples on this. First was Splice
Studio, our first product, which was just a collaboration tool that I made one of my
biggest career mistakes on, which was just not charging for it because I thought it wasn't good
enough. And, you know, honestly, if I had charged for it, I think we would have gotten a stronger
signal if people committed to it. And I think we would have invested more resources in it
because once you do generate revenue,
all your focus shifts to generating more revenue, right?
So when Splice Sounds generated revenue,
that was like our focus, right?
And so that was, so for Splice,
our biggest kind of real competition
at that point in time was piracy. People just stealing sounds, right? So for Splice, our biggest kind of real competition
at that point in time was piracy.
People just stealing sounds, right?
So we had to build a user experience
that was kind of good enough to,
kind of like what Spotify would do
from listening to music, right?
Like it now was like, oh, I'd rather do it.
If it's not on Spotify, I don't know if I'm gonna listen,
I might go to Torrent site anymore, right?
So we had to build great product.
And you know, initially that the price point was like 7.99 a month. Um, and,
you know,
we had to build all these tools to let people put their accounts on hold
because musicians would literally go month to month being like, all right,
it's Netflix or splice this month. Right.
And so we kind of kept that price low.
And then also what we did is we shared revenue, major amounts of our revenue with the
content creators. And so all of a sudden we were a new revenue stream
for these people who then wanted to market their content on the platform,
which created this like pretty epic flywheel. And that still exists today.
I mean, I think if you pulled the numbers now,
I think we would have paid over $100 million
to artists for sound.
And that was just amazing.
And like, you know, some people would look at the model
and be like, well, you know, okay,
you're used on these top 40 tracks,
but the artist isn't making any money off,
the sound creator is not making any money off
because it's royalty free.
But then the answer is like,
they would never have used the sound if they had to go cut a percentage deal
to use your drum loop.
So like, so, you know, it really found the sweet spot
where everyone can win in a scenario.
And then we moved over to this other thing called
our plugins, our rent to own model for plugins.
So the problem again, that was pirating sounds,
then there's the pirating of the software.
So like music software, you know,
when it goes to like the top piracy,
pirated apps in the world, it's like, you know,
Microsoft Windows, Microsoft Office,
Adobe, then the music software.
It's like right there.
And so, you know, these guys,
most of the software wasn't like on SaaS yet,
and it didn't really even make sense to necessarily be on SaaS because it was like not getting
updates all the time.
It wasn't network connected.
So we kind of did this rent to own subscription model.
So I went out and I was like, I need to build a business model that even Reddit can't complain
about.
Which, you know, you want to go figure out if someone likes your product, go see what
they're saying about you on Reddit, right?
Yeah, it's a great goal.
Yeah. figure out if someone likes your product, go see what they're saying about you on Reddit, right? It's a great goal. Yeah, and so it was like, okay, low monthly fees
that are building up to eventually perpetual ownership,
you can stop it at any time, you can pause, you can resume,
and then even needed the feature of you could pay it all off
if you didn't wanna be in the Splays ecosystem anymore.
And by doing all those things,
we got people to pay for music software,
which was freaking great.
And honestly, Reddit didn't really complain about it.
They were like, we were the first purchase
for a lot of people in this category of software.
And look, that was a lot of both,
that was a nice mix of the intuition and the user feedback.
And, but I remember convincing our first software provider to be on rent to own.
He was like, yeah, you guys are going to sell like two of these a day max.
And, uh, you know, that was still would have been good for him, but we were
selling hundreds, hundreds.
And so again, like, it's gotta be that right mix
of not being afraid to kind of,
like a sweet spot for me too is kind of like,
moving into an industry, you know,
some people in tech are just like,
oh, I'm just gonna disrupt, disrupt, disrupt.
And they're like, I'll burn every bridge down along the way.
I really like to go in and kind of respect what exists.
You know, the music creators, you know,
even at Splice, the music creators, you know, even at Splice,
the way we think about AI, we have a very ethical,
you know, perspective on what we're trying to do with AI there.
And, you know, what I think we're doing in Sepco, too,
like, there's too many people in supplements
who are just, like, trying to burn down every institution
and, like, you know, medicine is terrible
and, like, all this stuff. We're like,
no, we're gonna figure out how to work with kind of everybody and, you know, medicine is terrible and like all this stuff. We're like, no, we're going to figure out how to work with kind of everybody and, and,
and, you know, let the good, honest players kind of like, you know, thrive in our ecosystem.
So, so yeah, I feel like that that's been another one that's been interesting is building products
in which the brand stands for something and kind of stands as a trusted, you know,
as infallible as you can be because you're truly looking out for, you know,
everybody in your ecosystem.
The brand is just as important as another layer in the, in the customer
experience because it travels.
Yeah.
I mean, and people trust the brand or they don't trust the brand.
If you, we used to have a line that said, oh, I love this one.
It was from my buddy John from the Disco Biscuits.
He said, you can't refund inspiration.
Like there's no amount of dollars I'm gonna give.
Maybe there's an amount of dollars,
but there's no amount of dollars
that I would have been able to give you
that made sense to refund the fact that I lost,
you know, six hours of your work
and you might never get it back.
You know, you just might never think of that thing again.
And so we had to be really, really well trusted.
And it sounds like you really had the customers best interest in mind with the ways that you
were charging them.
Yeah.
And look, I think that in what we're doing in CEPCO, right?
So we're totally free right now, but I wanna make sure that whatever model
comes down the pipeline is that it's never
just trying to sell you more.
Right?
I don't think you're gonna build the trusted.
I wanna be just as excited when you stop taking something
that's not working as when you're gonna try something new.
Right?
And like that, that is an alignment that I just feel that kind of value-driven care or outcome-driven
stuff in healthcare is where capitalism and health have their friction points.
And so, similar to what I think we did in music, I think we really want to do stuff
innovative on that front. Yeah, I mean, I have a bone to pick
in like for a lot of subscription-based models
where you get locked into something and you like can't leave
or else you like there's a punishment for leaving or pausing.
Like I have been a member of ClassPass for a long time
and I think this has changed,
but I don't know because I'm no longer a customer
because I couldn't pause.
I would have to throw out all my credits in order to pause,
and I was going away for three months,
and I was like, well, I don't want that,
and it took so much for me to,
they eventually paused it, but I was like blacklisted.
I never actually, like, there was no prompt to renew
and I just didn't because I was kind of annoyed.
And I'm like, that's such a missed opportunity.
Yeah, and look, we built that, right?
Like, because you do lose your splice credits
if you cancel, but we made, we were like,
we need pause right away.
And you can continue to pause and pause and pause
and pause as much as you want.
And that was important, right? Cause literally when someone says to you,
they're picking between Netflix and Splice this month,
you just do not wanna leave them hanging.
And also like, I think with these products
in the supplement space, like look,
because customer acquisition cost is so high
and because people do such a poor job
of sticking to the things,
whether they don't take them right
or they don't see their results
on the timelines they expect,
people are thinking about CAC LTV ratios in like months
when they really should be thinking about them
in years, if not decades.
I honestly don't understand why
that isn't the case all the time.
I mean, it's, and look, like business model transformations are hard, right?
Even the transition for Adobe to the classic change from upfront software to Adobe Creative Cloud,
it's the famous J-curve, right? Which is like, you're going to lose money for a period of time.
And people might be pissed, but you're gonna come out the other side
and it's gonna be worth the investment.
And Ecom Company is trying to really understand
how to transform their models
and maybe even lose a little bit of their margin
in the short term in order to play that longer game.
It's really hard for them to do.
And so for us, there's really hard for them to do.
And so, you know, for us, there's some things we're thinking about to help them in that
process.
And I think similar to what we've done in Splice is to create these kind of everybody
wins scenarios, which is, you know, it takes us effort to build stuff.
It's not easy.
And we take a lot of that on.
And sometimes our providers will do better than we do.
And that's okay because we're playing a really long game ourselves.
And yeah, and then just be customer focused, right?
Customer, supplier focused, kind of just looking out for everyone.
Yeah. Well, I think that's a great point to end on.
We have two last questions that we ask all of our guests.
And the first is, I'd love to hear about a recent experience that you had with a brand point to end on. We have two last questions that we ask all of our guests.
And the first is, I'd love to hear about a recent experience
that you had with a brand that left you impressed.
What was it?
All right, I'm gonna go into airlines,
which I don't know if many people say this to.
So one is JSX, which was the first experience
for flying for Jackson.
I have a five month old and we went up to a conference
in Napa and just the experience of not having the TSA.
And we do this in Blade on the East Coast
and the experience of having these kind of semi private
but low cost experiences and then them checking
all the bags for the baby like free. it was just like, okay, great.
This is a good first flight.
But that was like a 50 minute flight, right?
Short haul type of stuff.
Yep, yep.
And then the next one was JetBlue.
And they have upgraded their planes
into this JetBlue Mint Studio seat
that's in the front of the plane,
that like, yo, you can,
that thing converts into like a bed that is wide enough
that it has like a little extra bench,
it's only the first row seats,
that Jackson, me, and Kelly got to lay down
and like read books together on the flight.
Like, holy cow, like, that is a great experience.
And I think so many people overthink their airline.
Like, oh, I need, you know, who over thinks his airlines?
It's Nick.
You know, he's basically the points guy over there.
Tell me about it, yes.
And I'm just like, no, let's just fly JetBlue,
and you know, it's great every time.
Yeah, yeah, awesome. Well, I actually have never heard of JSX, so good to know. Come on, you's great every time. Yeah, yeah, awesome.
Well, I actually have never heard of JSX, so good to know.
Come on, you live in the South.
Look, over here, being-
I'm on the website right now.
Yeah, it's right here.
Being the blade guy talking about JSX is kind of a,
you know, Rob, it's time to come
to Southern California again, let's go.
That's awesome, all right, and my last question for you
is what is one piece of advice
that every customer experience leader should hear?
Oh man, I mean, look, we covered a lot of it here.
I think that using your own product,
I think that let's just go back to that,
keep your team inspired thing, right?
I just think that when your team's inspired
to build software instead of just crushing the tickets monotonously,
that whatever it takes to keep them excited and inspired
about what their impact is in the world,
featuring what the customers are doing with this,
telling the story of someone's life you made better
by building a feature, that inspiration goes a long way.
Oh my God, it goes so far.
When we're having a hard day, which is inevitable,
that we are all going to go through dark times
as we're building businesses, growing businesses.
Things are not always rosy, but that inspiration,
that why, that how are we impacting other people's lives
is really what will carry you through. And I know I've leaned on that many, that why, that how are we impacting other people's lives is really what will carry you through.
And I know I've leaned on that many, many times myself.
And I think it is really the leader's role to help
tell that story and draw those lines, even when it feels like
you're in the depths of it all.
I really appreciate that.
Well, Steve, thank you so, so much for coming on the show. It's been so awesome to have you.
You're my first friend on the pod. So you win.
Hopefully there's funny mores. We have some amazing people on our network.
We really do.
Thanks Lauren.
So we'll have a great day. I'll talk to you soon. See you next time. Bye for now. Bye for now. Bye for now. Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.
Bye for now.