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
- 6:41:44
Reviewing Heading Reveal Motion and Spacing
The review identifies two interface issues: heading reveals are slower than intended, and spacing is inconsistent. It proposes a faster per-letter reveal, checking a visual reference, and correcting the spacing.
- 6:43:10
What Counts as an AI Coding Harness?
An unresolved discussion considers what counts as an AI coding harness and how such an environment may differ from relying only on an API. Codex and Cursor were raised as examples, but the classification remained uncertain because the speaker was unsure and parts of the captions are unclear.
- 6:45:16
Refining the Interface Grid and Its Scroll Reveal
Practical interface feedback proposes containing a floating element in a glass-effect rectangle, avoiding an exact reuse of the homepage grid, and choosing a different geometry. The new grid lines should draw progressively on scroll, with the effect completing when the full dashboard enters the viewport.
- 6:54:24
Why Some Social Content Resonates
The speaker observes that one video about local problems drew notable interest and reflects on how difficult it can be to predict which topics audiences will care about.
- 6:57:04
An Interactive Burnishing Effect for the Burnish Website
While reviewing the website design, the speaker proposes restoring a light or pearl background behind the dashboard section and adding a mouse interaction that appears to polish its surface, tying the visual behavior to the meaning of Burnish.
- 6:59:05
Connecting a Manifesto to the Brand’s Meaning
The speaker discusses using a brand’s literal meaning as the foundation for a coherent manifesto. As an admired example, he describes reframing CRM from “customer relationship management” to “customer relationship magic,” then closing with a call to action tied to that magic theme.
- 7:01:12
Exploring “Answer Share” in AEO
The speaker suggests keeping AEO’s existing meaning while exploring “answer share” as a possible term for an industry mechanism, explicitly presenting it as an open direction to consider rather than a settled decision.
- 7:03:13
Question About a Short Ad for a Patient-Booking App
A viewer asks how to create a short promotional video for a patient appointment-booking app and what to do next to market it. The page does not provide a detailed public answer about production or distribution.
- 7:04:07
Scoping Questions Before Marketing a Video
Before planning social-media promotion for a video, the discussion recommends clarifying the distribution channel, expected outcome, and desired presentation, while noting that some video styles may be harder to produce than they appear.
- 7:06:43
Homepage Critique and Visual Continuity
The feedback calls for creating a clear geometric connection between the hero and dashboard and rethinking the later sections—especially a four-part layout—which the speaker considered overly plain and unattractive.
- 7:08:57
Solving the Cold Start for a Two-Sided Booking App
Presented as a personal view that may be mistaken, the discussion examines how to attract both providers and users to a booking app. It argues that building genuine public demand and usage may make provider recruitment easier. This follows a clarification that the app is intended to organize appointments and enable booking from home, rather than directly bring patients to providers.
- 7:14:07
Operating Models for a Medical Appointment Platform
The speaker distinguished between listing doctors for lead generation and managing the entire booking journey inside the app. In his view, end-to-end booking requires the provider’s consent and access to their schedule, while a simpler model could direct patients to contact the doctor or secretary. He also suggested subscriptions and advertising as later options after demonstrating customer acquisition, and reviewed Nabd positively for its straightforward design, booking journey, privacy and terms pages, and account-deletion flow, while recommending shorter, simpler copy.
- 7:28:48
Reviewing Security in AI-Assisted Applications
Answering a question about security in AI-assisted coding, the speaker qualified that his direct experience was limited because his hosted platform handles part of the security responsibility. For independent web applications, he suggested cloud protection services and a security agent that reviews the application at major milestones, and considered simulated attacks as a possible idea; no completed or successful security test was reported.
- 7:30:19
Website Launch Status at Session End
At the end of the session, the speaker said the website was live but still had issues and required more work. At that time, he hoped to finish it the following day rather than that evening.
- 7:32:21
Refining a Banner-Like Interface Element
The speaker discussed feedback that an interface element resembled a banner advertisement, compared it with a reference implementation he considered cleaner and less ad-like, and considered borrowing that design direction for the interface.
Got a question about something in this stream?
Ask in the group