Funneling, sequencing, & Going to Market
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 preparing a complete go-to-market system before increasing ad spend: reviewing the website, landing and pricing pages, prioritizing mobile UX, and building conversion funnels, email programs, and a unified metrics dashboard. Practical work covers brand consistency, motion, conversion sections, UI and background-job diagnosis, coordination between coding-agent sessions, and choosing AI tools based on quality, price, and usage. Audience discussions address learning marketing and sales through practice, pricing and trials, SEO and merchant visibility in AI answers, testing Google and Meta ads alongside email and SMS, and the importance of margins, supply chain, and early seasonal preparation. The speaker repeatedly stresses that marketing outcomes, pricing, and automation require measurement, market testing, and real user feedback. Several matters remain unresolved, including recurring failures, pricing changes, tool performance, and completion of the website and marketing system.
103 moments from the stream
- 2:20:01
Writing a Strong Message Without Sounding Arrogant
A review of marketing copy that feels overly aggressive or condescending despite strong placement on the page, with a proposal to preserve the section structure while brainstorming a powerful but more respectful statement.
- 2:24:49
Making a Coding Agent Confirm Requirements
After an implementation diverges from the request, the agent is told to stop and restate the requirements before proceeding: reproduce a reference page’s structure, retain the existing header and footer, substitute the appropriate content, remove a nonexistent tier, and ask clarifying questions in advance.
- 2:28:23
Faster Text Reveal and Reusing a UI Strip
A practical adjustment asks for less scrolling per text-reveal step and reuses the AI-engine strip already located beneath the home-page hero section.
- 2:33:53
Fixing the Homepage Dashboard Backdrop Width
A quick homepage review requests removing the black strips beside the dashboard preview below the hero section and extending its golden backdrop across the full width.
- 2:37:55
Pre-launch Email Marketing Readiness Audit
A request for a comprehensive review of email marketing: what has been completed, its current status, and what must be made robust before a launch described at the time as imminent, with the in-progress scan funnel identified as a known dependency.
- 2:41:04
Assessing Worker-Crash Severity and Preventing Recurrence
The speaker asks whether a worker crash can bring down parts of the backend and impair application efficiency, explicitly treating that impact as an understanding that needs confirmation. Given the reported recurring crashes, the speaker calls for a severity assessment and remediation aimed at preventing recurrence as far as possible.
- 2:45:36
Improving Merchant Visibility in AI Answers
A discussion of a field resembling SEO but focused on helping merchants appear when customers search for products through AI platforms instead of traditional search engines. Shopify was described as the current platform, while broader expansion was said to require greater resources.
- 2:47:19
Tuning Interface Motion and Trailing Effects
Implementation feedback to restore a smooth golden trailing effect for moving elements and adjust their resting duration.
- 2:48:42
Preserving Context When Compacting an AI Work Session
A workflow for requesting a concise brief that preserves the session, task, and current findings so an audit can continue after conversation compaction without losing prior context.
- 2:49:35
Preparing the Marketing Funnel
A rundown of remaining go-to-market work: completing the website and landing page, building the funnel, and preparing email marketing and advertising creatives. The key point is that a finished product does not mean the marketing system is ready.
- 2:51:31
Auditing a Recurring Background-Job Problem
A discussion of a recent recurring issue involving numerous background jobs, while explicitly avoiding the claim that the service was down. After inconclusive fix attempts, a deep audit was proposed to identify the cause and honest next steps rather than rely on unsupported assurances.
- 2:53:48
Using an AI Tool for Design Assistance
A brief note that a Claude-related design tool was used and was sometimes helpful with design tasks; the captions do not establish a more precise product identity.
- 2:56:03
Balancing Coding-Model Quality, Price, and Token Usage
An experience-based comparison argues that two tools are close in capability and that one may be better for some tasks, while pricing and token consumption can make the cheaper alternative more practical and productive. This is a personal assessment based on pricing at the time of recording, not a controlled test.
- 2:59:51
Reviewing a Website Redesign with Mobile as the Priority
A discussion of a website redesign described as a major step beyond its previous version, with a designer’s feedback sought on the logo and interface. The review covers a more meaningful logo, improved color harmony, readiness for marketing, and prioritizing the mobile experience over desktop before release.
- 3:02:45
Diagnosing Text Bleeding Outside a UI Section
A practical UI fix request identifies text bleeding beyond a section’s boundaries, as shown in an attached screenshot, and asks why the unintended visual overflow is occurring.
- 3:07:31
Structuring a Page and Guiding UI Implementation Step by Step
The speaker divides the page, excluding its footer, into a hero containing cards, a header and a logo strip, followed by a matrix and an FAQ section. He then directs the design incrementally, beginning with a dark background based on the newer homepage hero and reusing its logo strip.
- 3:08:37
Adapting Interface Ideas and Working Around AI Tool Limitations
The speaker discusses adapting ideas from other websites into his own design, using sketches, screenshots and manual intervention when the tool cannot reproduce a particular section. He also gives his dated opinion that Codex was stronger than Claude for web UI at the time, while noting that Claude had recently received a web-related update.
- 3:12:37
Diagnosing a Visual Overflow Issue After Scrolling
The speaker appreciates clarifying questions before a fix is attempted, then explains that browser-window size is not the cause because the issue also appears at full size. He narrows the behavior down to an element remaining visible and bleeding from the bottom after scrolling beyond the dark section.
- 3:15:05
Defining the Screen Region Before Capture
The discussion suggests marking the target region in advance so the tool can recognize it and capture a screenshot automatically. This was identified as a useful improvement to the workflow.
- 3:16:38
Tracking All Reported Metrics
Although the reported numbers were described as encouraging, the recommendation was to track every metric rather than rely on the initial impression alone.
Got a question about something in this stream?
Ask in the group