►
From YouTube: Acquisition Team Demo: Gitlab.com paid signup flow
Description
Demo of our work on Gitlab.com paid signup flow https://gitlab.com/gitlab-org/growth/product/issues/87
A
B
All
right,
okay,
so
for
the
sauce
paid,
sided
flow.
Nicholas
and
I
made
adjustments
to
the
about
gitlab
column
and
to
get
like
into
customers.
L3N
science
I'll
start
with
the
way
the
customer
enters
it's
about
to
come
and
running
everything
locally
by
the
way,
because
not
everything
is
people
register,
but
this
is
how
it
will
be
looking
once
it's
has
been
merged.
So
when
a
customer
clicks
on
pricing
and
sees
the
different
plans
that
are
available.
B
The
the
Buy
Now
links
now
redirects
to
the
to
the
github
instance
instead
of
the
customers
website.
So,
for
example,
if
we
click
on
the
silver
I
go
to
my
local
host
github
instance
and
since
I'm
not
signed
in
into
get
lab,
it
asks
me
to
register
which
I
will
do
now
by
the
way.
This
is
the
new
solid
floats
we
already
implement
it,
there's
just
a
little
bit
of
change.
The
first
name
and
last
name
has
been
divided
into
separate
fields.
B
So
once
I
registered,
it
asks
me
in
my
role
and
if
I'm
setting
up
for
a
company,
let's
say
now,
for
instance,
so
I'm
setting
up
very
personal
clean
here.
It
automatically
sets
the
number
of
users
to
one
and
its
priests.
Let's
the
group
at
the
plan
I
chose
in
this
case
over
I,
can
still
change
it
to
bronze
or
to
two
gold.
The
summary
details
on
the
right
to
reflect
my
change.
B
Currently,
this
is
loading
an
iframe
from
the
source,
inbox
API
with
stylesheet
included,
and
so
I
can
see
everything
here
without
actually
being
built.
I
have
to
use
this
card
number,
otherwise,
so
I
won't
accept
it
and,
for
example,
if
I
make
mistakes
in
this
field,
I
will
get
validation
from
Sora.
I
can
confirm
the
purchase.
B
B
A
B
B
B
B
B
Instead
of
the
the
page,
Stephanie
Sandra
and
I'll
go
to
the
existing
loop,
edit
page,
so
I
still
see
my
group
name
here
and
I
can
edit
it
here.
But
of
course
intention
is
to
go
to
a
custom
group
out
of
page,
but
you
can
still
see
the
seat
has
been
applied,
so
20
seats
for
the
gold
plan
and
if
I
log
into
the
customers
application.
B
C
B
C
C
The
nicknames
face
packages
also,
like
hardly
ever
upgraded
they've,
turned
out
at
a
higher
rate,
mostly
because
you
don't
understand
what
how
to
configure
it
or
like
what
features
are
getting
so.
The
intention
of
this
flows
to
make
it
so
that
everybody
signed
up
for
a
group
and
so
that
group,
edit
page
the
copy
on
that
group.
Edit
page
changes
based
on
the
answer
setting
up
a
company
for
myself,
okay,
yeah,
also
that
that
question
is
phrased
slightly
differently
in
the
in
the
final
designs.
C
C
C
C
Okay,
so
this
should
I
think
should
be
the
latest.
But
so
this
is
the
registration
page
once
they
click
on
app
a
package
and
I
think
on
ours.
We're
missing
this
updated
design
and
social
signup
links
which
is
fine,
would
like
for
now
we
can
launch
without
it's
not
absolutely
required
user
fills
out.
Their
information
accepts
privacy,
stuff
fills
out
their
first
name
and
role
for
the
first
name.
Last
name
enroll.
C
C
So
in
this
case
this
is
already
done
and
they
can
just
edit
it
right.
Okay,
because
we
we
already
know
that
the
plan
that
they
want
and
the
number
of
seats
that
they
want
is
just
one
okay,
and
so
then
they
enter
the
name
on
the
cut.
They
don't
have
to
fill
out
their
organization,
because
we
don't
actually
update
this
yeah,
that's
part
of
wanted.
They
don't
actually
have
an
organization.
C
B
C
E
Idea
is
it's
a
soft
deprecation
of
that?
We
know
that
people
that
sign
up
for
it
are
generally
confused
about
it
and
they
don't
get
all
the
features
anyway.
Eventually,
we
would
like
to
fully
deprecated
it,
but
that
would
that'll
require
a
lot
of
work
in
transitioning
people
that
currently
have
namespace
plans.
So
this
is
just
like
a
soft
abrogation,
basically
discouraging
people
from
doing
it.
Yeah.
C
D
Need
to
change
the
initial
state
like
if
it's
just
for
you
yep,
then
the
roster
yeah
initialize,
that
with
the
data
and
in
the
end
I
think
it's
still
fine.
Two
links
redirect
to
the
current
group
setting
page
I
think
it's
fine
for
the
first
iteration,
but
we
always
need
to
create
a
group.
That's
three
things.
B
B
D
B
B
D
C
Okay,
so
I
just
want
to
share
this
real
quick.
So
this
is
the
issue
for
when
a
user
inputs
are
their
credit
card
and
paste
directly.
So,
for
this
is
the
issue
for
this
page.
But
if
you
all
look
at
the
requirements,
section
I
tried
to
call
this
out
from
the
envision
link
but
like
when
a
user
has
selected
my
company
or
team
to
the
to
the
company
question
on
the
previous
screen
updates.
Your
organization
subscription
title
to
organization,
like
all
of
the
kind
of
differences,
are
called
out
in
this.
Yes,.
B
C
C
C
A
A
You
know,
even
when
we're
a
quarter
of
the
way
through
just
to
get
that
feedback
in
early
and
then
the
second
thing
is:
let's
also
do
you
the
design
walkthroughs
early
on,
so
that
we
can
cover
all
of
the
edge
cases,
Jensen
Thanks,
for
writing
all
of
the
edge
cases
out
in
the
requirements.
Sometimes
it
might
be
hard
to
understand
the
requirements
through
text.
A
B
A
B
D
C
C
A
C
C
Would
almost
suggest
that
you
guys
go
through
the
old
signup
flow
just
so
you
can
see
the
difference
because,
like
with,
if
I
went
through
it
like
two
days
ago,
this
is
such
a
huge
difference.
It's
like
it's.
It
almost
seems
like
it's
exactly
what
you
would
expect.
So
it's
not
super
impressive,
but
you
go
through
the
old
signup
flow
and
it's
like,
oh
my
gosh.
This
is
so
much
different.
It's
so
much
better!
It's
it's
incredible
to
see
and
I
just
think.
There's
gonna
be
so
many
more
people
to
make
it
through.