Scan Funnel Implementation
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
This portion centers on developing Burnish and an evolving proposed acquisition funnel for Shopify merchants. Some variants begin with only a store URL, while others also request a business email, then present a scan or audit report that may assess visibility in AI answers and identify product-data gaps before inviting a later action. The report’s scope, free depth and pricing, scan-engine integration, accuracy and cost, the mechanism for conversion into an install or subscription, and abuse controls all remained in development; the records do not establish completion. Practical work covered waiting and progress states, report depth, calls to action, mobile presentation, simplifying scan setup, and automating product and competitor selection, alongside investigation of UI, engine, worker, and deployment failures without a documented final resolution. Luqman argued that the product should deliver observable value, turn visibility measurement into useful recommendations, educate merchants, and avoid guaranteeing SEO or GEO outcomes, while organizing the roadmap, reducing context switching, and using parallel work where tasks are not tightly dependent. This overview prioritizes the central Burnish and funnel work, but the indexed pages also contain separate discussions of brand and domain naming, the unresolved availability of Stripe in Egypt, Perplexity MCP setup and Hermes evaluation, AI-assistant behavior, a second-hand and unverified claim about Shopify pre-submission checks, projects slowing near completion, and audience questions about starting within Shopify, patience with organic visibility, and web-design learning resources.
81 moments from the stream
- 1:45:22
Using a Free Audit for Pre-Launch Customer Acquisition
A pre-launch acquisition strategy is proposed: offer a useful audit at no charge to demonstrate value and earn prospective customers’ trust, instead of waiting until launch to begin marketing.
- 1:46:51
Showing Scan Progress on Desktop and Mobile
A clear green progress bar is proposed, visually related to the numbered step indicator, beneath the store card on desktop with an appropriate mobile treatment.
- 1:47:46
Strong Product Value Makes Marketing Easier
The speaker argues that software builders can create products that solve real problems, but entering a competitive market remains difficult. In his view, marketing becomes easier when a product delivers clear value and has genuine demand.
- 1:52:04
Reviewing Two Milestones Before Auditing
A request to review two milestones involving merchant admin surfaces and web components, identify remaining work, and prepare for dedicated audits. Some technical wording in the captions is unclear.
- 1:54:11
An Opinion on AI Tools Understanding Design Taste
The speaker says Claude seems to learn his design preferences better after several iterations, while explicitly noting that GPT is not bad, using a scan progress bar request as an example of inferred style.
- 1:54:51
Checking Mobile Performance and Responsive UI Defects
A discussion of perceived mobile heaviness and broken responsive components. The speaker says the speed report looked acceptable before optimization, though video and WebGL could affect it, while stressing that metrics vary by network and geography and should be supplemented with real-phone testing. A prior horizontal-swipe overflow defect is also described.
- 1:57:26
Repositioning the Mobile Scan Progress Bar
A proposed mobile change moves the scan progress bar near the top instead of leaving it hidden below, keeping progress visible while the report is generated within the limited viewport. The idea includes placing it beneath the signal card, centering the scan title, and reducing its size if needed.
- 2:04:04
Using a Shopify Store Scan as a Merchant Acquisition Funnel
The speaker outlined a website funnel where a merchant submits a business email and Shopify store URL for a scan, receives a polished teaser, and can later receive a deeper audit report and follow-up. The initial offer and its pricing were still under consideration, while the product vision included a command-center-style dashboard and an early focus on a strong website and marketing.
- 2:11:52
Why SEO Requires More Patience Than Paid Ads
The discussion considered SEO and GEO adoption and business owners’ awareness of them. In the speaker’s view, many merchants prefer social ads because traffic and feedback arrive faster, whereas organic visibility requires patience and a longer-term plan—a challenge he believed was not limited to Arab markets.
- 2:16:35
Opening Shopify Inside the Working Interface
During the practical work, the speaker noticed that Shopify could be opened from within the interface and said this would simplify the workflow. The application was open, while the Command Center section had not yet been implemented.
- 2:18:26
Educating Merchants Without Guaranteeing SEO Outcomes
The speaker argued that selling SEO and GEO services requires merchant education, a clear explanation of how the work operates, and potentially a presentation. He cautioned that specific score improvements or returns cannot be guaranteed because marketing outcomes are inherently uncertain, making expectation management central to the product offering.
- 2:21:27
Resources for Learning Web Design and UI/UX
A viewer asked which websites could help with learning web design, web development, and UI/UX. The brief response pointed to a design tool and suggested seeking further recommendations from the Telegram community, but the other resource names are unclear in the captions.
- 2:28:27
Evaluating a Project Name and Checking Domain Availability
The speaker evaluates a proposed name as expressive of its field and recommends first checking domain availability and deciding how it will be spelled in English, since many domains are already taken.
- 2:30:27
Reviewing the Product-Scan Setup Steps
The review questions two unclear setup steps: the purpose of the consent step needs explanation, while asking the user to choose a product to scan appears redundant if the system can already access the products and scan a selection automatically.
- 2:33:06
Automating Competitor and Product Selection
The discussion proposes that Burnish automatically identify competitors, leading products, and their categories, while allowing later fine-tuning in settings, followed by updating the milestone and defining the next verification step.
- 2:35:52
Broken Continuation UI After Response Handling
During continuation-flow inspection, clicking Continue led to a response-handling state followed by a missing menu and blank page; after refresh, the interface still appeared broken and required investigation.
- 2:40:15
Choosing Burnish Amid Naming Availability Constraints
The discussion describes the difficulty of finding an available English name and says Burnish was chosen for its polishing meaning and closeness to the intended idea after considering many alternatives.
- 2:42:20
Verifying Report States and Activation Flow
The full-page experience was reviewed for strong-score, weak-score, and engine-failure states, followed by inspection of the screen reached after charge approval and comparison with the code, activation status, and onboarding continuation. The backend portion appeared aligned, while interface and flow questions remained under review.
- 2:47:07
Exposing Audit-Report Depth in the UI
The discussion examines what the in-depth report should provide, including named analysis of several products and their gaps, and asks for the maximum depth currently available. The stated view is that the backend produces a deeper report than the interface displays, so the UI should expose the full value rather than compressing it for presentation.
- 2:51:39
Showing Backend Capabilities and Fixing the Reservation Banner
An implementation review asks for the interface to reflect the full depth of supported backend capabilities and for the reservation banner to float at the bottom. The banner’s exact label is unclear in the captions.
Got a question about something in this stream?
Ask in the group