WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:02.990 align:start position:0% Google's<00:00:00.720> Gemini<00:00:01.320> AI<00:00:01.840> just<00:00:02.120> hit<00:00:02.320> 1<00:00:02.560> billion 00:00:02.990 --> 00:00:03.000 align:start position:0% Google's Gemini AI just hit 1 billion 00:00:03.000 --> 00:00:04.910 align:start position:0% Google's Gemini AI just hit 1 billion monthly<00:00:03.360> users.<00:00:03.800> And<00:00:03.920> in<00:00:04.000> the<00:00:04.080> same<00:00:04.360> week, 00:00:04.910 --> 00:00:04.920 align:start position:0% monthly users. And in the same week, 00:00:04.920 --> 00:00:07.670 align:start position:0% monthly users. And in the same week, Google<00:00:05.240> gave<00:00:05.520> it<00:00:05.800> 13<00:00:06.600> new<00:00:06.880> powers.<00:00:07.360> That's<00:00:07.600> the 00:00:07.670 --> 00:00:07.680 align:start position:0% Google gave it 13 new powers. That's the 00:00:07.680 --> 00:00:10.310 align:start position:0% Google gave it 13 new powers. That's the story<00:00:08.000> today.<00:00:08.600> Google's<00:00:09.080> Gemini<00:00:09.520> AI<00:00:10.080> just 00:00:10.310 --> 00:00:10.320 align:start position:0% story today. Google's Gemini AI just 00:00:10.320 --> 00:00:12.430 align:start position:0% story today. Google's Gemini AI just crossed<00:00:10.800> 1<00:00:11.080> billion<00:00:11.440> people<00:00:11.840> using<00:00:12.120> it<00:00:12.240> every 00:00:12.430 --> 00:00:12.440 align:start position:0% crossed 1 billion people using it every 00:00:12.440 --> 00:00:14.310 align:start position:0% crossed 1 billion people using it every month.<00:00:13.000> Sundar<00:00:13.360> Pichai<00:00:13.840> announced<00:00:14.240> it 00:00:14.310 --> 00:00:14.320 align:start position:0% month. Sundar Pichai announced it 00:00:14.320 --> 00:00:16.150 align:start position:0% month. Sundar Pichai announced it himself.<00:00:15.000> He<00:00:15.160> called<00:00:15.440> it<00:00:15.520> the<00:00:15.600> fastest 00:00:16.150 --> 00:00:16.160 align:start position:0% himself. He called it the fastest 00:00:16.160 --> 00:00:17.950 align:start position:0% himself. He called it the fastest growing<00:00:16.480> product<00:00:16.840> in<00:00:16.960> Google's<00:00:17.280> 28-year 00:00:17.950 --> 00:00:17.960 align:start position:0% growing product in Google's 28-year 00:00:17.960 --> 00:00:20.110 align:start position:0% growing product in Google's 28-year history.<00:00:18.280> Not<00:00:18.480> the<00:00:18.560> fastest<00:00:19.120> AI<00:00:19.400> product,<00:00:20.040> the 00:00:20.110 --> 00:00:20.120 align:start position:0% history. Not the fastest AI product, the 00:00:20.120 --> 00:00:22.590 align:start position:0% history. Not the fastest AI product, the fastest<00:00:20.600> product,<00:00:21.160> period.<00:00:22.000> Faster<00:00:22.440> than 00:00:22.590 --> 00:00:22.600 align:start position:0% fastest product, period. Faster than 00:00:22.600 --> 00:00:25.110 align:start position:0% fastest product, period. Faster than search,<00:00:23.240> faster<00:00:23.680> than<00:00:23.840> Gmail,<00:00:24.480> faster<00:00:24.960> than 00:00:25.110 --> 00:00:25.120 align:start position:0% search, faster than Gmail, faster than 00:00:25.120 --> 00:00:27.190 align:start position:0% search, faster than Gmail, faster than YouTube.<00:00:25.800> Here's<00:00:26.040> how<00:00:26.160> fast.<00:00:26.520> In<00:00:26.680> May<00:00:26.880> last 00:00:27.190 --> 00:00:27.200 align:start position:0% YouTube. Here's how fast. In May last 00:00:27.200 --> 00:00:30.230 align:start position:0% YouTube. Here's how fast. In May last year,<00:00:27.680> Gemini<00:00:28.160> had<00:00:28.400> 400<00:00:29.000> million<00:00:29.320> users.<00:00:30.080> By 00:00:30.230 --> 00:00:30.240 align:start position:0% year, Gemini had 400 million users. By 00:00:30.240 --> 00:00:32.630 align:start position:0% year, Gemini had 400 million users. By this<00:00:30.480> May,<00:00:30.920> it<00:00:31.040> hit<00:00:31.200> 900<00:00:31.760> million.<00:00:32.360> Then<00:00:32.560> in 00:00:32.630 --> 00:00:32.640 align:start position:0% this May, it hit 900 million. Then in 00:00:32.640 --> 00:00:35.630 align:start position:0% this May, it hit 900 million. Then in July,<00:00:33.360> it<00:00:33.440> was<00:00:33.560> at<00:00:33.680> 950<00:00:34.640> million.<00:00:35.200> And<00:00:35.320> in<00:00:35.440> less 00:00:35.630 --> 00:00:35.640 align:start position:0% July, it was at 950 million. And in less 00:00:35.640 --> 00:00:37.110 align:start position:0% July, it was at 950 million. And in less than<00:00:35.760> a<00:00:35.800> month<00:00:36.040> after<00:00:36.280> that,<00:00:36.520> it<00:00:36.600> crossed<00:00:36.920> 1 00:00:37.110 --> 00:00:37.120 align:start position:0% than a month after that, it crossed 1 00:00:37.120 --> 00:00:39.550 align:start position:0% than a month after that, it crossed 1 billion.<00:00:37.720> That<00:00:37.920> last<00:00:38.200> stretch<00:00:38.560> from<00:00:38.760> 950 00:00:39.550 --> 00:00:39.560 align:start position:0% billion. That last stretch from 950 00:00:39.560 --> 00:00:41.950 align:start position:0% billion. That last stretch from 950 million<00:00:39.840> to<00:00:39.960> 1<00:00:40.120> billion<00:00:40.720> took<00:00:40.960> Gemini<00:00:41.400> about<00:00:41.760> 2 00:00:41.950 --> 00:00:41.960 align:start position:0% million to 1 billion took Gemini about 2 00:00:41.960 --> 00:00:44.870 align:start position:0% million to 1 billion took Gemini about 2 weeks.<00:00:42.680> 2<00:00:42.880> weeks<00:00:43.120> to<00:00:43.200> add<00:00:43.360> 50<00:00:43.680> million<00:00:43.960> people. 00:00:44.870 --> 00:00:44.880 align:start position:0% weeks. 2 weeks to add 50 million people. 00:00:44.880 --> 00:00:47.150 align:start position:0% weeks. 2 weeks to add 50 million people. A<00:00:45.000> year<00:00:45.240> ago,<00:00:45.600> an<00:00:45.840> AI<00:00:46.120> app<00:00:46.320> crossing<00:00:46.680> 400 00:00:47.150 --> 00:00:47.160 align:start position:0% A year ago, an AI app crossing 400 00:00:47.160 --> 00:00:49.510 align:start position:0% A year ago, an AI app crossing 400 million<00:00:47.480> users<00:00:48.200> felt<00:00:48.520> huge.<00:00:48.880> Now,<00:00:49.040> Google<00:00:49.400> is 00:00:49.510 --> 00:00:49.520 align:start position:0% million users felt huge. Now, Google is 00:00:49.520 --> 00:00:51.390 align:start position:0% million users felt huge. Now, Google is adding<00:00:49.760> tens<00:00:50.160> of<00:00:50.240> millions<00:00:50.520> of<00:00:50.640> users<00:00:51.240> in<00:00:51.360> a 00:00:51.390 --> 00:00:51.400 align:start position:0% adding tens of millions of users in a 00:00:51.400 --> 00:00:53.150 align:start position:0% adding tens of millions of users in a matter<00:00:51.640> of<00:00:51.720> days.<00:00:52.360> That's<00:00:52.640> the<00:00:52.720> curve<00:00:53.040> we're 00:00:53.150 --> 00:00:53.160 align:start position:0% matter of days. That's the curve we're 00:00:53.160 --> 00:00:55.310 align:start position:0% matter of days. That's the curve we're on.<00:00:53.560> It's<00:00:53.760> not<00:00:54.000> slowing<00:00:54.320> down.<00:00:54.760> It's<00:00:54.920> speeding 00:00:55.310 --> 00:00:55.320 align:start position:0% on. It's not slowing down. It's speeding 00:00:55.320 --> 00:00:56.790 align:start position:0% on. It's not slowing down. It's speeding up.<00:00:55.520> And<00:00:55.640> Google<00:00:55.920> isn't<00:00:56.160> just<00:00:56.320> celebrating 00:00:56.790 --> 00:00:56.800 align:start position:0% up. And Google isn't just celebrating 00:00:56.800 --> 00:00:58.990 align:start position:0% up. And Google isn't just celebrating the<00:00:56.880> number.<00:00:57.560> They<00:00:57.680> used<00:00:57.920> that<00:00:58.080> same<00:00:58.360> week<00:00:58.880> to 00:00:58.990 --> 00:00:59.000 align:start position:0% the number. They used that same week to 00:00:59.000 --> 00:01:01.510 align:start position:0% the number. They used that same week to roll<00:00:59.240> out<00:00:59.480> two<00:00:59.760> big<00:01:00.080> changes<00:01:00.840> to<00:01:00.960> what<00:01:01.120> Gemini 00:01:01.510 --> 00:01:01.520 align:start position:0% roll out two big changes to what Gemini 00:01:01.520 --> 00:01:02.910 align:start position:0% roll out two big changes to what Gemini can<00:01:01.680> actually<00:01:02.000> do<00:01:02.160> for<00:01:02.320> you.<00:01:02.480> The<00:01:02.600> first 00:01:02.910 --> 00:01:02.920 align:start position:0% can actually do for you. The first 00:01:02.920 --> 00:01:05.390 align:start position:0% can actually do for you. The first change<00:01:03.160> is<00:01:03.280> inside<00:01:03.960> Gemini<00:01:04.400> notebook.<00:01:05.160> If<00:01:05.320> you 00:01:05.390 --> 00:01:05.400 align:start position:0% change is inside Gemini notebook. If you 00:01:05.400 --> 00:01:07.310 align:start position:0% change is inside Gemini notebook. If you don't<00:01:05.600> know<00:01:05.760> Gemini<00:01:06.160> notebook,<00:01:06.880> think<00:01:07.120> of<00:01:07.200> it 00:01:07.310 --> 00:01:07.320 align:start position:0% don't know Gemini notebook, think of it 00:01:07.320 --> 00:01:09.230 align:start position:0% don't know Gemini notebook, think of it as<00:01:07.440> a<00:01:07.520> folder<00:01:08.240> where<00:01:08.400> you<00:01:08.520> dump<00:01:08.920> all<00:01:09.040> your 00:01:09.230 --> 00:01:09.240 align:start position:0% as a folder where you dump all your 00:01:09.240 --> 00:01:11.430 align:start position:0% as a folder where you dump all your research,<00:01:09.840> documents,<00:01:10.440> and<00:01:10.560> notes,<00:01:11.200> and<00:01:11.320> the 00:01:11.430 --> 00:01:11.440 align:start position:0% research, documents, and notes, and the 00:01:11.440 --> 00:01:13.670 align:start position:0% research, documents, and notes, and the AI<00:01:11.800> reads<00:01:12.240> through<00:01:12.480> everything<00:01:12.880> for<00:01:13.160> you.<00:01:13.600> It 00:01:13.670 --> 00:01:13.680 align:start position:0% AI reads through everything for you. It 00:01:13.680 --> 00:01:16.110 align:start position:0% AI reads through everything for you. It used<00:01:13.880> to<00:01:13.960> be<00:01:14.040> called<00:01:14.320> notebook<00:01:14.920> LM.<00:01:15.720> Google 00:01:16.110 --> 00:01:16.120 align:start position:0% used to be called notebook LM. Google 00:01:16.120 --> 00:01:18.030 align:start position:0% used to be called notebook LM. Google renamed<00:01:16.560> it<00:01:16.680> back<00:01:16.920> in<00:01:17.000> July.<00:01:17.560> Now,<00:01:17.720> here's<00:01:17.960> the 00:01:18.030 --> 00:01:18.040 align:start position:0% renamed it back in July. Now, here's the 00:01:18.040 --> 00:01:20.150 align:start position:0% renamed it back in July. Now, here's the new<00:01:18.240> part.<00:01:18.680> As<00:01:18.840> of<00:01:18.960> August<00:01:19.280> 12th,<00:01:19.880> you<00:01:20.000> can 00:01:20.150 --> 00:01:20.160 align:start position:0% new part. As of August 12th, you can 00:01:20.160 --> 00:01:22.510 align:start position:0% new part. As of August 12th, you can copy<00:01:20.520> someone<00:01:20.840> else's<00:01:21.160> entire<00:01:21.520> notebook,<00:01:22.240> not 00:01:22.510 --> 00:01:22.520 align:start position:0% copy someone else's entire notebook, not 00:01:22.520 --> 00:01:24.630 align:start position:0% copy someone else's entire notebook, not just<00:01:22.720> their<00:01:22.840> notes,<00:01:23.560> their<00:01:23.720> sources,<00:01:24.160> too. 00:01:24.630 --> 00:01:24.640 align:start position:0% just their notes, their sources, too. 00:01:24.640 --> 00:01:26.990 align:start position:0% just their notes, their sources, too. And<00:01:24.880> any<00:01:25.080> documents,<00:01:25.680> guides,<00:01:26.160> or<00:01:26.280> summaries 00:01:26.990 --> 00:01:27.000 align:start position:0% And any documents, guides, or summaries 00:01:27.000 --> 00:01:29.070 align:start position:0% And any documents, guides, or summaries the<00:01:27.160> AI<00:01:27.480> already<00:01:27.840> built<00:01:28.080> for<00:01:28.160> them.<00:01:28.880> Think 00:01:29.070 --> 00:01:29.080 align:start position:0% the AI already built for them. Think 00:01:29.080 --> 00:01:31.150 align:start position:0% the AI already built for them. Think about<00:01:29.400> what<00:01:29.560> that<00:01:29.760> actually<00:01:30.160> means.<00:01:30.760> Before 00:01:31.150 --> 00:01:31.160 align:start position:0% about what that actually means. Before 00:01:31.160 --> 00:01:32.590 align:start position:0% about what that actually means. Before this,<00:01:31.400> if<00:01:31.560> a<00:01:31.600> colleague<00:01:32.040> built<00:01:32.280> a<00:01:32.320> great 00:01:32.590 --> 00:01:32.600 align:start position:0% this, if a colleague built a great 00:01:32.600 --> 00:01:34.350 align:start position:0% this, if a colleague built a great research<00:01:33.000> notebook,<00:01:33.680> you<00:01:33.800> could<00:01:33.960> look<00:01:34.120> at<00:01:34.240> it, 00:01:34.350 --> 00:01:34.360 align:start position:0% research notebook, you could look at it, 00:01:34.360 --> 00:01:36.270 align:start position:0% research notebook, you could look at it, but<00:01:34.520> you<00:01:34.640> couldn't<00:01:35.000> easily<00:01:35.320> make<00:01:35.600> it<00:01:35.680> your<00:01:35.880> own 00:01:36.270 --> 00:01:36.280 align:start position:0% but you couldn't easily make it your own 00:01:36.280 --> 00:01:37.950 align:start position:0% but you couldn't easily make it your own and<00:01:36.400> build<00:01:36.640> on<00:01:36.760> top<00:01:36.960> of<00:01:37.080> it.<00:01:37.520> Now,<00:01:37.640> you<00:01:37.760> click 00:01:37.950 --> 00:01:37.960 align:start position:0% and build on top of it. Now, you click 00:01:37.960 --> 00:01:39.830 align:start position:0% and build on top of it. Now, you click one<00:01:38.120> button,<00:01:38.680> and<00:01:38.800> the<00:01:38.920> whole<00:01:39.120> notebook, 00:01:39.830 --> 00:01:39.840 align:start position:0% one button, and the whole notebook, 00:01:39.840 --> 00:01:42.190 align:start position:0% one button, and the whole notebook, sources,<00:01:40.480> documents,<00:01:41.120> everything<00:01:41.840> becomes 00:01:42.190 --> 00:01:42.200 align:start position:0% sources, documents, everything becomes 00:01:42.200 --> 00:01:43.990 align:start position:0% sources, documents, everything becomes yours<00:01:42.440> to<00:01:42.560> edit.<00:01:43.080> Here's<00:01:43.280> a<00:01:43.360> one-sentence 00:01:43.990 --> 00:01:44.000 align:start position:0% yours to edit. Here's a one-sentence 00:01:44.000 --> 00:01:46.790 align:start position:0% yours to edit. Here's a one-sentence example.<00:01:44.840> Inside<00:01:45.320> the<00:01:45.480> AI<00:01:45.760> Profit<00:01:46.120> Boardroom, 00:01:46.790 --> 00:01:46.800 align:start position:0% example. Inside the AI Profit Boardroom, 00:01:46.800 --> 00:01:48.910 align:start position:0% example. Inside the AI Profit Boardroom, if<00:01:47.000> one<00:01:47.160> of<00:01:47.280> our<00:01:47.400> coaches<00:01:47.840> builds<00:01:48.120> a<00:01:48.160> notebook 00:01:48.910 --> 00:01:48.920 align:start position:0% if one of our coaches builds a notebook 00:01:48.920 --> 00:01:50.870 align:start position:0% if one of our coaches builds a notebook packed<00:01:49.280> with<00:01:49.440> proven<00:01:49.800> prompts<00:01:50.480> and<00:01:50.600> case 00:01:50.870 --> 00:01:50.880 align:start position:0% packed with proven prompts and case 00:01:50.880 --> 00:01:52.950 align:start position:0% packed with proven prompts and case studies<00:01:51.240> for<00:01:51.400> automating<00:01:51.920> client<00:01:52.240> outreach, 00:01:52.950 --> 00:01:52.960 align:start position:0% studies for automating client outreach, 00:01:52.960 --> 00:01:54.630 align:start position:0% studies for automating client outreach, any<00:01:53.200> member<00:01:53.480> can<00:01:53.640> now<00:01:53.840> copy<00:01:54.120> that<00:01:54.280> entire 00:01:54.630 --> 00:01:54.640 align:start position:0% any member can now copy that entire 00:01:54.640 --> 00:01:56.670 align:start position:0% any member can now copy that entire notebook<00:01:55.320> in<00:01:55.480> one<00:01:55.680> click<00:01:56.280> and<00:01:56.400> start 00:01:56.670 --> 00:01:56.680 align:start position:0% notebook in one click and start 00:01:56.680 --> 00:01:58.590 align:start position:0% notebook in one click and start customizing<00:01:57.400> it<00:01:57.760> for<00:01:57.880> their<00:01:58.080> own<00:01:58.240> business 00:01:58.590 --> 00:01:58.600 align:start position:0% customizing it for their own business 00:01:58.600 --> 00:02:00.510 align:start position:0% customizing it for their own business the<00:01:58.720> same<00:01:58.960> day.<00:01:59.440> That's<00:01:59.720> the<00:01:59.840> shift.<00:02:00.440> A 00:02:00.510 --> 00:02:00.520 align:start position:0% the same day. That's the shift. A 00:02:00.520 --> 00:02:02.150 align:start position:0% the same day. That's the shift. A notebook<00:02:01.080> isn't<00:02:01.320> just<00:02:01.520> something<00:02:01.840> you<00:02:01.960> read 00:02:02.150 --> 00:02:02.160 align:start position:0% notebook isn't just something you read 00:02:02.160 --> 00:02:03.350 align:start position:0% notebook isn't just something you read anymore.<00:02:02.640> It's<00:02:02.760> something<00:02:03.080> you<00:02:03.200> can 00:02:03.350 --> 00:02:03.360 align:start position:0% anymore. It's something you can 00:02:03.360 --> 00:02:05.190 align:start position:0% anymore. It's something you can duplicate<00:02:03.960> like<00:02:04.120> a<00:02:04.160> template<00:02:04.720> and<00:02:04.800> make<00:02:05.040> your 00:02:05.190 --> 00:02:05.200 align:start position:0% duplicate like a template and make your 00:02:05.200 --> 00:02:06.830 align:start position:0% duplicate like a template and make your own.<00:02:05.680> Now,<00:02:05.920> if<00:02:06.080> you're<00:02:06.200> watching<00:02:06.520> this<00:02:06.720> and 00:02:06.830 --> 00:02:06.840 align:start position:0% own. Now, if you're watching this and 00:02:06.840 --> 00:02:08.190 align:start position:0% own. Now, if you're watching this and thinking,<00:02:07.360> "I<00:02:07.400> don't<00:02:07.600> even<00:02:07.760> know<00:02:07.920> where<00:02:08.080> to 00:02:08.190 --> 00:02:08.200 align:start position:0% thinking, "I don't even know where to 00:02:08.200 --> 00:02:10.070 align:start position:0% thinking, "I don't even know where to start<00:02:08.520> with<00:02:08.679> tools<00:02:08.920> like<00:02:09.080> Gemini<00:02:09.440> notebook." 00:02:10.070 --> 00:02:10.080 align:start position:0% start with tools like Gemini notebook." 00:02:10.080 --> 00:02:11.990 align:start position:0% start with tools like Gemini notebook." That's<00:02:10.360> exactly<00:02:10.920> why<00:02:11.120> we<00:02:11.280> built<00:02:11.560> the<00:02:11.760> AI 00:02:11.990 --> 00:02:12.000 align:start position:0% That's exactly why we built the AI 00:02:12.000 --> 00:02:14.430 align:start position:0% That's exactly why we built the AI Profit<00:02:12.320> Boardroom.<00:02:13.000> It's<00:02:13.200> a<00:02:13.280> community<00:02:14.160> built 00:02:14.430 --> 00:02:14.440 align:start position:0% Profit Boardroom. It's a community built 00:02:14.440 --> 00:02:16.390 align:start position:0% Profit Boardroom. It's a community built around<00:02:14.920> learning<00:02:15.240> to<00:02:15.400> use<00:02:15.680> tools<00:02:15.959> like<00:02:16.160> this 00:02:16.390 --> 00:02:16.400 align:start position:0% around learning to use tools like this 00:02:16.400 --> 00:02:18.070 align:start position:0% around learning to use tools like this the<00:02:16.480> right<00:02:16.680> way,<00:02:16.920> so<00:02:17.080> you<00:02:17.240> save<00:02:17.480> real<00:02:17.680> time<00:02:18.000> in 00:02:18.070 --> 00:02:18.080 align:start position:0% the right way, so you save real time in 00:02:18.080 --> 00:02:19.870 align:start position:0% the right way, so you save real time in your<00:02:18.200> business<00:02:18.840> instead<00:02:19.120> of<00:02:19.240> wasting<00:02:19.600> hours 00:02:19.870 --> 00:02:19.880 align:start position:0% your business instead of wasting hours 00:02:19.880 --> 00:02:21.550 align:start position:0% your business instead of wasting hours figuring<00:02:20.200> it<00:02:20.320> out<00:02:20.440> alone.<00:02:21.080> If<00:02:21.240> you<00:02:21.320> want<00:02:21.480> a 00:02:21.550 --> 00:02:21.560 align:start position:0% figuring it out alone. If you want a 00:02:21.560 --> 00:02:23.390 align:start position:0% figuring it out alone. If you want a walk-through<00:02:22.040> on<00:02:22.200> copying<00:02:22.640> and<00:02:22.760> customizing 00:02:23.390 --> 00:02:23.400 align:start position:0% walk-through on copying and customizing 00:02:23.400 --> 00:02:25.310 align:start position:0% walk-through on copying and customizing an<00:02:23.560> AI<00:02:23.760> notebook<00:02:24.200> for<00:02:24.320> your<00:02:24.440> own<00:02:24.560> business, 00:02:25.310 --> 00:02:25.320 align:start position:0% an AI notebook for your own business, 00:02:25.320 --> 00:02:26.830 align:start position:0% an AI notebook for your own business, specifically<00:02:25.920> how<00:02:26.080> to<00:02:26.200> set<00:02:26.400> it<00:02:26.520> up<00:02:26.640> so<00:02:26.760> it 00:02:26.830 --> 00:02:26.840 align:start position:0% specifically how to set it up so it 00:02:26.840 --> 00:02:28.670 align:start position:0% specifically how to set it up so it saves<00:02:27.160> you<00:02:27.360> hours<00:02:27.640> on<00:02:27.760> research<00:02:28.200> and<00:02:28.320> content 00:02:28.670 --> 00:02:28.680 align:start position:0% saves you hours on research and content 00:02:28.680 --> 00:02:30.870 align:start position:0% saves you hours on research and content planning,<00:02:29.280> that's<00:02:29.600> inside<00:02:30.080> the<00:02:30.280> AI<00:02:30.520> Profit 00:02:30.870 --> 00:02:30.880 align:start position:0% planning, that's inside the AI Profit 00:02:30.880 --> 00:02:32.150 align:start position:0% planning, that's inside the AI Profit Boardroom<00:02:31.280> right<00:02:31.480> now.<00:02:31.720> Link's<00:02:32.000> in<00:02:32.080> the 00:02:32.150 --> 00:02:32.160 align:start position:0% Boardroom right now. Link's in the 00:02:32.160 --> 00:02:33.949 align:start position:0% Boardroom right now. Link's in the comments<00:02:32.480> and<00:02:32.560> description.<00:02:33.280> Okay,<00:02:33.600> back<00:02:33.880> to 00:02:33.949 --> 00:02:33.959 align:start position:0% comments and description. Okay, back to 00:02:33.959 --> 00:02:35.430 align:start position:0% comments and description. Okay, back to the<00:02:34.080> second<00:02:34.400> big<00:02:34.600> change.<00:02:34.920> This<00:02:35.160> one<00:02:35.320> is 00:02:35.430 --> 00:02:35.440 align:start position:0% the second big change. This one is 00:02:35.440 --> 00:02:37.670 align:start position:0% the second big change. This one is bigger.<00:02:36.080> Google<00:02:36.520> is<00:02:36.680> connecting<00:02:37.120> Gemini<00:02:37.520> to 00:02:37.670 --> 00:02:37.680 align:start position:0% bigger. Google is connecting Gemini to 00:02:37.680 --> 00:02:40.550 align:start position:0% bigger. Google is connecting Gemini to 13<00:02:38.240> outside<00:02:38.720> apps,<00:02:39.080> not<00:02:39.360> next<00:02:39.680> year,<00:02:40.200> over<00:02:40.480> the 00:02:40.550 --> 00:02:40.560 align:start position:0% 13 outside apps, not next year, over the 00:02:40.560 --> 00:02:42.350 align:start position:0% 13 outside apps, not next year, over the next<00:02:40.800> few<00:02:41.000> weeks.<00:02:41.360> Google<00:02:41.680> announced<00:02:42.040> this<00:02:42.200> on 00:02:42.350 --> 00:02:42.360 align:start position:0% next few weeks. Google announced this on 00:02:42.360 --> 00:02:44.270 align:start position:0% next few weeks. Google announced this on August<00:02:42.640> 12th<00:02:43.240> at<00:02:43.400> their<00:02:43.560> Made<00:02:43.800> by<00:02:43.959> Google 00:02:44.270 --> 00:02:44.280 align:start position:0% August 12th at their Made by Google 00:02:44.280 --> 00:02:46.949 align:start position:0% August 12th at their Made by Google event.<00:02:45.160> Here's<00:02:45.440> the<00:02:45.520> full<00:02:45.760> list<00:02:46.360> broken<00:02:46.720> into 00:02:46.949 --> 00:02:46.959 align:start position:0% event. Here's the full list broken into 00:02:46.959 --> 00:02:49.150 align:start position:0% event. Here's the full list broken into four<00:02:47.160> groups.<00:02:47.840> For<00:02:48.000> work,<00:02:48.400> Gemini<00:02:48.800> connects 00:02:49.150 --> 00:02:49.160 align:start position:0% four groups. For work, Gemini connects 00:02:49.160 --> 00:02:52.550 align:start position:0% four groups. For work, Gemini connects to<00:02:49.240> Granola,<00:02:50.080> Otter.ai,<00:02:51.520> and<00:02:51.720> Wix.<00:02:52.400> For 00:02:52.550 --> 00:02:52.560 align:start position:0% to Granola, Otter.ai, and Wix. For 00:02:52.560 --> 00:02:54.310 align:start position:0% to Granola, Otter.ai, and Wix. For booking<00:02:52.920> things,<00:02:53.320> it<00:02:53.440> connects<00:02:53.760> to<00:02:53.880> Fever, 00:02:54.310 --> 00:02:54.320 align:start position:0% booking things, it connects to Fever, 00:02:54.320 --> 00:02:56.830 align:start position:0% booking things, it connects to Fever, GetYourGuide,<00:02:55.040> Localizer,<00:02:55.880> OpenTable,<00:02:56.680> and 00:02:56.830 --> 00:02:56.840 align:start position:0% GetYourGuide, Localizer, OpenTable, and 00:02:56.840 --> 00:02:58.870 align:start position:0% GetYourGuide, Localizer, OpenTable, and Ticketmaster.<00:02:57.640> For<00:02:57.760> music,<00:02:58.240> it<00:02:58.360> connects<00:02:58.640> to 00:02:58.870 --> 00:02:58.880 align:start position:0% Ticketmaster. For music, it connects to 00:02:58.880 --> 00:03:00.710 align:start position:0% Ticketmaster. For music, it connects to iHeartRadio<00:02:59.480> and<00:02:59.600> Pandora.<00:03:00.480> And<00:03:00.600> for 00:03:00.710 --> 00:03:00.720 align:start position:0% iHeartRadio and Pandora. And for 00:03:00.720 --> 00:03:02.550 align:start position:0% iHeartRadio and Pandora. And for everyday<00:03:01.040> life,<00:03:01.360> it<00:03:01.480> connects<00:03:01.760> to<00:03:01.920> Angie, 00:03:02.550 --> 00:03:02.560 align:start position:0% everyday life, it connects to Angie, 00:03:02.560 --> 00:03:04.790 align:start position:0% everyday life, it connects to Angie, Thumbtack,<00:03:03.400> and<00:03:03.560> Zocdoc.<00:03:04.239> Let<00:03:04.360> me<00:03:04.440> explain 00:03:04.790 --> 00:03:04.800 align:start position:0% Thumbtack, and Zocdoc. Let me explain 00:03:04.800 --> 00:03:06.550 align:start position:0% Thumbtack, and Zocdoc. Let me explain why<00:03:04.959> this<00:03:05.120> matters<00:03:05.480> because<00:03:06.000> on<00:03:06.160> its<00:03:06.320> own, 00:03:06.550 --> 00:03:06.560 align:start position:0% why this matters because on its own, 00:03:06.560 --> 00:03:08.310 align:start position:0% why this matters because on its own, that<00:03:06.760> list<00:03:07.000> just<00:03:07.160> sounds<00:03:07.400> like<00:03:07.600> logos.<00:03:08.120> Right 00:03:08.310 --> 00:03:08.320 align:start position:0% that list just sounds like logos. Right 00:03:08.320 --> 00:03:09.910 align:start position:0% that list just sounds like logos. Right now,<00:03:08.440> if<00:03:08.560> you<00:03:08.680> want<00:03:08.840> concert<00:03:09.200> tickets,<00:03:09.840> you 00:03:09.910 --> 00:03:09.920 align:start position:0% now, if you want concert tickets, you 00:03:09.920 --> 00:03:12.229 align:start position:0% now, if you want concert tickets, you open<00:03:10.160> Gemini,<00:03:10.880> ask<00:03:11.120> a<00:03:11.160> question,<00:03:11.880> then<00:03:12.040> leave 00:03:12.229 --> 00:03:12.239 align:start position:0% open Gemini, ask a question, then leave 00:03:12.239 --> 00:03:14.110 align:start position:0% open Gemini, ask a question, then leave Gemini,<00:03:12.920> open<00:03:13.200> a<00:03:13.239> browser,<00:03:13.760> search 00:03:14.110 --> 00:03:14.120 align:start position:0% Gemini, open a browser, search 00:03:14.120 --> 00:03:16.310 align:start position:0% Gemini, open a browser, search Ticketmaster,<00:03:14.959> find<00:03:15.320> the<00:03:15.400> show,<00:03:15.920> and<00:03:16.040> buy<00:03:16.200> the 00:03:16.310 --> 00:03:16.320 align:start position:0% Ticketmaster, find the show, and buy the 00:03:16.320 --> 00:03:18.190 align:start position:0% Ticketmaster, find the show, and buy the ticket.<00:03:16.880> That's<00:03:17.160> five<00:03:17.400> steps<00:03:17.720> across<00:03:18.000> two 00:03:18.190 --> 00:03:18.200 align:start position:0% ticket. That's five steps across two 00:03:18.200 --> 00:03:20.150 align:start position:0% ticket. That's five steps across two apps.<00:03:18.760> Once<00:03:19.000> this<00:03:19.200> rolls<00:03:19.480> out,<00:03:19.880> you'll<00:03:20.040> be 00:03:20.150 --> 00:03:20.160 align:start position:0% apps. Once this rolls out, you'll be 00:03:20.160 --> 00:03:22.270 align:start position:0% apps. Once this rolls out, you'll be able<00:03:20.320> to<00:03:20.440> just<00:03:20.680> ask<00:03:20.920> Gemini<00:03:21.280> directly,<00:03:22.000> "Find 00:03:22.270 --> 00:03:22.280 align:start position:0% able to just ask Gemini directly, "Find 00:03:22.280 --> 00:03:23.630 align:start position:0% able to just ask Gemini directly, "Find me<00:03:22.360> a<00:03:22.440> concert<00:03:22.840> this<00:03:23.000> weekend<00:03:23.360> under<00:03:23.560> a 00:03:23.630 --> 00:03:23.640 align:start position:0% me a concert this weekend under a 00:03:23.640 --> 00:03:25.710 align:start position:0% me a concert this weekend under a certain<00:03:23.920> price."<00:03:24.519> And<00:03:24.640> Gemini<00:03:25.040> can<00:03:25.200> pull<00:03:25.480> real 00:03:25.710 --> 00:03:25.720 align:start position:0% certain price." And Gemini can pull real 00:03:25.720 --> 00:03:27.270 align:start position:0% certain price." And Gemini can pull real Ticketmaster<00:03:26.320> listings<00:03:26.880> without<00:03:27.200> you 00:03:27.270 --> 00:03:27.280 align:start position:0% Ticketmaster listings without you 00:03:27.280 --> 00:03:29.470 align:start position:0% Ticketmaster listings without you leaving<00:03:27.560> the<00:03:27.640> conversation.<00:03:28.600> Same<00:03:28.959> idea<00:03:29.239> with 00:03:29.470 --> 00:03:29.480 align:start position:0% leaving the conversation. Same idea with 00:03:29.480 --> 00:03:31.830 align:start position:0% leaving the conversation. Same idea with OpenTable<00:03:30.160> for<00:03:30.280> booking<00:03:30.600> a<00:03:30.640> table,<00:03:31.280> Zocdoc 00:03:31.830 --> 00:03:31.840 align:start position:0% OpenTable for booking a table, Zocdoc 00:03:31.840 --> 00:03:33.790 align:start position:0% OpenTable for booking a table, Zocdoc for<00:03:31.959> booking<00:03:32.239> a<00:03:32.280> doctor,<00:03:32.920> and<00:03:33.120> Wix<00:03:33.640> for 00:03:33.790 --> 00:03:33.800 align:start position:0% for booking a doctor, and Wix for 00:03:33.800 --> 00:03:36.310 align:start position:0% for booking a doctor, and Wix for editing<00:03:34.160> a<00:03:34.200> website.<00:03:35.040> Here's<00:03:35.440> a<00:03:35.519> one-sentence 00:03:36.310 --> 00:03:36.320 align:start position:0% editing a website. Here's a one-sentence 00:03:36.320 --> 00:03:38.630 align:start position:0% editing a website. Here's a one-sentence example.<00:03:37.120> Say<00:03:37.360> the<00:03:37.680> AI<00:03:37.920> Profit<00:03:38.239> Boardroom 00:03:38.630 --> 00:03:38.640 align:start position:0% example. Say the AI Profit Boardroom 00:03:38.640 --> 00:03:40.870 align:start position:0% example. Say the AI Profit Boardroom wanted<00:03:39.000> a<00:03:39.040> new<00:03:39.239> landing<00:03:39.560> page.<00:03:40.239> With<00:03:40.480> Wix 00:03:40.870 --> 00:03:40.880 align:start position:0% wanted a new landing page. With Wix 00:03:40.880 --> 00:03:42.949 align:start position:0% wanted a new landing page. With Wix connected<00:03:41.360> to<00:03:41.440> Gemini,<00:03:42.200> our<00:03:42.400> team<00:03:42.800> could 00:03:42.949 --> 00:03:42.959 align:start position:0% connected to Gemini, our team could 00:03:42.959 --> 00:03:44.430 align:start position:0% connected to Gemini, our team could simply<00:03:43.239> tell<00:03:43.440> Gemini<00:03:43.840> to<00:03:44.000> update<00:03:44.360> the 00:03:44.430 --> 00:03:44.440 align:start position:0% simply tell Gemini to update the 00:03:44.440 --> 00:03:46.229 align:start position:0% simply tell Gemini to update the homepage<00:03:44.920> headline<00:03:45.560> to<00:03:45.680> highlight<00:03:46.120> our 00:03:46.229 --> 00:03:46.239 align:start position:0% homepage headline to highlight our 00:03:46.239 --> 00:03:48.470 align:start position:0% homepage headline to highlight our weekly<00:03:46.680> automation<00:03:47.200> coaching<00:03:47.560> calls,<00:03:48.160> and<00:03:48.320> it 00:03:48.470 --> 00:03:48.480 align:start position:0% weekly automation coaching calls, and it 00:03:48.480 --> 00:03:50.390 align:start position:0% weekly automation coaching calls, and it edits<00:03:48.840> the<00:03:48.959> actual<00:03:49.239> site.<00:03:49.840> That's<00:03:50.160> a<00:03:50.200> real 00:03:50.390 --> 00:03:50.400 align:start position:0% edits the actual site. That's a real 00:03:50.400 --> 00:03:53.630 align:start position:0% edits the actual site. That's a real shift<00:03:51.000> from<00:03:51.200> an<00:03:51.320> AI<00:03:51.920> you<00:03:52.040> talk<00:03:52.360> to<00:03:52.600> into<00:03:52.880> an<00:03:53.040> AI 00:03:53.630 --> 00:03:53.640 align:start position:0% shift from an AI you talk to into an AI 00:03:53.640 --> 00:03:55.710 align:start position:0% shift from an AI you talk to into an AI that<00:03:53.800> can<00:03:54.040> act<00:03:54.320> on<00:03:54.440> your<00:03:54.560> behalf<00:03:55.000> inside<00:03:55.440> tools 00:03:55.710 --> 00:03:55.720 align:start position:0% that can act on your behalf inside tools 00:03:55.720 --> 00:03:57.790 align:start position:0% that can act on your behalf inside tools you<00:03:55.840> already<00:03:56.080> use.<00:03:56.720> Now,<00:03:56.880> one<00:03:57.080> honest<00:03:57.320> caveat 00:03:57.790 --> 00:03:57.800 align:start position:0% you already use. Now, one honest caveat 00:03:57.800 --> 00:03:59.670 align:start position:0% you already use. Now, one honest caveat because<00:03:58.160> I<00:03:58.200> don't<00:03:58.440> want<00:03:58.600> to<00:03:58.720> overhype<00:03:59.120> this, 00:03:59.670 --> 00:03:59.680 align:start position:0% because I don't want to overhype this, 00:03:59.680 --> 00:04:02.070 align:start position:0% because I don't want to overhype this, Ticketmaster's<00:04:00.520> OpenTable<00:04:01.160> connection<00:04:01.880> is 00:04:02.070 --> 00:04:02.080 align:start position:0% Ticketmaster's OpenTable connection is 00:04:02.080 --> 00:04:04.070 align:start position:0% Ticketmaster's OpenTable connection is UK<00:04:02.560> only<00:04:02.880> for<00:04:03.000> now,<00:04:03.280> and<00:04:03.440> Google's<00:04:03.920> own 00:04:04.070 --> 00:04:04.080 align:start position:0% UK only for now, and Google's own 00:04:04.080 --> 00:04:06.870 align:start position:0% UK only for now, and Google's own documentation<00:04:05.080> says<00:04:05.360> availability<00:04:06.120> changes 00:04:06.870 --> 00:04:06.880 align:start position:0% documentation says availability changes 00:04:06.880 --> 00:04:08.870 align:start position:0% documentation says availability changes depending<00:04:07.320> on<00:04:07.440> your<00:04:07.560> country,<00:04:08.240> your<00:04:08.400> device, 00:04:08.870 --> 00:04:08.880 align:start position:0% depending on your country, your device, 00:04:08.880 --> 00:04:10.430 align:start position:0% depending on your country, your device, and<00:04:09.040> your<00:04:09.160> account.<00:04:09.560> So,<00:04:09.680> don't<00:04:09.920> expect<00:04:10.280> every 00:04:10.430 --> 00:04:10.440 align:start position:0% and your account. So, don't expect every 00:04:10.440 --> 00:04:12.310 align:start position:0% and your account. So, don't expect every one<00:04:10.600> of<00:04:10.680> these<00:04:10.880> 13<00:04:11.360> apps<00:04:11.640> to<00:04:11.760> work<00:04:12.000> for<00:04:12.120> you<00:04:12.200> on 00:04:12.310 --> 00:04:12.320 align:start position:0% one of these 13 apps to work for you on 00:04:12.320 --> 00:04:14.230 align:start position:0% one of these 13 apps to work for you on day<00:04:12.520> one.<00:04:13.040> Some<00:04:13.360> will<00:04:13.520> roll<00:04:13.760> out<00:04:13.920> slower 00:04:14.230 --> 00:04:14.240 align:start position:0% day one. Some will roll out slower 00:04:14.240 --> 00:04:16.110 align:start position:0% day one. Some will roll out slower depending<00:04:14.680> on<00:04:14.760> where<00:04:14.920> you<00:04:15.040> live. 00:04:16.110 --> 00:04:16.120 align:start position:0% depending on where you live. 00:04:16.120 --> 00:04:17.830 align:start position:0% depending on where you live. There's<00:04:16.239> also<00:04:16.519> a<00:04:16.560> bigger<00:04:16.840> reason<00:04:17.320> Google<00:04:17.720> is 00:04:17.830 --> 00:04:17.840 align:start position:0% There's also a bigger reason Google is 00:04:17.840 --> 00:04:19.990 align:start position:0% There's also a bigger reason Google is doing<00:04:18.120> this.<00:04:18.359> It's<00:04:18.519> not<00:04:18.720> random.<00:04:19.400> Google<00:04:19.760> has 00:04:19.990 --> 00:04:20.000 align:start position:0% doing this. It's not random. Google has 00:04:20.000 --> 00:04:22.190 align:start position:0% doing this. It's not random. Google has a<00:04:20.040> separate<00:04:20.519> project<00:04:20.880> called<00:04:21.040> Gemini<00:04:21.480> Spark. 00:04:22.190 --> 00:04:22.200 align:start position:0% a separate project called Gemini Spark. 00:04:22.200 --> 00:04:24.230 align:start position:0% a separate project called Gemini Spark. Spark<00:04:22.640> is<00:04:22.800> built<00:04:23.120> to<00:04:23.240> work<00:04:23.560> in<00:04:23.680> the<00:04:23.760> background 00:04:24.230 --> 00:04:24.240 align:start position:0% Spark is built to work in the background 00:04:24.240 --> 00:04:27.030 align:start position:0% Spark is built to work in the background for<00:04:24.400> you<00:04:24.800> using<00:04:25.200> tools<00:04:25.480> like<00:04:25.720> Gmail,<00:04:26.280> Docs, 00:04:27.030 --> 00:04:27.040 align:start position:0% for you using tools like Gmail, Docs, 00:04:27.040 --> 00:04:29.030 align:start position:0% for you using tools like Gmail, Docs, and<00:04:27.200> now<00:04:27.400> these<00:04:27.640> connected<00:04:28.120> apps<00:04:28.680> without<00:04:28.960> you 00:04:29.030 --> 00:04:29.040 align:start position:0% and now these connected apps without you 00:04:29.040 --> 00:04:30.870 align:start position:0% and now these connected apps without you having<00:04:29.280> to<00:04:29.400> ask<00:04:29.680> for<00:04:29.800> every<00:04:30.040> single<00:04:30.320> step. 00:04:30.870 --> 00:04:30.880 align:start position:0% having to ask for every single step. 00:04:30.880 --> 00:04:33.310 align:start position:0% having to ask for every single step. Spark<00:04:31.280> can<00:04:31.400> even<00:04:31.600> use<00:04:31.760> something<00:04:32.040> called<00:04:32.320> MCP, 00:04:33.310 --> 00:04:33.320 align:start position:0% Spark can even use something called MCP, 00:04:33.320 --> 00:04:34.790 align:start position:0% Spark can even use something called MCP, which<00:04:33.480> just<00:04:33.680> means<00:04:33.919> it<00:04:34.000> can<00:04:34.120> plug<00:04:34.360> into<00:04:34.600> other 00:04:34.790 --> 00:04:34.800 align:start position:0% which just means it can plug into other 00:04:34.800 --> 00:04:36.270 align:start position:0% which just means it can plug into other tools<00:04:35.080> that<00:04:35.200> weren't<00:04:35.440> built<00:04:35.640> by<00:04:35.800> Google<00:04:36.120> at 00:04:36.270 --> 00:04:36.280 align:start position:0% tools that weren't built by Google at 00:04:36.280 --> 00:04:38.390 align:start position:0% tools that weren't built by Google at all.<00:04:36.720> Put<00:04:36.880> those<00:04:37.080> two<00:04:37.240> things<00:04:37.480> together,<00:04:38.160> 1 00:04:38.390 --> 00:04:38.400 align:start position:0% all. Put those two things together, 1 00:04:38.400 --> 00:04:40.830 align:start position:0% all. Put those two things together, 1 billion<00:04:38.760> users,<00:04:39.440> and<00:04:39.560> an<00:04:39.760> AI<00:04:40.360> that<00:04:40.480> can<00:04:40.600> now 00:04:40.830 --> 00:04:40.840 align:start position:0% billion users, and an AI that can now 00:04:40.840 --> 00:04:43.310 align:start position:0% billion users, and an AI that can now act<00:04:41.160> inside<00:04:41.640> real<00:04:41.880> apps,<00:04:42.560> and<00:04:42.720> you<00:04:42.800> can<00:04:42.960> see 00:04:43.310 --> 00:04:43.320 align:start position:0% act inside real apps, and you can see 00:04:43.320 --> 00:04:45.190 align:start position:0% act inside real apps, and you can see where<00:04:43.560> this<00:04:43.720> is<00:04:43.840> heading.<00:04:44.520> Gemini<00:04:44.919> isn't 00:04:45.190 --> 00:04:45.200 align:start position:0% where this is heading. Gemini isn't 00:04:45.200 --> 00:04:46.630 align:start position:0% where this is heading. Gemini isn't trying<00:04:45.440> to<00:04:45.560> be<00:04:45.680> the<00:04:45.760> smartest<00:04:46.280> chatbot 00:04:46.630 --> 00:04:46.640 align:start position:0% trying to be the smartest chatbot 00:04:46.640 --> 00:04:48.390 align:start position:0% trying to be the smartest chatbot anymore.<00:04:47.200> It's<00:04:47.400> trying<00:04:47.640> to<00:04:47.760> become<00:04:48.040> the<00:04:48.160> one 00:04:48.390 --> 00:04:48.400 align:start position:0% anymore. It's trying to become the one 00:04:48.400 --> 00:04:50.390 align:start position:0% anymore. It's trying to become the one place<00:04:48.680> you<00:04:48.800> go<00:04:48.960> to<00:04:49.080> get<00:04:49.280> anything<00:04:49.600> done.<00:04:50.200> Let's 00:04:50.390 --> 00:04:50.400 align:start position:0% place you go to get anything done. Let's 00:04:50.400 --> 00:04:51.830 align:start position:0% place you go to get anything done. Let's talk<00:04:50.560> about<00:04:50.800> who<00:04:51.000> this<00:04:51.200> actually<00:04:51.520> helps 00:04:51.830 --> 00:04:51.840 align:start position:0% talk about who this actually helps 00:04:51.840 --> 00:04:53.270 align:start position:0% talk about who this actually helps because<00:04:52.120> that's<00:04:52.400> more<00:04:52.560> important<00:04:53.040> than<00:04:53.160> the 00:04:53.270 --> 00:04:53.280 align:start position:0% because that's more important than the 00:04:53.280 --> 00:04:55.230 align:start position:0% because that's more important than the tech<00:04:53.520> itself.<00:04:54.160> If<00:04:54.360> you're<00:04:54.480> a<00:04:54.520> student, 00:04:55.230 --> 00:04:55.240 align:start position:0% tech itself. If you're a student, 00:04:55.240 --> 00:04:57.470 align:start position:0% tech itself. If you're a student, imagine<00:04:55.680> your<00:04:55.800> professor<00:04:56.560> shares<00:04:56.919> one<00:04:57.160> master 00:04:57.470 --> 00:04:57.480 align:start position:0% imagine your professor shares one master 00:04:57.480 --> 00:04:59.310 align:start position:0% imagine your professor shares one master notebook<00:04:58.160> with<00:04:58.320> every<00:04:58.560> lecture,<00:04:59.040> every 00:04:59.310 --> 00:04:59.320 align:start position:0% notebook with every lecture, every 00:04:59.320 --> 00:05:01.150 align:start position:0% notebook with every lecture, every reading,<00:04:59.960> and<00:05:00.120> a<00:05:00.160> study<00:05:00.520> guide<00:05:00.840> already 00:05:01.150 --> 00:05:01.160 align:start position:0% reading, and a study guide already 00:05:01.160 --> 00:05:02.710 align:start position:0% reading, and a study guide already built.<00:05:01.520> You<00:05:01.600> copy<00:05:01.880> the<00:05:01.960> whole<00:05:02.160> thing<00:05:02.400> in<00:05:02.520> one 00:05:02.710 --> 00:05:02.720 align:start position:0% built. You copy the whole thing in one 00:05:02.720 --> 00:05:04.470 align:start position:0% built. You copy the whole thing in one click<00:05:03.280> and<00:05:03.400> build<00:05:03.640> your<00:05:03.800> own<00:05:03.919> study<00:05:04.240> plan 00:05:04.470 --> 00:05:04.480 align:start position:0% click and build your own study plan 00:05:04.480 --> 00:05:06.150 align:start position:0% click and build your own study plan around<00:05:04.800> it<00:05:04.880> that<00:05:05.040> night. 00:05:06.150 --> 00:05:06.160 align:start position:0% around it that night. 00:05:06.160 --> 00:05:07.870 align:start position:0% around it that night. If<00:05:06.240> you<00:05:06.360> run<00:05:06.480> a<00:05:06.520> small<00:05:06.800> business,<00:05:07.440> imagine 00:05:07.870 --> 00:05:07.880 align:start position:0% If you run a small business, imagine 00:05:07.880 --> 00:05:10.150 align:start position:0% If you run a small business, imagine connecting<00:05:08.360> Gemini<00:05:08.800> to<00:05:08.960> Granola<00:05:09.760> so<00:05:09.919> every 00:05:10.150 --> 00:05:10.160 align:start position:0% connecting Gemini to Granola so every 00:05:10.160 --> 00:05:11.350 align:start position:0% connecting Gemini to Granola so every client<00:05:10.480> call<00:05:10.680> gets<00:05:10.880> summarized 00:05:11.350 --> 00:05:11.360 align:start position:0% client call gets summarized 00:05:11.360 --> 00:05:13.150 align:start position:0% client call gets summarized automatically<00:05:12.280> with<00:05:12.400> the<00:05:12.520> action<00:05:12.840> items 00:05:13.150 --> 00:05:13.160 align:start position:0% automatically with the action items 00:05:13.160 --> 00:05:14.870 align:start position:0% automatically with the action items ready<00:05:13.440> before<00:05:13.720> your<00:05:13.840> next<00:05:14.080> meeting.<00:05:14.760> If 00:05:14.870 --> 00:05:14.880 align:start position:0% ready before your next meeting. If 00:05:14.880 --> 00:05:16.630 align:start position:0% ready before your next meeting. If you're<00:05:15.040> planning<00:05:15.440> your<00:05:15.560> weekend,<00:05:16.400> you<00:05:16.520> can 00:05:16.630 --> 00:05:16.640 align:start position:0% you're planning your weekend, you can 00:05:16.640 --> 00:05:18.150 align:start position:0% you're planning your weekend, you can just<00:05:16.840> tell<00:05:17.040> Gemini<00:05:17.440> what<00:05:17.600> kind<00:05:17.760> of<00:05:17.880> evening 00:05:18.150 --> 00:05:18.160 align:start position:0% just tell Gemini what kind of evening 00:05:18.160 --> 00:05:19.950 align:start position:0% just tell Gemini what kind of evening you<00:05:18.280> want,<00:05:18.760> and<00:05:18.840> it<00:05:18.960> can<00:05:19.080> check<00:05:19.400> real<00:05:19.640> event 00:05:19.950 --> 00:05:19.960 align:start position:0% you want, and it can check real event 00:05:19.960 --> 00:05:21.990 align:start position:0% you want, and it can check real event listings<00:05:20.640> and<00:05:20.800> real<00:05:21.000> restaurant<00:05:21.440> openings 00:05:21.990 --> 00:05:22.000 align:start position:0% listings and real restaurant openings 00:05:22.000 --> 00:05:23.390 align:start position:0% listings and real restaurant openings without<00:05:22.320> you<00:05:22.440> juggling<00:05:22.840> four<00:05:23.080> different 00:05:23.390 --> 00:05:23.400 align:start position:0% without you juggling four different 00:05:23.400 --> 00:05:25.390 align:start position:0% without you juggling four different apps.<00:05:24.000> None<00:05:24.280> of<00:05:24.360> this<00:05:24.560> needs<00:05:24.800> you<00:05:24.919> to<00:05:25.040> know<00:05:25.200> how 00:05:25.390 --> 00:05:25.400 align:start position:0% apps. None of this needs you to know how 00:05:25.400 --> 00:05:27.230 align:start position:0% apps. None of this needs you to know how to<00:05:25.520> code.<00:05:26.120> None<00:05:26.320> of<00:05:26.400> it<00:05:26.520> needs<00:05:26.720> a<00:05:26.760> technical 00:05:27.230 --> 00:05:27.240 align:start position:0% to code. None of it needs a technical 00:05:27.240 --> 00:05:29.070 align:start position:0% to code. None of it needs a technical background.<00:05:27.960> That's<00:05:28.240> actually<00:05:28.520> the<00:05:28.640> point<00:05:28.960> of 00:05:29.070 --> 00:05:29.080 align:start position:0% background. That's actually the point of 00:05:29.080 --> 00:05:31.430 align:start position:0% background. That's actually the point of connected<00:05:29.520> apps.<00:05:30.080> Google<00:05:30.800> built<00:05:31.080> this<00:05:31.320> for 00:05:31.430 --> 00:05:31.440 align:start position:0% connected apps. Google built this for 00:05:31.440 --> 00:05:33.030 align:start position:0% connected apps. Google built this for regular<00:05:31.800> people,<00:05:32.160> not<00:05:32.360> developers.<00:05:32.880> Now, 00:05:33.030 --> 00:05:33.040 align:start position:0% regular people, not developers. Now, 00:05:33.040 --> 00:05:34.670 align:start position:0% regular people, not developers. Now, here's<00:05:33.360> the<00:05:33.440> bigger<00:05:33.680> picture<00:05:34.320> because<00:05:34.600> I 00:05:34.670 --> 00:05:34.680 align:start position:0% here's the bigger picture because I 00:05:34.680 --> 00:05:36.550 align:start position:0% here's the bigger picture because I think<00:05:34.880> this<00:05:35.040> is<00:05:35.160> the<00:05:35.280> part<00:05:35.520> people<00:05:35.800> miss.<00:05:36.440> For 00:05:36.550 --> 00:05:36.560 align:start position:0% think this is the part people miss. For 00:05:36.560 --> 00:05:38.790 align:start position:0% think this is the part people miss. For years,<00:05:37.120> AI<00:05:37.400> meant<00:05:37.640> one<00:05:37.840> thing.<00:05:38.360> You<00:05:38.480> type<00:05:38.720> a 00:05:38.790 --> 00:05:38.800 align:start position:0% years, AI meant one thing. You type a 00:05:38.800 --> 00:05:40.630 align:start position:0% years, AI meant one thing. You type a question,<00:05:39.440> it<00:05:39.560> gives<00:05:39.800> you<00:05:39.880> an<00:05:40.000> answer.<00:05:40.480> That 00:05:40.630 --> 00:05:40.640 align:start position:0% question, it gives you an answer. That 00:05:40.640 --> 00:05:42.830 align:start position:0% question, it gives you an answer. That was<00:05:40.760> it.<00:05:41.000> Now,<00:05:41.200> we're<00:05:41.320> watching<00:05:41.760> AI<00:05:42.040> move<00:05:42.640> from 00:05:42.830 --> 00:05:42.840 align:start position:0% was it. Now, we're watching AI move from 00:05:42.840 --> 00:05:44.670 align:start position:0% was it. Now, we're watching AI move from just<00:05:43.200> answering<00:05:43.520> questions<00:05:44.280> to<00:05:44.400> actually 00:05:44.670 --> 00:05:44.680 align:start position:0% just answering questions to actually 00:05:44.680 --> 00:05:46.750 align:start position:0% just answering questions to actually doing<00:05:44.960> tasks<00:05:45.640> inside<00:05:46.080> the<00:05:46.200> apps<00:05:46.440> you<00:05:46.560> already 00:05:46.750 --> 00:05:46.760 align:start position:0% doing tasks inside the apps you already 00:05:46.760 --> 00:05:50.110 align:start position:0% doing tasks inside the apps you already use,<00:05:47.440> booking,<00:05:48.160> editing,<00:05:48.920> summarizing,<00:05:49.920> all 00:05:50.110 --> 00:05:50.120 align:start position:0% use, booking, editing, summarizing, all 00:05:50.120 --> 00:05:52.470 align:start position:0% use, booking, editing, summarizing, all from<00:05:50.320> one<00:05:50.480> conversation.<00:05:51.680> And<00:05:51.760> Google<00:05:52.160> didn't 00:05:52.470 --> 00:05:52.480 align:start position:0% from one conversation. And Google didn't 00:05:52.480 --> 00:05:54.270 align:start position:0% from one conversation. And Google didn't get<00:05:52.680> here<00:05:52.840> by<00:05:53.000> accident.<00:05:53.720> They<00:05:53.840> got<00:05:54.080> here 00:05:54.270 --> 00:05:54.280 align:start position:0% get here by accident. They got here 00:05:54.280 --> 00:05:55.990 align:start position:0% get here by accident. They got here because<00:05:54.560> Gemini<00:05:55.040> already<00:05:55.320> has<00:05:55.520> 1<00:05:55.720> billion 00:05:55.990 --> 00:05:56.000 align:start position:0% because Gemini already has 1 billion 00:05:56.000 --> 00:05:57.790 align:start position:0% because Gemini already has 1 billion people<00:05:56.320> using<00:05:56.600> it<00:05:56.680> every<00:05:56.840> month.<00:05:57.440> That's<00:05:57.720> the 00:05:57.790 --> 00:05:57.800 align:start position:0% people using it every month. That's the 00:05:57.800 --> 00:05:59.790 align:start position:0% people using it every month. That's the distribution<00:05:58.520> most<00:05:58.800> companies<00:05:59.200> would<00:05:59.320> need 00:05:59.790 --> 00:05:59.800 align:start position:0% distribution most companies would need 00:05:59.800 --> 00:06:01.710 align:start position:0% distribution most companies would need years<00:06:00.080> to<00:06:00.200> build.<00:06:00.520> Google<00:06:00.880> already<00:06:01.160> had<00:06:01.320> it. 00:06:01.710 --> 00:06:01.720 align:start position:0% years to build. Google already had it. 00:06:01.720 --> 00:06:03.870 align:start position:0% years to build. Google already had it. So,<00:06:01.840> when<00:06:01.960> they<00:06:02.160> add<00:06:02.600> a<00:06:02.640> new<00:06:02.920> connected<00:06:03.400> app, 00:06:03.870 --> 00:06:03.880 align:start position:0% So, when they add a new connected app, 00:06:03.880 --> 00:06:05.830 align:start position:0% So, when they add a new connected app, it<00:06:04.000> doesn't<00:06:04.360> launch<00:06:04.680> to<00:06:04.800> a<00:06:04.840> small<00:06:05.120> test<00:06:05.400> group. 00:06:05.830 --> 00:06:05.840 align:start position:0% it doesn't launch to a small test group. 00:06:05.840 --> 00:06:07.590 align:start position:0% it doesn't launch to a small test group. It<00:06:06.000> launches<00:06:06.400> to<00:06:06.520> a<00:06:06.600> huge<00:06:07.000> chunk<00:06:07.200> of<00:06:07.280> the<00:06:07.360> world 00:06:07.590 --> 00:06:07.600 align:start position:0% It launches to a huge chunk of the world 00:06:07.600 --> 00:06:09.150 align:start position:0% It launches to a huge chunk of the world at<00:06:07.720> once.<00:06:08.200> If<00:06:08.360> you're<00:06:08.480> a<00:06:08.560> business<00:06:08.920> owner 00:06:09.150 --> 00:06:09.160 align:start position:0% at once. If you're a business owner 00:06:09.160 --> 00:06:10.590 align:start position:0% at once. If you're a business owner watching<00:06:09.520> this,<00:06:09.960> here's<00:06:10.200> the<00:06:10.360> honest 00:06:10.590 --> 00:06:10.600 align:start position:0% watching this, here's the honest 00:06:10.600 --> 00:06:12.830 align:start position:0% watching this, here's the honest takeaway.<00:06:11.320> The<00:06:11.440> businesses<00:06:12.240> that<00:06:12.400> figure<00:06:12.720> out 00:06:12.830 --> 00:06:12.840 align:start position:0% takeaway. The businesses that figure out 00:06:12.840 --> 00:06:14.990 align:start position:0% takeaway. The businesses that figure out how<00:06:13.000> to<00:06:13.120> use<00:06:13.320> tools<00:06:13.640> like<00:06:13.800> Gemini<00:06:14.240> early<00:06:14.920> are 00:06:14.990 --> 00:06:15.000 align:start position:0% how to use tools like Gemini early are 00:06:15.000 --> 00:06:16.750 align:start position:0% how to use tools like Gemini early are going<00:06:15.200> to<00:06:15.280> move<00:06:15.480> faster<00:06:16.200> than<00:06:16.320> the<00:06:16.400> ones<00:06:16.640> who 00:06:16.750 --> 00:06:16.760 align:start position:0% going to move faster than the ones who 00:06:16.760 --> 00:06:18.590 align:start position:0% going to move faster than the ones who wait<00:06:16.960> and<00:06:17.080> see.<00:06:17.640> Not<00:06:17.840> because<00:06:18.080> the<00:06:18.200> tool<00:06:18.480> is 00:06:18.590 --> 00:06:18.600 align:start position:0% wait and see. Not because the tool is 00:06:18.600 --> 00:06:20.630 align:start position:0% wait and see. Not because the tool is magic,<00:06:19.360> but<00:06:19.520> because<00:06:19.880> every<00:06:20.120> week<00:06:20.360> you're<00:06:20.440> not 00:06:20.630 --> 00:06:20.640 align:start position:0% magic, but because every week you're not 00:06:20.640 --> 00:06:22.510 align:start position:0% magic, but because every week you're not using<00:06:20.960> it,<00:06:21.360> someone<00:06:21.760> else<00:06:21.960> in<00:06:22.040> your<00:06:22.160> space 00:06:22.510 --> 00:06:22.520 align:start position:0% using it, someone else in your space 00:06:22.520 --> 00:06:24.270 align:start position:0% using it, someone else in your space already<00:06:22.840> is.<00:06:23.280> So,<00:06:23.480> what<00:06:23.720> should<00:06:23.919> you<00:06:24.000> actually 00:06:24.270 --> 00:06:24.280 align:start position:0% already is. So, what should you actually 00:06:24.280 --> 00:06:25.950 align:start position:0% already is. So, what should you actually do<00:06:24.480> with<00:06:24.600> this?<00:06:25.120> If<00:06:25.280> you're<00:06:25.400> just<00:06:25.760> getting 00:06:25.950 --> 00:06:25.960 align:start position:0% do with this? If you're just getting 00:06:25.960 --> 00:06:28.390 align:start position:0% do with this? If you're just getting started<00:06:26.360> with<00:06:26.560> AI,<00:06:27.200> open<00:06:27.520> Gemini<00:06:27.919> notebook 00:06:28.390 --> 00:06:28.400 align:start position:0% started with AI, open Gemini notebook 00:06:28.400 --> 00:06:30.790 align:start position:0% started with AI, open Gemini notebook this<00:06:28.640> week<00:06:29.120> and<00:06:29.240> try<00:06:29.520> copying<00:06:30.200> a<00:06:30.320> public 00:06:30.790 --> 00:06:30.800 align:start position:0% this week and try copying a public 00:06:30.800 --> 00:06:32.830 align:start position:0% this week and try copying a public notebook<00:06:31.320> on<00:06:31.440> a<00:06:31.480> topic<00:06:31.840> you<00:06:31.919> care<00:06:32.120> about<00:06:32.640> just 00:06:32.830 --> 00:06:32.840 align:start position:0% notebook on a topic you care about just 00:06:32.840 --> 00:06:35.310 align:start position:0% notebook on a topic you care about just to<00:06:32.919> feel<00:06:33.200> how<00:06:33.360> the<00:06:33.440> copy<00:06:33.720> feature<00:06:34.080> works. 00:06:35.310 --> 00:06:35.320 align:start position:0% to feel how the copy feature works. 00:06:35.320 --> 00:06:37.270 align:start position:0% to feel how the copy feature works. If<00:06:35.440> you<00:06:35.560> already<00:06:35.880> use<00:06:36.080> Gemini<00:06:36.480> regularly, 00:06:37.270 --> 00:06:37.280 align:start position:0% If you already use Gemini regularly, 00:06:37.280 --> 00:06:39.070 align:start position:0% If you already use Gemini regularly, check<00:06:37.560> your<00:06:37.720> connected<00:06:38.200> app<00:06:38.400> settings<00:06:38.919> over 00:06:39.070 --> 00:06:39.080 align:start position:0% check your connected app settings over 00:06:39.080 --> 00:06:40.990 align:start position:0% check your connected app settings over the<00:06:39.160> next<00:06:39.400> few<00:06:39.560> weeks<00:06:40.080> as<00:06:40.240> these<00:06:40.480> 13 00:06:40.990 --> 00:06:41.000 align:start position:0% the next few weeks as these 13 00:06:41.000 --> 00:06:42.909 align:start position:0% the next few weeks as these 13 integrations<00:06:41.680> roll<00:06:41.919> out<00:06:42.360> and<00:06:42.480> turn<00:06:42.720> on<00:06:42.840> the 00:06:42.909 --> 00:06:42.919 align:start position:0% integrations roll out and turn on the 00:06:42.919 --> 00:06:44.630 align:start position:0% integrations roll out and turn on the ones<00:06:43.200> that<00:06:43.320> match<00:06:43.600> tools<00:06:43.880> you<00:06:44.000> already<00:06:44.360> use 00:06:44.630 --> 00:06:44.640 align:start position:0% ones that match tools you already use 00:06:44.640 --> 00:06:46.750 align:start position:0% ones that match tools you already use daily.<00:06:45.320> If<00:06:45.480> you<00:06:45.600> run<00:06:45.720> a<00:06:45.760> business,<00:06:46.440> start 00:06:46.750 --> 00:06:46.760 align:start position:0% daily. If you run a business, start 00:06:46.760 --> 00:06:47.909 align:start position:0% daily. If you run a business, start thinking<00:06:47.040> about<00:06:47.320> which<00:06:47.520> one<00:06:47.640> of<00:06:47.720> these 00:06:47.909 --> 00:06:47.919 align:start position:0% thinking about which one of these 00:06:47.919 --> 00:06:50.430 align:start position:0% thinking about which one of these connected<00:06:48.400> apps<00:06:49.000> could<00:06:49.200> remove<00:06:49.720> a<00:06:49.760> repetitive 00:06:50.430 --> 00:06:50.440 align:start position:0% connected apps could remove a repetitive 00:06:50.440 --> 00:06:52.470 align:start position:0% connected apps could remove a repetitive task<00:06:51.040> from<00:06:51.240> your<00:06:51.400> week.<00:06:51.760> Meeting<00:06:52.120> notes, 00:06:52.470 --> 00:06:52.480 align:start position:0% task from your week. Meeting notes, 00:06:52.480 --> 00:06:54.150 align:start position:0% task from your week. Meeting notes, bookings,<00:06:52.880> website<00:06:53.320> edits,<00:06:53.640> pick<00:06:53.880> one<00:06:54.040> and 00:06:54.150 --> 00:06:54.160 align:start position:0% bookings, website edits, pick one and 00:06:54.160 --> 00:06:56.110 align:start position:0% bookings, website edits, pick one and test<00:06:54.440> it.<00:06:54.840> And<00:06:54.960> if<00:06:55.080> you<00:06:55.160> manage<00:06:55.480> a<00:06:55.520> team,<00:06:55.919> this 00:06:56.110 --> 00:06:56.120 align:start position:0% test it. And if you manage a team, this 00:06:56.120 --> 00:06:58.230 align:start position:0% test it. And if you manage a team, this is<00:06:56.240> worth<00:06:56.480> a<00:06:56.560> 5-minute<00:06:57.080> conversation<00:06:58.000> in<00:06:58.120> your 00:06:58.230 --> 00:06:58.240 align:start position:0% is worth a 5-minute conversation in your 00:06:58.240 --> 00:07:00.270 align:start position:0% is worth a 5-minute conversation in your next<00:06:58.520> meeting.<00:06:59.160> Not<00:06:59.400> because<00:06:59.680> everyone<00:07:00.040> needs 00:07:00.270 --> 00:07:00.280 align:start position:0% next meeting. Not because everyone needs 00:07:00.280 --> 00:07:02.270 align:start position:0% next meeting. Not because everyone needs to<00:07:00.360> become<00:07:00.640> an<00:07:00.760> AI<00:07:01.000> expert,<00:07:01.720> but<00:07:01.880> because<00:07:02.160> the 00:07:02.270 --> 00:07:02.280 align:start position:0% to become an AI expert, but because the 00:07:02.280 --> 00:07:04.470 align:start position:0% to become an AI expert, but because the tools<00:07:02.640> your<00:07:02.800> team<00:07:03.120> uses<00:07:03.520> every<00:07:03.760> day<00:07:04.320> are 00:07:04.470 --> 00:07:04.480 align:start position:0% tools your team uses every day are 00:07:04.480 --> 00:07:06.510 align:start position:0% tools your team uses every day are quietly<00:07:05.040> getting<00:07:05.320> more<00:07:05.520> capable.<00:07:06.240> And<00:07:06.360> it's 00:07:06.510 --> 00:07:06.520 align:start position:0% quietly getting more capable. And it's 00:07:06.520 --> 00:07:08.270 align:start position:0% quietly getting more capable. And it's worth<00:07:06.800> knowing<00:07:07.080> what's<00:07:07.240> available<00:07:07.960> before 00:07:08.270 --> 00:07:08.280 align:start position:0% worth knowing what's available before 00:07:08.280 --> 00:07:10.310 align:start position:0% worth knowing what's available before someone<00:07:08.600> on<00:07:08.720> your<00:07:08.840> team<00:07:09.320> stumbles<00:07:09.800> onto<00:07:10.080> it<00:07:10.200> by 00:07:10.310 --> 00:07:10.320 align:start position:0% someone on your team stumbles onto it by 00:07:10.320 --> 00:07:12.310 align:start position:0% someone on your team stumbles onto it by accident.<00:07:11.040> If<00:07:11.200> you<00:07:11.320> want<00:07:11.520> help<00:07:11.800> figuring<00:07:12.200> out 00:07:12.310 --> 00:07:12.320 align:start position:0% accident. If you want help figuring out 00:07:12.320 --> 00:07:14.110 align:start position:0% accident. If you want help figuring out exactly<00:07:12.800> how<00:07:12.960> to<00:07:13.080> use<00:07:13.320> tools<00:07:13.600> like<00:07:13.800> Gemini 00:07:14.110 --> 00:07:14.120 align:start position:0% exactly how to use tools like Gemini 00:07:14.120 --> 00:07:16.350 align:start position:0% exactly how to use tools like Gemini notebook<00:07:14.840> and<00:07:14.960> connected<00:07:15.440> apps<00:07:15.680> to<00:07:15.800> save<00:07:16.040> time 00:07:16.350 --> 00:07:16.360 align:start position:0% notebook and connected apps to save time 00:07:16.360 --> 00:07:17.990 align:start position:0% notebook and connected apps to save time and<00:07:16.440> grow<00:07:16.640> your<00:07:16.760> business,<00:07:17.520> that's<00:07:17.760> what<00:07:17.880> we 00:07:17.990 --> 00:07:18.000 align:start position:0% and grow your business, that's what we 00:07:18.000 --> 00:07:19.830 align:start position:0% and grow your business, that's what we do<00:07:18.240> every<00:07:18.480> week<00:07:18.760> inside<00:07:19.120> the<00:07:19.240> AI<00:07:19.480> Profit 00:07:19.830 --> 00:07:19.840 align:start position:0% do every week inside the AI Profit 00:07:19.840 --> 00:07:21.390 align:start position:0% do every week inside the AI Profit Boardroom.<00:07:20.560> We're<00:07:20.680> already<00:07:21.000> building<00:07:21.360> a 00:07:21.390 --> 00:07:21.400 align:start position:0% Boardroom. We're already building a 00:07:21.400 --> 00:07:23.390 align:start position:0% Boardroom. We're already building a walk-through<00:07:22.160> on<00:07:22.320> setting<00:07:22.720> up<00:07:22.880> Gemini's 00:07:23.390 --> 00:07:23.400 align:start position:0% walk-through on setting up Gemini's 00:07:23.400 --> 00:07:25.310 align:start position:0% walk-through on setting up Gemini's connected<00:07:23.840> apps<00:07:24.360> specifically<00:07:25.000> for<00:07:25.120> lead 00:07:25.310 --> 00:07:25.320 align:start position:0% connected apps specifically for lead 00:07:25.320 --> 00:07:27.030 align:start position:0% connected apps specifically for lead generation<00:07:25.840> and<00:07:25.960> client<00:07:26.200> bookings,<00:07:26.880> so 00:07:27.030 --> 00:07:27.040 align:start position:0% generation and client bookings, so 00:07:27.040 --> 00:07:28.470 align:start position:0% generation and client bookings, so you're<00:07:27.160> not<00:07:27.360> guessing<00:07:27.760> when<00:07:27.880> it<00:07:27.960> rolls<00:07:28.200> out<00:07:28.400> to 00:07:28.470 --> 00:07:28.480 align:start position:0% you're not guessing when it rolls out to 00:07:28.480 --> 00:07:30.470 align:start position:0% you're not guessing when it rolls out to your<00:07:28.600> account.<00:07:29.280> Four<00:07:29.560> coaching<00:07:29.960> calls<00:07:30.240> every 00:07:30.470 --> 00:07:30.480 align:start position:0% your account. Four coaching calls every 00:07:30.480 --> 00:07:32.830 align:start position:0% your account. Four coaching calls every week,<00:07:30.760> daily<00:07:31.120> step-by-step<00:07:31.880> tutorials<00:07:32.720> the 00:07:32.830 --> 00:07:32.840 align:start position:0% week, daily step-by-step tutorials the 00:07:32.840 --> 00:07:35.310 align:start position:0% week, daily step-by-step tutorials the moment<00:07:33.320> new<00:07:33.600> AI<00:07:33.880> features<00:07:34.320> like<00:07:34.480> this<00:07:34.680> launch, 00:07:35.310 --> 00:07:35.320 align:start position:0% moment new AI features like this launch, 00:07:35.320 --> 00:07:37.230 align:start position:0% moment new AI features like this launch, a<00:07:35.400> prompt<00:07:35.760> library<00:07:36.160> built<00:07:36.440> for<00:07:36.600> real<00:07:36.880> business 00:07:37.230 --> 00:07:37.240 align:start position:0% a prompt library built for real business 00:07:37.240 --> 00:07:39.750 align:start position:0% a prompt library built for real business use,<00:07:37.760> not<00:07:38.040> generic<00:07:38.480> examples,<00:07:39.280> and<00:07:39.400> a<00:07:39.480> member 00:07:39.750 --> 00:07:39.760 align:start position:0% use, not generic examples, and a member 00:07:39.760 --> 00:07:41.790 align:start position:0% use, not generic examples, and a member map<00:07:40.280> so<00:07:40.440> you<00:07:40.560> can<00:07:40.720> connect<00:07:41.400> with<00:07:41.560> other 00:07:41.790 --> 00:07:41.800 align:start position:0% map so you can connect with other 00:07:41.800 --> 00:07:43.750 align:start position:0% map so you can connect with other business<00:07:42.160> owners<00:07:42.480> near<00:07:42.760> you<00:07:43.160> who<00:07:43.280> are<00:07:43.360> testing 00:07:43.750 --> 00:07:43.760 align:start position:0% business owners near you who are testing 00:07:43.760 --> 00:07:45.550 align:start position:0% business owners near you who are testing the<00:07:43.840> same<00:07:44.080> tools.<00:07:44.680> Link<00:07:44.920> is<00:07:45.040> in<00:07:45.160> the<00:07:45.240> comments 00:07:45.550 --> 00:07:45.560 align:start position:0% the same tools. Link is in the comments 00:07:45.560 --> 00:07:47.110 align:start position:0% the same tools. Link is in the comments and<00:07:45.640> description<00:07:46.400> or<00:07:46.600> head<00:07:46.800> to 00:07:47.110 --> 00:07:47.120 align:start position:0% and description or head to 00:07:47.120 --> 00:07:49.550 align:start position:0% and description or head to aiprofitboardroom.com. 00:07:49.550 --> 00:07:49.560 align:start position:0% aiprofitboardroom.com. 00:07:49.560 --> 00:07:51.150 align:start position:0% aiprofitboardroom.com. And<00:07:49.680> if<00:07:49.800> you<00:07:49.880> just<00:07:50.080> want<00:07:50.200> to<00:07:50.280> start<00:07:50.560> smaller, 00:07:51.150 --> 00:07:51.160 align:start position:0% And if you just want to start smaller, 00:07:51.160 --> 00:07:53.550 align:start position:0% And if you just want to start smaller, free,<00:07:51.760> no<00:07:51.960> pressure,<00:07:52.560> join<00:07:52.800> the<00:07:52.920> AI<00:07:53.160> Success 00:07:53.550 --> 00:07:53.560 align:start position:0% free, no pressure, join the AI Success 00:07:53.560 --> 00:07:55.590 align:start position:0% free, no pressure, join the AI Success Lab.<00:07:54.000> It's<00:07:54.200> our<00:07:54.320> free<00:07:54.520> community.<00:07:55.240> And<00:07:55.360> if<00:07:55.480> you 00:07:55.590 --> 00:07:55.600 align:start position:0% Lab. It's our free community. And if you 00:07:55.600 --> 00:07:57.990 align:start position:0% Lab. It's our free community. And if you want<00:07:55.800> the<00:07:55.880> full<00:07:56.120> process,<00:07:56.880> the<00:07:57.040> SOPs,<00:07:57.840> and 00:07:57.990 --> 00:07:58.000 align:start position:0% want the full process, the SOPs, and 00:07:58.000 --> 00:08:00.470 align:start position:0% want the full process, the SOPs, and over<00:07:58.200> 100<00:07:58.760> AI<00:07:59.000> use<00:07:59.240> cases<00:07:59.880> like<00:08:00.080> the<00:08:00.160> ones<00:08:00.400> I 00:08:00.470 --> 00:08:00.480 align:start position:0% over 100 AI use cases like the ones I 00:08:00.480 --> 00:08:02.190 align:start position:0% over 100 AI use cases like the ones I covered<00:08:00.760> today,<00:08:01.360> that's<00:08:01.600> exactly<00:08:02.000> what's 00:08:02.190 --> 00:08:02.200 align:start position:0% covered today, that's exactly what's 00:08:02.200 --> 00:08:03.590 align:start position:0% covered today, that's exactly what's inside.<00:08:02.760> You'll<00:08:02.880> get<00:08:03.040> all<00:08:03.160> the<00:08:03.240> notes<00:08:03.480> from 00:08:03.590 --> 00:08:03.600 align:start position:0% inside. You'll get all the notes from 00:08:03.600 --> 00:08:05.470 align:start position:0% inside. You'll get all the notes from this<00:08:03.760> video<00:08:04.040> there,<00:08:04.520> plus<00:08:04.880> access<00:08:05.280> to<00:08:05.400> a 00:08:05.470 --> 00:08:05.480 align:start position:0% this video there, plus access to a 00:08:05.480 --> 00:08:07.670 align:start position:0% this video there, plus access to a community<00:08:05.960> of<00:08:06.040> 75,000<00:08:06.880> members<00:08:07.400> who<00:08:07.520> are 00:08:07.670 --> 00:08:07.680 align:start position:0% community of 75,000 members who are 00:08:07.680 --> 00:08:09.630 align:start position:0% community of 75,000 members who are already<00:08:08.000> using<00:08:08.280> tools<00:08:08.600> like<00:08:08.760> Gemini<00:08:09.400> to<00:08:09.480> get 00:08:09.630 --> 00:08:09.640 align:start position:0% already using tools like Gemini to get 00:08:09.640 --> 00:08:11.110 align:start position:0% already using tools like Gemini to get ahead.<00:08:10.200> Links<00:08:10.520> in<00:08:10.600> the<00:08:10.680> comments<00:08:11.000> and 00:08:11.110 --> 00:08:11.120 align:start position:0% ahead. Links in the comments and 00:08:11.120 --> 00:08:13.350 align:start position:0% ahead. Links in the comments and description.<00:08:11.880> Gemini<00:08:12.360> just<00:08:12.640> crossed<00:08:13.080> 1 00:08:13.350 --> 00:08:13.360 align:start position:0% description. Gemini just crossed 1 00:08:13.360 --> 00:08:15.230 align:start position:0% description. Gemini just crossed 1 billion<00:08:13.720> users,<00:08:14.480> and<00:08:14.600> it's<00:08:14.760> only<00:08:14.960> getting 00:08:15.230 --> 00:08:15.240 align:start position:0% billion users, and it's only getting 00:08:15.240 --> 00:08:17.070 align:start position:0% billion users, and it's only getting more<00:08:15.400> capable<00:08:15.919> from<00:08:16.120> here.<00:08:16.640> The<00:08:16.720> question 00:08:17.070 --> 00:08:17.080 align:start position:0% more capable from here. The question 00:08:17.080 --> 00:08:18.510 align:start position:0% more capable from here. The question isn't<00:08:17.360> whether<00:08:17.560> tools<00:08:17.880> like<00:08:18.040> this<00:08:18.240> become 00:08:18.510 --> 00:08:18.520 align:start position:0% isn't whether tools like this become 00:08:18.520 --> 00:08:20.070 align:start position:0% isn't whether tools like this become part<00:08:18.720> of<00:08:18.840> how<00:08:18.960> you<00:08:19.080> run<00:08:19.280> your<00:08:19.360> day,<00:08:19.960> it's 00:08:20.070 --> 00:08:20.080 align:start position:0% part of how you run your day, it's 00:08:20.080 --> 00:08:21.710 align:start position:0% part of how you run your day, it's whether<00:08:20.280> you<00:08:20.400> start<00:08:20.680> using<00:08:20.919> them<00:08:21.040> now<00:08:21.560> or 00:08:21.710 --> 00:08:21.720 align:start position:0% whether you start using them now or 00:08:21.720 --> 00:08:24.640 align:start position:0% whether you start using them now or catch<00:08:22.000> up<00:08:22.120> later.