Website Scan Funnel Completion
Want to back the stream? The «داعم» membership on YouTube is EGP 60 a month: badges, emoji, and I answer your questions first on stream. Become a supporter
The gist
The stream centers on preparing a Shopify app’s website and conversion journey before launch: clarifying the product message, standardizing page templates, prioritizing mobile usability, and designing a funnel that moves from a free scan through email nurturing to installation before paid advertising begins. Practical work covers design, navigation, and dashboard reviews, alongside repeated advice to ship without excessive polish, test whether the website explains itself, and evaluate pricing, acquisition costs, and unit economics. Audience discussions also address learning marketing, researching business ideas, building software with AI, and choosing tools and architecture according to the application. The stream explores agent workflows, code review, and coordination across sessions, as well as an unfinished investigation into Supabase connection limits; after the initial diagnosis was challenged, a Railway web-and-worker deployment issue appeared more plausible, but the precise mechanism remained unresolved. The speaker also offers attributed forecasts about AEO/GEO growth and expanding agent roles in marketing and software, presenting them as opinions rather than proven results. Ad creatives, mobile dashboard adaptation, and parts of the funnel were still works in progress.
129 moments from the stream
- 0:03:15
Daily Planning Without Overthinking
In response to an audience question, the speaker suggests setting a specific goal and agenda each day, recording unfinished tasks to improve later estimates, and reviewing whether a plan was too ambitious or too light when it goes off track. His practical conclusion is to return to execution rather than overthink the plan.
- 0:05:04
Moving from Website Building to Marketing
The speaker explains that he wants to finish the website’s essential refinements—especially mobile optimization—before concentrating on marketing and the landing page. He also plans to organize the branches of the marketing strategy into a visual chart, while avoiding extra polish that is not essential.
- 0:07:10
Product Website Goals and the Free-Audit Funnel
The speaker argues that a product website should establish brand identity, explain the product, its market, and pricing, and ultimately lead visitors toward installation. Because some visitors will not be ready to install immediately, he proposes a landing page offering a free audit in exchange for store information and an email address, giving them a tangible result before they enter a follow-up nurturing funnel.
- 0:10:33
Building a Post-Scan Email Funnel
He outlines a five-email funnel that begins with delivering the scan report and explaining the result, then moves into later offers and installation calls to action. The goal is to nurture leads and make better use of paid traffic instead of losing visitors after the first click.
- 0:11:41
Preparing the Website, Mobile Experience, and Landing Page for Launch
He reviews progress on the website interface, including cleaner structure, spacing, and dashboards, while treating the mobile experience and landing page as necessary work before launch.
- 0:13:40
Preparing the Funnel Before Ad Spend and Automating Marketing
Answering an audience question, he says paid advertising should follow a well-prepared funnel and describes a future marketing agent that could continuously support ads and organic posting. He qualifies that the organic component is unfinished and the automation remains a future goal.
- 0:16:04
Ship First, Then Polish the Small Details
He relays and agrees with a group member’s observation that project owners can spend too long polishing small website or app details instead of publishing, and that they can launch first and refine nonessential details later.
- 0:17:12
Using AI to Reproduce a Reference Site’s Structure, Then Rebrand It
Answering a design-tools question, he mentions Impeccable and describes his own method: asking an AI tool to reproduce the codebase and effects of a reference site he likes, despite possible copyright-related refusals, then applying his branding and changing some elements. He presents it as a method that worked for him rather than the only approach and says people with a strong original vision can design from scratch.
- 0:19:23
Connecting Claude to an Ad Platform via MCP for Performance Analysis
He discusses connecting Claude to advertising-platform data through MCP so a user can ask natural-language questions about performance metrics and why they changed. He presents it as a way to simplify analysis, not as a proven replacement for marketing expertise.
- 0:21:38
Using Multiple Website References Without Copying the Design
The speaker describes building a site section by section from ideas found on reference websites, while changing the design, grid, and colors and improving the result. The review also covers enlarging a button, reducing motion that distracts from the primary action, trimming excessive text, and keeping interface effects consistent across pages.
- 0:26:19
When to Learn Marketing Yourself or Hire a Specialist
Answering an audience question, the speaker ties the decision to available time and resources: hire experienced help when time is limited, or learn marketing hands-on when time is available. In his view, understanding metrics and their purpose is essential, and AI can assist learning; he cites his own practical Google Ads experience from 2016 without presenting it as a universal rule.
- 0:29:25
A Website Funnel for Different Levels of Visitor Intent
The speaker discusses designing the page for two visitor types: someone who already knows what they want and goes straight to the CTA, and someone who first needs to understand the service. He also focuses on a funnel for visitors who understand the product but are not yet ready to install, providing an appropriate extra nudge toward a decision.
- 0:30:39
Prioritizing Mobile Optimization in a Website Review
The speaker explains that judging the desktop experience from a phone screenshot would be inaccurate because the mobile version is unfinished. Although he starts with desktop to establish a foundation, he considers mobile the higher priority. He also discusses browsers forcing dark mode onto sites not designed for it, while deferring secondary polish until the core work is complete.
- 0:37:52
Adapting Dashboards for Mobile with a Coding Agent
The speaker distinguishes relatively straightforward mobile adaptation of shared site elements—such as the header, footer, layout, and blocks—from the harder task of redesigning every dashboard. He proposes first having a coding agent study the mobile version and a React-based design system to adapt the dashboards, then falling back to manual instructions if that attempt is insufficient.
- 0:41:43
Planning the Website’s Mobile Optimization
Work began on improving the website’s mobile experience, starting with a review of open branches and active work. The discussion considered inspecting and capturing the mobile layout in Shopify, with the view that the agent might handle this without the full manual setup.
- 0:43:58
Reviewing Table Design and Messaging Accuracy
The review found that both the table’s design and content needed careful reworking. The key messaging challenge was to describe Burnish accurately: it is not an SEO tool, although it may help SEO to a limited extent, so the table should not imply more than that.
- 0:47:49
Complexity Across Multiple Servers and Worktrees
The practical work highlighted that switching among multiple servers and worktrees can make changes difficult to track, a workflow concern during website development.
- 0:48:57
Confusion About Fast Mode Availability in Claude
The speaker expressed confusion about Fast Mode being turned off and why it was unavailable to him; the issue was not resolved on this page.
- 1:01:20
Reusing Templates for Similar Pages
An audience member suggested creating templates for pages and elements with similar designs to reduce repeated work. The speaker said he already uses template families that retain the same structure while changing each page’s context and content, and that this has saved time.
- 1:02:28
Prioritizing Desktop and Mobile Work
The speaker and an audience member discussed how to sequence interface work: completing shared changes first can resolve issues across several pages, but the speaker emphasized that mobile should take priority when a tradeoff is unavoidable, even if the desktop version must concede something.
Got a question about something in this stream?
Ask in the group