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:40:02
Friction in the branching and deployment workflow
The speaker mentions recurring difficulties involving branches, deployment activity, and Cloudflare. The final technical details are unclear in the captions, so the precise cause and resolution cannot be established.
- 0:40:57
A Shopify Audit Funnel Designed to Drive App Installs
The discussion outlines an acquisition funnel that accepts only a Shopify store URL, helping qualify the intended audience and deliver a detailed audit and useful information before inviting the merchant to install the app. The multi-step interface is still a design sandbox that needs refinement and testing.
- 0:45:33
An Unverified Claim About Pre-Submission Shopify App Checks
The speaker relayed another developer’s claim that Shopify may offer an AI-assisted check to validate an app before submission, potentially reducing review delays. He explicitly treated the report as second-hand and hoped it was accurate, so it remains unverified.
- 0:46:51
Cloudflare Deployment and Branch Workflow Problems
While preparing a build for mobile preview, the speaker encountered Cloudflare deployment issues and uncertainty around branches, pushes, and commits; a previous attempt was said to have broken the site and been difficult to recover from. Automatic deployment was considered, but the issue was deferred to avoid spending more time, and no definitive solution is captured here.
- 0:52:20
Why Start Inside Shopify Before Building an Independent Platform?
In response to an audience question, the speaker argued that immediately building an independent platform would require substantial work and resources while exposing the product to broader competition. His strategy is to start within Shopify as a narrower setting in which to prove the product’s value, with a possible independent platform considered only after that foothold succeeds.
- 0:55:36
Merchant Retention Requires Observable Product Value
The discussion stresses that admission to the Shopify app ecosystem is not enough: merchants will leave if they cannot observe useful results. When outcomes fall short, the product itself should be revisited and iteratively improved. It also distinguishes the free website assessment used to encourage installation from the app intended to operate inside Shopify initially.
- 1:00:27
Balancing Implementation Depth with Growth Priorities
The speaker reflects on why an entrepreneur cannot master every technical detail, arguing for moving through some implementation work quickly while anticipating marketing, traffic, and outreach challenges.
- 1:02:48
Designing a Useful Store-Scan Wait Experience
The scan flow uses a visual teaser for the analysis engines and withholds figures until all scan steps finish. Because the wait may feel long, the speaker considers progress states and small interactions that encourage users to remain for the full report, while noting that a clearer desired outcome makes UI decisions faster.
- 1:08:01
Improving the Scan Funnel Across Touchpoints
The speaker explains that the scan section lives in a relatively isolated environment, making later design changes less convenient than edits to ordinary site pages. Planned follow-up work includes refining mobile behavior, the report page, the PDF, the email, and the overall funnel design.
- 1:13:08
Auditing a Roadmap with Multiple Analysis Agents
The speaker requests a multi-agent review of the project manifesto and roadmap, including milestone status and a clear separation between work that directly affects the Shopify application and external work such as scanning and the website frontend.
- 1:14:53
Mobile-First Review Followed by Manual Refinement
Mobile is prioritized over desktop: an agent first reviews the layout and fixes visible fit issues, after which the speaker evaluates the result and makes further structural and content adjustments rather than relying on automatic responsive conversion alone.
- 1:15:57
Running Project Workstreams in Parallel
The speaker discusses using an organized roadmap to distinguish Shopify application work from external funnel work, then using agent wait time to advance backend tasks or other milestones in parallel instead of letting one section gate all progress.
- 1:22:52
Expanding the Full Report In-Page
The discussion asks how to keep users on the same page while a scan report is generated, then expand its deeper sections there instead of navigating elsewhere.
- 1:26:06
Making a Generating Score a Responsive Teaser
The generated score should be visually distinct from the final result across desktop and mobile. A literal blur treatment was later rejected in favor of exploring teaser-like directions, alongside fixing the mobile logo glyph’s rendering quality.
- 1:27:10
The Scan Report’s Role in Customer Acquisition
The site is described as guiding visitors toward a store scan and audit report. The speaker says the backend has already received work, while the current priority is polishing the report’s presentation so the experience can encourage subscriptions.
- 1:29:12
Organizing Product Milestones Beyond Channel Labels
Milestones were to be grouped into clear swimlanes and positioned by progress along a timeline without explicit dates. A simple platform-versus-off-platform split was judged too shallow, prompting a request for more meaningful domains.
- 1:35:22
Building Merchant Trust in Scan Reports
Drawing on his past experience as a Shopify merchant, the speaker says he personally viewed ‘scan my store’ and free-scan offers as gimmicks, which informs his effort to polish the current report experience.
- 1:36:56
Improving Tangible Value Before Returning to Market
One possible response to a broad competing tool is to go deeper on a single job. The broader lesson is that an app must deliver tangible merchant value; if it changes little in practice, step back, improve it, and return to the market iteratively.
- 1:40:42
How the Shopify Store Scan Works Behind the Scenes
An explanation of the proposed scan pipeline: smaller models gather information about products, metafields, titles, descriptions, tags, categories, blogs, and the store’s niche, then generate niche-specific prompts for several AI engines. The responses are checked for merchant visibility, and an audit identifies gaps in product information. The stated runtime varies with store size.
- 1:44:36
Limiting the Results Display to Three Rows
A practical design note asks to retain the row presentation while finding a way to display no more than three rows.
Got a question about something in this stream?
Ask in the group