ALMOST 70% BUILT
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 documents the practical development of Burnish, a product beginning on Shopify and exploring how stores can improve their visibility in AI answers and platforms through GEO. Much of the work centers on the website and product message: clarifying the problem, solution, and customer outcome; structuring the homepage and pricing page; routing “Scan My Store” calls to action consistently; and refining cards, contrast, mobile layouts, scroll interactions, and a floating 3D logo. Visual reviews repeatedly led to revisions or removal of immersive effects when they distracted from the product, alongside recognition that excessive polish could delay shipping. The pricing experience advanced, but the homepage and especially the scan flow still required substantial frontend and backend work. The proposed scan collects a native Shopify store address and business email, then leads toward a deeper AI-visibility report. Important questions remained unresolved, including audit cost, the instant result or teaser, brand-name detection, usage limits, protection of shared public infrastructure, report-email delivery, and the terms of a refundable reservation. The discussion emphasized honest scarcity indicators and responsible marketing claims. Lighthouse and browser inspection provided preliminary performance signals, but measurements from an older site were not treated as final evidence for the heavier new version; screenshot and animation problems also remained under investigation. For implementation, Luqman compares Claude and Codex and assigns design, backend, migration, and audit work according to their perceived strengths. The workflow uses separated specifications, milestones, dependencies, a Command Center, coding agents, audits, and human visual review. His practical conclusion is that specific instructions, clean context handoffs, and deliberate sequential work are often more manageable than too many simultaneous sessions. The stream does not establish that every migration, audit, or automated workflow was completed successfully. The broader discussion turns to go-to-market work: validating demand before launch, building a list and organic distribution, warming an email domain, and testing advertising or direct sales in phases. Luqman argues that market response—not personal enthusiasm—is the real test of an idea, and that a strong product still needs marketing and distribution. He presents GEO and AEO as emerging relatives of SEO; based on his reading of trends, he observed growing interest during 2025 and predicted further growth by September 2026, explicitly as an opinion rather than confirmed market evidence. Audience questions also cover whether non-developers can build with AI, learning by doing, Micro-SaaS and B2B opportunities, model and hosting choices, and choosing Telegram or Discord for an Arabic-speaking community. Overall, this is an unfinished build-and-validation journey rather than a completed launch, with product viability and growth channels still awaiting real market evidence.
163 moments from the stream
- 3:33:35
Reviewing a report email and magic link
Fragmentary captions indicate a review of a report email involving a PDF or HTML attachment, required-email behavior, a magic-link headline, and a report token; the unclear wording does not support firmer implementation details.
- 3:34:44
Clarifying brand-name detection
The speaker asks for a brief explanation of an install-related brand-name detection section and calls it important, but the captions do not clearly establish how the detection works.
- 3:41:03
Possible review of attack surface and abuse behavior
The garbled captions appear to discuss a security review of possible abuse behavior, mentioning a weakly protected secret or attack surface and repeated clicking or scanning; the exact details remain uncertain.
- 3:42:35
Warming Up an Email Domain Before Launch
The discussion recommends preparing pre-launch outreach early because a new email domain needs time to build reputation and improve deliverability. It compares this with the trust-building period for a new website domain in search and notes that the process requires documented execution, multiple steps, and patience.
- 3:44:46
Expanding the Scan Report and Connecting It to the App Dashboard
The scan report should cover the dashboard’s sections while offering more depth and value than the in-app view. After installation, relevant report findings could be pulled into the application’s command center.
- 3:45:47
Defining Refundable Reservation Terms
The discussion identifies questions that a pre-launch reservation offer must resolve: when the deposit is refunded, whether installation triggers an automatic refund, and what happens if installation never occurs. The terms and mechanics need to be explained clearly on the pricing page.
- 3:46:56
The Purpose of the Homepage Free-Scan CTA
The free scan is framed as the website’s primary call to action: it collects the business information needed for the scan and helps distinguish interested merchants who are willing to make a pre-launch reservation commitment. The discussion then turns to how this flow should appear on the homepage.
- 3:53:05
Splitting Specs and Working with Codex Step by Step
The work was split into two separate specs: one for the scan funnel and another for email support. Luqman explained that he now moves more deliberately with Codex after finding that running roughly six sessions in parallel was impractical, so he prefers to proceed one task at a time.
- 4:05:26
Turning the Core Product Goal into Milestones and Tasks
Completed items are marked to unblock dependent work, followed by a proposal to add two phased implementation paths within the Burnish product lane and expose them as real tasks. Although this expands the workload, it is treated as necessary because the store-scanning function is central to the website’s purpose, with the first path prioritized ahead of the later alternative.
- 4:11:33
What Is Generative Engine Optimization?
A concise explanation of generative engine optimization as a field related to SEO but focused on helping merchants appear more effectively in AI platforms. Shopify is presented as the initial platform for evaluating the results.
- 4:13:30
The Market Is the Real Test of an Idea
The speaker argues that personal enthusiasm does not establish whether an idea is good; market response is the deciding test. He discusses marketing, sustainability analysis, and market validation while emphasizing the amount of work involved.
- 4:21:01
Why Companies May Keep Using SaaS Products
The speaker argues that a company’s ability to build a specialized system internally does not mean it will choose to do so. Staffing, skills, and cost can make an external service more sensible when it delivers worthwhile ROI, so he expects SaaS to keep growing rather than decline.
- 4:29:54
Reviewing Product Pages and the Remaining Homepage Work
The speaker reviews the product website: pricing, FAQs, and product-education messaging appear close to complete, while the free-scan call-to-action flow and homepage still need work. He notes that the education section helps visitors understand what the application does, then judges a homepage visual effect as promising but says its internal cards need refinement, while avoiding unnecessary polishing.
- 4:34:12
Refining Cards, Logos, and Scroll Response
A visual review of the Burnish interface recommends enlarging logos and the wordmark, making cards more prominent and immersive, and slowing the section’s scroll response. The speaker prefers giving feedback incrementally and reviewing visual results in stages.
- 4:40:01
Dividing Validation Between the Agent and Human Review
The speaker distinguishes validation that requires inspecting or running code, which can be delegated to an agent, from validation requiring human visual judgment of the interface. When there are no specific UI concerns, work can proceed with a later audit instead of manually verifying every step.
- 4:47:30
Improving Interface Spacing and Section Sizes
A UI review notes improved scroll speed, suggests creatively filling the large gap between the AI icons and the result, and recommends allowing sections to vary in size instead of forcing a uniform layout.
- 4:48:35
Is the Issue Caused by Localhost or the Code?
A cautious troubleshooting discussion leans toward the code, rather than localhost, as the cause because other animations work in both local and production environments. The speaker notes that he is not a web developer and presents this only as a suspicion.
- 4:50:44
Planning a Shopify Store Visibility Audit
Planning for a feature that takes a Shopify store URL and produces a deeper report on the store’s visibility across AI-assisted search engines and tools. The concept compares appearances in prompts, restricts access around the store URL, and aims to give merchants a useful report; it remains a plan rather than a demonstrated implementation.
- 4:54:12
Reviewing Interface Performance and Empty Space
A review of whether image sizing, formats, and custom motion might create technical load, followed by approval of a visual improvement and a note that the next board contains empty space that needs attention. The speaker explicitly remains unsure about the effect’s technical details.
- 4:58:38
Bringing AI into Marketing Execution
The speaker expects the sessions to shift from vibe coding toward marketing and wants to explore ways for AI to perform or assist with marketing tasks. He distinguishes product-building work from go-to-market work and notes that some tasks remain human-operated while parts of the workflow may be automated.
Got a question about something in this stream?
Ask in the group