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
- 3:00:56
Clarifying the Testing Problem for an Automatic Video-Cutting Plugin
A participant raised the difficulty of adequately testing a Premiere plugin that automatically cuts videos before releasing it to production. The speaker restated the idea without assuming a solution and asked for clarification about the exact testing problem.
- 3:05:01
A Qualified View of OpenRouter
The speaker describes OpenRouter as a good option but says its suitability depends on the intended purpose, adding that it is reasonable for personal use.
- 3:06:12
Testing Environment Differences and Monitoring Errors with Sentry
The speaker discusses how an app or plugin may work for its developer yet fail for customers because their plugins and environments differ, suggesting that an AI tool can help enumerate likely scenarios and variables. He then recommends connecting Sentry to alerts such as Slack, with the option of passing an alert to Claude to propose a fix or open a GitHub pull request. He warns that fully automated fixing is risky and favors reviewing issues one by one.
- 3:09:51
Qualified Expectations for Gemini and Claude
Responding to a question about a future Gemini release, the speaker offers a personal expectation that it could surpass an older Claude release while remaining behind the newer release he mentions, and says lower cost could make it a practical alternative. These are attributed expectations, not results of a documented test on the page.
- 3:12:47
Desktop or Laptop for Long Work Sessions?
While acknowledging limited hardware expertise, the speaker favors a Mac mini or Mac Studio with a large display for prolonged primary work, while viewing a laptop as more suitable for frequent travel or working away from a desk. This is presented as personal preference and experience, not a comprehensive technical comparison.
- 3:15:33
Testing the Clarity of an AEO Services Website
A request to review the desktop version of a work-in-progress website and assess whether it explains the AEO field simply enough for visitors, treating confusion as a sign that the message needs improvement. The work also included requesting a dark background for the AI-engines section, while noting that the mobile experience still needed development.
- 3:27:38
Refining the Fullscreen Interface Header
Practical feedback to reduce the header font size so it does not touch the vertical lines, along with a request to remove the “what they currently say” section.
- 3:29:00
An Opinion on SaaS and Software Engineering in the AI Era
The speaker rejects the claim that SaaS is ending, arguing instead that AI is changing how software gets built and reducing some traditional engineering roles rather than eliminating the need for software products. He advises evaluating sources with attention to bias and argues that developers who combine programming knowledge with openness to agents and AI-assisted coding have a strong advantage. Speaking in 2026, he also makes a bold personal prediction that the debate will largely fade by 2027; this is presented as an opinion and forecast, not an established result.
- 3:36:04
A Secondhand Impression of Replit
Asked about Replit, he said he had not tried it himself but had heard positive things, making this a secondhand impression rather than hands-on experience.
- 3:36:44
Building Software Through Business Expertise Without a Coding Background
He explained how market knowledge and business experience helped him turn application ideas into products despite having no programming background. The difficult process taught him many software-engineering concepts, while he acknowledged that an experienced developer could build the same work faster and better.
- 3:41:18
Explaining Interface Changes with a Screenshot and Sketch
While revising a hero section, he described the placement of logos and vertical lines, then used a screenshot and sketch to clarify the intended layout. He requested an English restatement of the requirements and later said he had merged the change.
- 3:43:21
Balancing Premium Pricing with Customer-Acquisition Risk
He discussed positioning a Shopify application as a premium offering because the intended service carries meaningful value and cost. At the same time, he said market acceptance of the price, ad-creative performance, and customer-acquisition cost remained unresolved factors to test.
- 3:48:56
Choosing a Framework and Backend for the Application
He explains that recommending a framework or backend service without understanding the application may produce a poor fit. He suggests first documenting a clear manifesto and roadmap, then using an AI assistant to compare options against the app’s content and requirements.
- 3:52:26
From Gross Margin to Net Profit
A conceptual discussion of moving from gross margin to estimated net profit by accounting for operating expenses, fees, and marketing. The speaker notes that marketing may dominate early costs and that stronger organic sales could improve margins later, while stressing that the estimate remains incomplete.
- 3:57:40
Planning Burnish’s Catalog and Revenue Dashboard Sections
A review of making Burnish’s catalog-article and revenue dashboard sections more dynamic, including adding first-party pixel data and a graph from the homepage to the revenue area, with an emphasis on careful planning and prioritization.
- 3:59:36
Fixed and Variable Costs in Pricing Decisions
A general discussion of balancing price against cost, distinguishing fixed from variable costs, and how variable costs grow with users and may require service trade-offs to reduce. It also notes that uncertain marketing costs make net-profit estimates harder.
- 4:01:57
Refining the Hero Section’s Visual Motion
Design notes to remove vertical lines behind the header and reorganize the dots so they begin at the top center and travel toward both sides as part of refining the hero interface.
- 4:04:18
Improving Claude’s Output with Clear Standards and Skills
A discussion of why asking Claude to improve a design using subjective labels such as “bad” is insufficient without defined quality criteria. The proposed approach is to provide clearer standards and tests through skills, including responsive behavior, while leaving comparisons among several skills and their updates unresolved.
- 4:08:43
Installing a Design Skill and Distinguishing It from Impeccable
The speaker asked to install a new skill in the repository, clearly distinguish its invocation from Impeccable, and then test it. After trying it, he felt it could better communicate why certain visual choices were unsuitable, while reviewing issues such as lines appearing behind the header.
- 4:14:59
Sequencing the Remaining Website Funnel Work
The speaker broadly outlined the remaining work: finish parts of the website and funnel, prioritizing the website scan, then address email sequences, advertising creatives, and application polish before publishing. He presented this as a changeable estimate and work plan, not a confirmed launch date.
Got a question about something in this stream?
Ask in the group