WEBVTT

00:00:04.910 --> 00:00:07.312 align:center
Hello, this is the engineering team.

00:00:08.132 --> 00:00:08.973 align:center
This is FinOps.

00:00:09.413 --> 00:00:10.794 align:center
Have you found any cost efficiencies

00:00:10.834 --> 00:00:10.974 align:center
yet?

00:00:11.554 --> 00:00:12.575 align:center
I don't have time for cost

00:00:12.635 --> 00:00:13.215 align:center
efficiencies.

00:00:13.776 --> 00:00:14.896 align:center
I have to fix the pipeline

00:00:14.936 --> 00:00:16.077 align:center
and deploy more AI.

00:00:17.578 --> 00:00:19.739 align:center
No, we need to find efficiencies.

00:00:20.260 --> 00:00:21.500 align:center
Who cares about saving costs if

00:00:21.540 --> 00:00:22.621 align:center
the pipeline is down?

00:00:22.701 --> 00:00:25.483 align:center
We need to find savings now!

00:00:44.475 --> 00:00:45.315 align:center
There's got to be a better

00:00:45.375 --> 00:00:45.596 align:center
way.

00:00:46.816 --> 00:00:47.237 align:center
There is.

00:00:47.837 --> 00:00:50.659 align:center
It's called .5. Who are you?

00:00:51.679 --> 00:00:52.600 align:center
Wait, are you AI?

00:00:52.930 --> 00:00:53.591 align:center
Are you?

00:00:54.652 --> 00:00:55.714 align:center
I don't even know anymore.

00:00:56.214 --> 00:00:56.915 align:center
What did you say?

00:00:57.616 --> 00:00:58.878 align:center
I can't hear anything in this

00:00:58.958 --> 00:00:59.719 align:center
stupid suit.

00:01:00.259 --> 00:01:01.621 align:center
Point 5 can help with that.

00:01:02.242 --> 00:01:02.622 align:center
How?

00:01:03.143 --> 00:01:04.805 align:center
Well, Point 5 helps engineers to

00:01:04.825 --> 00:01:06.207 align:center
own cloud efficiency.

00:01:06.267 --> 00:01:08.169 align:center
So you're not underwater and drowning

00:01:08.209 --> 00:01:09.831 align:center
in fixes while finance is asking

00:01:09.851 --> 00:01:10.973 align:center
you to just find savings.

00:01:11.514 --> 00:01:12.955 align:center
Does that mean I could finally

00:01:13.055 --> 00:01:14.277 align:center
take this thing off?

00:01:15.058 --> 00:01:15.438 align:center
It does.

00:01:21.326 --> 00:01:23.268 align:center
And teams actually see measurable savings?

00:01:24.029 --> 00:01:24.550 align:center
They do.

00:01:24.690 --> 00:01:26.232 align:center
With the waste detected by 0.5,

00:01:26.972 --> 00:01:29.174 align:center
teams see incredible savings, and usually

00:01:29.214 --> 00:01:30.275 align:center
within just a few weeks.

00:01:30.756 --> 00:01:31.717 align:center
So you wouldn't be lost at

00:01:31.757 --> 00:01:33.599 align:center
sea searching for efficiencies anymore.

00:01:34.399 --> 00:01:37.923 align:center
So, no more oceans of spreadsheets?

00:01:40.205 --> 00:01:41.586 align:center
I could finally see my family

00:01:41.667 --> 00:01:41.887 align:center
again.

00:01:43.308 --> 00:01:46.091 align:center
That is really dark, but hey,

00:01:46.411 --> 00:01:47.092 align:center
glad we could help.

00:01:47.873 --> 00:01:49.114 align:center
It feels so good to finally

00:01:49.174 --> 00:01:49.935 align:center
touch my face.

00:01:50.976 --> 00:01:51.696 align:center
It's been years.

00:01:52.377 --> 00:01:53.838 align:center
Okay, well looks like you guys

00:01:53.878 --> 00:01:54.539 align:center
are all set.

00:01:54.599 --> 00:01:55.460 align:center
I'll be on my way.

00:01:58.060 --> 00:01:59.341 align:center
efficiency that hits!