WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:02.750 align:start position:0% New<00:00:00.520> Google<00:00:01.000> AI<00:00:01.280> updates<00:00:01.880> are<00:00:02.160> absolutely 00:00:02.750 --> 00:00:02.760 align:start position:0% New Google AI updates are absolutely 00:00:02.760 --> 00:00:04.430 align:start position:0% New Google AI updates are absolutely insane<00:00:03.440> and<00:00:03.560> this<00:00:03.760> week<00:00:04.000> was<00:00:04.160> one<00:00:04.280> of<00:00:04.360> the 00:00:04.430 --> 00:00:04.440 align:start position:0% insane and this week was one of the 00:00:04.440 --> 00:00:06.550 align:start position:0% insane and this week was one of the biggest<00:00:04.760> weeks<00:00:05.080> Google<00:00:05.440> has<00:00:05.600> had<00:00:05.840> all<00:00:06.000> year. 00:00:06.550 --> 00:00:06.560 align:start position:0% biggest weeks Google has had all year. 00:00:06.560 --> 00:00:08.990 align:start position:0% biggest weeks Google has had all year. Five<00:00:06.920> things<00:00:07.240> dropped,<00:00:07.840> a<00:00:07.920> new<00:00:08.200> voice<00:00:08.520> model 00:00:08.990 --> 00:00:09.000 align:start position:0% Five things dropped, a new voice model 00:00:09.000 --> 00:00:10.990 align:start position:0% Five things dropped, a new voice model that<00:00:09.200> talks<00:00:09.640> and<00:00:09.800> thinks<00:00:10.200> at<00:00:10.360> the<00:00:10.440> exact<00:00:10.760> same 00:00:10.990 --> 00:00:11.000 align:start position:0% that talks and thinks at the exact same 00:00:11.000 --> 00:00:13.390 align:start position:0% that talks and thinks at the exact same time,<00:00:11.560> an<00:00:11.800> AI<00:00:12.120> agent<00:00:12.720> that<00:00:12.920> got<00:00:13.080> its<00:00:13.240> own 00:00:13.390 --> 00:00:13.400 align:start position:0% time, an AI agent that got its own 00:00:13.400 --> 00:00:15.470 align:start position:0% time, an AI agent that got its own Google<00:00:13.720> account<00:00:14.320> and<00:00:14.440> now<00:00:14.640> runs<00:00:15.000> a<00:00:15.120> whole 00:00:15.470 --> 00:00:15.480 align:start position:0% Google account and now runs a whole 00:00:15.480 --> 00:00:17.830 align:start position:0% Google account and now runs a whole household,<00:00:16.200> a<00:00:16.280> brand<00:00:16.600> new<00:00:16.800> image<00:00:17.120> tool<00:00:17.600> built 00:00:17.830 --> 00:00:17.840 align:start position:0% household, a brand new image tool built 00:00:17.840 --> 00:00:19.790 align:start position:0% household, a brand new image tool built straight<00:00:18.160> into<00:00:18.360> Google<00:00:18.640> Docs<00:00:18.920> and<00:00:19.040> Slides,<00:00:19.720> a 00:00:19.790 --> 00:00:19.800 align:start position:0% straight into Google Docs and Slides, a 00:00:19.800 --> 00:00:21.470 align:start position:0% straight into Google Docs and Slides, a personal<00:00:20.240> story<00:00:20.600> app<00:00:20.720> that<00:00:20.880> went<00:00:21.040> live<00:00:21.320> for 00:00:21.470 --> 00:00:21.480 align:start position:0% personal story app that went live for 00:00:21.480 --> 00:00:24.230 align:start position:0% personal story app that went live for everyone<00:00:21.840> in<00:00:22.040> the<00:00:22.160> US,<00:00:22.880> and<00:00:23.000> a<00:00:23.040> map<00:00:23.680> of<00:00:23.880> 9 00:00:24.230 --> 00:00:24.240 align:start position:0% everyone in the US, and a map of 9 00:00:24.240 --> 00:00:26.550 align:start position:0% everyone in the US, and a map of 9 billion<00:00:24.600> changes<00:00:25.080> to<00:00:25.200> human<00:00:25.480> DNA.<00:00:26.280> I<00:00:26.360> want<00:00:26.480> to 00:00:26.550 --> 00:00:26.560 align:start position:0% billion changes to human DNA. I want to 00:00:26.560 --> 00:00:28.430 align:start position:0% billion changes to human DNA. I want to go<00:00:26.720> through<00:00:27.040> all<00:00:27.200> five,<00:00:27.800> but<00:00:27.920> I<00:00:27.960> want<00:00:28.120> to<00:00:28.200> start 00:00:28.430 --> 00:00:28.440 align:start position:0% go through all five, but I want to start 00:00:28.440 --> 00:00:30.750 align:start position:0% go through all five, but I want to start with<00:00:28.560> the<00:00:28.640> one<00:00:29.160> that<00:00:29.400> changes<00:00:30.040> how<00:00:30.240> you<00:00:30.400> work 00:00:30.750 --> 00:00:30.760 align:start position:0% with the one that changes how you work 00:00:30.760 --> 00:00:32.630 align:start position:0% with the one that changes how you work because<00:00:31.360> I<00:00:31.440> think<00:00:31.680> most<00:00:31.960> people<00:00:32.279> are<00:00:32.360> going<00:00:32.560> to 00:00:32.630 --> 00:00:32.640 align:start position:0% because I think most people are going to 00:00:32.640 --> 00:00:35.150 align:start position:0% because I think most people are going to miss<00:00:33.000> why<00:00:33.200> it<00:00:33.280> matters.<00:00:34.000> On<00:00:34.160> September<00:00:34.640> 15th, 00:00:35.150 --> 00:00:35.160 align:start position:0% miss why it matters. On September 15th, 00:00:35.160 --> 00:00:38.190 align:start position:0% miss why it matters. On September 15th, Google<00:00:35.520> launched<00:00:36.120> Gemini<00:00:36.680> 3.8<00:00:37.480> live<00:00:38.040> and 00:00:38.190 --> 00:00:38.200 align:start position:0% Google launched Gemini 3.8 live and 00:00:38.200 --> 00:00:41.190 align:start position:0% Google launched Gemini 3.8 live and Gemini<00:00:38.640> 3.8<00:00:39.520> live<00:00:39.880> extended<00:00:40.480> thinking. 00:00:41.190 --> 00:00:41.200 align:start position:0% Gemini 3.8 live extended thinking. 00:00:41.200 --> 00:00:43.550 align:start position:0% Gemini 3.8 live extended thinking. Google<00:00:41.560> calls<00:00:41.840> them<00:00:42.320> their<00:00:42.520> most<00:00:42.920> advanced 00:00:43.550 --> 00:00:43.560 align:start position:0% Google calls them their most advanced 00:00:43.560 --> 00:00:46.710 align:start position:0% Google calls them their most advanced live<00:00:43.920> dialogue<00:00:44.280> models<00:00:44.720> yet.<00:00:45.440> They<00:00:45.600> speak<00:00:46.000> 97 00:00:46.710 --> 00:00:46.720 align:start position:0% live dialogue models yet. They speak 97 00:00:46.720 --> 00:00:48.830 align:start position:0% live dialogue models yet. They speak 97 languages,<00:00:47.520> they're<00:00:47.680> built<00:00:48.000> on<00:00:48.120> Gemini<00:00:48.520> 3 00:00:48.830 --> 00:00:48.840 align:start position:0% languages, they're built on Gemini 3 00:00:48.840 --> 00:00:50.870 align:start position:0% languages, they're built on Gemini 3 Pro,<00:00:49.440> and<00:00:49.600> they<00:00:49.720> do<00:00:49.960> something<00:00:50.360> no<00:00:50.560> voice 00:00:50.870 --> 00:00:50.880 align:start position:0% Pro, and they do something no voice 00:00:50.880 --> 00:00:53.710 align:start position:0% Pro, and they do something no voice assistant<00:00:51.560> has<00:00:51.880> ever<00:00:52.440> really<00:00:53.000> done<00:00:53.320> well. 00:00:53.710 --> 00:00:53.720 align:start position:0% assistant has ever really done well. 00:00:53.720 --> 00:00:55.510 align:start position:0% assistant has ever really done well. Hey,<00:00:53.920> if<00:00:54.080> we<00:00:54.160> have<00:00:54.280> not<00:00:54.480> met<00:00:54.680> already,<00:00:55.320> I<00:00:55.400> am 00:00:55.510 --> 00:00:55.520 align:start position:0% Hey, if we have not met already, I am 00:00:55.520 --> 00:00:58.270 align:start position:0% Hey, if we have not met already, I am the<00:00:55.640> digital<00:00:56.120> avatar<00:00:56.560> of<00:00:56.720> Julian<00:00:57.000> Goldie,<00:00:57.600> CEO 00:00:58.270 --> 00:00:58.280 align:start position:0% the digital avatar of Julian Goldie, CEO 00:00:58.280 --> 00:01:00.230 align:start position:0% the digital avatar of Julian Goldie, CEO of<00:00:58.440> Goldie<00:00:58.760> Agency.<00:00:59.520> While<00:00:59.720> he's<00:00:59.920> out<00:01:00.080> there 00:01:00.230 --> 00:01:00.240 align:start position:0% of Goldie Agency. While he's out there 00:01:00.240 --> 00:01:02.190 align:start position:0% of Goldie Agency. While he's out there helping<00:01:00.520> clients<00:01:00.880> grow,<00:01:01.400> I<00:01:01.520> am<00:01:01.640> here<00:01:01.880> keeping 00:01:02.190 --> 00:01:02.200 align:start position:0% helping clients grow, I am here keeping 00:01:02.200 --> 00:01:04.390 align:start position:0% helping clients grow, I am here keeping you<00:01:02.320> up<00:01:02.440> to<00:01:02.560> date<00:01:02.760> on<00:01:02.960> everything<00:01:03.440> AI.<00:01:04.000> Julian 00:01:04.390 --> 00:01:04.400 align:start position:0% you up to date on everything AI. Julian 00:01:04.400 --> 00:01:06.270 align:start position:0% you up to date on everything AI. Julian reads<00:01:04.640> every<00:01:04.879> comment,<00:01:05.199> so<00:01:05.320> drop<00:01:05.560> one<00:01:05.680> below 00:01:06.270 --> 00:01:06.280 align:start position:0% reads every comment, so drop one below 00:01:06.280 --> 00:01:08.070 align:start position:0% reads every comment, so drop one below and<00:01:06.440> he<00:01:06.600> will<00:01:06.800> see<00:01:07.000> it.<00:01:07.400> Here's<00:01:07.640> the<00:01:07.720> problem 00:01:08.070 --> 00:01:08.080 align:start position:0% and he will see it. Here's the problem 00:01:08.080 --> 00:01:10.030 align:start position:0% and he will see it. Here's the problem with<00:01:08.360> every<00:01:08.640> voice<00:01:09.000> AI<00:01:09.280> you've<00:01:09.480> used<00:01:09.720> up<00:01:09.880> to 00:01:10.030 --> 00:01:10.040 align:start position:0% with every voice AI you've used up to 00:01:10.040 --> 00:01:12.070 align:start position:0% with every voice AI you've used up to now.<00:01:10.640> You<00:01:10.800> ask<00:01:11.000> it<00:01:11.120> something,<00:01:11.560> it<00:01:11.720> needs<00:01:12.000> to 00:01:12.070 --> 00:01:12.080 align:start position:0% now. You ask it something, it needs to 00:01:12.080 --> 00:01:13.870 align:start position:0% now. You ask it something, it needs to look<00:01:12.240> something<00:01:12.560> up,<00:01:12.920> and<00:01:13.000> it<00:01:13.080> goes<00:01:13.280> quiet. 00:01:13.870 --> 00:01:13.880 align:start position:0% look something up, and it goes quiet. 00:01:13.880 --> 00:01:15.990 align:start position:0% look something up, and it goes quiet. Dead<00:01:14.120> silence.<00:01:14.840> You<00:01:14.960> sit<00:01:15.120> there<00:01:15.320> wondering<00:01:15.880> if 00:01:15.990 --> 00:01:16.000 align:start position:0% Dead silence. You sit there wondering if 00:01:16.000 --> 00:01:18.230 align:start position:0% Dead silence. You sit there wondering if the<00:01:16.120> thing<00:01:16.400> crashed.<00:01:17.200> Then<00:01:17.560> 30<00:01:17.880> seconds 00:01:18.230 --> 00:01:18.240 align:start position:0% the thing crashed. Then 30 seconds 00:01:18.240 --> 00:01:20.710 align:start position:0% the thing crashed. Then 30 seconds later,<00:01:18.800> it<00:01:18.960> comes<00:01:19.280> back<00:01:19.840> with<00:01:20.000> an<00:01:20.120> answer. 00:01:20.710 --> 00:01:20.720 align:start position:0% later, it comes back with an answer. 00:01:20.720 --> 00:01:23.870 align:start position:0% later, it comes back with an answer. That<00:01:21.000> gap<00:01:21.680> killed<00:01:22.160> voice<00:01:22.600> AI<00:01:23.160> for<00:01:23.360> real<00:01:23.640> work. 00:01:23.870 --> 00:01:23.880 align:start position:0% That gap killed voice AI for real work. 00:01:23.880 --> 00:01:25.310 align:start position:0% That gap killed voice AI for real work. Nobody<00:01:24.200> wants<00:01:24.440> to<00:01:24.520> talk<00:01:24.760> to<00:01:24.880> something<00:01:25.160> that 00:01:25.310 --> 00:01:25.320 align:start position:0% Nobody wants to talk to something that 00:01:25.320 --> 00:01:28.430 align:start position:0% Nobody wants to talk to something that freezes<00:01:25.920> mid-sentence.<00:01:26.840> Gemini<00:01:27.360> 3.8<00:01:28.160> live 00:01:28.430 --> 00:01:28.440 align:start position:0% freezes mid-sentence. Gemini 3.8 live 00:01:28.440 --> 00:01:30.270 align:start position:0% freezes mid-sentence. Gemini 3.8 live fixes<00:01:28.800> that.<00:01:29.240> It<00:01:29.400> runs<00:01:29.680> the<00:01:29.760> look<00:01:29.960> up<00:01:30.120> in<00:01:30.200> the 00:01:30.270 --> 00:01:30.280 align:start position:0% fixes that. It runs the look up in the 00:01:30.280 --> 00:01:31.990 align:start position:0% fixes that. It runs the look up in the background<00:01:30.960> while<00:01:31.160> it<00:01:31.280> keeps<00:01:31.520> talking<00:01:31.880> to 00:01:31.990 --> 00:01:32.000 align:start position:0% background while it keeps talking to 00:01:32.000 --> 00:01:34.350 align:start position:0% background while it keeps talking to you.<00:01:32.320> Google's<00:01:32.760> own<00:01:33.000> words<00:01:33.560> describe<00:01:34.000> it<00:01:34.160> as 00:01:34.350 --> 00:01:34.360 align:start position:0% you. Google's own words describe it as 00:01:34.360 --> 00:01:36.390 align:start position:0% you. Google's own words describe it as running<00:01:34.680> tool<00:01:34.880> calls<00:01:35.480> without<00:01:35.800> interrupting 00:01:36.390 --> 00:01:36.400 align:start position:0% running tool calls without interrupting 00:01:36.400 --> 00:01:38.110 align:start position:0% running tool calls without interrupting the<00:01:36.480> conversation.<00:01:37.320> The<00:01:37.440> model<00:01:37.720> can<00:01:37.880> say, 00:01:38.110 --> 00:01:38.120 align:start position:0% the conversation. The model can say, 00:01:38.120 --> 00:01:39.630 align:start position:0% the conversation. The model can say, "Let<00:01:38.360> me<00:01:38.480> check<00:01:38.760> that."<00:01:39.040> and<00:01:39.160> actually<00:01:39.480> go 00:01:39.630 --> 00:01:39.640 align:start position:0% "Let me check that." and actually go 00:01:39.640 --> 00:01:41.790 align:start position:0% "Let me check that." and actually go check<00:01:40.080> while<00:01:40.280> still<00:01:40.520> speaking.<00:01:41.200> The<00:01:41.320> extended 00:01:41.790 --> 00:01:41.800 align:start position:0% check while still speaking. The extended 00:01:41.800 --> 00:01:43.390 align:start position:0% check while still speaking. The extended thinking<00:01:42.120> version<00:01:42.480> goes<00:01:42.720> further.<00:01:43.240> It 00:01:43.390 --> 00:01:43.400 align:start position:0% thinking version goes further. It 00:01:43.400 --> 00:01:45.510 align:start position:0% thinking version goes further. It narrates<00:01:43.800> progress<00:01:44.280> as<00:01:44.400> it<00:01:44.520> works,<00:01:44.920> so<00:01:45.320> it'll 00:01:45.510 --> 00:01:45.520 align:start position:0% narrates progress as it works, so it'll 00:01:45.520 --> 00:01:47.070 align:start position:0% narrates progress as it works, so it'll tell<00:01:45.720> you<00:01:45.800> what<00:01:45.960> step<00:01:46.200> it's<00:01:46.360> on<00:01:46.760> while<00:01:46.960> it's 00:01:47.070 --> 00:01:47.080 align:start position:0% tell you what step it's on while it's 00:01:47.080 --> 00:01:48.590 align:start position:0% tell you what step it's on while it's doing<00:01:47.360> it.<00:01:47.560> Think<00:01:47.760> about<00:01:47.960> a<00:01:48.040> real<00:01:48.240> person 00:01:48.590 --> 00:01:48.600 align:start position:0% doing it. Think about a real person 00:01:48.600 --> 00:01:50.270 align:start position:0% doing it. Think about a real person doing<00:01:48.840> a<00:01:48.880> task<00:01:49.240> for<00:01:49.400> you,<00:01:49.840> they<00:01:49.960> don't<00:01:50.160> go 00:01:50.270 --> 00:01:50.280 align:start position:0% doing a task for you, they don't go 00:01:50.280 --> 00:01:51.790 align:start position:0% doing a task for you, they don't go silent.<00:01:50.840> They<00:01:50.960> say,<00:01:51.160> "Okay,<00:01:51.440> I'm<00:01:51.560> pulling 00:01:51.790 --> 00:01:51.800 align:start position:0% silent. They say, "Okay, I'm pulling 00:01:51.800 --> 00:01:52.950 align:start position:0% silent. They say, "Okay, I'm pulling that<00:01:51.960> up<00:01:52.080> now,<00:01:52.240> give<00:01:52.400> me<00:01:52.480> a<00:01:52.520> second.<00:01:52.880> All 00:01:52.950 --> 00:01:52.960 align:start position:0% that up now, give me a second. All 00:01:52.960 --> 00:01:55.030 align:start position:0% that up now, give me a second. All right,<00:01:53.160> I<00:01:53.200> see<00:01:53.400> it."<00:01:53.880> That's<00:01:54.240> the<00:01:54.320> behavior 00:01:55.030 --> 00:01:55.040 align:start position:0% right, I see it." That's the behavior 00:01:55.040 --> 00:01:58.070 align:start position:0% right, I see it." That's the behavior Google<00:01:55.400> just<00:01:55.640> built<00:01:56.240> into<00:01:56.920> a<00:01:57.120> model.<00:01:57.720> Google 00:01:58.070 --> 00:01:58.080 align:start position:0% Google just built into a model. Google 00:01:58.080 --> 00:02:00.470 align:start position:0% Google just built into a model. Google also<00:01:58.360> shipped<00:01:58.800> Gemini<00:01:59.280> 3.5<00:01:59.960> Transcriber 00:02:00.470 --> 00:02:00.480 align:start position:0% also shipped Gemini 3.5 Transcriber 00:02:00.480 --> 00:02:02.430 align:start position:0% also shipped Gemini 3.5 Transcriber alongside<00:02:01.000> it.<00:02:01.400> That's<00:02:01.680> a<00:02:01.760> dedicated 00:02:02.430 --> 00:02:02.440 align:start position:0% alongside it. That's a dedicated 00:02:02.440 --> 00:02:05.190 align:start position:0% alongside it. That's a dedicated speech-to-text<00:02:03.200> model<00:02:03.760> covering<00:02:04.240> 85<00:02:04.840> plus 00:02:05.190 --> 00:02:05.200 align:start position:0% speech-to-text model covering 85 plus 00:02:05.200 --> 00:02:07.430 align:start position:0% speech-to-text model covering 85 plus languages<00:02:05.840> with<00:02:06.040> low<00:02:06.280> error<00:02:06.600> rates.<00:02:07.280> Now, 00:02:07.430 --> 00:02:07.440 align:start position:0% languages with low error rates. Now, 00:02:07.440 --> 00:02:09.070 align:start position:0% languages with low error rates. Now, before<00:02:07.800> I<00:02:07.840> get<00:02:08.000> into<00:02:08.240> the<00:02:08.399> agent<00:02:08.720> that<00:02:08.800> got<00:02:08.960> its 00:02:09.070 --> 00:02:09.080 align:start position:0% before I get into the agent that got its 00:02:09.080 --> 00:02:10.790 align:start position:0% before I get into the agent that got its own<00:02:09.240> Google<00:02:09.520> account,<00:02:10.119> and<00:02:10.240> this<00:02:10.440> one<00:02:10.600> is 00:02:10.790 --> 00:02:10.800 align:start position:0% own Google account, and this one is 00:02:10.800 --> 00:02:12.070 align:start position:0% own Google account, and this one is genuinely<00:02:11.240> strange,<00:02:11.640> I<00:02:11.720> want<00:02:11.880> to<00:02:11.959> say 00:02:12.070 --> 00:02:12.080 align:start position:0% genuinely strange, I want to say 00:02:12.080 --> 00:02:14.150 align:start position:0% genuinely strange, I want to say something<00:02:12.400> quick.<00:02:13.080> Voice<00:02:13.400> models<00:02:14.000> like 00:02:14.150 --> 00:02:14.160 align:start position:0% something quick. Voice models like 00:02:14.160 --> 00:02:16.670 align:start position:0% something quick. Voice models like Gemini<00:02:14.560> 3.8<00:02:15.360> live<00:02:15.720> only<00:02:16.000> pay<00:02:16.160> off<00:02:16.360> if<00:02:16.480> you<00:02:16.560> know 00:02:16.670 --> 00:02:16.680 align:start position:0% Gemini 3.8 live only pay off if you know 00:02:16.680 --> 00:02:18.150 align:start position:0% Gemini 3.8 live only pay off if you know what<00:02:16.840> to<00:02:16.920> point<00:02:17.120> them<00:02:17.240> at.<00:02:17.680> That's<00:02:17.920> the<00:02:18.000> whole 00:02:18.150 --> 00:02:18.160 align:start position:0% what to point them at. That's the whole 00:02:18.160 --> 00:02:20.030 align:start position:0% what to point them at. That's the whole game<00:02:18.400> now.<00:02:18.880> Inside<00:02:19.280> the<00:02:19.440> AI<00:02:19.720> Profit 00:02:20.030 --> 00:02:20.040 align:start position:0% game now. Inside the AI Profit 00:02:20.040 --> 00:02:22.550 align:start position:0% game now. Inside the AI Profit Boardroom,<00:02:20.720> we've<00:02:20.880> got<00:02:21.080> a<00:02:21.120> 30-day<00:02:21.840> roadmap 00:02:22.550 --> 00:02:22.560 align:start position:0% Boardroom, we've got a 30-day roadmap 00:02:22.560 --> 00:02:25.030 align:start position:0% Boardroom, we've got a 30-day roadmap for<00:02:22.680> exactly<00:02:23.280> this,<00:02:23.840> how<00:02:24.040> to<00:02:24.200> set<00:02:24.400> up<00:02:24.560> voice 00:02:25.030 --> 00:02:25.040 align:start position:0% for exactly this, how to set up voice 00:02:25.040 --> 00:02:26.590 align:start position:0% for exactly this, how to set up voice agents<00:02:25.600> that<00:02:25.680> handle<00:02:25.920> your<00:02:26.040> follow-ups,<00:02:26.480> your 00:02:26.590 --> 00:02:26.600 align:start position:0% agents that handle your follow-ups, your 00:02:26.600 --> 00:02:29.070 align:start position:0% agents that handle your follow-ups, your client<00:02:26.920> calls,<00:02:27.400> your<00:02:27.560> inbox<00:02:28.080> hands-free.<00:02:28.920> We 00:02:29.070 --> 00:02:29.080 align:start position:0% client calls, your inbox hands-free. We 00:02:29.080 --> 00:02:30.949 align:start position:0% client calls, your inbox hands-free. We run<00:02:29.320> four<00:02:29.600> coaching<00:02:29.959> calls<00:02:30.280> every<00:02:30.480> week,<00:02:30.800> and 00:02:30.949 --> 00:02:30.959 align:start position:0% run four coaching calls every week, and 00:02:30.959 --> 00:02:32.510 align:start position:0% run four coaching calls every week, and right<00:02:31.160> now<00:02:31.320> a<00:02:31.360> lot<00:02:31.520> of<00:02:31.640> those<00:02:31.840> calls<00:02:32.400> are 00:02:32.510 --> 00:02:32.520 align:start position:0% right now a lot of those calls are 00:02:32.520 --> 00:02:34.150 align:start position:0% right now a lot of those calls are people<00:02:32.920> working<00:02:33.240> through<00:02:33.480> Gemini<00:02:33.959> and 00:02:34.150 --> 00:02:34.160 align:start position:0% people working through Gemini and 00:02:34.160 --> 00:02:36.310 align:start position:0% people working through Gemini and Workspace<00:02:34.760> automations<00:02:35.680> live.<00:02:36.040> Bring<00:02:36.240> your 00:02:36.310 --> 00:02:36.320 align:start position:0% Workspace automations live. Bring your 00:02:36.320 --> 00:02:38.270 align:start position:0% Workspace automations live. Bring your setup,<00:02:36.959> we'll<00:02:37.080> fix<00:02:37.320> it<00:02:37.440> on<00:02:37.520> the<00:02:37.600> call.<00:02:38.120> There's 00:02:38.270 --> 00:02:38.280 align:start position:0% setup, we'll fix it on the call. There's 00:02:38.280 --> 00:02:39.949 align:start position:0% setup, we'll fix it on the call. There's a<00:02:38.360> prompt<00:02:38.680> library<00:02:39.120> built<00:02:39.480> for<00:02:39.600> Google's 00:02:39.949 --> 00:02:39.959 align:start position:0% a prompt library built for Google's 00:02:39.959 --> 00:02:42.190 align:start position:0% a prompt library built for Google's tools<00:02:40.200> specifically,<00:02:41.160> daily<00:02:41.480> tutorials<00:02:42.080> that 00:02:42.190 --> 00:02:42.200 align:start position:0% tools specifically, daily tutorials that 00:02:42.200 --> 00:02:44.270 align:start position:0% tools specifically, daily tutorials that walk<00:02:42.440> you<00:02:42.560> through<00:02:42.760> new<00:02:43.000> releases<00:02:43.480> like<00:02:43.720> this 00:02:44.270 --> 00:02:44.280 align:start position:0% walk you through new releases like this 00:02:44.280 --> 00:02:45.550 align:start position:0% walk you through new releases like this one<00:02:44.520> step<00:02:44.760> by<00:02:44.880> step,<00:02:45.200> so<00:02:45.320> you're<00:02:45.400> not 00:02:45.550 --> 00:02:45.560 align:start position:0% one step by step, so you're not 00:02:45.560 --> 00:02:47.550 align:start position:0% one step by step, so you're not guessing.<00:02:46.400> And<00:02:46.560> business<00:02:46.959> owners<00:02:47.200> in<00:02:47.320> there, 00:02:47.550 --> 00:02:47.560 align:start position:0% guessing. And business owners in there, 00:02:47.560 --> 00:02:49.390 align:start position:0% guessing. And business owners in there, a<00:02:47.640> lot<00:02:47.840> of<00:02:47.920> them<00:02:48.240> already<00:02:48.600> running<00:02:48.920> Gemini 00:02:49.390 --> 00:02:49.400 align:start position:0% a lot of them already running Gemini 00:02:49.400 --> 00:02:51.630 align:start position:0% a lot of them already running Gemini agents<00:02:49.840> in<00:02:49.959> their<00:02:50.400> business<00:02:50.760> today.<00:02:51.440> There's 00:02:51.630 --> 00:02:51.640 align:start position:0% agents in their business today. There's 00:02:51.640 --> 00:02:53.550 align:start position:0% agents in their business today. There's a<00:02:51.680> member<00:02:52.000> map,<00:02:52.600> so<00:02:52.760> you<00:02:52.880> can<00:02:53.000> find<00:02:53.280> people 00:02:53.550 --> 00:02:53.560 align:start position:0% a member map, so you can find people 00:02:53.560 --> 00:02:55.430 align:start position:0% a member map, so you can find people near<00:02:53.800> you<00:02:53.920> doing<00:02:54.160> the<00:02:54.240> same<00:02:54.440> thing.<00:02:54.959> Link<00:02:55.360> in 00:02:55.430 --> 00:02:55.440 align:start position:0% near you doing the same thing. Link in 00:02:55.440 --> 00:02:57.230 align:start position:0% near you doing the same thing. Link in the<00:02:55.520> comments<00:02:55.880> and<00:02:55.959> description,<00:02:56.720> or<00:02:56.880> go<00:02:57.000> to 00:02:57.230 --> 00:02:57.240 align:start position:0% the comments and description, or go to 00:02:57.240 --> 00:02:59.470 align:start position:0% the comments and description, or go to aprofitboardroom.com.<00:02:58.520> Okay,<00:02:59.040> the<00:02:59.160> agent 00:02:59.470 --> 00:02:59.480 align:start position:0% aprofitboardroom.com. Okay, the agent 00:02:59.480 --> 00:03:01.070 align:start position:0% aprofitboardroom.com. Okay, the agent with<00:02:59.600> its<00:02:59.800> own<00:03:00.040> Google<00:03:00.320> account.<00:03:00.959> On 00:03:01.070 --> 00:03:01.080 align:start position:0% with its own Google account. On 00:03:01.080 --> 00:03:02.910 align:start position:0% with its own Google account. On September<00:03:01.400> 17th,<00:03:01.959> Google<00:03:02.239> Labs<00:03:02.519> announced<00:03:02.880> a 00:03:02.910 --> 00:03:02.920 align:start position:0% September 17th, Google Labs announced a 00:03:02.920 --> 00:03:05.550 align:start position:0% September 17th, Google Labs announced a new<00:03:03.200> version<00:03:03.600> of<00:03:03.680> CC.<00:03:04.400> CC<00:03:04.880> started<00:03:05.440> in 00:03:05.550 --> 00:03:05.560 align:start position:0% new version of CC. CC started in 00:03:05.560 --> 00:03:08.590 align:start position:0% new version of CC. CC started in December<00:03:05.959> 2025<00:03:07.200> as<00:03:07.360> a<00:03:07.400> personal<00:03:07.880> productivity 00:03:08.590 --> 00:03:08.600 align:start position:0% December 2025 as a personal productivity 00:03:08.600 --> 00:03:11.030 align:start position:0% December 2025 as a personal productivity agent.<00:03:09.200> It<00:03:09.320> got<00:03:09.519> popular<00:03:09.920> fast<00:03:10.560> with<00:03:10.760> early 00:03:11.030 --> 00:03:11.040 align:start position:0% agent. It got popular fast with early 00:03:11.040 --> 00:03:13.710 align:start position:0% agent. It got popular fast with early testers.<00:03:11.840> In<00:03:12.000> May,<00:03:12.640> Google<00:03:13.040> brought<00:03:13.360> it<00:03:13.480> into 00:03:13.710 --> 00:03:13.720 align:start position:0% testers. In May, Google brought it into 00:03:13.720 --> 00:03:16.430 align:start position:0% testers. In May, Google brought it into the<00:03:13.800> Gemini<00:03:14.280> app<00:03:14.840> as<00:03:15.160> Daily<00:03:15.560> Brief.<00:03:16.200> Now, 00:03:16.430 --> 00:03:16.440 align:start position:0% the Gemini app as Daily Brief. Now, 00:03:16.440 --> 00:03:18.949 align:start position:0% the Gemini app as Daily Brief. Now, Google<00:03:16.800> rebuilt<00:03:17.280> it<00:03:17.400> completely.<00:03:18.120> CC<00:03:18.640> is<00:03:18.800> now 00:03:18.949 --> 00:03:18.959 align:start position:0% Google rebuilt it completely. CC is now 00:03:18.959 --> 00:03:20.550 align:start position:0% Google rebuilt it completely. CC is now an<00:03:19.080> agent<00:03:19.400> for<00:03:19.519> families<00:03:19.920> and<00:03:20.040> households, 00:03:20.550 --> 00:03:20.560 align:start position:0% an agent for families and households, 00:03:20.560 --> 00:03:22.270 align:start position:0% an agent for families and households, and<00:03:20.640> here's<00:03:20.880> the<00:03:20.959> part<00:03:21.200> that<00:03:21.320> made<00:03:21.519> me<00:03:21.640> stop. 00:03:22.270 --> 00:03:22.280 align:start position:0% and here's the part that made me stop. 00:03:22.280 --> 00:03:24.670 align:start position:0% and here's the part that made me stop. CC<00:03:22.760> now<00:03:23.000> has<00:03:23.200> its<00:03:23.320> own<00:03:23.519> Google<00:03:23.840> account,<00:03:24.560> not 00:03:24.670 --> 00:03:24.680 align:start position:0% CC now has its own Google account, not 00:03:24.680 --> 00:03:26.470 align:start position:0% CC now has its own Google account, not your<00:03:24.880> account,<00:03:25.320> its<00:03:25.519> own,<00:03:25.959> with<00:03:26.120> its<00:03:26.280> own 00:03:26.470 --> 00:03:26.480 align:start position:0% your account, its own, with its own 00:03:26.480 --> 00:03:28.790 align:start position:0% your account, its own, with its own email<00:03:26.760> address,<00:03:27.200> its<00:03:27.400> own<00:03:27.560> identity,<00:03:28.440> its<00:03:28.600> own 00:03:28.790 --> 00:03:28.800 align:start position:0% email address, its own identity, its own 00:03:28.800 --> 00:03:30.750 align:start position:0% email address, its own identity, its own permission<00:03:29.239> set.<00:03:29.680> Up<00:03:29.920> to<00:03:30.040> six<00:03:30.320> people<00:03:30.600> can 00:03:30.750 --> 00:03:30.760 align:start position:0% permission set. Up to six people can 00:03:30.760 --> 00:03:33.190 align:start position:0% permission set. Up to six people can join<00:03:31.160> one<00:03:31.400> CC.<00:03:32.120> Each<00:03:32.360> person<00:03:32.680> picks<00:03:32.959> what<00:03:33.120> they 00:03:33.190 --> 00:03:33.200 align:start position:0% join one CC. Each person picks what they 00:03:33.200 --> 00:03:34.949 align:start position:0% join one CC. Each person picks what they share<00:03:33.440> with<00:03:33.600> it.<00:03:33.959> Emails<00:03:34.400> from<00:03:34.560> your<00:03:34.680> kids' 00:03:34.949 --> 00:03:34.959 align:start position:0% share with it. Emails from your kids' 00:03:34.959 --> 00:03:37.030 align:start position:0% share with it. Emails from your kids' school,<00:03:35.480> the<00:03:35.560> swim<00:03:35.840> center,<00:03:36.280> the<00:03:36.400> vet,<00:03:36.920> you 00:03:37.030 --> 00:03:37.040 align:start position:0% school, the swim center, the vet, you 00:03:37.040 --> 00:03:38.750 align:start position:0% school, the swim center, the vet, you can<00:03:37.200> forward<00:03:37.519> things<00:03:37.800> to<00:03:37.920> CC's<00:03:38.440> email 00:03:38.750 --> 00:03:38.760 align:start position:0% can forward things to CC's email 00:03:38.760 --> 00:03:40.270 align:start position:0% can forward things to CC's email address,<00:03:39.200> or<00:03:39.360> you<00:03:39.440> can<00:03:39.560> set<00:03:39.760> it<00:03:39.840> so<00:03:39.959> certain 00:03:40.270 --> 00:03:40.280 align:start position:0% address, or you can set it so certain 00:03:40.280 --> 00:03:42.509 align:start position:0% address, or you can set it so certain senders<00:03:40.640> always<00:03:40.880> go<00:03:41.080> to<00:03:41.200> CC<00:03:41.840> automatically. 00:03:42.509 --> 00:03:42.519 align:start position:0% senders always go to CC automatically. 00:03:42.519 --> 00:03:45.150 align:start position:0% senders always go to CC automatically. Google<00:03:42.800> says<00:03:43.320> CC<00:03:43.800> will<00:03:43.959> even<00:03:44.120> suggest<00:03:44.720> senders 00:03:45.150 --> 00:03:45.160 align:start position:0% Google says CC will even suggest senders 00:03:45.160 --> 00:03:47.670 align:start position:0% Google says CC will even suggest senders to<00:03:45.280> add<00:03:45.560> each<00:03:45.840> week.<00:03:46.400> Then<00:03:46.560> CC<00:03:47.040> sorts<00:03:47.440> through 00:03:47.670 --> 00:03:47.680 align:start position:0% to add each week. Then CC sorts through 00:03:47.680 --> 00:03:49.590 align:start position:0% to add each week. Then CC sorts through all<00:03:47.800> of<00:03:47.920> it<00:03:48.280> and<00:03:48.400> builds<00:03:48.760> one<00:03:49.000> shared<00:03:49.320> daily 00:03:49.590 --> 00:03:49.600 align:start position:0% all of it and builds one shared daily 00:03:49.600 --> 00:03:51.470 align:start position:0% all of it and builds one shared daily brief<00:03:50.160> for<00:03:50.280> the<00:03:50.360> whole<00:03:50.600> household.<00:03:51.160> Google 00:03:51.470 --> 00:03:51.480 align:start position:0% brief for the whole household. Google 00:03:51.480 --> 00:03:53.510 align:start position:0% brief for the whole household. Google calls<00:03:51.760> it<00:03:51.880> Your<00:03:52.080> day<00:03:52.360> ahead.<00:03:53.040> It<00:03:53.160> connects<00:03:53.440> to 00:03:53.510 --> 00:03:53.520 align:start position:0% calls it Your day ahead. It connects to 00:03:53.520 --> 00:03:56.030 align:start position:0% calls it Your day ahead. It connects to calendar<00:03:54.000> and<00:03:54.160> tasks.<00:03:54.920> It<00:03:55.120> adds<00:03:55.480> events 00:03:56.030 --> 00:03:56.040 align:start position:0% calendar and tasks. It adds events 00:03:56.040 --> 00:03:57.630 align:start position:0% calendar and tasks. It adds events automatically<00:03:56.720> based<00:03:57.080> on<00:03:57.200> what<00:03:57.360> people 00:03:57.630 --> 00:03:57.640 align:start position:0% automatically based on what people 00:03:57.640 --> 00:03:59.310 align:start position:0% automatically based on what people share.<00:03:58.200> But,<00:03:58.320> it<00:03:58.400> doesn't<00:03:58.640> stop<00:03:58.880> at<00:03:59.000> reading. 00:03:59.310 --> 00:03:59.320 align:start position:0% share. But, it doesn't stop at reading. 00:03:59.320 --> 00:04:00.830 align:start position:0% share. But, it doesn't stop at reading. It<00:03:59.400> does<00:03:59.600> things.<00:03:59.920> CC<00:04:00.320> can<00:04:00.520> fill<00:04:00.720> out 00:04:00.830 --> 00:04:00.840 align:start position:0% It does things. CC can fill out 00:04:00.840 --> 00:04:02.390 align:start position:0% It does things. CC can fill out permission<00:04:01.200> slips.<00:04:01.760> It<00:04:01.880> can<00:04:02.040> fill<00:04:02.240> in 00:04:02.390 --> 00:04:02.400 align:start position:0% permission slips. It can fill in 00:04:02.400 --> 00:04:04.870 align:start position:0% permission slips. It can fill in registration<00:04:03.040> PDFs.<00:04:03.920> It<00:04:04.080> can<00:04:04.280> build<00:04:04.640> school 00:04:04.870 --> 00:04:04.880 align:start position:0% registration PDFs. It can build school 00:04:04.880 --> 00:04:06.750 align:start position:0% registration PDFs. It can build school supply<00:04:05.240> shopping<00:04:05.560> lists.<00:04:06.040> It<00:04:06.200> can<00:04:06.360> plan 00:04:06.750 --> 00:04:06.760 align:start position:0% supply shopping lists. It can plan 00:04:06.760 --> 00:04:08.470 align:start position:0% supply shopping lists. It can plan weekly<00:04:07.120> meals.<00:04:07.480> It<00:04:07.600> can<00:04:07.760> work<00:04:08.000> out<00:04:08.160> drive 00:04:08.470 --> 00:04:08.480 align:start position:0% weekly meals. It can work out drive 00:04:08.480 --> 00:04:10.510 align:start position:0% weekly meals. It can work out drive times<00:04:08.760> between<00:04:09.120> activities.<00:04:10.000> So,<00:04:10.240> you<00:04:10.400> know, 00:04:10.510 --> 00:04:10.520 align:start position:0% times between activities. So, you know, 00:04:10.520 --> 00:04:12.190 align:start position:0% times between activities. So, you know, if<00:04:10.640> you<00:04:10.760> can<00:04:10.880> actually<00:04:11.120> make<00:04:11.320> both.<00:04:11.840> It<00:04:12.040> can 00:04:12.190 --> 00:04:12.200 align:start position:0% if you can actually make both. It can 00:04:12.200 --> 00:04:14.110 align:start position:0% if you can actually make both. It can create<00:04:12.560> shared<00:04:12.880> docs<00:04:13.120> and<00:04:13.240> sheets.<00:04:13.880> And<00:04:14.000> if 00:04:14.110 --> 00:04:14.120 align:start position:0% create shared docs and sheets. And if 00:04:14.120 --> 00:04:15.630 align:start position:0% create shared docs and sheets. And if it's<00:04:14.280> missing<00:04:14.600> something<00:04:14.959> it<00:04:15.120> needs,<00:04:15.480> it 00:04:15.630 --> 00:04:15.640 align:start position:0% it's missing something it needs, it 00:04:15.640 --> 00:04:17.870 align:start position:0% it's missing something it needs, it asks.<00:04:16.320> Then,<00:04:16.519> it<00:04:16.680> updates<00:04:17.120> its<00:04:17.280> group<00:04:17.519> memory 00:04:17.870 --> 00:04:17.880 align:start position:0% asks. Then, it updates its group memory 00:04:17.880 --> 00:04:19.550 align:start position:0% asks. Then, it updates its group memory so<00:04:18.040> it<00:04:18.120> doesn't<00:04:18.359> have<00:04:18.480> to<00:04:18.600> ask<00:04:18.840> again.<00:04:19.480> All 00:04:19.550 --> 00:04:19.560 align:start position:0% so it doesn't have to ask again. All 00:04:19.560 --> 00:04:21.270 align:start position:0% so it doesn't have to ask again. All right,<00:04:19.799> third<00:04:20.040> one.<00:04:20.519> This<00:04:20.760> one<00:04:20.920> is<00:04:21.120> more 00:04:21.270 --> 00:04:21.280 align:start position:0% right, third one. This one is more 00:04:21.280 --> 00:04:22.950 align:start position:0% right, third one. This one is more immediately<00:04:21.720> useful<00:04:22.320> for<00:04:22.440> most<00:04:22.640> people 00:04:22.950 --> 00:04:22.960 align:start position:0% immediately useful for most people 00:04:22.960 --> 00:04:25.350 align:start position:0% immediately useful for most people watching.<00:04:23.800> Google<00:04:24.200> picks.<00:04:24.960> It<00:04:25.120> went 00:04:25.350 --> 00:04:25.360 align:start position:0% watching. Google picks. It went 00:04:25.360 --> 00:04:27.470 align:start position:0% watching. Google picks. It went generally<00:04:25.720> available<00:04:26.200> on<00:04:26.360> September<00:04:26.760> 1st. 00:04:27.470 --> 00:04:27.480 align:start position:0% generally available on September 1st. 00:04:27.480 --> 00:04:29.510 align:start position:0% generally available on September 1st. It's<00:04:27.800> Google's<00:04:28.360> AI<00:04:28.720> image<00:04:29.000> creation<00:04:29.400> and 00:04:29.510 --> 00:04:29.520 align:start position:0% It's Google's AI image creation and 00:04:29.520 --> 00:04:31.270 align:start position:0% It's Google's AI image creation and editing<00:04:29.880> tool.<00:04:30.400> And<00:04:30.520> it's<00:04:30.640> built<00:04:30.880> directly 00:04:31.270 --> 00:04:31.280 align:start position:0% editing tool. And it's built directly 00:04:31.280 --> 00:04:33.790 align:start position:0% editing tool. And it's built directly into<00:04:31.480> workspace.<00:04:32.320> It<00:04:32.480> runs<00:04:32.760> on<00:04:32.880> Nala<00:04:33.080> Banana, 00:04:33.790 --> 00:04:33.800 align:start position:0% into workspace. It runs on Nala Banana, 00:04:33.800 --> 00:04:35.350 align:start position:0% into workspace. It runs on Nala Banana, Google's<00:04:34.160> image<00:04:34.440> model.<00:04:34.919> The<00:04:35.040> thing<00:04:35.240> that 00:04:35.350 --> 00:04:35.360 align:start position:0% Google's image model. The thing that 00:04:35.360 --> 00:04:37.710 align:start position:0% Google's image model. The thing that makes<00:04:35.600> picks<00:04:35.840> different<00:04:36.480> from<00:04:36.680> most<00:04:37.120> AI<00:04:37.440> image 00:04:37.710 --> 00:04:37.720 align:start position:0% makes picks different from most AI image 00:04:37.720 --> 00:04:40.470 align:start position:0% makes picks different from most AI image tools<00:04:38.280> is<00:04:38.560> object-level<00:04:39.400> editing.<00:04:40.120> Most 00:04:40.470 --> 00:04:40.480 align:start position:0% tools is object-level editing. Most 00:04:40.480 --> 00:04:42.590 align:start position:0% tools is object-level editing. Most image<00:04:40.760> AI<00:04:41.040> works<00:04:41.400> one<00:04:41.560> shot.<00:04:42.160> You<00:04:42.280> type<00:04:42.520> a 00:04:42.590 --> 00:04:42.600 align:start position:0% image AI works one shot. You type a 00:04:42.600 --> 00:04:44.350 align:start position:0% image AI works one shot. You type a prompt,<00:04:43.120> you<00:04:43.240> get<00:04:43.400> an<00:04:43.480> image.<00:04:44.000> And<00:04:44.080> if<00:04:44.200> one 00:04:44.350 --> 00:04:44.360 align:start position:0% prompt, you get an image. And if one 00:04:44.360 --> 00:04:46.390 align:start position:0% prompt, you get an image. And if one thing<00:04:44.560> is<00:04:44.680> wrong,<00:04:45.200> you<00:04:45.320> start<00:04:45.640> over.<00:04:46.200> New 00:04:46.390 --> 00:04:46.400 align:start position:0% thing is wrong, you start over. New 00:04:46.400 --> 00:04:48.670 align:start position:0% thing is wrong, you start over. New prompt,<00:04:46.960> new<00:04:47.160> image,<00:04:47.600> new<00:04:47.840> everything.<00:04:48.480> Then, 00:04:48.670 --> 00:04:48.680 align:start position:0% prompt, new image, new everything. Then, 00:04:48.680 --> 00:04:50.870 align:start position:0% prompt, new image, new everything. Then, you<00:04:48.800> lose<00:04:49.000> the<00:04:49.120> parts<00:04:49.360> you<00:04:49.480> liked.<00:04:50.120> Picks<00:04:50.600> lets 00:04:50.870 --> 00:04:50.880 align:start position:0% you lose the parts you liked. Picks lets 00:04:50.880 --> 00:04:52.550 align:start position:0% you lose the parts you liked. Picks lets you<00:04:51.000> select<00:04:51.320> a<00:04:51.360> single<00:04:51.680> object<00:04:52.120> inside<00:04:52.480> the 00:04:52.550 --> 00:04:52.560 align:start position:0% you select a single object inside the 00:04:52.560 --> 00:04:54.630 align:start position:0% you select a single object inside the image<00:04:53.120> and<00:04:53.280> change<00:04:53.680> just<00:04:53.880> that.<00:04:54.280> The<00:04:54.400> rest 00:04:54.630 --> 00:04:54.640 align:start position:0% image and change just that. The rest 00:04:54.640 --> 00:04:57.510 align:start position:0% image and change just that. The rest stays<00:04:54.919> put.<00:04:55.400> You<00:04:55.520> can<00:04:55.760> edit<00:04:56.240> text<00:04:56.919> inside<00:04:57.400> an 00:04:57.510 --> 00:04:57.520 align:start position:0% stays put. You can edit text inside an 00:04:57.520 --> 00:04:59.670 align:start position:0% stays put. You can edit text inside an image.<00:04:58.120> You<00:04:58.240> can<00:04:58.360> translate<00:04:58.880> words<00:04:59.160> inside<00:04:59.560> an 00:04:59.670 --> 00:04:59.680 align:start position:0% image. You can translate words inside an 00:04:59.680 --> 00:05:01.909 align:start position:0% image. You can translate words inside an image.<00:05:00.240> You<00:05:00.360> can<00:05:00.640> isolate<00:05:01.120> one<00:05:01.320> element<00:05:01.800> and 00:05:01.909 --> 00:05:01.919 align:start position:0% image. You can isolate one element and 00:05:01.919 --> 00:05:03.909 align:start position:0% image. You can isolate one element and swap<00:05:02.200> it<00:05:02.320> out.<00:05:02.720> It<00:05:02.840> also<00:05:03.120> generates<00:05:03.600> several 00:05:03.909 --> 00:05:03.919 align:start position:0% swap it out. It also generates several 00:05:03.919 --> 00:05:05.430 align:start position:0% swap it out. It also generates several options<00:05:04.320> from<00:05:04.480> one<00:05:04.640> prompt<00:05:05.000> so<00:05:05.120> you<00:05:05.240> pick 00:05:05.430 --> 00:05:05.440 align:start position:0% options from one prompt so you pick 00:05:05.440 --> 00:05:07.190 align:start position:0% options from one prompt so you pick instead<00:05:05.760> of<00:05:05.840> re-rolling.<00:05:06.560> You<00:05:06.680> get<00:05:06.880> to<00:05:07.000> it<00:05:07.120> at 00:05:07.190 --> 00:05:07.200 align:start position:0% instead of re-rolling. You get to it at 00:05:07.200 --> 00:05:09.750 align:start position:0% instead of re-rolling. You get to it at picks.new.<00:05:08.240> It<00:05:08.400> works<00:05:08.720> as<00:05:08.840> a<00:05:08.919> standalone<00:05:09.480> app 00:05:09.750 --> 00:05:09.760 align:start position:0% picks.new. It works as a standalone app 00:05:09.760 --> 00:05:11.550 align:start position:0% picks.new. It works as a standalone app on<00:05:09.840> the<00:05:09.919> web<00:05:10.440> and<00:05:10.560> it's<00:05:10.720> built<00:05:10.919> into<00:05:11.160> docs<00:05:11.440> and 00:05:11.550 --> 00:05:11.560 align:start position:0% on the web and it's built into docs and 00:05:11.560 --> 00:05:13.350 align:start position:0% on the web and it's built into docs and slides<00:05:11.880> already.<00:05:12.280> Select<00:05:12.600> an<00:05:12.680> image<00:05:13.000> inside<00:05:13.320> a 00:05:13.350 --> 00:05:13.360 align:start position:0% slides already. Select an image inside a 00:05:13.360 --> 00:05:15.510 align:start position:0% slides already. Select an image inside a doc<00:05:13.680> or<00:05:13.800> a<00:05:13.840> slide,<00:05:14.480> click<00:05:14.800> once<00:05:15.200> and<00:05:15.360> you're 00:05:15.510 --> 00:05:15.520 align:start position:0% doc or a slide, click once and you're 00:05:15.520 --> 00:05:17.950 align:start position:0% doc or a slide, click once and you're editing<00:05:16.200> with<00:05:16.400> the<00:05:16.480> full<00:05:17.000> picks<00:05:17.280> tool<00:05:17.480> set 00:05:17.950 --> 00:05:17.960 align:start position:0% editing with the full picks tool set 00:05:17.960 --> 00:05:19.590 align:start position:0% editing with the full picks tool set without<00:05:18.280> leaving<00:05:18.600> the<00:05:18.680> tab.<00:05:19.240> Drive 00:05:19.590 --> 00:05:19.600 align:start position:0% without leaving the tab. Drive 00:05:19.600 --> 00:05:21.390 align:start position:0% without leaving the tab. Drive integration<00:05:20.160> is<00:05:20.280> rolling<00:05:20.600> out.<00:05:20.960> And<00:05:21.120> Google 00:05:21.390 --> 00:05:21.400 align:start position:0% integration is rolling out. And Google 00:05:21.400 --> 00:05:23.150 align:start position:0% integration is rolling out. And Google said<00:05:21.680> you'll<00:05:21.800> be<00:05:21.919> able<00:05:22.120> to<00:05:22.240> open<00:05:22.480> and<00:05:22.640> edit 00:05:23.150 --> 00:05:23.160 align:start position:0% said you'll be able to open and edit 00:05:23.160 --> 00:05:25.510 align:start position:0% said you'll be able to open and edit nearly<00:05:23.520> any<00:05:23.800> image<00:05:24.120> saved<00:05:24.440> in<00:05:24.520> Drive<00:05:25.160> with<00:05:25.360> one 00:05:25.510 --> 00:05:25.520 align:start position:0% nearly any image saved in Drive with one 00:05:25.520 --> 00:05:27.390 align:start position:0% nearly any image saved in Drive with one click.<00:05:26.120> And<00:05:26.240> it<00:05:26.360> collaborates<00:05:26.919> like<00:05:27.080> the<00:05:27.160> rest 00:05:27.390 --> 00:05:27.400 align:start position:0% click. And it collaborates like the rest 00:05:27.400 --> 00:05:29.310 align:start position:0% click. And it collaborates like the rest of<00:05:27.520> workspace.<00:05:28.280> Share<00:05:28.600> a<00:05:28.640> link.<00:05:29.160> Your 00:05:29.310 --> 00:05:29.320 align:start position:0% of workspace. Share a link. Your 00:05:29.320 --> 00:05:31.350 align:start position:0% of workspace. Share a link. Your teammate<00:05:29.840> edits<00:05:30.120> the<00:05:30.200> same<00:05:30.440> image.<00:05:31.000> Same<00:05:31.240> as<00:05:31.320> a 00:05:31.350 --> 00:05:31.360 align:start position:0% teammate edits the same image. Same as a 00:05:31.360 --> 00:05:33.670 align:start position:0% teammate edits the same image. Same as a doc.<00:05:31.960> Dream<00:05:32.240> beans.<00:05:32.800> It's<00:05:32.960> a<00:05:33.040> Google<00:05:33.360> Labs 00:05:33.670 --> 00:05:33.680 align:start position:0% doc. Dream beans. It's a Google Labs 00:05:33.680 --> 00:05:36.110 align:start position:0% doc. Dream beans. It's a Google Labs app.<00:05:34.120> It<00:05:34.280> launched<00:05:34.640> back<00:05:34.880> in<00:05:35.000> June<00:05:35.640> for<00:05:35.840> AI 00:05:36.110 --> 00:05:36.120 align:start position:0% app. It launched back in June for AI 00:05:36.120 --> 00:05:38.630 align:start position:0% app. It launched back in June for AI Ultra<00:05:36.440> subscribers<00:05:37.280> in<00:05:37.400> the<00:05:37.520> US.<00:05:38.320> Earlier 00:05:38.630 --> 00:05:38.640 align:start position:0% Ultra subscribers in the US. Earlier 00:05:38.640 --> 00:05:40.670 align:start position:0% Ultra subscribers in the US. Earlier this<00:05:38.840> month,<00:05:39.400> Google<00:05:39.760> opened<00:05:40.040> it<00:05:40.160> up<00:05:40.360> to<00:05:40.520> all 00:05:40.670 --> 00:05:40.680 align:start position:0% this month, Google opened it up to all 00:05:40.680 --> 00:05:42.870 align:start position:0% this month, Google opened it up to all accounts<00:05:41.120> in<00:05:41.240> the<00:05:41.320> US<00:05:41.640> 18<00:05:42.000> and<00:05:42.120> over<00:05:42.640> on 00:05:42.870 --> 00:05:42.880 align:start position:0% accounts in the US 18 and over on 00:05:42.880 --> 00:05:45.190 align:start position:0% accounts in the US 18 and over on Android<00:05:43.320> and<00:05:43.440> iOS.<00:05:44.240> Here's<00:05:44.480> what<00:05:44.600> it<00:05:44.680> does. 00:05:45.190 --> 00:05:45.200 align:start position:0% Android and iOS. Here's what it does. 00:05:45.200 --> 00:05:46.790 align:start position:0% Android and iOS. Here's what it does. Overnight,<00:05:45.760> it<00:05:45.880> goes<00:05:46.120> through<00:05:46.360> the<00:05:46.440> Google 00:05:46.790 --> 00:05:46.800 align:start position:0% Overnight, it goes through the Google 00:05:46.800 --> 00:05:48.830 align:start position:0% Overnight, it goes through the Google apps<00:05:47.360> you<00:05:47.480> connect<00:05:48.000> and<00:05:48.120> builds<00:05:48.440> you<00:05:48.520> a<00:05:48.560> small 00:05:48.830 --> 00:05:48.840 align:start position:0% apps you connect and builds you a small 00:05:48.840 --> 00:05:50.710 align:start position:0% apps you connect and builds you a small set<00:05:49.000> of<00:05:49.080> stories<00:05:49.720> for<00:05:49.880> the<00:05:50.000> morning.<00:05:50.600> The 00:05:50.710 --> 00:05:50.720 align:start position:0% set of stories for the morning. The 00:05:50.720 --> 00:05:52.670 align:start position:0% set of stories for the morning. The connected<00:05:51.120> apps<00:05:51.440> are<00:05:51.560> Gmail,<00:05:52.120> calendar, 00:05:52.670 --> 00:05:52.680 align:start position:0% connected apps are Gmail, calendar, 00:05:52.680 --> 00:05:55.150 align:start position:0% connected apps are Gmail, calendar, photos,<00:05:53.480> YouTube<00:05:53.920> search<00:05:54.240> history,<00:05:54.840> and<00:05:54.960> now 00:05:55.150 --> 00:05:55.160 align:start position:0% photos, YouTube search history, and now 00:05:55.160 --> 00:05:57.030 align:start position:0% photos, YouTube search history, and now Gemini.<00:05:55.720> You<00:05:55.840> pick<00:05:56.080> which<00:05:56.320> ones.<00:05:56.560> It<00:05:56.680> needs<00:05:56.920> at 00:05:57.030 --> 00:05:57.040 align:start position:0% Gemini. You pick which ones. It needs at 00:05:57.040 --> 00:05:59.190 align:start position:0% Gemini. You pick which ones. It needs at least<00:05:57.280> one<00:05:57.520> to<00:05:57.640> work.<00:05:58.240> It<00:05:58.400> runs<00:05:58.640> on<00:05:58.760> Google's 00:05:59.190 --> 00:05:59.200 align:start position:0% least one to work. It runs on Google's 00:05:59.200 --> 00:06:01.070 align:start position:0% least one to work. It runs on Google's personal<00:05:59.560> intelligence<00:06:00.040> system,<00:06:00.720> the<00:06:00.840> same 00:06:01.070 --> 00:06:01.080 align:start position:0% personal intelligence system, the same 00:06:01.080 --> 00:06:03.830 align:start position:0% personal intelligence system, the same one<00:06:01.240> behind<00:06:01.640> the<00:06:01.720> Gemini<00:06:02.160> app<00:06:02.680> and<00:06:02.880> AI<00:06:03.120> mode. 00:06:03.830 --> 00:06:03.840 align:start position:0% one behind the Gemini app and AI mode. 00:06:03.840 --> 00:06:06.230 align:start position:0% one behind the Gemini app and AI mode. And<00:06:04.000> it<00:06:04.120> uses<00:06:04.600> nano<00:06:04.880> banana<00:06:05.240> two<00:06:05.880> to<00:06:05.960> draw<00:06:06.200> a 00:06:06.230 --> 00:06:06.240 align:start position:0% And it uses nano banana two to draw a 00:06:06.240 --> 00:06:07.790 align:start position:0% And it uses nano banana two to draw a custom<00:06:06.640> illustration<00:06:07.160> for<00:06:07.320> every<00:06:07.560> single 00:06:07.790 --> 00:06:07.800 align:start position:0% custom illustration for every single 00:06:07.800 --> 00:06:10.030 align:start position:0% custom illustration for every single story.<00:06:08.520> Google<00:06:08.800> was<00:06:08.960> clear<00:06:09.240> about<00:06:09.480> the<00:06:09.560> design 00:06:10.030 --> 00:06:10.040 align:start position:0% story. Google was clear about the design 00:06:10.040 --> 00:06:12.110 align:start position:0% story. Google was clear about the design goal.<00:06:10.640> In<00:06:10.800> their<00:06:11.000> words,<00:06:11.360> the<00:06:11.480> goal<00:06:11.720> is<00:06:11.840> not<00:06:12.040> to 00:06:12.110 --> 00:06:12.120 align:start position:0% goal. In their words, the goal is not to 00:06:12.120 --> 00:06:13.670 align:start position:0% goal. In their words, the goal is not to scroll<00:06:12.400> forever.<00:06:13.120> It's<00:06:13.200> a<00:06:13.280> finite 00:06:13.670 --> 00:06:13.680 align:start position:0% scroll forever. It's a finite 00:06:13.680 --> 00:06:15.670 align:start position:0% scroll forever. It's a finite collection.<00:06:14.360> You<00:06:14.480> finish<00:06:14.800> it.<00:06:15.120> It<00:06:15.200> ends. 00:06:15.670 --> 00:06:15.680 align:start position:0% collection. You finish it. It ends. 00:06:15.680 --> 00:06:17.350 align:start position:0% collection. You finish it. It ends. That's<00:06:15.840> a<00:06:15.920> real<00:06:16.080> choice.<00:06:16.640> Every<00:06:16.920> other<00:06:17.080> feed 00:06:17.350 --> 00:06:17.360 align:start position:0% That's a real choice. Every other feed 00:06:17.360 --> 00:06:18.990 align:start position:0% That's a real choice. Every other feed on<00:06:17.440> your<00:06:17.560> phone<00:06:17.800> is<00:06:17.960> built<00:06:18.200> to<00:06:18.280> never<00:06:18.520> end. 00:06:18.990 --> 00:06:19.000 align:start position:0% on your phone is built to never end. 00:06:19.000 --> 00:06:20.990 align:start position:0% on your phone is built to never end. Google<00:06:19.360> built<00:06:19.560> one<00:06:19.680> that<00:06:19.800> stops.<00:06:20.480> The<00:06:20.600> stories 00:06:20.990 --> 00:06:21.000 align:start position:0% Google built one that stops. The stories 00:06:21.000 --> 00:06:22.830 align:start position:0% Google built one that stops. The stories can<00:06:21.120> be<00:06:21.240> places<00:06:21.680> to<00:06:21.760> explore,<00:06:22.400> shows<00:06:22.720> to 00:06:22.830 --> 00:06:22.840 align:start position:0% can be places to explore, shows to 00:06:22.840 --> 00:06:24.590 align:start position:0% can be places to explore, shows to watch,<00:06:23.360> reminders<00:06:23.800> about<00:06:24.040> something<00:06:24.320> coming 00:06:24.590 --> 00:06:24.600 align:start position:0% watch, reminders about something coming 00:06:24.600 --> 00:06:26.670 align:start position:0% watch, reminders about something coming up.<00:06:24.960> You<00:06:25.080> can<00:06:25.200> tap<00:06:25.440> in<00:06:25.600> to<00:06:25.680> go<00:06:25.800> deeper,<00:06:26.440> book 00:06:26.670 --> 00:06:26.680 align:start position:0% up. You can tap in to go deeper, book 00:06:26.680 --> 00:06:28.590 align:start position:0% up. You can tap in to go deeper, book something,<00:06:27.200> save<00:06:27.520> it,<00:06:27.640> or<00:06:27.760> share<00:06:28.040> it.<00:06:28.400> If<00:06:28.520> a 00:06:28.590 --> 00:06:28.600 align:start position:0% something, save it, or share it. If a 00:06:28.600 --> 00:06:30.750 align:start position:0% something, save it, or share it. If a story<00:06:28.919> misses,<00:06:29.600> you<00:06:29.720> thumbs<00:06:30.040> down<00:06:30.280> it<00:06:30.360> or<00:06:30.480> tune 00:06:30.750 --> 00:06:30.760 align:start position:0% story misses, you thumbs down it or tune 00:06:30.760 --> 00:06:32.390 align:start position:0% story misses, you thumbs down it or tune it.<00:06:31.080> If<00:06:31.200> it<00:06:31.320> missed<00:06:31.560> a<00:06:31.600> new<00:06:31.760> hobby<00:06:32.040> you<00:06:32.160> picked 00:06:32.390 --> 00:06:32.400 align:start position:0% it. If it missed a new hobby you picked 00:06:32.400 --> 00:06:34.190 align:start position:0% it. If it missed a new hobby you picked up,<00:06:32.600> you<00:06:32.760> tell<00:06:32.960> it<00:06:33.320> and<00:06:33.440> future<00:06:33.720> collections 00:06:34.190 --> 00:06:34.200 align:start position:0% up, you tell it and future collections 00:06:34.200 --> 00:06:36.270 align:start position:0% up, you tell it and future collections reflect<00:06:34.560> that.<00:06:34.960> It<00:06:35.080> takes<00:06:35.320> up<00:06:35.480> to<00:06:35.600> a<00:06:35.640> day<00:06:36.160> to 00:06:36.270 --> 00:06:36.280 align:start position:0% reflect that. It takes up to a day to 00:06:36.280 --> 00:06:37.870 align:start position:0% reflect that. It takes up to a day to build<00:06:36.520> your<00:06:36.640> first<00:06:36.880> set.<00:06:37.360> And<00:06:37.480> your<00:06:37.600> dream 00:06:37.870 --> 00:06:37.880 align:start position:0% build your first set. And your dream 00:06:37.880 --> 00:06:39.510 align:start position:0% build your first set. And your dream being<00:06:38.080> settings<00:06:38.680> are<00:06:38.760> separate<00:06:39.200> from<00:06:39.400> your 00:06:39.510 --> 00:06:39.520 align:start position:0% being settings are separate from your 00:06:39.520 --> 00:06:42.150 align:start position:0% being settings are separate from your Gemini<00:06:39.919> and<00:06:40.120> AI<00:06:40.320> mode<00:06:40.560> settings.<00:06:41.360> So,<00:06:41.600> choices 00:06:42.150 --> 00:06:42.160 align:start position:0% Gemini and AI mode settings. So, choices 00:06:42.160 --> 00:06:44.070 align:start position:0% Gemini and AI mode settings. So, choices in<00:06:42.400> one<00:06:42.600> don't<00:06:42.840> bleed<00:06:43.080> into<00:06:43.320> the<00:06:43.480> other.<00:06:43.960> You 00:06:44.070 --> 00:06:44.080 align:start position:0% in one don't bleed into the other. You 00:06:44.080 --> 00:06:46.030 align:start position:0% in one don't bleed into the other. You can<00:06:44.200> delete<00:06:44.520> your<00:06:44.640> data<00:06:45.320> or<00:06:45.440> clear<00:06:45.720> parts<00:06:45.960> of 00:06:46.030 --> 00:06:46.040 align:start position:0% can delete your data or clear parts of 00:06:46.040 --> 00:06:47.710 align:start position:0% can delete your data or clear parts of your<00:06:46.120> feedback<00:06:46.520> history<00:06:46.840> in<00:06:46.919> the<00:06:47.040> app.<00:06:47.560> And 00:06:47.710 --> 00:06:47.720 align:start position:0% your feedback history in the app. And 00:06:47.720 --> 00:06:49.350 align:start position:0% your feedback history in the app. And fifth,<00:06:48.240> this<00:06:48.440> one<00:06:48.600> has<00:06:48.720> nothing<00:06:49.000> to<00:06:49.120> do<00:06:49.240> with 00:06:49.350 --> 00:06:49.360 align:start position:0% fifth, this one has nothing to do with 00:06:49.360 --> 00:06:50.590 align:start position:0% fifth, this one has nothing to do with marketing<00:06:49.840> and<00:06:49.919> I<00:06:49.960> still<00:06:50.200> think<00:06:50.400> it's<00:06:50.520> the 00:06:50.590 --> 00:06:50.600 align:start position:0% marketing and I still think it's the 00:06:50.600 --> 00:06:52.470 align:start position:0% marketing and I still think it's the most<00:06:50.880> impressive<00:06:51.320> thing<00:06:51.880> Google<00:06:52.200> shipped 00:06:52.470 --> 00:06:52.480 align:start position:0% most impressive thing Google shipped 00:06:52.480 --> 00:06:54.830 align:start position:0% most impressive thing Google shipped this<00:06:52.640> month,<00:06:52.919> AlphaFold<00:06:53.640> Atlas.<00:06:54.480> Google 00:06:54.830 --> 00:06:54.840 align:start position:0% this month, AlphaFold Atlas. Google 00:06:54.840 --> 00:06:56.909 align:start position:0% this month, AlphaFold Atlas. Google DeepMind<00:06:55.360> released<00:06:55.720> it<00:06:55.840> on<00:06:55.960> September<00:06:56.400> 8th. 00:06:56.909 --> 00:06:56.919 align:start position:0% DeepMind released it on September 8th. 00:06:56.919 --> 00:06:59.110 align:start position:0% DeepMind released it on September 8th. Human<00:06:57.240> DNA<00:06:57.760> has<00:06:58.000> about<00:06:58.240> 3<00:06:58.480> billion<00:06:58.840> base 00:06:59.110 --> 00:06:59.120 align:start position:0% Human DNA has about 3 billion base 00:06:59.120 --> 00:07:01.270 align:start position:0% Human DNA has about 3 billion base pairs.<00:06:59.720> There<00:06:59.880> are<00:07:00.000> roughly<00:07:00.400> 9<00:07:00.880> billion 00:07:01.270 --> 00:07:01.280 align:start position:0% pairs. There are roughly 9 billion 00:07:01.280 --> 00:07:03.230 align:start position:0% pairs. There are roughly 9 billion possible<00:07:01.720> single<00:07:02.040> letter<00:07:02.320> changes<00:07:02.960> you<00:07:03.080> could 00:07:03.230 --> 00:07:03.240 align:start position:0% possible single letter changes you could 00:07:03.240 --> 00:07:04.909 align:start position:0% possible single letter changes you could make<00:07:03.480> to<00:07:03.600> it.<00:07:03.880> DeepMind<00:07:04.360> predicted<00:07:04.840> the 00:07:04.909 --> 00:07:04.919 align:start position:0% make to it. DeepMind predicted the 00:07:04.919 --> 00:07:06.950 align:start position:0% make to it. DeepMind predicted the effect<00:07:05.480> of<00:07:05.640> all<00:07:05.800> 9<00:07:06.080> billion<00:07:06.400> of<00:07:06.520> them,<00:07:06.760> every 00:07:06.950 --> 00:07:06.960 align:start position:0% effect of all 9 billion of them, every 00:07:06.960 --> 00:07:08.870 align:start position:0% effect of all 9 billion of them, every single<00:07:07.240> one,<00:07:07.600> and<00:07:07.720> put<00:07:07.840> it<00:07:07.919> in<00:07:08.000> a<00:07:08.080> database. 00:07:08.870 --> 00:07:08.880 align:start position:0% single one, and put it in a database. 00:07:08.880 --> 00:07:11.230 align:start position:0% single one, and put it in a database. It's<00:07:09.120> a<00:07:09.240> 1<00:07:09.560> petabyte<00:07:10.040> data<00:07:10.280> set.<00:07:10.760> Scientific 00:07:11.230 --> 00:07:11.240 align:start position:0% It's a 1 petabyte data set. Scientific 00:07:11.240 --> 00:07:13.150 align:start position:0% It's a 1 petabyte data set. Scientific American<00:07:11.600> noted<00:07:12.160> it's<00:07:12.320> about<00:07:12.560> 30<00:07:12.880> times 00:07:13.150 --> 00:07:13.160 align:start position:0% American noted it's about 30 times 00:07:13.160 --> 00:07:15.190 align:start position:0% American noted it's about 30 times larger<00:07:13.600> than<00:07:13.840> the<00:07:13.919> AlphaFold<00:07:14.440> database, 00:07:15.190 --> 00:07:15.200 align:start position:0% larger than the AlphaFold database, 00:07:15.200 --> 00:07:16.590 align:start position:0% larger than the AlphaFold database, though<00:07:15.360> less<00:07:15.600> accurate.<00:07:16.200> Here's<00:07:16.400> why<00:07:16.520> it 00:07:16.590 --> 00:07:16.600 align:start position:0% though less accurate. Here's why it 00:07:16.600 --> 00:07:19.070 align:start position:0% though less accurate. Here's why it matters.<00:07:17.200> Scientists<00:07:17.760> understand<00:07:18.320> the<00:07:18.440> 2%<00:07:19.000> of 00:07:19.070 --> 00:07:19.080 align:start position:0% matters. Scientists understand the 2% of 00:07:19.080 --> 00:07:20.710 align:start position:0% matters. Scientists understand the 2% of the<00:07:19.200> genome<00:07:19.640> that<00:07:19.800> codes<00:07:20.120> for<00:07:20.240> proteins 00:07:20.710 --> 00:07:20.720 align:start position:0% the genome that codes for proteins 00:07:20.720 --> 00:07:23.790 align:start position:0% the genome that codes for proteins fairly<00:07:21.000> well.<00:07:21.440> The<00:07:21.680> other<00:07:22.040> 98%<00:07:23.360> is<00:07:23.600> the 00:07:23.790 --> 00:07:23.800 align:start position:0% fairly well. The other 98% is the 00:07:23.800 --> 00:07:26.070 align:start position:0% fairly well. The other 98% is the control<00:07:24.240> panel.<00:07:24.880> It<00:07:25.000> decides<00:07:25.520> when<00:07:25.720> genes 00:07:26.070 --> 00:07:26.080 align:start position:0% control panel. It decides when genes 00:07:26.080 --> 00:07:28.310 align:start position:0% control panel. It decides when genes turn<00:07:26.360> on,<00:07:26.760> how<00:07:26.919> much,<00:07:27.400> and<00:07:27.560> where.<00:07:28.000> Most 00:07:28.310 --> 00:07:28.320 align:start position:0% turn on, how much, and where. Most 00:07:28.320 --> 00:07:30.510 align:start position:0% turn on, how much, and where. Most variations<00:07:28.880> tied<00:07:29.240> to<00:07:29.360> traits<00:07:29.720> and<00:07:29.840> disease 00:07:30.510 --> 00:07:30.520 align:start position:0% variations tied to traits and disease 00:07:30.520 --> 00:07:33.030 align:start position:0% variations tied to traits and disease sit<00:07:30.840> in<00:07:30.960> that<00:07:31.160> 98%<00:07:32.400> and<00:07:32.520> it's<00:07:32.680> been<00:07:32.960> the 00:07:33.030 --> 00:07:33.040 align:start position:0% sit in that 98% and it's been the 00:07:33.040 --> 00:07:35.070 align:start position:0% sit in that 98% and it's been the hardest<00:07:33.400> part<00:07:33.640> to<00:07:33.760> read.<00:07:34.320> Before<00:07:34.640> this,<00:07:35.000> a 00:07:35.070 --> 00:07:35.080 align:start position:0% hardest part to read. Before this, a 00:07:35.080 --> 00:07:36.909 align:start position:0% hardest part to read. Before this, a researcher<00:07:35.680> had<00:07:35.880> to<00:07:35.960> pick<00:07:36.160> which<00:07:36.400> variants<00:07:36.800> to 00:07:36.909 --> 00:07:36.919 align:start position:0% researcher had to pick which variants to 00:07:36.919 --> 00:07:39.350 align:start position:0% researcher had to pick which variants to test,<00:07:37.600> then<00:07:37.840> run<00:07:38.040> the<00:07:38.120> model<00:07:38.440> on<00:07:38.640> each<00:07:38.880> one, 00:07:39.350 --> 00:07:39.360 align:start position:0% test, then run the model on each one, 00:07:39.360 --> 00:07:40.790 align:start position:0% test, then run the model on each one, which<00:07:39.560> means<00:07:39.960> you<00:07:40.080> had<00:07:40.280> to<00:07:40.360> already<00:07:40.600> have<00:07:40.760> a 00:07:40.790 --> 00:07:40.800 align:start position:0% which means you had to already have a 00:07:40.800 --> 00:07:42.590 align:start position:0% which means you had to already have a guess.<00:07:41.360> So,<00:07:41.600> let<00:07:41.800> me<00:07:41.920> tie<00:07:42.120> these<00:07:42.360> five 00:07:42.590 --> 00:07:42.600 align:start position:0% guess. So, let me tie these five 00:07:42.600 --> 00:07:44.470 align:start position:0% guess. So, let me tie these five together<00:07:43.240> because<00:07:43.560> there's<00:07:43.800> a<00:07:43.840> pattern. 00:07:44.470 --> 00:07:44.480 align:start position:0% together because there's a pattern. 00:07:44.480 --> 00:07:45.990 align:start position:0% together because there's a pattern. Every<00:07:44.760> single<00:07:45.040> one<00:07:45.200> of<00:07:45.280> them<00:07:45.520> is<00:07:45.680> about<00:07:45.920> the 00:07:45.990 --> 00:07:46.000 align:start position:0% Every single one of them is about the 00:07:46.000 --> 00:07:48.510 align:start position:0% Every single one of them is about the same<00:07:46.240> thing.<00:07:46.840> Taking<00:07:47.280> work<00:07:48.000> that<00:07:48.160> used<00:07:48.400> to 00:07:48.510 --> 00:07:48.520 align:start position:0% same thing. Taking work that used to 00:07:48.520 --> 00:07:49.870 align:start position:0% same thing. Taking work that used to happen<00:07:48.800> in<00:07:48.920> sequence<00:07:49.400> and<00:07:49.520> doing<00:07:49.720> it<00:07:49.800> in 00:07:49.870 --> 00:07:49.880 align:start position:0% happen in sequence and doing it in 00:07:49.880 --> 00:07:52.310 align:start position:0% happen in sequence and doing it in parallel.<00:07:50.520> Gemini<00:07:50.920> 3.8<00:07:51.600> live<00:07:51.840> doesn't<00:07:52.120> stop 00:07:52.310 --> 00:07:52.320 align:start position:0% parallel. Gemini 3.8 live doesn't stop 00:07:52.320 --> 00:07:54.790 align:start position:0% parallel. Gemini 3.8 live doesn't stop talking<00:07:52.680> to<00:07:52.760> go<00:07:52.880> do<00:07:53.040> the<00:07:53.160> task.<00:07:53.840> It<00:07:53.960> does<00:07:54.200> both. 00:07:54.790 --> 00:07:54.800 align:start position:0% talking to go do the task. It does both. 00:07:54.800 --> 00:07:56.630 align:start position:0% talking to go do the task. It does both. CC<00:07:55.200> doesn't<00:07:55.480> wait<00:07:55.680> for<00:07:55.800> one<00:07:55.920> person<00:07:56.280> to<00:07:56.360> gather 00:07:56.630 --> 00:07:56.640 align:start position:0% CC doesn't wait for one person to gather 00:07:56.640 --> 00:07:58.470 align:start position:0% CC doesn't wait for one person to gather everything.<00:07:57.280> Six<00:07:57.560> people<00:07:57.880> feed<00:07:58.120> it<00:07:58.280> and<00:07:58.400> it 00:07:58.470 --> 00:07:58.480 align:start position:0% everything. Six people feed it and it 00:07:58.480 --> 00:08:00.630 align:start position:0% everything. Six people feed it and it sorts.<00:07:59.160> Pिक्स<00:07:59.480> doesn't<00:07:59.720> make<00:07:59.920> you<00:08:00.080> regenerate 00:08:00.630 --> 00:08:00.640 align:start position:0% sorts. Pिक्स doesn't make you regenerate 00:08:00.640 --> 00:08:02.670 align:start position:0% sorts. Pिक्स doesn't make you regenerate the<00:08:00.720> whole<00:08:00.960> image<00:08:01.360> to<00:08:01.480> change<00:08:01.800> one<00:08:01.960> word.<00:08:02.520> It 00:08:02.670 --> 00:08:02.680 align:start position:0% the whole image to change one word. It 00:08:02.680 --> 00:08:04.670 align:start position:0% the whole image to change one word. It edits<00:08:03.000> the<00:08:03.120> part.<00:08:03.680> Dream<00:08:03.920> Beans<00:08:04.240> doesn't<00:08:04.480> make 00:08:04.670 --> 00:08:04.680 align:start position:0% edits the part. Dream Beans doesn't make 00:08:04.680 --> 00:08:06.750 align:start position:0% edits the part. Dream Beans doesn't make you<00:08:04.760> check<00:08:05.280> six<00:08:05.720> apps.<00:08:06.120> It<00:08:06.320> reads<00:08:06.560> them 00:08:06.750 --> 00:08:06.760 align:start position:0% you check six apps. It reads them 00:08:06.760 --> 00:08:08.830 align:start position:0% you check six apps. It reads them overnight<00:08:07.200> and<00:08:07.320> hands<00:08:07.600> you<00:08:07.720> one<00:08:07.880> short<00:08:08.160> stack. 00:08:08.830 --> 00:08:08.840 align:start position:0% overnight and hands you one short stack. 00:08:08.840 --> 00:08:10.710 align:start position:0% overnight and hands you one short stack. Alpha<00:08:09.120> Genome<00:08:09.560> Atlas<00:08:10.200> doesn't<00:08:10.520> make 00:08:10.710 --> 00:08:10.720 align:start position:0% Alpha Genome Atlas doesn't make 00:08:10.720 --> 00:08:12.590 align:start position:0% Alpha Genome Atlas doesn't make researchers<00:08:11.320> run<00:08:11.520> the<00:08:11.600> model<00:08:11.880> one<00:08:12.080> variant<00:08:12.480> at 00:08:12.590 --> 00:08:12.600 align:start position:0% researchers run the model one variant at 00:08:12.600 --> 00:08:15.630 align:start position:0% researchers run the model one variant at a<00:08:12.640> time.<00:08:13.240> It<00:08:13.440> ran<00:08:13.800> all<00:08:14.000> 9<00:08:14.280> billion<00:08:14.720> in<00:08:14.840> advance. 00:08:15.630 --> 00:08:15.640 align:start position:0% a time. It ran all 9 billion in advance. 00:08:15.640 --> 00:08:18.590 align:start position:0% a time. It ran all 9 billion in advance. Same<00:08:16.000> idea<00:08:16.560> five<00:08:16.880> times<00:08:17.480> in<00:08:17.640> one<00:08:17.840> week.<00:08:18.320> Both 00:08:18.590 --> 00:08:18.600 align:start position:0% Same idea five times in one week. Both 00:08:18.600 --> 00:08:20.710 align:start position:0% Same idea five times in one week. Both groups<00:08:18.919> have<00:08:19.160> access<00:08:19.880> to<00:08:20.000> the<00:08:20.120> exact<00:08:20.480> same 00:08:20.710 --> 00:08:20.720 align:start position:0% groups have access to the exact same 00:08:20.720 --> 00:08:22.510 align:start position:0% groups have access to the exact same tools.<00:08:21.120> One<00:08:21.360> group<00:08:21.680> just<00:08:21.919> sat<00:08:22.120> down<00:08:22.400> and 00:08:22.510 --> 00:08:22.520 align:start position:0% tools. One group just sat down and 00:08:22.520 --> 00:08:23.670 align:start position:0% tools. One group just sat down and learned<00:08:22.720> them.<00:08:23.000> If<00:08:23.120> you<00:08:23.200> want<00:08:23.320> to<00:08:23.400> be<00:08:23.480> in<00:08:23.560> the 00:08:23.670 --> 00:08:23.680 align:start position:0% learned them. If you want to be in the 00:08:23.680 --> 00:08:25.790 align:start position:0% learned them. If you want to be in the first<00:08:24.000> group,<00:08:24.520> that's<00:08:24.800> what<00:08:24.919> we<00:08:25.080> built<00:08:25.360> the<00:08:25.520> AI 00:08:25.790 --> 00:08:25.800 align:start position:0% first group, that's what we built the AI 00:08:25.800 --> 00:08:27.870 align:start position:0% first group, that's what we built the AI Profit<00:08:26.160> Boardroom<00:08:26.560> for.<00:08:27.040> We've<00:08:27.160> got<00:08:27.280> a<00:08:27.320> 30-day 00:08:27.870 --> 00:08:27.880 align:start position:0% Profit Boardroom for. We've got a 30-day 00:08:27.880 --> 00:08:30.070 align:start position:0% Profit Boardroom for. We've got a 30-day roadmap<00:08:28.600> for<00:08:28.800> Google's<00:08:29.400> agent<00:08:29.760> stack 00:08:30.070 --> 00:08:30.080 align:start position:0% roadmap for Google's agent stack 00:08:30.080 --> 00:08:32.909 align:start position:0% roadmap for Google's agent stack specifically.<00:08:31.000> Gemini<00:08:31.560> live<00:08:31.919> voice<00:08:32.240> agents, 00:08:32.909 --> 00:08:32.919 align:start position:0% specifically. Gemini live voice agents, 00:08:32.919 --> 00:08:34.830 align:start position:0% specifically. Gemini live voice agents, workspace<00:08:33.440> automations,<00:08:34.320> Pिक्स<00:08:34.599> for<00:08:34.680> your 00:08:34.830 --> 00:08:34.840 align:start position:0% workspace automations, Pिक्स for your 00:08:34.840 --> 00:08:36.709 align:start position:0% workspace automations, Pिक्स for your visuals,<00:08:35.440> shared<00:08:35.800> agents<00:08:36.120> for<00:08:36.240> your<00:08:36.360> team, 00:08:36.709 --> 00:08:36.719 align:start position:0% visuals, shared agents for your team, 00:08:36.719 --> 00:08:38.510 align:start position:0% visuals, shared agents for your team, four<00:08:37.000> coaching<00:08:37.320> calls<00:08:37.560> every<00:08:37.760> week<00:08:38.320> where<00:08:38.400> we 00:08:38.510 --> 00:08:38.520 align:start position:0% four coaching calls every week where we 00:08:38.520 --> 00:08:40.550 align:start position:0% four coaching calls every week where we go<00:08:38.680> deep<00:08:39.000> on<00:08:39.120> this<00:08:39.280> exact<00:08:39.599> stuff<00:08:40.200> and<00:08:40.320> you<00:08:40.400> can 00:08:40.550 --> 00:08:40.560 align:start position:0% go deep on this exact stuff and you can 00:08:40.560 --> 00:08:42.430 align:start position:0% go deep on this exact stuff and you can bring<00:08:40.880> your<00:08:41.080> own<00:08:41.200> setup<00:08:41.640> and<00:08:41.800> ask<00:08:41.960> questions 00:08:42.430 --> 00:08:42.440 align:start position:0% bring your own setup and ask questions 00:08:42.440 --> 00:08:44.990 align:start position:0% bring your own setup and ask questions live.<00:08:43.000> Daily<00:08:43.440> tutorials<00:08:44.480> showing<00:08:44.880> you 00:08:44.990 --> 00:08:45.000 align:start position:0% live. Daily tutorials showing you 00:08:45.000 --> 00:08:47.310 align:start position:0% live. Daily tutorials showing you step-by-step<00:08:45.720> how<00:08:45.880> to<00:08:46.000> use<00:08:46.320> each<00:08:46.520> release<00:08:47.120> as 00:08:47.310 --> 00:08:47.320 align:start position:0% step-by-step how to use each release as 00:08:47.320 --> 00:08:49.350 align:start position:0% step-by-step how to use each release as it<00:08:47.440> ships<00:08:48.080> so<00:08:48.240> you're<00:08:48.360> never<00:08:48.560> behind.<00:08:49.280> A 00:08:49.350 --> 00:08:49.360 align:start position:0% it ships so you're never behind. A 00:08:49.360 --> 00:08:51.390 align:start position:0% it ships so you're never behind. A prompt<00:08:49.760> library<00:08:50.240> built<00:08:50.680> around<00:08:51.000> Google's 00:08:51.390 --> 00:08:51.400 align:start position:0% prompt library built around Google's 00:08:51.400 --> 00:08:53.430 align:start position:0% prompt library built around Google's tools.<00:08:51.960> Business<00:08:52.320> owners<00:08:52.640> inside,<00:08:53.080> plenty<00:08:53.400> of 00:08:53.430 --> 00:08:53.440 align:start position:0% tools. Business owners inside, plenty of 00:08:53.440 --> 00:08:54.990 align:start position:0% tools. Business owners inside, plenty of them<00:08:53.600> already<00:08:53.880> automating<00:08:54.360> their<00:08:54.520> lead, 00:08:54.990 --> 00:08:55.000 align:start position:0% them already automating their lead, 00:08:55.000 --> 00:08:56.590 align:start position:0% them already automating their lead, follow-up,<00:08:55.360> and<00:08:55.480> content<00:08:55.880> with<00:08:56.000> Gemini<00:08:56.360> right 00:08:56.590 --> 00:08:56.600 align:start position:0% follow-up, and content with Gemini right 00:08:56.600 --> 00:08:58.510 align:start position:0% follow-up, and content with Gemini right now.<00:08:57.080> And<00:08:57.200> a<00:08:57.240> member<00:08:57.520> map<00:08:57.800> so<00:08:57.920> you<00:08:58.000> can<00:08:58.160> connect 00:08:58.510 --> 00:08:58.520 align:start position:0% now. And a member map so you can connect 00:08:58.520 --> 00:08:59.829 align:start position:0% now. And a member map so you can connect with<00:08:58.640> people<00:08:58.960> near<00:08:59.160> you<00:08:59.280> doing<00:08:59.520> the<00:08:59.600> same 00:08:59.829 --> 00:08:59.839 align:start position:0% with people near you doing the same 00:08:59.839 --> 00:09:01.990 align:start position:0% with people near you doing the same work.<00:09:00.360> Someone's<00:09:00.800> always<00:09:01.000> online.<00:09:01.640> Link<00:09:01.920> in 00:09:01.990 --> 00:09:02.000 align:start position:0% work. Someone's always online. Link in 00:09:02.000 --> 00:09:03.590 align:start position:0% work. Someone's always online. Link in the<00:09:02.080> comments<00:09:02.360> and<00:09:02.440> description<00:09:03.120> or<00:09:03.240> go<00:09:03.400> to 00:09:03.590 --> 00:09:03.600 align:start position:0% the comments and description or go to 00:09:03.600 --> 00:09:05.150 align:start position:0% the comments and description or go to aiprofitboardroom.com. 00:09:05.150 --> 00:09:05.160 align:start position:0% aiprofitboardroom.com. 00:09:05.160 --> 00:09:06.590 align:start position:0% aiprofitboardroom.com. If<00:09:05.320> you're<00:09:05.480> creating<00:09:05.839> all<00:09:05.920> this<00:09:06.080> content<00:09:06.440> with 00:09:06.590 --> 00:09:06.600 align:start position:0% If you're creating all this content with 00:09:06.600 --> 00:09:08.430 align:start position:0% If you're creating all this content with AI<00:09:06.880> but<00:09:07.040> nobody's<00:09:07.400> finding<00:09:07.680> it<00:09:07.800> online, 00:09:08.430 --> 00:09:08.440 align:start position:0% AI but nobody's finding it online, 00:09:08.440 --> 00:09:09.950 align:start position:0% AI but nobody's finding it online, you've<00:09:08.600> got<00:09:08.760> a<00:09:08.800> traffic<00:09:09.200> problem.<00:09:09.760> That's 00:09:09.950 --> 00:09:09.960 align:start position:0% you've got a traffic problem. That's 00:09:09.960 --> 00:09:12.510 align:start position:0% you've got a traffic problem. That's where<00:09:10.200> SEO<00:09:10.920> comes<00:09:11.200> in.<00:09:11.600> Great<00:09:11.880> content<00:09:12.280> means 00:09:12.510 --> 00:09:12.520 align:start position:0% where SEO comes in. Great content means 00:09:12.520 --> 00:09:14.270 align:start position:0% where SEO comes in. Great content means nothing<00:09:12.880> if<00:09:13.000> it's<00:09:13.120> not<00:09:13.280> built<00:09:13.480> to<00:09:13.600> rank<00:09:14.120> and 00:09:14.270 --> 00:09:14.280 align:start position:0% nothing if it's not built to rank and 00:09:14.280 --> 00:09:16.030 align:start position:0% nothing if it's not built to rank and most<00:09:14.520> businesses<00:09:15.120> are<00:09:15.240> sitting<00:09:15.520> on<00:09:15.640> content 00:09:16.030 --> 00:09:16.040 align:start position:0% most businesses are sitting on content 00:09:16.040 --> 00:09:17.790 align:start position:0% most businesses are sitting on content that<00:09:16.160> nobody<00:09:16.480> will<00:09:16.600> ever<00:09:16.760> see<00:09:16.960> because<00:09:17.560> the 00:09:17.790 --> 00:09:17.800 align:start position:0% that nobody will ever see because the 00:09:17.800 --> 00:09:19.870 align:start position:0% that nobody will ever see because the SEO<00:09:18.320> side<00:09:18.600> was<00:09:18.720> never<00:09:18.920> handled<00:09:19.280> properly. 00:09:19.870 --> 00:09:19.880 align:start position:0% SEO side was never handled properly. 00:09:19.880 --> 00:09:21.910 align:start position:0% SEO side was never handled properly. That's<00:09:20.120> exactly<00:09:20.480> what<00:09:20.640> my<00:09:20.760> team<00:09:21.000> focuses<00:09:21.520> on 00:09:21.910 --> 00:09:21.920 align:start position:0% That's exactly what my team focuses on 00:09:21.920 --> 00:09:24.350 align:start position:0% That's exactly what my team focuses on every<00:09:22.200> single<00:09:22.480> day.<00:09:23.080> Book<00:09:23.360> a<00:09:23.440> free<00:09:23.839> SEO 00:09:24.350 --> 00:09:24.360 align:start position:0% every single day. Book a free SEO 00:09:24.360 --> 00:09:26.510 align:start position:0% every single day. Book a free SEO strategy<00:09:25.120> session<00:09:25.480> with<00:09:25.600> my<00:09:25.720> team<00:09:26.280> and<00:09:26.400> we'll 00:09:26.510 --> 00:09:26.520 align:start position:0% strategy session with my team and we'll 00:09:26.520 --> 00:09:28.710 align:start position:0% strategy session with my team and we'll walk<00:09:26.760> you<00:09:26.880> through<00:09:27.400> what<00:09:27.560> it<00:09:27.680> actually<00:09:28.000> takes 00:09:28.710 --> 00:09:28.720 align:start position:0% walk you through what it actually takes 00:09:28.720 --> 00:09:30.950 align:start position:0% walk you through what it actually takes to<00:09:28.800> get<00:09:28.960> your<00:09:29.080> site<00:09:29.520> ranking<00:09:30.000> on<00:09:30.200> Google<00:09:30.800> and 00:09:30.950 --> 00:09:30.960 align:start position:0% to get your site ranking on Google and 00:09:30.960 --> 00:09:33.070 align:start position:0% to get your site ranking on Google and pulling<00:09:31.200> in<00:09:31.400> real<00:09:31.600> traffic.<00:09:32.360> The<00:09:32.440> link<00:09:32.760> is<00:09:32.960> in 00:09:33.070 --> 00:09:33.080 align:start position:0% pulling in real traffic. The link is in 00:09:33.080 --> 00:09:36.520 align:start position:0% pulling in real traffic. The link is in the<00:09:33.160> comments<00:09:33.520> and<00:09:33.640> description<00:09:34.120> below.