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
- 5:06:23
Can a Non-Developer Build a Website with AI?
The speaker argues that someone without a web-development background can build an acceptable website with AI, while acknowledging that programming experience makes the work faster and helps developers give more precise instructions and communicate ideas more easily.
- 5:08:42
Execution Matters More Than an Original Idea
The speaker notes how difficult it is to find an idea that has never been attempted and argues that meaningful differentiation usually comes from execution rather than the idea’s claimed originality.
- 5:09:24
Learning by Building and the Value of Coding
The speaker favors learning through hands-on building while stressing that the best method depends on the learner’s goal: completing a project may be enough for some, while studying programming helps those who want to understand the underlying logic. He also recalls, with uncertainty about the source, a view that code training may strengthen language models’ reasoning abilities.
- 5:15:40
Workflow Commands by Task Complexity
An explanation of a workflow that reserves prepare for medium, large, and architectural tasks, followed by build after preparation, while small tasks use a separate command and auto is also available. It also proposes recording dependencies in a blocked section, automatically moving dependent tasks into the to-do list when unblocked, and adding complexity labels in two plans.
- 5:23:27
Token Usage Across Building and Debugging
The speaker’s view is that the initial building phase consumes more tokens than later work such as debugging, even though that work remains important, and notes that multiple tasks are being run in parallel within the workflow.
- 5:25:49
Generative Engine Optimization for Shopify Commerce
An explanation of generative engine optimization as an AI-oriented counterpart to SEO, noting increased activity since 2025 and the speaker’s view that Shopify remains relatively less crowded while still requiring market education.
- 5:28:27
Multiple Products Need a Repeatable Distribution Playbook
The speaker argues that repeatedly building products or companies can work with a clear launch and distribution playbook; the major mistake is releasing something and assuming the market will buy it on its own.
- 5:29:20
Requesting a Static Logo from a Visual Reference
A practical request to pull a static 3D-style logo shown inside a circle in a visual reference and place it in a specific section. The excerpt records the request but does not establish that extraction or implementation succeeded.
- 5:30:05
When to Polish One Product and When to Expand Experiments
The speaker treats the choice between one highly polished product and multiple products as context-dependent. He stresses that a product must deliver real results and value to merchants and acknowledges that falling build costs and faster development may shift the balance. He also notes that reaching a degree of self-sustaining acquisition and recurring revenue may change the expansion decision. He says he does not yet want to move on to another idea.
- 5:37:05
What Comes After Product–Market Fit?
The speaker explains that reaching product–market fit opens several paths: scaling one product or keeping it steady while building others in parallel, with the choice depending on the founder’s personality and vision.
- 5:38:30
Freedom as a Personal Measure of Success
The speaker shares the view that the goal is not maximizing income for its own sake, but reaching a level of freedom and financial independence whose meaning differs from person to person.
- 5:39:18
Balancing Website Polish with Shipping
The speaker works on turning a logo into a floating 3D element and adjusting its lighting, then critically considers the time spent polishing it. He says the site could function without that level of finish, but wants inbound visitors to see a credible experience while completing the core flow and moving on to remaining backend work.
- 5:43:37
Splitting Work Between Codex and Claude
The speaker checks Codex’s progress on a task within a milestone and mentions assigning a small task to Claude, reflecting a multi-assistant workflow. The page ends before the final task is fully explained.
- 5:44:15
Using a Deep Store Scan as a Funnel Entry Point
He outlines a funnel that collects a Shopify store URL and business email, then provides an in-depth report on products and their visibility across AI platforms. The intended value is to encourage merchants to continue, potentially through a refundable reservation in the sign-up journey.
- 5:46:44
Preparing Email Delivery for Reports and Avoiding Spam
He discusses how delivering scan reports requires more than creating an address on a new domain: domain authentication such as DKIM and sender reputation also matter. He distinguishes cold-outreach tooling from sending reports directly through Google Workspace and considers other services without confirming that they solve the issue.
- 5:49:42
A Landing Page Should Explain the Product on Its Own
Responding to difficulty following the stream, he explains that it documents his company-building process rather than serving as a course. He wants the finished website to become the immediate explanation of what is being built; if visitors still cannot understand it, that signals a communication and design problem.
- 5:57:05
Final Homepage Polish Before Deployment
He reviews interface refinements including enlarging the logo, removing an outer border, improving the zoom transition when leaving a scrolling loop, and smoothing the motion. He notes that the available performance result belongs to the old site, so the heavier new deployment must be evaluated separately, while non-urgent legal and security footer items can be deferred.
- 6:05:35
Building a Homepage Narrative Around AI-Platform Visibility
The speaker walks through the homepage sequence: introduce merchants’ limited visibility on AI platforms, show visibility measurement across several engines, describe work inside Shopify on optimization opportunities, and connect measurement with fixes in a closed loop. He notes that parts of the page and its messaging still need refinement and does not present these concepts as proven outcomes.
- 6:09:32
Pricing Research and Validating Serious Interest
The speaker says pricing was informed by research into gross margin and the product’s feature set. He discusses a refundable deposit paired with an initial audit as a way to test whether merchants are seriously interested, and treats the store-scan call to action as a central website element while the strategy remains in development.
- 6:13:16
Why “Overnight” Claims Are Misleading
The speaker rejects “overnight” language in this field because it can misleadingly imply immediate results, and invites feedback if similar wording appears on the website.
Got a question about something in this stream?
Ask in the group