WEBVTT

00:00:00.050 --> 00:00:01.634 align:center
Hi, my name is Ryan.

00:00:01.734 --> 00:00:03.038 align:center
I am the founder of a

00:00:03.138 --> 00:00:04.301 align:center
company called Rootly.

00:00:04.361 --> 00:00:06.226 align:center
We are an HR technology company

00:00:07.148 --> 00:00:09.675 align:center
and about two years ago one

00:00:09.715 --> 00:00:10.818 align:center
of the key members of our

00:00:10.958 --> 00:00:12.783 align:center
team was getting ready to move

00:00:12.863 --> 00:00:14.367 align:center
on to bigger and better things

00:00:14.768 --> 00:00:15.530 align:center
and it had us

00:00:15.690 --> 00:00:17.432 align:center
kind of facing the decision of

00:00:17.513 --> 00:00:18.874 align:center
whether or not we fill that

00:00:18.995 --> 00:00:21.518 align:center
void with another full-time salaried employee

00:00:21.759 --> 00:00:23.301 align:center
or do we go the agency

00:00:23.381 --> 00:00:26.285 align:center
route and so started googling and

00:00:26.425 --> 00:00:28.728 align:center
searching and looking around and combing

00:00:28.768 --> 00:00:31.332 align:center
through linkedin posts and vacancy quickly

00:00:31.352 --> 00:00:32.834 align:center
arrived at the top of our

00:00:32.914 --> 00:00:35.057 align:center
list of an agency that we

00:00:35.137 --> 00:00:36.459 align:center
really wanted to talk to and

00:00:37.180 --> 00:00:38.482 align:center
to get a better understanding of

00:00:38.903 --> 00:00:39.824 align:center
so we set up a call

00:00:39.864 --> 00:00:41.406 align:center
with vacancy and from our very

00:00:41.486 --> 00:00:43.829 align:center
first interaction we were blown away

00:00:43.910 --> 00:00:44.250 align:center
with

00:00:44.270 --> 00:00:45.555 align:center
by how great they are.

00:00:46.439 --> 00:00:47.663 align:center
On our initial call, they took

00:00:47.744 --> 00:00:50.113 align:center
so much time to understand the

00:00:50.173 --> 00:00:52.523 align:center
company, the technology, the customers, the

00:00:52.764 --> 00:00:54.430 align:center
users, and to ask some

00:00:54.650 --> 00:00:57.514 align:center
extremely thoughtful questions and to offer

00:00:57.534 --> 00:00:59.837 align:center
insight and advice on how things

00:00:59.978 --> 00:01:01.320 align:center
may be able to work.

00:01:01.340 --> 00:01:02.381 align:center
And after about two or three

00:01:02.421 --> 00:01:04.204 align:center
phone calls, we felt comfortable enough

00:01:04.404 --> 00:01:05.806 align:center
with giving a small piece of

00:01:05.846 --> 00:01:07.889 align:center
the project to Bakency in the

00:01:07.949 --> 00:01:09.331 align:center
back of our minds, thinking this

00:01:09.411 --> 00:01:10.633 align:center
was going to be, you know,

00:01:10.693 --> 00:01:12.656 align:center
a three or six month engagement.

00:01:13.377 --> 00:01:14.959 align:center
We are now going on to

00:01:14.979 --> 00:01:17.042 align:center
the end of our second year

00:01:17.423 --> 00:01:18.825 align:center
of working with Bakency.

00:01:19.406 --> 00:01:21.969 align:center
We've been completely blown away, impressed

00:01:22.210 --> 00:01:22.350 align:center
at

00:01:22.430 --> 00:01:25.157 align:center
every possible opportunity as we've been

00:01:25.197 --> 00:01:26.901 align:center
working with them and in my

00:01:26.962 --> 00:01:28.866 align:center
mind there are three key areas

00:01:29.167 --> 00:01:31.453 align:center
where vacancy really shines.

00:01:31.934 --> 00:01:35.163 align:center
The first is communication and in

00:01:35.584 --> 00:01:38.110 align:center
a situation like this communication is

00:01:38.140 --> 00:01:39.362 align:center
absolutely critical.

00:01:39.462 --> 00:01:40.484 align:center
I don't have to sell anybody

00:01:40.544 --> 00:01:42.327 align:center
on that, but vacancy has been

00:01:42.367 --> 00:01:44.631 align:center
available to answer questions, to offer

00:01:44.812 --> 00:01:45.232 align:center
insight.

00:01:45.593 --> 00:01:47.055 align:center
We try to operate in a

00:01:47.156 --> 00:01:49.800 align:center
pretty calm manner, but it's software

00:01:49.880 --> 00:01:52.485 align:center
and sometimes things go wrong after

00:01:52.565 --> 00:01:53.246 align:center
working hours.

00:01:53.687 --> 00:01:55.610 align:center
Vacancy has been completely responsive in

00:01:55.650 --> 00:01:56.472 align:center
those situations.

00:01:56.492 --> 00:01:57.694 align:center
I've always come up with a

00:01:57.774 --> 00:01:59.357 align:center
solution to get things taken care

00:01:59.417 --> 00:02:01.360 align:center
of quickly and effectively.

00:02:01.760 --> 00:02:03.926 align:center
The second way that vacancy really

00:02:04.006 --> 00:02:07.234 align:center
shines is in competency, meaning I

00:02:07.254 --> 00:02:09.500 align:center
have never doubted the skills and

00:02:09.580 --> 00:02:10.844 align:center
ability of the people that have

00:02:10.864 --> 00:02:12.528 align:center
been assigned to our project.

00:02:13.992 --> 00:02:16.398 align:center
There have been times where things

00:02:16.479 --> 00:02:17.060 align:center
have been

00:02:17.200 --> 00:02:18.804 align:center
brought to the table that weren't

00:02:18.964 --> 00:02:20.167 align:center
on our radar and end up

00:02:20.267 --> 00:02:22.031 align:center
getting into the product because they

00:02:22.071 --> 00:02:24.517 align:center
were exactly what the product needed.

00:02:24.537 --> 00:02:27.243 align:center
The third thing that Bakency does

00:02:27.283 --> 00:02:30.631 align:center
really well is collaborates and very

00:02:30.791 --> 00:02:31.934 align:center
much connected to the point that

00:02:31.974 --> 00:02:32.836 align:center
I was just making.

00:02:33.176 --> 00:02:34.780 align:center
This isn't...

00:02:34.400 --> 00:02:37.147 align:center
us needing to dictate every single

00:02:37.187 --> 00:02:38.510 align:center
little thing to vacancy or it

00:02:38.530 --> 00:02:40.395 align:center
doesn't get done, vacancy takes the

00:02:40.455 --> 00:02:41.798 align:center
project and they run with it.

00:02:42.079 --> 00:02:44.464 align:center
They adopt it as their own

00:02:44.605 --> 00:02:45.046 align:center
product.

00:02:45.387 --> 00:02:48.053 align:center
They make adjustments and improvements that

00:02:48.715 --> 00:02:50.459 align:center
we didn't ask for but have

00:02:50.539 --> 00:02:50.920 align:center
become.

00:02:52.430 --> 00:02:54.253 align:center
fantastically effective things for our

00:02:54.313 --> 00:02:54.834 align:center
customers

00:02:54.955 --> 00:02:55.856 align:center
and our users.

00:02:56.457 --> 00:02:58.421 align:center
The developer that we've been assigned,

00:02:58.461 --> 00:03:00.805 align:center
Ashvin, has become more than just

00:03:00.826 --> 00:03:01.507 align:center
a developer.

00:03:01.567 --> 00:03:03.490 align:center
He's a friend of mine and

00:03:03.531 --> 00:03:04.873 align:center
he's somebody that I trust with

00:03:04.973 --> 00:03:06.396 align:center
our product and with our company

00:03:06.456 --> 00:03:06.716 align:center
name.

00:03:07.277 --> 00:03:08.500 align:center
I joke with him about him

00:03:08.560 --> 00:03:10.363 align:center
being the superhero because there have

00:03:10.383 --> 00:03:12.187 align:center
been multiple times where he saves

00:03:12.267 --> 00:03:14.090 align:center
the day with...

00:03:13.850 --> 00:03:15.552 align:center
you know, a fix or a

00:03:15.733 --> 00:03:17.155 align:center
piece of the product that wasn't

00:03:17.275 --> 00:03:18.456 align:center
on our radar that ends up

00:03:18.496 --> 00:03:20.639 align:center
being something absolutely fantastic.

00:03:21.280 --> 00:03:22.842 align:center
Disha who's just joined our team

00:03:22.902 --> 00:03:25.226 align:center
has been absolutely phenomenal and really

00:03:25.326 --> 00:03:27.629 align:center
shines when it comes to communication

00:03:27.889 --> 00:03:30.473 align:center
and collaboration on this project and

00:03:30.513 --> 00:03:32.075 align:center
making sure we know exactly where

00:03:32.115 --> 00:03:33.597 align:center
we're going and her taking the

00:03:33.657 --> 00:03:34.859 align:center
reins and making sure that it

00:03:34.899 --> 00:03:35.380 align:center
gets there.

00:03:36.201 --> 00:03:37.042 align:center
If I had to do this

00:03:37.182 --> 00:03:38.384 align:center
over again, there isn't a doubt

00:03:38.464 --> 00:03:40.146 align:center
in my mind that I would

00:03:40.206 --> 00:03:42.249 align:center
select vacancy to jump in and

00:03:42.650 --> 00:03:42.910 align:center
take

00:03:43.180 --> 00:03:44.564 align:center
this role with our company.

00:03:44.765 --> 00:03:47.754 align:center
I've been extremely impressed with every

00:03:48.075 --> 00:03:49.500 align:center
aspect of the way that Vacancy

00:03:49.941 --> 00:03:50.623 align:center
does business.

00:03:51.084 --> 00:03:52.689 align:center
We are super fortunate to have

00:03:52.710 --> 00:03:53.572 align:center
them on our team and are

00:03:53.592 --> 00:03:54.796 align:center
really looking forward to see where

00:03:54.856 --> 00:03:55.298 align:center
things go.

00:03:55.859 --> 00:03:56.120 align:center
Thanks!