Launching New Website + Scan funnel
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 centers on practical Burnish website work: unifying template families and the design system, refining grids, motion, spacing, and the ChatGPT, pricing, Manifesto, and scan-funnel experiences, while planning mobile versions. Several issues remained unresolved, including elements hidden behind the header, scrolling behavior, overlapping voice-over, and unfinished pages; by the end, the site was available but still needed fixes. In parallel, Luqman discussed coding-agent limits, task drift, Command Center and Sentry workflows, and keeping a human in the loop, arguing that workflows should fit the person and task. Audience questions covered learning by building with Claude or Codex, freelancing and Upwork, SaaS distribution, commerce and payments in Egypt and Saudi Arabia, databases and hosting, security, and marketing a medical-booking app. The stream also explored Remotion-based video and synthetic voice-over production, but no final voice choice or proven advertising result was established.
135 moments from the stream
- 0:03:08
Preserving Work-Session Context Before Continuing Templates
After the earlier work was merged, a brief session instruction was requested to preserve context before continuing the page families and templates, beginning with the ChatGPT template.
- 0:05:58
Should the Boards Use Generated Voice-Over?
The discussion asks whether certain boards should include voice-over, noting that ElevenLabs makes generation easy while cautioning against overcorrecting the plan. The final verdict is unclear in the captions.
- 0:15:25
Designing a Reusable ChatGPT Page Template
The ChatGPT page is reviewed from top to bottom with the intention of applying its settled design to sibling pages. The hero direction calls for a more structured grid, a light background, and golden circles consistent with the homepage and pricing page.
- 0:30:12
Differentiating the Design Grid from the Homepage Hero
Luqman criticized reusing the homepage hero’s grid lines and said the new design needed a distinct grid rather than the same pattern.
- 0:33:57
Claude’s Computer-Control Indicator and Mouse Conflict
Luqman explained that the orange indicator meant Claude was using the computer to inspect an application, and noted that moving the mouse could conflict with the agent’s control.
- 0:35:13
Creating an AI-Assisted Video with Remotion
Answering a question, Luqman said the video was created with AI using Remotion and described making something similar as relatively straightforward.
- 0:37:05
Reducing Distractions and Prioritizing the Website
Luqman decided to defer videos, creative assets, and the application so he could focus on the website first after several days of switching between tasks, while noting that progress was slow.
- 0:41:22
How Building in Public and Work Livestreams Can Help
The speaker says building websites in public helped him form a small community and learn through it. He also values the stream archive as a way to revisit earlier work and see progress over time, and believes working in front of an audience helps him stay focused and avoid distractions.
- 0:46:51
Adapting a Reference Page for Engine-Specific Sections
The speaker reviews a reference page and proposes adapting several suitable patterns: presenting each engine as its own platform, showing a monthly usage or views indicator, adding a visual banner, and structuring three reasons why optimization for each engine matters. The intent is to replace the current presentation with adapted versions of those ideas.
- 0:53:22
Why the Command Center Was Set Aside
The speaker explained that Command Center helped during the building phase but was not designed for debugging. As AI tools advanced quickly, keeping it updated would divert focus from his main project, so he set it aside while leaving open the possibility of a more current version later.
- 0:57:42
Controlling Agents and Building a Suitable Workflow
Responding to a question about many agents exhausting usage limits, the speaker recommended explicitly limiting how many agents may be launched and noted that research can consume more tokens than building itself. He said there is no single workflow for everyone; a workflow should fit the person and task, possibly adapting a strong published example.
- 0:59:45
Research Proposal for an Agent-Based Development Platform
A proposed academic title was read aloud for a platform using agents to develop and maintain web applications. Additional wording appeared to mention orchestration, observation, and defect detection, but it was unclear and is not presented as a confirmed scope.
- 1:01:20
A Community Platform for Software Agents
A tentative description, explicitly acknowledging uncertainty, of a Slack-like community space where members add their agents so the agents can interact with the group.
- 1:03:26
Giving Burnish Sections a Clear Geometric Structure
Design feedback argues that Burnish components should follow a consistent geometric structure and that one section still feels visually unanchored, with a reference offered as a possible model.
- 1:05:13
An Opinion on the Rise of Agentic Automation
The speaker argues that agent-based automation is becoming an important direction in 2026 and suggests looking toward 2027 when assessing the field. Later product names and historical claims are unclear in the captions and are not treated as verified facts.
- 1:09:45
Website Completion and Scan-Funnel Plan
The work plan starts with completing the website and optimizing it for mobile and desktop, then finishing a landing page that collects a store name and email for a scan before offering an app install. It also includes preparing creative assets and later testing multiple advertising channels.
- 1:11:39
Guiding a Coding Agent with a Visual Reference
A practical instruction for an agent to open a link, inspect a specific section and its visual grid, capture the three referenced items, and reproduce that layout in another website section.
- 1:12:58
Creating an Ad with Remotion and Testing Creative
The discussion outlines an ad workflow developed after brainstorming and built with Remotion, including voice selection and scene-timed voice-over writing. The speaker considers creative a major performance factor and proposes comparing the produced ad with a founder-led video, while leaving the outcome to measured results.
- 1:24:55
Why an AI Command Center Needs Continuous Development
Answering a question about implementing a command center, the speaker explains that AI tools and agent platforms change extremely quickly, so a system that is not continually updated can lose its usefulness. As a historical example from March, he says he had agents exchange information through a JSON file before similar capabilities later became available within Claude. In his view, this does not make a command center obsolete, but raises the level of development it needs.
- 1:29:06
Reviewing Voice-Over Audio During the Workflow
While trying voice-over clips, the speaker checks whether the audience can hear them and notes that playback may require a separate media player. After listening, he decides that he does not like the voices themselves, without stating a more precise criterion or approving a final alternative.
Got a question about something in this stream?
Ask in the group