WEBVTT 00:00:00.000 --> 00:00:04.759 Imagine an AI platform claiming $36 million in 00:00:04.759 --> 00:00:09.259 revenue in just 45 days. 45 days. That's why. 00:00:09.259 --> 00:00:11.939 That's a staggering pace, right? Mm -hmm. Is 00:00:11.939 --> 00:00:15.140 that meteoric rise backed by real, tangible value, 00:00:15.679 --> 00:00:17.699 or are we just looking at another wave of, well, 00:00:17.879 --> 00:00:20.219 pure hype? That's the big question. Today, we're 00:00:20.219 --> 00:00:22.399 peeling back the layers and diving deep into 00:00:22.399 --> 00:00:25.210 Genspark. Welcome back to the Deep Dive. This 00:00:25.210 --> 00:00:27.489 is where we distill complex information into 00:00:27.489 --> 00:00:30.670 clear, actionable insights for you. And today, 00:00:31.469 --> 00:00:34.329 we're unpacking a comprehensive hands -on review 00:00:34.329 --> 00:00:37.789 of Ganspark. It's a fascinating, very new player 00:00:37.789 --> 00:00:41.189 in the rapidly evolving AI landscape. Definitely 00:00:41.189 --> 00:00:42.689 new, definitely making noise. We're going to 00:00:42.689 --> 00:00:45.350 rigorously explore its bold claims, put it through 00:00:45.350 --> 00:00:47.750 its paces in several real -world business scenarios, 00:00:47.950 --> 00:00:50.090 and ultimately help you decide if it's a tool 00:00:50.090 --> 00:00:52.229 that belongs in your toolkit. That's right. We're 00:00:52.229 --> 00:00:54.350 going to dig into its undeniable strengths, pinpoint 00:00:54.350 --> 00:00:56.229 exactly where it falls short, and give you an 00:00:56.229 --> 00:00:58.350 objective view. Because this isn't sponsored 00:00:58.350 --> 00:01:01.869 content. This review used the paid version, putting 00:01:01.869 --> 00:01:04.250 it to work just like, well, any business professional 00:01:04.250 --> 00:01:07.010 would. Our goal is to bring you that crucial 00:01:07.010 --> 00:01:11.599 aha. moment. So Gensburg actually started its 00:01:11.599 --> 00:01:14.620 journey as a search engine, had a pretty impressive 00:01:14.620 --> 00:01:16.879 user base too, around five million I think? Five 00:01:16.879 --> 00:01:19.689 million, yeah. Then, just a few months ago, they 00:01:19.689 --> 00:01:22.469 made a really dramatic pivot. Big pivot. They 00:01:22.469 --> 00:01:25.609 didn't just tweak things. They completely reimagined 00:01:25.609 --> 00:01:28.670 their core offering. And that pivot was profound. 00:01:29.129 --> 00:01:31.489 They transformed into what they now call a super 00:01:31.489 --> 00:01:33.810 agent platform. Super agent, yeah. Think of it 00:01:33.810 --> 00:01:36.409 as a specialized collection of AI tools. These 00:01:36.409 --> 00:01:38.989 aren't general purpose chatbots. They're specifically 00:01:38.989 --> 00:01:40.890 engineered to assist businesses with a whole 00:01:40.890 --> 00:01:43.750 spectrum of tasks, from market research to content 00:01:43.750 --> 00:01:46.150 creation. Right, like having a team of AI specialists 00:01:46.150 --> 00:01:48.390 on call. Exactly. It's like having a team of 00:01:48.390 --> 00:01:50.849 specialized AI consultants at your fingertips, 00:01:51.269 --> 00:01:53.609 each ready for a different part of your company's 00:01:53.609 --> 00:01:55.829 operations. And the growth numbers since that 00:01:55.829 --> 00:01:58.109 pivot? Honestly, they're truly staggering. They 00:01:58.109 --> 00:02:00.730 reported hitting $10 million in annual recurring 00:02:00.730 --> 00:02:04.049 revenue, or ARR. That's the predictable recurring 00:02:04.049 --> 00:02:07.469 stuff. Exactly. That ARR number hit $10 million 00:02:07.469 --> 00:02:11.250 in just nine days after launching this new agent 00:02:11.250 --> 00:02:14.490 platform. Nine days. Wow. Now, barely 45 days 00:02:14.490 --> 00:02:18.289 in, they're at an astonishing $36 million ARR. 00:02:18.509 --> 00:02:21.050 That's essentially adding nearly $1 million in 00:02:21.050 --> 00:02:23.729 revenue daily. A million a day. When numbers 00:02:23.729 --> 00:02:26.210 like that hit the street, it sends ripples through 00:02:26.210 --> 00:02:29.129 Silicon Valley. Yeah, absolutely. So they're 00:02:29.129 --> 00:02:31.509 clearly positioning themselves as a direct competitor 00:02:31.509 --> 00:02:34.500 to establish AI behemoths like, say, Chat, GPT, 00:02:34.500 --> 00:02:36.900 and Claude. Mm -hmm, aiming high. But here's 00:02:36.900 --> 00:02:39.060 the million -dollar question for you. Are they 00:02:39.060 --> 00:02:42.000 truly competitive? Given that explosive, almost 00:02:42.000 --> 00:02:44.879 unbelievable growth, does Ginsburg truly deliver 00:02:44.879 --> 00:02:47.639 on its ambitious promises in practical business 00:02:47.639 --> 00:02:49.719 applications? Well, we're about to find out if 00:02:49.719 --> 00:02:52.000 that utility truly matches those impressive high 00:02:52.000 --> 00:02:54.680 -speed numbers. OK, so our investigation began 00:02:54.680 --> 00:02:57.199 by tackling a fundamental business challenge, 00:02:57.580 --> 00:02:59.840 creating a compelling investor presentation. 00:02:59.919 --> 00:03:02.939 Right, the pitch deck. For our first test, we 00:03:02.939 --> 00:03:05.099 asked Genspark to build an investor pitch deck 00:03:05.099 --> 00:03:07.780 for a hypothetical SaaS company software as a 00:03:07.780 --> 00:03:10.780 service we called Kinexfair. This fictional company 00:03:10.780 --> 00:03:15.710 uses AI to automate B2B. business to business, 00:03:15.969 --> 00:03:18.550 prospect outreach, pretty common problem for 00:03:18.550 --> 00:03:21.250 sales teams. We wanted to see if GenSpark could 00:03:21.250 --> 00:03:24.289 craft a story that would genuinely excite investors. 00:03:24.650 --> 00:03:26.449 And the prompt we gave, it was quite specific, 00:03:26.610 --> 00:03:30.030 right? We needed a compelling 15 -minute presentation 00:03:30.030 --> 00:03:33.229 for a seed round, aiming to raise between $1 00:03:33.229 --> 00:03:35.870 .5 and $2 million. We really pushed for something 00:03:35.870 --> 00:03:38.289 that didn't just convey information, but built 00:03:38.289 --> 00:03:42.150 a narrative that could get VCs, venture capitalists, 00:03:42.150 --> 00:03:44.750 interested. The initial design, frankly, was 00:03:44.750 --> 00:03:46.530 pretty terrible. Oh, really? Yeah, I'd give it 00:03:46.530 --> 00:03:49.650 a generous 3 out of 10. It was bland, uninspired, 00:03:49.849 --> 00:03:52.610 like something pulled straight from a 2015 template 00:03:52.610 --> 00:03:55.569 you'd find deep in some dusty archive. No modern 00:03:55.569 --> 00:03:58.789 flair, no visual punch. beat, but the content, 00:03:58.830 --> 00:04:00.930 that was a completely different story. Ah, okay, 00:04:01.030 --> 00:04:03.569 so the substance. The research quality was genuinely 00:04:03.569 --> 00:04:06.710 impressive, an easy 8 out of 10. Gainspark really 00:04:06.710 --> 00:04:09.870 dug into ConnectSphere's value proposition, synthesizing 00:04:09.870 --> 00:04:13.509 key arguments. For example, it insightfully highlighted 00:04:13.509 --> 00:04:16.769 a critical pain point for sales teams. An average 00:04:16.769 --> 00:04:19.430 sales representative spends only 35 % of their 00:04:19.430 --> 00:04:22.089 time actually selling. That's a powerful step. 00:04:22.329 --> 00:04:24.470 Right. A data -backed insight that immediately 00:04:24.470 --> 00:04:27.089 validates the need for a solution like ConnectSphere. 00:04:27.670 --> 00:04:30.470 Really strong point. So seeing the potential 00:04:30.470 --> 00:04:33.250 there, we asked for a redesign. We explicitly 00:04:33.250 --> 00:04:35.550 requested something clean and professional, kind 00:04:35.550 --> 00:04:37.750 of like the aesthetic of HubSpot or Salesforce. 00:04:38.389 --> 00:04:40.589 Going for that established look. Exactly. And 00:04:40.589 --> 00:04:43.050 it improved significantly, jumping to about a 00:04:43.050 --> 00:04:45.329 6 out of 10. Better. Still not a visual masterpiece, 00:04:45.410 --> 00:04:47.769 don't get me wrong, but definitely usable. A 00:04:47.769 --> 00:04:50.449 solid first draft, ready for a human designer 00:04:50.449 --> 00:04:53.629 to polish up. So what this tells us is Genspark 00:04:53.629 --> 00:04:56.170 delivered strong content, the actual subsist 00:04:56.170 --> 00:04:59.600 was good, But the visual design clearly needs 00:04:59.600 --> 00:05:02.199 human intervention, right? Precisely. It shows 00:05:02.199 --> 00:05:04.699 AI can generate the story, the core message, 00:05:04.839 --> 00:05:07.860 but that visual finesse. That still requires 00:05:07.860 --> 00:05:09.600 human oversight, especially for high -stakes 00:05:09.600 --> 00:05:13.740 presentations. Okay, next up. We wanted to truly 00:05:13.740 --> 00:05:17.100 push Ginsburg's capabilities, right? Challenge 00:05:17.100 --> 00:05:20.259 it with something far more complex. Yep. An interactive 00:05:20.259 --> 00:05:22.720 product demo for a Kinexphere. The prompt was 00:05:22.720 --> 00:05:26.060 ambitious. a single page HTML demo, that's the 00:05:26.060 --> 00:05:29.079 web page language, complete with features, testimonials, 00:05:29.279 --> 00:05:32.519 an ROI calculator, lead capture forms. It works. 00:05:32.819 --> 00:05:34.839 And we specifically requested it look like it 00:05:34.839 --> 00:05:38.019 costs, what, $25 ,000 to build, aiming for a 00:05:38.019 --> 00:05:40.209 really high fidelity output. And here's where 00:05:40.209 --> 00:05:42.449 it got really interesting. Almost bizarre, actually. 00:05:43.069 --> 00:05:45.810 Genspark made a huge fundamental mistake. Instead 00:05:45.810 --> 00:05:48.230 of building a demo for our B2B outreach tool, 00:05:48.569 --> 00:05:51.009 it just veered off course entirely. What did 00:05:51.009 --> 00:05:54.410 it build? It created an internal employee networking 00:05:54.410 --> 00:05:56.949 platform for a completely different hypothetical 00:05:56.949 --> 00:06:00.310 business. No way. Total prompt drift. A complete 00:06:00.310 --> 00:06:03.569 misunderstanding of the core request. Wild. What's 00:06:03.569 --> 00:06:06.009 truly fascinating here, though, and this is a... 00:06:05.709 --> 00:06:08.449 Genuine moment of wonder for me is that this 00:06:08.449 --> 00:06:11.069 mistake led to an incredible discovery. Right. 00:06:11.069 --> 00:06:13.149 Genspark didn't just mock it up with static images 00:06:13.149 --> 00:06:16.170 or text. It built a fully functional interactive 00:06:16.170 --> 00:06:18.589 web application for this employee networking 00:06:18.589 --> 00:06:21.790 idea. Clickable elements, dynamic forms. A working 00:06:21.790 --> 00:06:23.990 application, not just a concept sketch. It was 00:06:23.990 --> 00:06:27.170 astonishing. It included customizable employee 00:06:27.170 --> 00:06:30.170 profiles, recommendation features, a virtual 00:06:30.170 --> 00:06:33.980 coffee scheduler. Even a working news feed and 00:06:33.980 --> 00:06:36.560 interactive ROI calculators. And it actually 00:06:36.560 --> 00:06:38.899 worked? It worked. The technical execution was 00:06:38.899 --> 00:06:42.579 solid. Obust, even. Despite the colossal misunderstanding 00:06:42.579 --> 00:06:46.220 of the initial brief, it just cranked out a working 00:06:46.220 --> 00:06:49.759 application almost effortlessly. Just imagine 00:06:49.759 --> 00:06:52.360 the implications here, rapidly prototyping and 00:06:52.360 --> 00:06:55.259 testing entirely new startup ideas or internal 00:06:55.259 --> 00:06:58.160 tools, maybe, with this kind of speed and surprising 00:06:58.160 --> 00:07:00.279 functionality. It's like being able to instantly 00:07:00.279 --> 00:07:02.879 manifest a minimum viable product that's a serious, 00:07:02.879 --> 00:07:05.759 serious capability, even with that prompt misunderstanding. 00:07:06.040 --> 00:07:08.579 So, okay, the Spark fundamentally missed the 00:07:08.579 --> 00:07:10.759 mark on what to build for us, but how well did 00:07:10.759 --> 00:07:13.420 it build the actual functionality? It profoundly 00:07:13.420 --> 00:07:15.480 misunderstood the request, yeah, yet built a 00:07:15.480 --> 00:07:17.259 fully functional application with really impressive 00:07:17.259 --> 00:07:19.500 technical execution. All right, test number three. 00:07:20.240 --> 00:07:22.459 We zeroed in on social media, a critical area 00:07:22.459 --> 00:07:24.459 for building brand awareness and engagement, 00:07:24.639 --> 00:07:27.459 especially now. Absolutely crucial. We asked 00:07:27.459 --> 00:07:30.279 Gensburg for a complete visual content system 00:07:30.279 --> 00:07:33.000 for LinkedIn and Twitter. Things like, quote, 00:07:33.300 --> 00:07:36.879 graphics, infographic templates. This test, unfortunately, 00:07:37.360 --> 00:07:40.120 revealed Gensburg's biggest, most glaring weakness. 00:07:40.339 --> 00:07:42.959 Which is? It's abysmal handling of text within 00:07:42.959 --> 00:07:47.009 images. The, quote, graphics. Riddled with embarrassing 00:07:47.009 --> 00:07:50.189 spelling errors, inconsistencies, awkward formatting. 00:07:50.449 --> 00:07:53.730 Oof. Not bad. Yeah. And the design itself was 00:07:53.730 --> 00:07:55.870 just mediocre, too. Nothing that would really 00:07:55.870 --> 00:07:59.110 stand out in a busy feed. However, to its credit, 00:07:59.529 --> 00:08:02.269 the underlying strategic framework Genspark generated 00:08:02.269 --> 00:08:05.129 was remarkably solid. That's interesting. The 00:08:05.129 --> 00:08:07.329 content calendar structure was well thought out. 00:08:07.470 --> 00:08:10.410 It proposed logical weekly themes, a strategic 00:08:10.410 --> 00:08:13.069 posting schedule. The ideas were there. The structure 00:08:13.069 --> 00:08:16.089 was sound. Just the execution on the visual side 00:08:16.089 --> 00:08:18.550 was poor. We tried to redeem it, you know, gave 00:08:18.550 --> 00:08:20.629 it a second chance. We asked for quotes from 00:08:20.629 --> 00:08:22.689 specific well -known leaders like Aaron Ross, 00:08:23.310 --> 00:08:25.949 requested fresher, more modern designs. It did 00:08:25.949 --> 00:08:28.930 improve slightly, but that persistent text and 00:08:28.930 --> 00:08:31.550 image problem, it stubbornly remained. I have 00:08:31.550 --> 00:08:34.039 to admit. I still wrestle with prompt drift myself 00:08:34.039 --> 00:08:36.600 sometimes, finding the perfect phrasing to get 00:08:36.600 --> 00:08:38.879 AI to do exactly what I envision. Yeah, it's 00:08:38.879 --> 00:08:41.860 tricky. So while it's understandable, it's a 00:08:41.860 --> 00:08:43.960 clear and persistent limitation for Genspark 00:08:43.960 --> 00:08:46.539 in this area. So for creating actual graphics 00:08:46.539 --> 00:08:49.759 with text, Genspark is a definite no -go then. 00:08:50.259 --> 00:08:52.620 But the strategic content planning behind it, 00:08:52.919 --> 00:08:54.960 that part is surprisingly good. Graphics struggle 00:08:54.960 --> 00:08:57.259 significantly, yeah. Yeah. Yet the strategic 00:08:57.259 --> 00:09:00.539 content planning and conceptualization, undeniably 00:09:00.539 --> 00:09:03.590 strong. Okay, for our fourth test, we've entered 00:09:03.590 --> 00:09:07.110 into highly sensitive territory, building a comprehensive 00:09:07.110 --> 00:09:09.350 data room. Right, this is essential for fundraising 00:09:09.350 --> 00:09:12.429 or selling a company. Complex, detail -oriented, 00:09:12.970 --> 00:09:15.909 needs precision. Absolutely. The prompt was to 00:09:15.909 --> 00:09:18.149 create a professionally organized virtual data 00:09:18.149 --> 00:09:20.809 room site. Sections for financial docs, traction 00:09:20.809 --> 00:09:23.330 dashboards, and market analysis designed specifically 00:09:23.330 --> 00:09:25.769 to impress top -tier VCs. High stakes. How did 00:09:25.769 --> 00:09:27.809 it do you? The structural organization was genuinely 00:09:27.809 --> 00:09:30.850 impressive. Sections for detailed financial scenarios, 00:09:31.190 --> 00:09:33.409 clear breakdowns of tune credentials, market 00:09:33.409 --> 00:09:36.169 opportunity analyses, it laid it all out logically. 00:09:36.389 --> 00:09:38.610 Sounds good so far. But here's the crucial catch, 00:09:38.850 --> 00:09:42.600 a significant caveat. Genspark fabricated information 00:09:42.600 --> 00:09:45.620 where it didn't have access to real data. It 00:09:45.620 --> 00:09:47.779 filled in the blanks with plausible sounding, 00:09:48.279 --> 00:09:51.460 but entirely made up numbers and details. This 00:09:51.460 --> 00:09:53.639 is critical for you to remember. It's a framework, 00:09:54.320 --> 00:09:57.299 not a fact generator. Interestingly though, When 00:09:57.299 --> 00:10:00.019 it created a fake advisory board for our Kinexphere 00:10:00.019 --> 00:10:02.279 company, it didn't just invent random names. 00:10:02.299 --> 00:10:05.559 Oh. It pulled names of real well -known investors 00:10:05.559 --> 00:10:08.860 in the B2B SaaS space. Wow, really? Yeah. So 00:10:08.860 --> 00:10:11.179 the research capability to identify relevant 00:10:11.179 --> 00:10:13.779 figures is clearly there, even if the data it 00:10:13.779 --> 00:10:16.379 then generates to fill a template is purely fictional. 00:10:16.639 --> 00:10:19.120 That's a unique aspect, shows it has some deep 00:10:19.120 --> 00:10:21.379 understanding of who's who in that industry. 00:10:21.840 --> 00:10:24.120 So Gensmark offers an excellent structure, a 00:10:24.120 --> 00:10:26.519 solid framework for that data room. But what 00:10:26.519 --> 00:10:28.980 about populating it with the actual accurate 00:10:28.980 --> 00:10:31.360 numbers and sensitive data? The framework is 00:10:31.360 --> 00:10:34.159 excellent, yeah. But for critical data, manual 00:10:34.159 --> 00:10:36.480 input and verification are absolutely necessary. 00:10:36.500 --> 00:10:40.240 You can't trust its generated numbers. Now, this 00:10:40.240 --> 00:10:43.220 next test, arguably the most important for any 00:10:43.220 --> 00:10:45.860 business leader, right? I'd agree. We asked Genspark 00:10:45.860 --> 00:10:49.059 to research and create detailed customer personas 00:10:49.059 --> 00:10:51.940 for ConnectSphere, focusing on two key roles, 00:10:52.620 --> 00:10:55.620 VPs of sales and sales managers. Understanding 00:10:55.620 --> 00:10:58.299 your customer, it's everything. It's the foundation 00:10:58.299 --> 00:11:00.740 of effective marketing, sales, product development, 00:11:01.320 --> 00:11:04.580 everything. And this test, it truly produced 00:11:04.580 --> 00:11:07.559 the best, most actionable results of the entire 00:11:07.559 --> 00:11:11.000 evaluation. Really? The best. By far. It created 00:11:11.000 --> 00:11:13.879 incredibly detailed, nuanced personas. These 00:11:13.879 --> 00:11:16.159 weren't just surface -level demographic profiles. 00:11:16.340 --> 00:11:19.019 They were rich, insightful portraits of target 00:11:19.019 --> 00:11:21.080 customers. Like what? What kind of detail? It 00:11:21.080 --> 00:11:23.320 included comprehensive demographic profiles, 00:11:23.919 --> 00:11:26.159 critical key performance indicators, KPIs, those 00:11:26.159 --> 00:11:28.580 crucial metrics, and even deeply insightful pain 00:11:28.580 --> 00:11:31.120 points. It even provided direct quotes that felt 00:11:31.120 --> 00:11:33.750 authentic, like, My team spends too much time 00:11:33.750 --> 00:11:35.929 on manual prospecting instead of closing deals. 00:11:36.029 --> 00:11:38.750 Wow, that's specific. That's not just info. That's 00:11:38.750 --> 00:11:41.389 raw, actionable insight you can build a marketing 00:11:41.389 --> 00:11:44.610 campaign around. The platform went even deeper. 00:11:45.210 --> 00:11:47.470 It identified specific language patterns these 00:11:47.470 --> 00:11:50.090 customers would use, the emotional triggers that 00:11:50.090 --> 00:11:52.850 motivate them, common objections they might raise 00:11:52.850 --> 00:11:55.090 during a sales cycle. OK, that's impressive. 00:11:55.490 --> 00:11:58.049 It even offered insights into which specific 00:11:58.049 --> 00:12:01.149 features customers would actually pay for. That's 00:12:01.149 --> 00:12:03.929 a huge win for product managers trying to prioritize 00:12:03.929 --> 00:12:07.090 development. This level of granular customer 00:12:07.090 --> 00:12:10.070 insight, right out of the box. Yeah. That's pure 00:12:10.070 --> 00:12:12.950 gold for any founder, any marketing team. Totally. 00:12:13.169 --> 00:12:15.289 You could literally feed these personas directly 00:12:15.289 --> 00:12:17.389 into your copywriting, your sales scripts, your 00:12:17.389 --> 00:12:19.389 product roadmap. That's like having a dedicated 00:12:19.389 --> 00:12:21.769 market research team working for you for a fraction 00:12:21.769 --> 00:12:24.169 of the cost. So you're saying this is a real 00:12:24.169 --> 00:12:26.809 bona fide game changer for deeply understanding 00:12:26.809 --> 00:12:29.529 your customers and their needs. Yes, absolutely. 00:12:29.929 --> 00:12:32.909 It provides genuinely actionable, deeply insightful 00:12:32.909 --> 00:12:34.950 customer profiles that are ready for immediate 00:12:34.950 --> 00:12:37.450 use. All right. For our final test, we focused 00:12:37.450 --> 00:12:40.870 on growth. We asked Genspark to identify comprehensive 00:12:40.870 --> 00:12:43.230 distribution channels and partnership opportunities 00:12:43.230 --> 00:12:45.250 to effectively reach those sales leaders we just 00:12:45.250 --> 00:12:48.210 defined. Right. How do you actually get your 00:12:48.210 --> 00:12:50.230 product in front of the right people? Who should 00:12:50.230 --> 00:12:52.129 you collaborate with? Exactly. And how did it 00:12:52.129 --> 00:12:54.690 do there? It delivered a remarkably thorough 00:12:54.690 --> 00:12:57.990 analysis, identified high -impact channels moved 00:12:57.990 --> 00:13:01.149 beyond the obvious stuff, pinpointed specific 00:13:01.149 --> 00:13:03.690 strategies like content -led growth, suggesting 00:13:03.690 --> 00:13:06.269 precise content types like analytical reports, 00:13:06.809 --> 00:13:09.009 even recommending long -tail keyword strategies 00:13:09.009 --> 00:13:12.370 for SEO, stuff often overlooked by general AI. 00:13:12.649 --> 00:13:14.870 It wasn't just generic advice. It felt like a 00:13:14.870 --> 00:13:17.909 targeted roadmap. It also suggested specific 00:13:17.909 --> 00:13:20.649 platform integrations with widely used sales 00:13:20.649 --> 00:13:24.529 tools like Slack and Salesforce, and even marketplace 00:13:24.529 --> 00:13:27.649 listings on AppExchange. Ah, the Salesforce marketplace. 00:13:27.769 --> 00:13:30.149 That's smart. Right. That's particularly insightful 00:13:30.149 --> 00:13:32.669 because it's a direct channel to Salesforce's 00:13:32.669 --> 00:13:36.110 massive enterprise user base, something a generic 00:13:36.110 --> 00:13:39.129 AI might completely miss. And for each suggested 00:13:39.129 --> 00:13:41.789 channel, Gainsbourg provided estimates, right? 00:13:41.850 --> 00:13:44.889 For effort required, time to results, potential 00:13:44.889 --> 00:13:47.929 costs. Yep, all laid out. That's incredibly helpful 00:13:47.929 --> 00:13:50.009 for prioritizing your go -to -market strategy. 00:13:50.409 --> 00:13:52.789 Gives you a practical roadmap for allocating 00:13:52.789 --> 00:13:56.529 resources. So, in essence, it acts like a strategic 00:13:56.529 --> 00:13:59.470 consultant in a box, specifically for identifying 00:13:59.470 --> 00:14:01.870 growth and distribution strategies. Exactly. 00:14:02.210 --> 00:14:05.049 It offers comprehensive, actionable strategic 00:14:05.049 --> 00:14:07.889 channel analysis, complete with estimated resource 00:14:07.889 --> 00:14:10.659 requirements. Very useful framework. Now, let's 00:14:10.659 --> 00:14:14.019 talk pricing and something else. Ginsburg positions 00:14:14.019 --> 00:14:16.759 itself as highly affordable at $25 per month. 00:14:17.080 --> 00:14:19.399 Seems reasonable. On the surface, yeah. But we 00:14:19.399 --> 00:14:21.379 uncovered a serious issue with its cancellation 00:14:21.379 --> 00:14:23.820 policy, something you absolutely need to be aware 00:14:23.820 --> 00:14:26.200 of before subscribing. Yeah, this was not great. 00:14:26.299 --> 00:14:28.679 This isn't just a minor annoyance. It really 00:14:28.679 --> 00:14:31.440 touches on a fundamental aspect of trust. We 00:14:31.440 --> 00:14:33.419 actively try to cancel a subscription. Search 00:14:33.419 --> 00:14:35.639 diligently for a self -service option. Anyone 00:14:35.639 --> 00:14:38.440 on the website, click here to cancel. Nope. Couldn't 00:14:38.440 --> 00:14:40.340 find it. Couldn't find one. To double check, 00:14:40.519 --> 00:14:42.519 we even asked Gensbruck itself through its chat 00:14:42.519 --> 00:14:45.080 interface how to cancel. It couldn't find a self 00:14:45.080 --> 00:14:47.259 -service option either. It just provided generic 00:14:47.259 --> 00:14:51.120 email or phone support contact info. See, that 00:14:51.120 --> 00:14:55.019 is a major undeniable red flag for trust. Shopify 00:14:55.019 --> 00:14:58.120 founder Toby Litke's concept of the trust battery 00:14:58.120 --> 00:15:01.039 comes to mind here. Every positive interaction 00:15:01.039 --> 00:15:03.759 charges that battery. Every negative one drains 00:15:03.759 --> 00:15:06.480 it. This kind of forced friction around cancellation, 00:15:06.940 --> 00:15:09.200 it immediately depletes that trust. Absolutely. 00:15:09.299 --> 00:15:11.120 Especially when you're dealing with a tool handling 00:15:11.120 --> 00:15:13.940 business data, strategic plans. Trust is paramount. 00:15:13.980 --> 00:15:16.259 It's a deal breaker for many, regardless of how 00:15:16.259 --> 00:15:18.500 good the tech is. So despite all its impressive 00:15:18.500 --> 00:15:20.860 functional strengths, there is significant kind 00:15:20.860 --> 00:15:23.480 of user hostile trust issue when it comes to 00:15:23.480 --> 00:15:25.860 canceling your subscription, correct? Yes. The 00:15:25.860 --> 00:15:29.600 lack of easy, transparent cancellation is a significant 00:15:29.600 --> 00:15:32.879 and worrying concern that really undermines user 00:15:32.879 --> 00:15:35.519 confidence. OK, let's zoom out a bit. How does 00:15:35.519 --> 00:15:38.039 Genspark truly stack up against the other major 00:15:38.039 --> 00:15:41.190 AI players in the ecosystem? Where does it fit 00:15:41.190 --> 00:15:43.950 into this broader AI landscape we're all navigating? 00:15:44.750 --> 00:15:47.629 Right. Well, Genspark's distinct advantage over 00:15:47.629 --> 00:15:51.029 a more general AI like ChatGPT is definitely 00:15:51.029 --> 00:15:54.090 its sharp business focus. Its ability to conduct 00:15:54.090 --> 00:15:56.850 deep research seems better, and it has those 00:15:56.850 --> 00:15:59.470 integrated built -in tools for business tasks. 00:15:59.870 --> 00:16:03.090 But ChatGPT? Chat GPT still offers a better general 00:16:03.090 --> 00:16:05.809 conversation experience and honestly a much cleaner, 00:16:06.009 --> 00:16:08.529 more intuitive user interface. It's just built 00:16:08.529 --> 00:16:10.889 for broad interaction. Okay, what about compared 00:16:10.889 --> 00:16:14.789 to Claude? Another powerful model. Ginsburg clearly 00:16:14.789 --> 00:16:17.629 shines with its very specific business tools 00:16:17.629 --> 00:16:19.730 like that integrated slide creation feature, 00:16:19.769 --> 00:16:21.789 which is pretty neat. But Claude? Claude, on 00:16:21.789 --> 00:16:24.009 the other hand, often provides better reasoning, 00:16:24.029 --> 00:16:26.690 I think. More nuanced, thoughtful responses, 00:16:26.909 --> 00:16:28.710 especially when you're tackling really complex 00:16:28.710 --> 00:16:31.600 text analysis tasks. and against perplexity, 00:16:31.720 --> 00:16:33.919 which is really strong as an AI -powered research 00:16:33.919 --> 00:16:37.139 engine. Genspark truly stands out with its integrated 00:16:37.139 --> 00:16:39.279 creation tools. You can build actual deliverables 00:16:39.279 --> 00:16:41.519 right there in the platform. Whereas perplexity? 00:16:41.840 --> 00:16:44.299 Perplexity has superior search integration, I'd 00:16:44.299 --> 00:16:46.580 say, and a much clearer, more transparent way 00:16:46.580 --> 00:16:48.659 of presenting information, showing its sources, 00:16:49.320 --> 00:16:51.320 especially if you're primarily just looking for 00:16:51.320 --> 00:16:53.159 answers and sources. So what we're seeing is 00:16:53.159 --> 00:16:55.720 that Genspark isn't trying to be a general purpose 00:16:55.720 --> 00:16:59.429 AI, like a chat GPT or... Claude. It's carved 00:16:59.429 --> 00:17:01.929 out a very specialized niche in the business 00:17:01.929 --> 00:17:04.269 world, correct? Correct. It's a specialized tool 00:17:04.269 --> 00:17:06.549 specifically designed to address business challenges 00:17:06.549 --> 00:17:09.190 rather than general queries or broad creative 00:17:09.190 --> 00:17:12.470 tasks. It knows its lane, sponsor. So pulling 00:17:12.470 --> 00:17:15.250 all of these threads together, what does this 00:17:15.250 --> 00:17:18.369 deep dive into GenSpark ultimately tell us? What's 00:17:18.369 --> 00:17:21.500 the big picture? It represents, I think, A compelling 00:17:21.500 --> 00:17:24.859 new wave of specialized AI tools, purpose -built 00:17:24.859 --> 00:17:27.839 for specific business functions. While it clearly 00:17:27.839 --> 00:17:30.019 has limitations, especially in visual design, 00:17:30.380 --> 00:17:32.880 those awkward text and image errors and that 00:17:32.880 --> 00:17:35.500 frustrating, almost predatory cancellation policy. 00:17:35.839 --> 00:17:38.440 Its core research and strategic planning capabilities 00:17:38.440 --> 00:17:41.869 show genuine promise. It truly shines, without 00:17:41.869 --> 00:17:44.650 a doubt, in areas like customer persona development. 00:17:45.150 --> 00:17:47.650 That provides incredibly actionable insights 00:17:47.650 --> 00:17:50.069 that can directly impact your marketing and product 00:17:50.069 --> 00:17:53.390 strategy. And it's surprising ability to build 00:17:53.390 --> 00:17:55.869 functional web applications quickly, even when 00:17:55.869 --> 00:17:58.829 it completely misunderstands the prompt. That's 00:17:58.829 --> 00:18:02.009 a fascinating and powerful capability. Unexpected, 00:18:02.390 --> 00:18:05.750 but powerful. So should you add GenSpark to your 00:18:05.750 --> 00:18:09.809 AI toolkit? Yeah. Big question. Well, if you're 00:18:09.809 --> 00:18:11.450 a founder or a business professional who's willing 00:18:11.450 --> 00:18:14.390 to work through its design limitations, understands 00:18:14.390 --> 00:18:16.690 its potential for contextual misunderstandings, 00:18:16.970 --> 00:18:19.230 that prompt drift we talked about, and you see 00:18:19.230 --> 00:18:22.140 the value in its strength. It offers unique value 00:18:22.140 --> 00:18:24.680 in areas like market research, deep customer 00:18:24.680 --> 00:18:26.819 understanding, strategic planning, and maybe 00:18:26.819 --> 00:18:29.099 even rapid prototyping. Think of it as a powerful, 00:18:29.559 --> 00:18:31.920 hyper -efficient first draft generator. But you 00:18:31.920 --> 00:18:34.380 should absolutely skip it for design -heavy projects, 00:18:34.519 --> 00:18:36.480 especially anything that involves complex text 00:18:36.480 --> 00:18:38.859 and graphics. Just don't go there. And if you're 00:18:38.859 --> 00:18:41.180 uncomfortable with a tool that has significant 00:18:41.180 --> 00:18:43.319 trust issues around its cancellation policy, 00:18:43.720 --> 00:18:46.440 it's probably a hard pass. Good point. It's also 00:18:46.440 --> 00:18:49.799 probably overkill for simple queries. You could 00:18:49.799 --> 00:18:52.980 just ask a more general AI like ChatGPT or Claude. 00:18:53.140 --> 00:18:56.039 Use the right tool for the job. The AI landscape 00:18:56.039 --> 00:18:59.099 continues to evolve at breakneck speed. It's 00:18:59.099 --> 00:19:01.680 pushing the boundaries of what's possible with 00:19:01.680 --> 00:19:04.559 these increasingly specialized tools. It's a 00:19:04.559 --> 00:19:07.880 dynamic, exciting, and sometimes, frankly, bewildering 00:19:07.880 --> 00:19:11.480 space. Tools like Gansburg, for all their imperfections, 00:19:11.559 --> 00:19:14.180 represent a crucial, important step toward more 00:19:14.180 --> 00:19:16.759 specialized, business -focused AI applications. 00:19:17.279 --> 00:19:18.920 They're definitely something worth paying attention 00:19:18.920 --> 00:19:21.519 to as the ecosystem matures, even with the flaws. 00:19:21.940 --> 00:19:24.460 The future, it seems, belongs to those who can 00:19:24.460 --> 00:19:27.160 navigate this complex landscape, understanding 00:19:27.160 --> 00:19:30.039 each tool's specific strengths, knowing its inherent 00:19:30.039 --> 00:19:32.480 limitations, and effectively integrating them 00:19:32.480 --> 00:19:35.279 into their workflow. Gansburg might just be one 00:19:35.279 --> 00:19:37.200 intriguing piece of that intricate, evolving 00:19:37.200 --> 00:19:39.259 puzzle for you. Thanks for joining us for this 00:19:39.259 --> 00:19:41.619 deep dive into Genspark. We'll see you next time. 00:19:41.900 --> 00:19:42.660 Out Hero Music.