►
From YouTube: The Baseline Show - India
Description
The weekly office hours for the Baseline Protocol open source community. Learn more at https://baseline-protocol.org.
This is the India office hours hosted by Samrat Kishor | @samratkishor
A
Hey
everyone
we're
now
live
hi
designers.
Welcome,
so
welcome
once
again
to
another
episode
of
baseline
office
hours
in
india.
I'm
very
excited
about
this
new
community,
which
is
building
up
in
india.
My
name
is
amrat
kishore
and
I'm
one
of
the
technical
setting
committee
members
of
baseline
protocol,
as
well
as
the
head
of
community
in
india,
and
I'm
I'm
here
to
assure
you
that
there
are
tons
and
tons
of
announcements
which
are
coming.
A
So
you're
welcome
to
to
come
on
board
reach
out
to
me
on
linkedin
auditor,
and
we
can
start
interacting
and
we
can
and
you
can
come
on
board
if
you
are
watching
this.
Video
on
youtube
do
subscribe
to
the
channel.
This
is
a
common
channel
which
baseline
protocol
uses
to
communicate
all
announcements
as
well
as
host
office
hours
where
developers
can
come
and
and
get
support
on
things
that
they're
building
I'm
joined
with
chris
paul
he's
from
canada.
Chris.
A
I
would
ask
you
to
introduce
yourself
in
a
in
a
in
a
little
bit.
I'm
also
joined
with
mark
cattle
mark
is
from
the
enablement
team
of
baseline
protocol
and
I'm
going
to
talk
about.
You
know
big
time.
Today
we
are
going
to
talk
about
enablement.
How
do
we
go
to
market
so
so
two
sides
to
adoption,
which
I,
which
I
see
and
that's,
why
you
know
I
invited
my
top
mike
over.
A
You
know
this
saturday
morning
of
his
to
talk
about
enablement
and
go
to
market,
because
I
think
the
biggest
challenge
which
people
face
is
where
to
place
baseline
protocol.
I
think
that's
something
which
we
are
seeing
consistently.
Is
that
right,
mark
yeah,
so
so
correct?
A
Absolutely
so
so
I
think
a
lot
of
companies
which
have
reached
out
to
me
or
or
the
community
members
in
other
countries
as
well,
that
this
baseline
protocol
efforts
generally
fall
into
the
blockchain
guys
lab.
I
think
that
is
something
which
is
which
needs
to
change.
It
has
to
go
to
the
cio
or
the
cso,
and
then
we
start
looking
at
all
integrations
which
a
particular
organization
is
doing,
and
then
we
decide
so
on
one
side
it
can
be
integrations.
A
On
the
other
side,
you
can
be
a
product
organization
which
is
building
products
which
enable
multi-party
integrations,
intercompany
processes
and
cool
stuff.
Like
that,
so
you
know
in
any
b2b
transactions
there
are,
there
may
be
multiple
players
involved,
maybe
in
different
geographies,
maybe
in
different
countries
as
well.
So
what
baseline
protocol
does
is
it
provides
products,
a
set
of
tools
and
techniques
to
start
transacting
to
be
to
start
synchronizing
their
records
without
really
exchanging
any
data.
A
To
be
our
that
happens
to
be
our
war
cry,
you
know,
if
you
will
no
data
on
the
blockchain,
only
proofs
and
hashes
go
on
blockchain.
So
so
I
think,
with
that,
I'd
invite
mark
mark
talk
to
us
a
little
about
what
you
see
in
terms
of
enablement
and
adoption
for
baseline
protocol,
who
are
the
players
who
are
talking
to
you
and
what
are
the
day-to-day
conversations
that
they're
having
while
incorporating
baseline
protocol
in
their
current
or
future
products.
B
Well,
a
lot
of
us
basically
have
had
quite
a
bit
of
experience
in
the
blockchain
space
and
went
through
this
process
with
with
that
emerging
technology,
and
the
first
thing
that
we
keep
thinking
about.
Is
you
know
what
are
the?
B
What
are
the
well-meaning
mistakes
that
we
made
along
that
way
and
we
want
to
make
sure
that
we
do
not
have
you
know
a
repeating
of
that,
and
so
you
know
one
of
the
big
things
that
we
wondering
about
is
you
know
trying
to
look
at
it
for
through
the
eyes
of
the
audience.
B
You
know
what
is
it
that
you
know
what
we
are
bringing
is
going
to
make
their
lives
easier
or
at
least
make
their
lives?
You
know
suck
less
and
so
and
and
really
that's
you
know,
because
you
know
blockchain
technology,
you
know,
has
a
lot
of
very
powerful
capabilities.
It's
you
know,
making
people
that
are
not
the
true
believers
like
us,
you
know
become
true
believers,
and
so
I
mean
the
first
thing
that
we
want
to
do
is
take
a
look
at
you
know.
B
Any
type
of
process
that
is
already
either
fully
automated
or
you
know,
has
been
a
lot
of
the
low-level
tasks
have.
A
B
Largely
relegated
to
a
self-executing
environment
and
you
know
to
be
able
to
have
that
self-execution.
You
know
whether
it's
a
smart
contract
or
a
a
record
keeping.
You
know
it's,
it's
really.
You
know
a
lot
of
it.
We,
you
know
a
lot
of
it.
Pretty
much
sells
itself
as
soon
as
you
get
that
aha
moment
within
the
audience
where
they
basically
say.
Oh,
okay,
that's
exactly
how
this
works,
and
you
know.
A
B
We
do
with
an
enablement.
Is
we
really
de-emphasize
the
term
blockchain
yeah,
because
it
has
so
much
baggage
to
it,
because
the
minute
you
bring
up
blockchain
everyone's
mind
starts
thinking
either
about
cryptocurrencies
or
they'll
start.
You
know,
looking
at
some
other
type
of
use
case
that
they
might
have.
You
know,
read
about
within
the
past
two
years,
but
really
hasn't
seen,
production
or
has
failed
completely.
B
So
you
know
we
really
start
to
use
distributed
architecture
we'll
start
using
decentralized
environment.
That
generally
tends
to.
You
know
avoid
a
lot
of
the
baggage
that
the
term
blockchain
comes
with.
B
And
you
know
a
lot
of
times,
you
know
we
start
to
look
at
what
is
the
role
of
blockchain
technology
within
a
business
process
and
before
you
know
a
lot
of
people
when
they
were
starting
to
work
on
block
changes,
they
thought
of
them
as
either
entire
architectures
are
very,
very
robust
databases,
robust
and
expensive
databases,
and
you
know
right
now.
You
start
to
look
at
a
role
of
blockchain.
B
You
know
it
has.
Quite
you
know
a
little
bit
more
of
a
middleware
type
role,
specifically
within
baseline,
where
we
are
basically
proving
with
zero
knowledge
that
my
record-keeping
match
is
yours
and
that
really
attacks
one
of
the
persistent
problems
that
has
really
escaped
a
lot
of
technology
and
automation
is
back
office.
Reconciliation
generally,
that
is
going
to
be
anywhere
from
40
to
60
percent
of
your
operational
costs
are
in
that
lag
time.
You
know,
having
counterparties
agree.
B
I
record
keeping
matches
yours
and
so
especially
in
an
environment
to
where
I
don't
want
to
reveal
anything.
I
don't
want
to.
You
know,
give
my
competitors,
you
know,
maybe
an
advantage.
A
B
Revealing
something
I
want
to
be
able
to
you
know
it's
almost
like
two
messengers
on
the
other
side
of
a
wall.
You
know
my
name
is
tom.
What
is
and
he's
like,
my
name
is
my
name
is
john
and
you.
A
B
That
it's
going
to
be
correct
and
you
can
prove
it,
and
so
you
know-
and
that
brings
blockchain
away
from
being
that
single
source
of
truth
that
we
looked
at
you
know
when
we
were
really
starting
to
evangelize
blockchain
technology
into
you
know
with
baseline.
B
The
technology
is
more
that
proof
of
consistency
and
improving
that
consistency
is
really
key,
because
you
know
it
basically
takes
the
cycle
times
and
the
reconciliation
you
know
from
anywhere
from
days
or
months
to
mere
seconds
and.
B
And
so,
if
you
take
a
look
at
a
lot
of
different
environment,
business
environments
that
would
really
advan,
you
know,
you
know,
have
a
have
an
advantage
to
that.
You
know
within
supply
chain
within
identity
within
healthcare
is
one
that
I
you
know
always
could
bring
up
all
the
time,
because
healthcare
has
very
strict
data
privacy
requirements
to
where
they're
like.
I
am
very
limited.
B
What
I
can
do
as
far
as
trying
to
prove
a
consistency
in
my
data
sharing
and
handoff,
and
to
be
able
to
do
this
where
all
of
the
data
stays
within
each
system
of
record.
I
am
just
proving
to
you
that
my
record-keeping
match
is
yours,
and
so,
if
you
look
at
you
know
what
you
know
the
biggest
the
biggest
advantage
of
that
would
be
whether
the
cycle
times
involved
in
adjudicating
a
health
care
claim
within
the.
A
B
Yeah,
which,
which
even
in
under
ideal
conditions,
takes
60
to
90
days,
and
you
know
there
is
just
it's
an
enormous
amount
of
you-
know:
fraud
and
waste
that
really
come
about
from
exploiting
these
long
lag
times.
A
B
B
You
will
not
see
any
eroding
of
your
compliance.
You
will
not
see
anything
that
would
basically,
you
know,
cause
you
to
run
afoul
of
that.
So
I
mean
and
within
supply
chain
as
well.
You
know
having
to
you
know,
match
up.
You
know
when
you
start
to
see.
You
know
supply
chain
where
you
know
it's
easy
to
keep
the
first.
You
know
two
or
three
interactions
within
a
supply
chain.
It's
when
you
start
to
get
to
steps.
B
You
know
12
19
35,
you
know
around
in
there
and
most
of
the
people
that
far
downstream
have
no
idea
what
happened
back
in
the
origin.
This
way,
everyone
can
see
the
entire
movement.
A
B
And
so
I
mean
this
is
a
way
that
you
you
have,
that
you
know
that
transparency
and
it
kind
you
can
control
the
access.
As
far
as
you
know,
who's
allowed
to
see
it
and
all
of
that,
but
at
the
same
time
you
are
not
putting
any
data.
A
Yeah
exactly
exactly
you
know,
I
think
you
made
some
really
great
points
mark.
You
know
one
of
the
things
which
I
which
I
came
across.
You
know
one
in
in
a
recent
conversation
with
a
with
a
now
new
believer
of
baseline,
I
was
having
this
chat
and,
and,
and
you
know
it
came
out
that
it's
not
only
about
synchronization
saving
costs
and
time,
but
it's
also
about
a
great
experience.
A
You
know
when
you're
transacting,
with
an
organization
which
is
which
is
open
to
baselining
their
processes,
and-
and
you
know
that
that
also
means
you
know-
transactions
going
through
faster
payments,
going
through
faster,
no
friction
at
all.
You
know
everything
is
on
keto.
A
You
know
they
are
frustrated
at
times
doing
doing
stuff,
which
they
should
not
be
doing,
reconciling
and
making
calls
and
sending
emails
and
responding
to
all
those
calls
on
the
other
side.
So
so
I
think
it's
a
great
it's
a
win-win
for
all
parties
for
who
are
involved.
You
know
either
service
providers
or
or
even
you
know,
product
companies
who've
got
nothing
really
technology
in
general.
B
A
B
Are
having
trouble
either
scaling
or
really
completing
that
last
mile
yeah
baseline
allows
them
to
pivot,
while
still
maintaining
many
of
you
know
many
of
the
elements
of
the
service
agreement.
Look
instead
of
trying
to
build
this
entire
distributed
architecture.
B
That's
that's
really
an
advantage
that
you
know
that
we've
worked
out
within
baseline
we've
had
a
couple
of
the
participants,
some
of
the
companies
that
are
some
of
our
plank
holders.
Yeah
had
tremendous
success
coming
in
and
saying
you
know,
are
you
having
trouble
with
your
hyperledger
fabric?
B
Absolutely
you
know:
are
you
really
just
running
into
the
same
problems
that
so
many
other
people?
You
know
that
you
can
actually
pivot
away
from
this,
so
you
can
sleep
at
night,
and
so
you
can
actually
have
you
know
a
good
conversation
with
your
senior
management
when
they
ask
about
project
or
progress.
A
B
Because
a
lot
of
these
business
cases
were
still
fully
fledged
out,
it's
just
we
weren't
quite
using
the
best
tool
for
the
job
we
thought
so
at
the
time,
but
everyone
else
is
running
into
the
same
problems
with
scaling
and
just
really
especially
scaling,
but
also
the
last
mile.
When
it
comes
to
user
environments,
yeah
really
are
just
it's:
it's
success
has
become
elusive
and
yeah
baseline
is
a
way
to
actually
pivot
and
achieve
that
success.
A
Yeah
they
can
actually
get
rid
of
their
technical
debt.
I
think
they
can
also
talk
to
you
know,
as
you
rightly
pointed
out,
they
can
talk
to
their
senior
management
in
a
way
that
hey
you're,
cutting
out
you're
there
mark
oh
yeah
you're
here,
okay,
so
I
was
saying
that
you
know
one:
they
get
rid
of
the
technical
debt
that
they've
gathered
over
a
period
of
time
experimenting
with
various
blockchain
projects
in
various
shapes
and
forms.
A
They
can
also
look
at
you
know
the
investments
which
had
gotten,
I
think
that
it's
a
time
to
sort
of
salvage
them
and
and-
and
you
know
not
just
salvage,
of
course,
you
know-
one
side
is
of
course
salvaged,
but
the
other
side
is,
of
course,
thinking
of
a
new
business
model.
You
know
some
somewhat,
you
know
what
john
is
doing.
He
keeps
talking
about
it,
so
I
can
also
reference
to
it
that
he's
doing
securitization
of
invoices.
A
A
Can
exchange
data
can
synchronize
data
or
states
so
to
say
so.
So
I
think
very
important
point
that
you
brought
out
was
that
it's
the
last
mile.
I
think
that
part
a
lot.
A
lot
of
people
are
missing
that
you
know
the
the
conversation
goes
in
the
direction
of
you
know
which
blockchain
to
pick,
I
think
that's
a
different
conversation.
That's
not
the
conversation
that
a
baseliner
should
be
having
a
baseline
should
be
having
a
conversation
around
which
are
my
systems.
A
You
know
which
are
my
processes
which
need
baselining
right,
and
I
think
that's
why
I
keep
talking
to
people.
I
say
kyb
know
your
business,
you
know,
which
are
the
processes
which
are
required
to
talk
to
outside
parties
and
and
or
even
within
the
same
company,
two
different
entities
to
different
geographies.
I
mean,
I
know
a
company
which
is
doing
which,
which
has
for
people
sitting
just
consolidating
balance
sheet
from
from
their
multiple
countries
coming
in,
so
they
are
so
there
are
tons
of
use
cases.
A
I
think
the
industries
you
know
various
industries
are
are
full
of
places
where
there
are
transaction
interactions,
even
within
the
same
company
or
different
companies.
But
what
what
we
really
need
is
we
need
a
voice
within
the
organization
that
may
be
the
head
of
blockchain.
That
may
be
other
head
of
digital
transformation
that
maybe
the
cio
that
maybe
the
cdo
being
that
voice
and
and
taking
up
baseline
as
an
initiative
where
you
know
we
sort
of
go
scan
the
business
for
opportunities,
we
pick
up
the
ones
which
are
ripe
in
two
cents.
A
You
know
one
is,
of
course,
is
the
business
capable
of
handling
something
new
coming
in
you
know.
Is
it?
Is
it
open
to
that
change?
Second,
is
you
know
what
is
the
community?
Where
is
the
community
moving?
Where
are
these?
You
know
the
the
flag
bearers
or
the
the
plant
holders,
as
you
said,
are
moving
you
know
within
baseline
within
the
baseline
universe.
So
I
think
these
two
things
taken
care.
I
think
it
is
a
great
time
to
be
adopting
baseline.
A
That's
what
I
feel
this
is,
and
you
know,
as
I
said
in
the
last-
live
stream
as
well,
that
people
are
going
to
have
a
feeling
of
being
in
a
time
machine
when
they
see
you
know
people
who've
joined
in
now
versus
people
who
join,
let's
say
a
couple
of
years
down
the
line
so
they're
gonna
have
that
they're
gonna
have
that
feeling?
A
Second,
and
you
know
one
very
interesting
point,
I
think
it's
your
third
or
fourth
interesting
point.
I
think
you
just
added
so
many
kicks
to
this.
This
episode
mark.
Thank
you
so
much
for
making
it.
So
you
spoke
about
hyper
ledger
projects.
I
think
those
were
the
most
ambitious
one
and
those
were
the
ones
which
enterprises
had
jumped
on.
So
I
think
now
they
need
a
re-look
at
what
really
caused
that
failure.
A
You
know
were
we
aiming
for
the
stars
or
what
we
were
we
aiming
to
for
something
which
is
yes
purely
doable,
but
not
scalable
or
we
were
doing
for
or
we
were
aiming
for,
something
which
is
which
was
doable.
But
you
know
absolutely
nobody
knows
what
went
wrong
and
then
they
ran
into
a
situation
where
they,
their
investments
ran
out
and
they
they
all
you
know,
just
shunned
the
project
and
and
started
collaborating
on
other
things.
I
have
seen
all
these
three
categories
really.
A
You
know
I've
seen
I've
spoken
to
people
involved
in
all
three
categories
of
projects,
and
I
do
believe
when
they
see
this
either
they
speak
up
or
not.
But
when
I,
when
they
see
this,
they
are
going
to
have
a
feeling
that,
yes,
I
think
it
can
be
revived.
There
are
tons
of
projects
which
are
sitting
on
racks
which
can
be
pulled
out,
dusted
and
revived
by
you
know,
integrating
with
baseline,
something
like
baseline.
B
So
yeah,
I
would
say
a
common,
a
common
result
that
you
know
many
of
the
people
that
have
you
know
worked
within.
You
know
blockchain
use
cases
and
stuff.
Is
they
wind
up
with
a
solution
that
is
extremely
robust
and
it's
extremely
capable?
A
B
B
I
mean
it's
really
going
to
show
anything
yeah.
He
is
of
you
know
grave
importance
to
people
that
need
auditing
and
need
the
query
of
the
technology,
but
as
you're
just
going
through
a
regular
operational
environment.
Blockchain
is,
in
the
background,
just
absolutely
securing
everything,
but
you,
as
a
user,
are
not
going
to
notice
that.
A
B
Now,
with
baseline,
I
would
say
it's
you
know,
has
a
little
bit
more
visibility,
because
if
you
have,
you
know,
within
the
user
environment,
to
where
you're
dealing
with
different
counterparties-
and
you
have
a
certain
you
know,
piece
of
you
know
a
record
or
piece
of
data
that
you
need.
A
B
You
know
you
can
have
basically
a
small
icon
that
comes
up
that
says
baseline,
true
or
baseline,
false
if
you
use
a
boolean
and
you'll
just
be
able
to
say
yes,
this
is
baseline,
so
that
gives
you
just
by
having
you
know
certain
documents
or
certain
you
know,
elements
that
are
baseline,
that
are
proven.
You
now
have
that
confidence.
B
You
know
within
that
that
that
that
data
that
you're
you're
you're,
comparing
and
so
really,
where
was
I
going
with
this,
you
know
having
that
confidence
you
know
is
going
to
really
start
to
bring
forth
the
adoption,
because
you
know
confidence
is,
is
very
compelling.
It's
very
sexy.
It's
very.
B
B
What's
yeah,
you
know
well,
and
this
is
how
we,
how
we
explain
it
so
so,
within
the
enablement
team,
we
really
start
to
look
at.
You
know
what
is
it
that
we
want
to
be
heard
as
opposed
to
what
are
we
trying
to
tell
exactly?
I
think
that's
one
of
the
big
problems
that
we,
you
know
you
know
within
the
early
days
of
blockchain
was
we
were
so
passionate
about
the.
B
A
B
Yeah
a
chain
of
blocks
and
sort
of
stuff-
and
you
know
we
thought
that
was
so
cool
and
we're
looking
at
eyes
that
are
really
glazed
over
and
people
are
checking
their
watch
and
they're
starting
to
look
at
their
phone
and
they're
looking
around
because
we've
lost
them-
and
you
know
this
is
almost
like:
hey
come
on.
This
is
really
cool
they're
like
I'll,
be
the
judge
of
that.
Just
tell
me.
Let
me
show
me
something
that
is
going
to
be.
A
A
B
Yeah,
so
that's
really
what
we've
been
focused
on,
make
sure
that
we
still
have
that
audience.
Engagement
from
the
beginning
and
start
with
a
problem
and
say
this
is
this
is
what
you
live
and
breathe
every
day.
Well
then,
we
can
make
it,
you
know
so
much
simpler
and
you
can
actually,
you
know,
move
the
workflow
to
fruition
or
completion.
A
Yeah
yeah,
no,
absolutely,
I
think
I
think,
that's
a
great
thought
mark.
I
think
this
this
whole
messaging,
this
whole
shift
or
a
flip
in
messaging
that
you're
talking
about.
I
think
this
is
really
important
and
a
lot
of
people
miss
that
point.
You
know
they
just
they
just
blabber,
they
just
hammer
what
they
want
to
hammer
and
they
don't
want
to
listen
to
the
other
side,
and
especially,
I
feel
especially
talking
about
blockchain.
A
I
feel
when
people
start
throwing
things
like
you
know,
hash
rates
and
and-
and
you
know,
blocks
per
second
and
stuff
like
that-
I
think
I
think
that's
when
they
run
out
of
content
when
they
start
throwing
technical
stuff
to
throw
the
other
person
out
of
their
shoes.
So
I
think
it's
important
that
you
know
the
people
who
are
talking
about
enablement
should
be
the
ones
who
who
can
talk
about
business
value
first,
I
think
I
think
technology
comes
later
on.
A
You
know
when,
when
we,
when
we've
gone
through
the
gut,
then
comes
the
brain.
I
think
that's
the
that's
the
biggest
advantage.
I
see
in
baselines,
enablement
team
and
you
know
ably.
So
you
know
in
your
enabling
the
enablement
team-
I
would
say
that
so
so
kudos
kudos
to
the
works
of
our
mark.
Really,
I
think
I
think
I've
had
I've
had
a
lot
of
conversations.
I
know
I
would
also
share
you
know
now,
I'm
on
the
enablement
calls
as
well.
A
So
I
will
share
my
experiences
as
well
of
what
are
the
kind
of
questions
I'm
getting
and
I'm
sure
tons
of
our
other
members
are
also
getting
questions
from
leaders
who
want
to
join
in,
but
they
just
want
to
test
the
waters
first.
So
there
are
things
which
are
in
the
works.
There
are
some
indian
companies
as
well
who
are
calling
me
or
messaging
me.
In
fact,
I
got
messages
while
we
were
doing
this
so
so
you
would
have
seen
me
checking
my
phone
a
lot
of
times
because
they
were
constant
buzz.
A
So
so
there
is
a
there's,
a
lot
of
interest,
I
would
say
definitely,
but
people
seem
to
be
treading
very
carefully.
You
know,
after
that
whole
hype
and
and
fall
of
of
a
blockchain
people
at
some
point
in
time,
thought
that
you
know-
and
it
was
very
famously
tweeted
on
twitter
as
well
multiple
times
that
blockchain
has
a
problem.
Looking
for
solutions,
blockchain
is
the
solutions
looking
for
problems,
you
know
that
it.
B
Yeah,
a
big
shot,
a
big
shiny,
expensive
hammer
that
was
looking
for
nails
or
you
know
one
of
the
big
things
that
you
know
I
persistently
ran
into
was
you
know
you?
There
were
a
lot
of
assumptions
that
were
made
at
the
very
beginning
and
one
of.
A
B
I
think
probably
fatal
assumptions
that
were
made
was
that
blockchain
was
going
to
replace
much
of
the
existing
architecture.
Okay,
it's
new
distributed
robust
technology,
and
you
know
many
of
the
you
know,
people
that
you
were
you
know
really
pitching
the
adoption
to
were
people.
That
said,
look
we
are
either
in
the
middle
of
or
we
have
recently
completed
a
massive
multi-scale
erp
implementation.
B
Anyone
that's
ever
been
through
an
erp
implementation
knows
the
pain
that
is
involved
with
that,
and
it's
not
something.
People
want
to
go
through.
A
B
But
you
know
these
were
already
architectures
that
you
know
are,
you
know,
represented
multi-million
dollar
investments
over
multi-year
station
schedules
and
they
were
not
going
anywhere
and
so
say
we
like
your
blockchain
thing,
but
we're
already
too
deep
into
the
erp
and
we're.
B
B
I
mean
that
you
know,
can
then
prove
the
consistency,
and
you
don't
have
the
capital
investment
absolutely
anywhere
near
what
it
required
for
a
large
scale.
Implementation,
especially.
A
A
A
A
Exactly
you're
still
you're
still
sitting
on
the
same
problems.
You
know
you
just
have
a
fancy
container
to
keep
those
two
stores
or
products
problems.
So
just
with
a
just
with
a
bolt-on.
You
know
whether,
with
let's
say
two
to
five
percent
cost
and
that
too
in
opex
mode
you
can
you
can
get
rid
of
your
problems
and
you
know,
and
then
and
and
then
I
would
say
that
you
know
this
is
a
true
transformation,
not
just
implementation
of
a
new
cool
system.
B
A
B
Back
and
forth-
and
you
know
I
have
people
come
and
ask
me
they
say:
does
anyone
really
use
paper
anymore?
Yes,
they
do
yes,
because
that
is
what
their
service
agreement
calls
for,
and
that
is
what
they've
been
doing
for
decades,
and
you
know
there's
hey
this
this
process,
you
know
clumsy
and
expensive
as
it
may
be,
it
works
and
it
serves
the
purpose
that
we,
you
know,
have
been
working
on.
Why
are
we
necessarily
going
to
change
it?
We
can
try
and
digitize
it.
B
Maybe
do
some
batch
updates
and
do
you
know
you
know
some
some
back
and
forth,
but.
A
B
You
know
through
edi
or
some
other
protocol
yeah
they
basically
just
are
sitting
back
still
doing
the
the
same
process
and
so
the
transactional
costs.
You
know
when
you
start
to
look
at
the
larger
picture,
are.
B
You
know
one
other
thing,
one
other
aspect:
you
know
that
we
pay
attention
to
is
especially
when
you're
pitching
a
client
and
stuff
and
you're
explaining
to
where
hey
we're
going
to
eliminate.
You
know
the
reconciliation,
we're
going
to
eliminate
the
friction
and
the
lag
time
and
stuff
and
you'll
have
some.
You
know
we
had
a
client
that
basically
said
this
is
wonderful.
It's
incredible
get
out
of
my.
A
B
Because
you
know,
35
or
40
of
our
operational
revenue
is
on
multi-year
call
centers
that
we
operate
and
run.
You
know
to
you
know
that
to
tackle
this
persistent
problem
you're.
Basically,
if
we
did
this,
it
would
cannibalize
such
a
huge
portion
of
our
revenue
and
no
we're
not
going
to
do
it.
B
You
know
so
some
companies,
you
know,
are
in
the
business
we
are,
we
are
service
oriented
and
we
maintain
a
large.
You
know,
body
of
talent
and
resources
in
you
know,
checking
pushing
this
paper
checking
this
going.
A
B
Checking
all
this
going
back
and
forth
and
in
all
of
that
so
and
we're
paid
fairly
handsomely
for
it.
So
if.
A
A
B
A
A
A
No,
absolutely-
and
you
know
what
in
I
think
with
this-
you
know
I
was
talking
to
somebody
just
yesterday
and
and
and
he's
the
promoter
of
a
fairly
large
company
and
and
and
they're
into
the
business
of
invoice
discounting
and
their
company
when
they
started
off.
They
they
are
into
that
business
is
also
running
there
and
to
processing
invoices
on
behalf
of
their
clients,
they're
into
account,
payable,
processing
and
account
receivables
as
well
and
hro
as
well.
A
So
so
I
was
talking
to
the
promoter
of
the
company,
and
I
was
saying
that
you
know
this
gives
us
an
opportunity
to
create
a
gold
standard
of
an
organization
which
does
not
have
net
13
at
60.
It
pays
you
in
a
week
because
you
don't
need
you
don't
need
reconciliation,
don't
need
a
paper
trail
to
prove
that
the
service
or
the
goods
have
been
delivered.
A
B
A
B
At
at
the
invoice
level
I
mean,
if
you
have
you
know
they're,
you
know
they
will
have
a
like
a
database
saying
you
know,
don't
do
business
or
you
know,
make
sure
that
you're
really
getting
the
proper
documentation
and
assurances
from
this
invoice
seller
and
that
invoice
are
because
they've
been
known
to
sell
the
same
invoice
to
two
or
three
different
lenders
and
when
it
comes
time
to
collect
on
it,
it's
only
going
to
be
paid
once,
and
so
that
is.
A
A
B
This
basically
allows
you
know
to
you
know
to
have
have
had
that
confidence.
So
you
know
what
I
see
pretty
rapidly
within
the
invoice
financing
space.
Is
you
know
there?
There's
gonna
be
a
push
to
say:
we
only
want
baseline
invoices
and
we
will
give
better
terms
for
these
invoices
that
have
been
baselined,
because
we
know
we
have
the
singularity
and
we
have
the
permanence.
B
You
know
that
has
been
secured
by
the
proof,
and
you
know
we
have
that
extra
confidence,
so
we're
going
to
give
you
know
more
attractive
terms
and
at
the
same
time,
you
know,
probably
in
tandem
you're,
going
to
have
certain
lenders
that
are
going
to
say
unless
your
invoices
are
baseline,
don't
even
call.
A
Them,
oh
yeah,
exactly
exactly
so.
You
create
that
tier.
You
know
you've
played
that
year
by
means
of
business
practices.
You
know
people
would
love
to
work
with
companies
like
that.
So
so
I
think
I
think
you
know
with
this
and
since
this
show
is
happening
in
india.
You
know
I
would
say
that
there
are
two
things
which
I
wanted
to
bring
out
one.
There
was
a
there's,
a
very
famous
entrepreneur.
I
don't
know
if
I
should
be
naming
him,
but
I
can't
name
him
because
you
know
we
named
things
right.
A
So
so
he's
he's
kanal
shah
he's
he's
probably
the
most
successful
fintech
entrepreneur
that
I
follow
he's
built
cred.
You
know
he's
he's
and
that's
now
in
the
world,
top
50,
fintech,
apps
and
people
are
having
difficulty
in
figuring
out
his
business
model.
I
mean
he's,
he's
sharp,
so
he
had
tweeted
some
days
back
that
in
india
the
biggest
employer
is
not
a
government
agency.
A
A
If
there
was
a
paper
trail
going,
okay,
fine,
I
can
make
a
email
flow,
but
nobody
is
looking
at
process
transformation
saying
that
is
that
step
really
required
right.
So
a
lot
of
the
a
lot
of
the
products
which
are
built,
I
would
say
in
the
past
five
years-
are
so
built
in.
By
with
that
principle,
you
know
I'm
digitizing,
I'm
removing
paper,
but
while
you're
removing
paper
you
you've
got
this.
You
know
you've
got
this
nuts
and
bolts
opened.
So
you
look
under
the
hood
and
see
what
is
really
required.
A
You
know
there's
process
transformation
which
can
go
hand
in
hand.
Because
what
really
happens
is
you
know
you
implement
a
software
and
then
you
look
at
process
transformation
and
then,
when
the
process
transformation
has
happened,
then
you
realize
that
your
software,
which
was
implemented
very
recently,
is
of
no
use
or
lesser
use
than
what
your
envisaged,
and
that
is
why
the
value
you
know.
A
I
think
this
was
something
which
I
was
reading
a
few
days
back,
that
you
know
billions
of
dollars
go
into
digital
transformation
projects
but,
like
you
know,
almost
80
to
90
percent
fail
and
that's
the
and
and
it's
only
because
people
are
getting
the
getting
the
sequence
wrong.
So
to
say,
the
other
thing
which
I
wanted
to
bring
out
is
you
know
it's
only
a
matter
of
time.
You
know
india
has
looked
at
the
back
office
of
the
world.
A
You
know
a
lot
of
companies
are
operating
here
which
are
which
are
serving
customers
and
sometimes
their
own
offices
and
other
geographies
are
doing
doing
processes
so
there's
process
excellence,
definitely
hello
to
the
guest
new
baseliner.
Exactly
then
there
is
then
there
is
so
a
lot
of
people
are
doing
pros
these
processes
sitting
here.
It
may
be.
You
know
something
as,
as
you
know,
as
basic
as
medical
transcription,
for
example,
or
it
can
be
something.
As
you
know,
you
know
it
can
be
something
as
complex
as
fund
accounting.
A
You
know
it
can
be,
can
be
both
ways.
It
can
be
complex,
so
there's
a
whole
pyramid
which
I
see
which
is
built
here.
So
on
one
side
I
see
you
know,
there's
tons
of
transactions
which
are
which
are
being
passed
on
to
these
entities,
because
the
parent,
the
the
customers,
don't
want
to
do
them
with
themselves
or
you
know
when
you
go
higher
up
in
the
in
the
in
the
food
chain
or
or
the
process
chains,
how
to
say
the
processes
which
require
intelligence
that
have
also
started
coming
to
us.
A
That
is
also
you
know.
Even
software
development,
software
engineering
or
even
you
know,
financial
engineering
fund,
accounting
quant.
A
lot
of
quant
work
is
happening
here,
so
you
know
that
needs
specialist
skills.
So
so
I
feel
that
it's
just
in
the
mindset
that
people
when
people
start
looking
at
these-
you
know
these
opportunities.
You
know
that
you
know
what
there's
a
better
way
to
do.
A
This
there's
a
better
way
to
avoid
these
10
steps
in
a
process
and
look
at
a
highly
optimized
way
of
doing
this,
and
how
is
technology
augmenting
that
process
which
you've
just
designed
by
bringing
in
you
know
things
like
baseline,
I'm
not
saying
baseline,
don't
bring
baseline
blindly
baseline
again,
just
like
blockchain
baseline
again
cannot
solve
all
problems.
It
has
to
be.
You
know,
human
technology
process,
people
everything
goes
together.
So
so
you
know
back
to
my
discussion
back
to
our
discussion.
I
think
I
was.
A
I
was
trying
to
point
out
that
a
lot
of
companies
here
have
their
revenue
at
risk,
because
their
clients
will
eventually
it's
a
matter
of
time.
They
will
eventually
realize
that
the
inefficiencies
which
I
had
I
have
just
you
know
I've
just
put
it
in
somebody
else's
card,
and
I
may
be
paying
this
guy
by
the
hour,
sometimes
or
by
the
number
of
efficiency
inefficiencies
just
to
take
care
of
of
something
which
could
have
been
automatically
synchronized
using
things
like
baseline.
A
A
We
call
it
gic's
global
in-house
centers,
so
those
those
companies
should
start
looking
at
the
revenues
and
look
at
revenue
which
is
at
risk
of
being
disrupted
by
such
technology
coming
in
and
start
investing
in
things
like
baseline,
so
that
if
they
come,
if
they
come
with
their
own
platforms,
you
know
imagine
imagine
an
infosys
or
an
accenture,
I'm
just
taking
this
popping
these
names
out
out
of
my
head.
A
If
they
came
up
with
platforms
like
these
and
they
went
to
their
clients,
saying
you
know
what
we,
while
we
do,
your
accounting,
you
know
we
have
we,
we
do
your.
You
manage
your
ops,
you
manage
your
account
payables,
we
can
do
it.
You
know
here
is
our
platform.
If
you
integrate
your
erp
with
your
ven,
we
are
going
to
give
you
a
vendor
portal.
The
vendors
can
have
access
to
this
portal.
We
are
giving
you
an
api.
The
vendors
can
also
integrate.
A
With
the
same
with
the
same
platform,
this
whole
platform
can
just
take
care
of
all
synchronizations
and
we
can
just
keep
looking
at.
You
know
if
there
are
any
breaks
if
at
all,
if
there
is
any
debased,
because
I'm
sure
you
know
there'll
be
debates
records
as
well
and
there
will
be
somebody
required
to
look
at
those
as
well,
but
the
quantum
is
going
to
be
like
a
fraction
yeah
the
whole.
A
B
Well,
and
and
another
you
know,
big
start,
you
know
important
thing
that
we
do
within
the
enablement
team
is
you
know
we
sit
there
and
really
want
to
define
what
baseline
really
is
for
the
audience,
and
it
really
helps
by
defining
what
it
isn't.
B
Because
we
commonly
say
that
you
know
baseline
is
not
a
product,
it's
not
a
coin,
it's
not
a
a
a
different.
You
know
workflow
package
or
anything.
It's
a
technique.
B
Consistency-
and
you
know,
and
the
only
thing
that
is
being
secured
is
using
blockchain
as
that
proof
of
consistency
that
that
that
that
neutral,
umpire
between
counterparties.
That
basically
says
you
know
it
makes
no
judgments,
it
parses,
no
data,
it
basically
says
true
or
false.
Yes,
this
baseline
and
yeah.
You
know
that
right
there,
you
know
everybody
seems
to
think
that
I'm
going
to
have
to
basically
revamp
my
entire
architecture,
I'm
going
to
have
to
either
make
a
huge,
substantial
capital
investment
just
to
try
and
capture
this
capability.
B
A
B
Another
thing
is,
is
you
know
if
you
have,
you
know
different
state
machines
that
are
on
entirely
different?
You
know
operating
environments,
operating
systems
and
yeah,
but
so
long
as
you
have
that
type
of
translation
between
you
know,
whatever
data
point,
you
know
it
all
happens,
so
yeah
baseline.
Basically
it
doesn't
introduce
anything
particularly
new
because
it
basically
says.
A
B
A
I
think
it's
it's.
It's
really
key
that
we
understand
that
you're
not
required
to
rip
off
any
of
the
existing
systems.
Your
value
of
your
technology
investments
is
not
going
to
depreciate
it's
it's.
It's
just
augmenting
your
existing
operations
and
in
the
process
also
eliminating
inefficiencies
absolutely
so
so
mark.
A
I
had
also
committed
that
we
will
talk
about
insurance
and,
while
you've
touched
upon
it
a
bit,
you
know
in
your
previous
example,
but
we
want
to
talk
about
what
what's
the
difference
is
going
to
cause
to
insurers,
as
well
as
people
who
are
processing
insurance
claims.
You
know
there
are
a
lot
of
claims
processing
sort
of
bpos,
also
based
out
in
india,
so
we
can
use
that
messaging
for
for
these
companies
as
well.
A
B
Absolutely
and
right
now
you
know
messaging
is
what
they've
largely
been
doing
and
the
best
they've
been
able
to
try
and
tackle
it
is
through
edi,
which
is,
you
know,
coming
up
on
40
years
old
somewhere
around
in
there,
and
just
because
this
is
what
we've
always
been
using
as
crafty
and
leaky
as
it
may
be.
B
This
is
yeah,
really
it
beats
having
to
you
know,
take
a
stack
of
papers
and
mail
them
back
to
the
mail
them
back
to
you
know
the
the
healthcare
payer
and
I'm
like
well,
that's
still
done
and
really
and
it's
a
lot
of
the
innovation
is
is
is,
is
stymied
by
you
know
the
very
strict,
very
draconian
actually
data
privacy
laws
that
exist
for
a
reason
I
mean
within
hipaa
and
phi.
B
Reveal
anything-
or
I
run
a
foul
of
of
this
governing
body
and
I'm
now
subject
to
enforcement
action
and
I
don't
have
an
appeal
process
so
if
they,
if
they
say
I
did
wrong,
I
have
to
pay
the
fine.
I
mean
I
really
can't
fight
it.
A
B
That's
very
commonly
done,
but
the
big
thing,
if
you
take
a
look
at
how
you
have
to
you,
know,
really
go
through
the
process
of
documenting
billing
and
paying
for
your
healthcare
treatments.
You
know
most
people
don't
really
see
it.
You
know
how
much
is
going
back
now.
B
They
will
see
a
lot,
you
know
say
a
particular
procedure
or
what
we
would
call
an
episode
of
care
and
say
you
had
a
colonoscopy
and
you
know
within
the
u.s,
let's
just
assume
that
all
of
the
providers
are
that
are
involved
are
in
your
network
and
most
people
when
they
are
having
a
procedure,
the
only
you
know.
B
B
That
the
the
anesthetists
or
the
anesthesiologist,
of
course,
is
gonna,
build
twice
because
they're
gonna
bill
for
the
service
and
then
they're
gonna
bill
for
the
medication
yeah
that
they
used,
and
so
you
know
pretty
soon.
If
you
have
a
have
a
procedure
done,
you
know.
Within
a
week,
you're
gonna
have
anywhere
from
eight
to
ten
pieces
of
mail.
All
of
them.
You
know
securing
their
place
within
the
providing
of
your
health
care
service
and.
A
B
All
of
that
secures
the
entire
claim.
You
know
the
body
of
data
that
goes
into
building
everything
that
goes
around
your
particular
claim
and.
A
B
There
is
so
much
back
and
forth
that
most
you
know,
patients
or
users,
you
know,
would
never
see,
and
so
I
I
think
they
make
it.
A
B
A
B
Right
and
you
know,
especially
when
you
have
every
few
years,
you're
going
to
have
an
updating
of
the
medical
billing
and
coding
taxonomy
to
where
you
used
to
use.
You
know
code,
one
two,
three
four
now
uses
code,
one
two,
three,
four:
five:
six,
because
they've
added
so
many
new
codes
and
subsets
of
addict
of
existing
code.
B
Taxonomy
to
the
entire
body
of
that,
and
so
it
creates
another
inconsistency
that
has
to
be
worked
out
and
just
because
of
the
data
privacy
requirements.
The
only
way
of
doing
this
is
through
a
very
cumbersome
friction
process.
A
B
So
you
know
baseline
is
so
poised
to
cut
through.
So
much
of
that
and
yes,
there
will
be
some
cottage
industries
that
will
be
completely
disruptive,
just
absolutely
and
absolutely
the
process.
But
that
is
you
know
you
don't
you
cannot
make
an
omelette
without
cracking
an
egg,
so
there
will
be
a
lot
of
eggs
that
will.
B
That's
something
you
want
to
be.
You
want
to
be
aware
of,
because,
if
I'm
getting
to
a
services
company,
who
really
has
a
vested
interest
in
you
know
this,
the
process
being
is
frictioned
yes,
possible.
They're,
not
gonna,
be
very
receptive
to
it.
So.
A
Already
really
now,
somebody,
you
know,
put
up
a
really
interesting
name
on
the
chat
which
is
reliance
industries,
so
reliance
industries
is
the
biggest
probably
the
biggest
company
in
india,
which
is
into
everything
you
know
it's
interesting.
It's
into
consumer
goods
into.
It's
got
the
largest
telecom
player
largest
data
provider.
A
They
are
into
hospitals,
healthcare,
even
they're,
even
doing
a
lot
of
research
based
research
as
well.
So
I
think
for
for
a
company
like
that
adopting
this
their
their
chief
digital
officers,
should
be
talking
to
them
because
a
lot
of
times
you
know
what
I
feel
is
that
their
their
insurance
claims
would
have
been
processed.
You
know
they
would
also
come
into
this
the
supply
chain.
So,
let's
say
in
the
in
the
overall
five
or
six
entities
that
you
just
spoke
about.
B
And
so
so
much
of
that
process
is
yeah.
Ultimately
you
know
it
has
the
has
the
effect
of
you
know
it.
Delays,
pain.
A
B
Within
the
insurance
space,
one
thing
that
all
of
the
healthcare
payers
are,
you
know
trying
to
do.
Is
they
want
to
make
sure
that
the
you
know
the
claim
is,
you
know,
paid
settled
and
closed
the
the
most
efficient,
most
advantageous
time
possible.
B
A
You
know,
while
it
yeah
while
calling
it
while
calling
it
body
of
knowledge,
used
to
be
a
very
positive
term,
which
I
understood,
I
think,
calling
things
as
body
of
data.
It's
really
it's
really
intriguing,
for
you
know
it's
positive
and
negative,
both
at
the
same
time,
because
you
know
people
are
sitting
on
tons
of
data,
some
companies
know
how
to
do
how
to
deal
with
it.
A
Some
companies
absolutely
have
no
idea
how
to
how
to
deal
with
it,
and-
and
you
know
if,
if
they
really
dig
deep,
they
might,
they
might
find
that
you
know
40
50
of
that
is
not
usable
at
all
or
could
have
been
avoided
yeah,
so
so
so
those
are
the
kind
of
transformations
we
are
talking
about
here
on
the
on
the
baseline
on
the
baseline
show
so
so
mark.
I
think
we
are
on
the
top
of
the
hour.
We
can
probably
close
this
call.
I
think
it
was.
It
was
a
really
interesting
discussion.
A
You
know
we
had
today
thanks
thanks
so
much
for
sparing
time
for
this
one,
and
I
truly
appreciate
you
know
your
insights.
I
I
hope
people
on
youtube
also
find
some
value
in
this
discussion
and
if
people
are
watching
it
in
future,
then
do
share
with
with
your
techy
friends
and
people
whom
you
feel
should
be
using
baseline
and
also
subscribe
to
the
channel,
because
we
keep
sending
out
updates
through
the
channel.
Thank
you
so
much
mark
with
that.