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
- 0:00:17
Customer Acquisition Through a Scan Funnel
An explanation of a pre-launch scan funnel that gives merchants a store analysis and PDF report, then invites interested users to join the launch cohort or reserve a place. The funnel is framed as the website’s main conversion mechanism, with interface design and backend implementation treated as separate stages.
- 0:01:36
Treating the Website as an Evolvable Conversion Tool
A review of the landing page’s first phase and mobile version, paired with the view that the site should keep evolving through experiments, additional pages, and conversion optimization, with the pricing page expected to become a key page.
- 0:06:44
Balancing Scan Value Against Delivery Cost
An unresolved discussion of the scan report’s economics: producing a deep analysis through AI services has a cost, so options included offering it free to build trust, showing a teaser before selling the full report, or pairing it with a personal analysis service. No model was finalized, and the per-scan cost still needed measurement.
- 0:09:46
Prototyping the Funnel in a Sandbox Before Integration
A workflow that starts by building the scan-funnel design in a sandbox, reviewing it, then transferring it into the real funnel and testing it once the design is settled.
- 0:10:35
Question About Stripe Availability in Egypt
The speaker raises an unresolved question about using Stripe from Egypt and whether accessing its website may require a VPN; the segment does not provide a confirmed answer.
- 0:11:24
Qualifying Shopify Merchants Before a Free Scan
The discussion frames a high-value scan that requires a unique Shopify store URL and business email, limiting the funnel to target merchants. It also stresses measuring per-scan cost and later conversion into an app install or primary action, while acknowledging that actual costs and conversion rates are still unknown.
- 0:11:24
A Live Scan Experience with Email Results as a Fallback
The proposed scan page uses a live, dynamic experience to keep the user there until results appear. If they leave, the scan results and a PDF report are emailed as a fallback, while the intended primary action remains on the page rather than in the email.
- 0:15:38
Refining the Logo and Scan Progress Indicator
The UI feedback asks for the logo to remain static inside the Burnish Signal box while retaining the existing mouse-related effect, and for a white line to connect stages one and two as the scan progresses.
- 0:17:14
The Core Funnel from Store Details to Scan
The website is described as a simple funnel whose primary goal is to have a merchant submit a Shopify store URL and business email, then move to a page that performs the scan. Completing this flow is treated as the foundation for the rest of the funnel.
- 0:18:40
Email Verification and Cleaning in the Go-to-Market Plan
The discussion mentions including an email verification and cleaning service in the go-to-market plan, but the provider’s name is unclear in the captions and is therefore left unidentified.
- 0:19:24
Finishing the Website and Funnel Before Expanding Execution
The speaker presents the practical view that go-to-market work and broader project execution depend first on a completed website and funnel, so establishing that foundation was prioritized despite slower development.
- 0:20:20
Refining the Progress Indicator and Page Logo
Instructions to hide the progress line until the next step is completed, stop it at step six, and slightly reduce the logo while preserving its position and effect.
- 0:20:59
Differentiating a Store Scan with a Detailed Report
A critical comparison between a competitor’s temporary, high-level scan result and the proposed scan, which is intended to inspect a merchant’s products individually, identify issues, and assign visibility scores. The speaker frames the deeper scan as an acquisition hook despite its expected cost.
- 0:23:30
Why the Frontend Design Took Longer
A discussion explaining that the business purpose and acquisition path were understood, but uncertainty about the final visual direction and numerous small design decisions slowed the frontend work, especially given stronger backend than frontend experience.
- 0:25:18
Responsive Testing and Mobile Video Investigation
A review of Codex’s device and viewport tooling, paired with a practical decision to prioritize mobile and standard desktop rather than tune every dimension individually. After noting an earlier mobile fix, the speaker asks for investigation into a hero-section video that is not working on mobile; this page does not record the outcome.
- 0:28:42
Planning Scan Limits and Abuse Prevention
An audience question proposes limiting free scans by IP address or domain fingerprint while noting that some controls could be bypassed with a VPN. The speaker says the scan cost must first be established and that abuse prevention is already planned but is not IP-based; the alternative is not fully explained on this page.
- 0:30:20
Reducing scan abuse with a Shopify store URL
The speaker discusses requiring a Shopify store URL to start a scan, treating it as an identifier outsiders are unlikely to know and therefore viewing the abuse risk as limited. A fallback strategy is mentioned that does not rely on IP addresses, with an explicit qualification that the protection is not highly sophisticated.
- 0:31:43
Reviewing banner and hero-section design
The review asks for alternative design directions for a section that looks visually unsatisfactory, with the improvements applied to other banners using the same video asset and checks across the hero section and additional pages for consistency.
- 0:34:26
Designing a waiting state that keeps users in the scan funnel
The speaker describes the next section as a teaser-like state shown while the scan completes, intended to encourage the merchant to remain in the flow. If they leave, an automated email can deliver the PDF report; staying allows the funnel to continue to its next action. The discussion also raises whether the experience can move faster.
- 0:37:56
Clarifying score meaning and calculation
While reviewing the interface, the speaker feels the section is not working visually but first asks what the scores represent, why the displayed maximum is used, and what the values add up to. This points to a need to explain the scoring model before judging its presentation.
Got a question about something in this stream?
Ask in the group