►
From YouTube: [REC] Product Key Review (Public Stream)
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
A
B
A
lot
I'm
I'm
here,
I
know,
there's
been
a
lot
of
talk
around
tracking
pql's
product
qualified
leads.
I've
talked
to
craig
a
little
bit
about
it
as
well.
I'm
just
curious
what
everyone
thinks
the
first
iteration
looks
like
and
what
help
you
may
need
to
achieve
that.
C
I
can
take
this
one
brian,
so
my
team
is
working
on
implementing
pqls
in
the
product,
I'm
linked
to
the
epic,
where
we're
tracking
all
the
related
work.
This
milestone
we're
planning
on
implementing
the
endpoints
so
that
we
can
actually
send
the
data
directly
to
marketo
in
salesforce.
C
Part
of
this
work
is
going
to
be
creating
a
new
postgres
database
to
be
able
to
track
in
the
product
what
essentially,
what
pql
actions
we're
triggering
and
sending
so
that
over
time
we
can
track
those
two
actual
dollars
and
sales
accepted
opportunities.
So
we
know
the
essentially
the
product
influence
dollars
that
we're
driving
from
the
product
and
which
ones
are
driving
the
most
value
for
the
business
and
potentially,
which
ones
are
underperforming
over
time.
C
So
we're
starting
the
initial
work.
This
milestone.
My
goal
is
in
q3
to
have
an
okr
assigned
to
myself
to
generate
the
first
pqls
and
sending
them
to
the
sales
team
that
we
can
track
the
dollars
associated
with
them.
So
the
biggest
ask
I'm
going
to
have
is
from
the
data
team.
Once
we
have
this
postgres
database
created
to
ensure
that
it
is
in
size
sense
and
we're
able
to
join
it
with
everything
that
we
need
to
to
understand.
The
impact
of
pcos.
B
Excellent,
I
would
also
just
like
to
make
sure
that,
on
the
data
engineering
side
to
get
a
view
of
the
pipeline
itself
and
make
sure
that
that
looks
clean
as
well,
so
feel
free
to
involve
them
on
the
actual
integration
piece
too.
That
would
be
great,
as
we
start
to
build
out
that
data
quality
program.
B
Great
sam
thanks
a
lot
scott.
If
you
get
the
comment.
A
Yeah
still
type
in
here
I'll
finish
it
up.
I
talked
to
craig
about
this
yesterday.
He
mentioned
that
the
first
event
that
sam's
team
will
fire
over
to
them
in
marketo
is
trials
associated
with
the
company,
which
is
a
really
great
place
to
start
high
quality
lead
those
will
be
fed
into
the
lead
scoring
mechanism
within
marketo
it'll
drive
the
score
up
and
those
will
be
fed
into
the
sdr
team.
So
that's
the
general
flow
and
then,
as
sam
and
company
generate
additional
pqls.
A
B
Brian
head
number
four
yeah,
so
I
know
we
have
exciting
release
here
coming
up
august.
First,
I
just
really
wanted
to
provide
just
an
opportunity
just
to
put
a
little
color
on
v1.
What's
going
well
and
then
also
maybe
be
some
highlights
on
some
priorities
for
the
next
release:
v2
go
ahead,
justin.
D
Sure
yeah,
so
we
launched
cloud
licensing
to
the
field
this
week,
so
field
enablement
is
underway.
We
kicked
it
off
in
the
worldwide
field
sales
call.
On
monday
I
just
got
off
an
ama
with
the
apac
field
team.
So
so
far
feedback's
been
fantastic.
We've,
let
out
a
lot
of
great
questions.
The
enablement
content
seems
to
be
going
well
and
folks
on
our
gtm
teams
are
completing
the
knowledge,
assessments
and
learning
a
lot
and
no
major
flags
there.
So
it's
great
to
see
early
positive
results.
D
External
communication
goes
out
on
july
20th,
so
that
includes
blog
post
community
forum
post
and
then
emails
going
out
to
customers
whose
renewal
is
coming
up
around
the
effective
date
and
then
the
effective
date,
as
you
mentioned,
brian,
is
august
1st,
so
any
other
highlights
there.
You
think
I
should
call
out
or
any
other
questions
you
have.
B
D
Agreed
yeah
totally,
it's
definitely
coming
together,
yeah
and
then
you
asked
v2
priority.
So
I
listed
a
few
in
the
agenda.
These
are
the
what
what's
surfacing
as
the
top
priority
coming
out
of
our
launch
on
august
1st-
and
I
I
don't
have
you
know
concrete
dates
here-
we're
looking
at
q3q4
timeline
but
we'll
narrow
in
on
that
over
the
next
couple
weeks,
but
they're
they're
listed
in
priority
order.
So
we
need
to
support
customers
who
require
purchase
orders
right
now.
D
We
don't
have
that
process
detailed
out
of
how
a
customer
needs
a
purchase
order.
We
send
that
and
goes
back
and
forth
until
we
process
the
reconciliations
and
auto
renewals,
so
that'll
be
a
follow
all
channel
and
let's
say
most
channel
and
pubset.
Customers
require
purchase,
orders
and
so
we'll
need
that
in
place,
and
then
last-
and
we
talked
about
this
a
couple
months
back-
but
right
now-
we're
issuing
both
a
cloud
license
activation
code
and
a
license
file
to
activate
cloud
licensing
or
to
for
for
all
new
orders
and
renewals.
D
Starting
after
august
1st,
we
need
to
shift
to
strict,
which
means
we'll
only
deliver
cloud
license.
Activation
codes
for
any
transaction
after
after
launch-
and
we
don't
have
a
committed
date
on
that
yet,
but
that's
a
an
iteration
we'll
need
to
take
two.
B
I'll
just
add
real,
quick
on
the
start:
orders
on
the
zora
side,
we've
successfully
upgraded
our
cpq
environment
that
is
going
to
unlock
zora
orders
that
will
help
us
get
to
ramps
and
multi-year
deals
with
some
operational
efficiency.
So
that's
going
to
happen,
preparation
in
v2
and
then
with
a
expected,
go
live
for
the
field
in
november
and
really
it's
more
change
management
than
anything
else.
So
I'm
excited
about
that.
E
F
So
I
can
take
that,
so
there
is
a
recent
field
added
to
our
project
level.
Data
to
indicate
projects
created
through
this
default
learn:
git,
lab
user
onboarding
project
so
from
a
data
perspective,
we're
currently
exploring
how
we
can
integrate
this
project
level,
data
to
our
stage
adoption
and
engagement
data,
which
tends
to
be
more
user
and
name
space
focus
yeah.
When
you
say
integrate,
you
mean,
exclude,
that's
correct
and,
and
at
least
allow
for
the
opportunity
within
our
dashboards
to
filter.
You
know
to
allow
for
looks
with
and
without.
E
E
Well,
okay,
maybe
cool
thanks
for
that
stages
for
organization
seems
flat.
What's
the
best
way
to
increase
this.
G
Mike
yeah,
so
I
can
describe
what
we're
thinking
about
in
growth
here.
So
one
way
we
think
we
can
boost
spo
is
by
driving
sas
since
it
gets
you
into
both
ci
and
secure
at
once,
and
so
we
have
a
couple
experiments
that
we're
going
to
explore
there,
one
that's
introducing
empty
state
for
the
secure
widget.
That's
on
mrs
right
now.
If
you
don't
have
sas,
enabled
you
don't
even
know
it
unless
you
go
looking
for
it.
G
So
this
would
highlight
that
and
allow
you
to
get
into
enabling
it
and
then
we
also
think
there's
an
opportunity
to
allow
users
to
enable
this
when
they're
creating
the
project,
because
we
could
just
create
that
yaml
file
for
them
with
the
entries
that
we
need
for
sas
right
away.
So
they
don't
have
to
go
looking
for
it
and
go
jumping
through
hoops,
and
since
it's
one
of
those
features
that's
available
in
free
and
core,
we
don't
need
to
worry
about
upsetting
users
that
don't
have
access
to
it.
G
So
there's
a
couple
ways
there
and
then
longer
term.
We
also
want
to
explore
creating
a
new
dashboard
experience
when
users
log
in
right
now
that
view
is
kind
of
either
your
project,
your
to-do's,
you
can
pick
existing
views.
We
think
there's
an
opportunity
there
to
use
that
real
estate
to
highlight
like
which
stages
you're
using
and
which
ones
you
aren't,
and
provide
entry
points
to
those
additional
stages.
So
there's
a
few
things
we're
thinking
about
in
growth.
H
Yeah
and
then
from
the
ops
perspective.
Oh
sorry,
I
said
I
agree
that
release
is
probably
the
the
most
fruitful
path
to
go
down:
we're
proposing
a
q3
okr
to
do
just
that
within
the
release
and
configure
groups.
Actually
I
think
that
there's
some
low-hanging
fruit
for
awareness
purposes,
both
in
terms
of
showcasing
templates
that
can
direct
users
to
creating
deployment
jobs,
as
well
as
just
making
sure
they're
aware
of
our
release
capabilities
in
product.
H
So
mike
I
will
coordinate
with
you
on
making
sure
we
work
together
on
that
okr
and
then
I
also
wanted
to
point
out
that.
Well,
I
don't
think
it's
as
critical
as
release
because
it
doesn't
unlock
other
stages
like
release.
Does
we
are
seeing
strong
adoption
in
package
and
we'll
be
working
on
in-product
awareness
for
our
package
capabilities.
E
Oh
thanks
kenny
and
I
think
we
should
also
take
some
inspiration
from
what
harness
is
doing
in
release.
They
seem
to
have
that
traction.
Maybe
that's
a
good
way
to
unify
what
all
the
stuff
we're
doing.
H
Yeah,
I
think
you
had
suggested
the
templates
thing.
I
think
we
have
some
templates
that
we
just
don't
showcase
to
users
today
and
don't
highlight
to
them
and
when
now
that
we
have
this
kind
of,
we
have
a
drawer
in
the
pipeline
editor
that
will
allow
us
to
showcase
to
users
who
don't
have
a
deployment
job.
Oh
here's,
some
existing
templates
that
you
might
use
if
you're
deploying
to
xyz
pattern,
which
is
kind
of
the
the
easy
setup
thing
you
get
when
you
do
harness
harness
asks
you
like.
E
H
I
guess
something
different
in
that
when
I
use
harness
they're
like
wizard,
is
pretty
restrictive,
but
then
they
also
have
a
template
library
that
you
can
go
peruse
and
even
supply
to
developers
within
your
organization.
We
are
definitely
in
progress
of
building
the
template,
library
and
our
pipeline
editor
allows
us
to
showcase
templates
and
even
pre-fill
the
pipeline
definition
with
specific
content.
So
we
have
an
opportunity
to
showcase
hey.
There
are
some
templates
that
we
have
the
wizard
thing.
H
I
guess
I'm
I'm
a
little
bit
skeptical
that
that
is
more
like
the
toy
app
that
says.
Well,
here's
what
you
could
do,
but
then,
obviously
you
need
to
break
it
apart
to
build
what
you
actually
want
to
do
and
deliver
for
and
provide
for
developers,
but
yeah,
definitely
taking
inspiration
from
showcasing
the
capabilities
up
front.
H
E
Yeah
that
makes
sense,
and
it
makes
sense
as
a
starting
point.
I
wouldn't
dismiss
it
as
I
think.
The
thing
that
I
think
is
with
toy
is
is
his
innovator's
dilemma
like
every
everything
looks
like
a
toy
initially,
but
I
hear
what
you're
saying
like
if
that
wizard
is
never
going
to
be
sufficient
for
a
complex
project,
but
I
think
what
we're
seeing
in
our
adoption
rate
is
that
we
could
almost
double
adoption
so
might
be
good
to
focus
on
getting
people
started.
E
Even
if
it's
with
something
pretty
trivial,
that's
already
like
wait,
then
they're
using
it,
and
then
we
can
do
all
the
other
stuff
we're
very
much
focused
at
the
end
of
of
like
the
dependent,
the
yama
dependency
stream
and
stuff
like
that,
that
that's
what
we
do
really
well,
let's
focus
on
making
sure
we
have
a
super
simple
start
for
people,
and
then
we
can
always
we're
kings
of
complexity.
We
we
we're
already
nailing
that
use
case.
H
Yeah
great
point-
and
I
I
I
think
that
those
are
useful
and
for
me
maybe
this
is
worth
a
follow-up
discussion.
The
toy
thing
is
what
I
worry
about
is
that
we
don't
frame
it
as
hey.
This
is
the
starting
point
that
then
we
want
you
to
decompose
and
iterate
on,
but
I
totally
agree
that
we
can
do
the
job
upfront
of
saying
here
is
your
starting
point.
Let's,
let's
get
you
started
on
deployment.