Inbound vs Outbound Traffic
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 a widening gap between building products with AI—which is becoming easier—and the harder work of distribution, customer acquisition, and sales. Luqman reassesses a heavy reliance on inbound content and considers a broader mix of outbound outreach, cold email, advertising, partnerships, and SEO, with the practical principle of testing channels and concentrating on those that show real conversion signals. Practical work includes reconsidering Burnish’s pricing by replacing a time-limited trial with a free plan, investigating a reported HTTP 500 error and an observability gap, and simplifying AI-agent workflow diagrams; the records do not establish that these efforts were completed or successful. The discussion also explores multi-agent systems organized around shared goals, context, memory, and explicit follow-up, with a preference for starting small instead of introducing early complexity. In comparisons of Codex, Claude, and AI providers more broadly, Luqman emphasizes balancing quality, speed, price, usage limits, and completed workload, while repeatedly qualifying his views as personal and treating mixed reviews and benchmarks as insufficient for declaring an absolute winner. Audience questions broaden the stream to SaaS development, AI-engineering portfolios, content automation and scheduling, visibility in AI-generated search answers, team size, personal branding, transparent affiliate marketing, and AI support for study or business management. Major unresolved questions include the best acquisition channel, the commercial value of content, the right agent architecture, and the changing choice between tools and subscription plans.
133 moments from the stream
- 0:43:33
Finding the name for a multi-agent collaboration pattern
A question about the term for running several agents together, with uncertain candidate names and an acknowledgment that the field’s terminology is shifting and confused.
- 0:45:21
Personal experience versus benchmarks in model comparisons
A discussion compares models whose names are unclear in the captions for programming and video animation, then stresses that the preference was personal experience and that benchmarks alone are insufficient for a strong judgment; suitability remains task-dependent and subjective.
- 0:46:30
Choosing a tool plan from actual usage
Practical advice to start with a suitable plan and monitor weekly-limit consumption; repeatedly exhausting the allowance before the period ends indicates that an upgrade may be warranted.
- 0:47:20
Text-to-speech cost and voice selection
An answer about text-to-speech mentions using an OpenAI service with a voice sourced from another service whose name is unclear in the captions, while noting that longer spoken output can become expensive.
- 0:49:13
Generating content for multiple platforms through an agent system
A brief explanation of a workflow that generates posts across multiple platforms and accounts through an agent-based system, partially replacing manual page-by-page content creation. The system’s name is unclear in the captions.
- 0:51:14
Planning with a Coding Assistant, Then Executing via a Computer-Control Tool
The speaker suggests using a coding assistant such as Codex or Claude to prepare a plan, then giving computer access to another tool whose name is unclear in the captions so it can execute the plan and build the system or app. This is the speaker’s recommendation, not a documented execution or success in the excerpt.
- 0:54:17
Comparing the OpenAI and Anthropic Ecosystems
The speaker shares his personal, time-specific view that OpenAI appeared to offer a broader AI ecosystem than Anthropic in terms of the variety of capabilities and tools. This was an impression rather than a comprehensive benchmark, and unclear model names in the captions are omitted.
- 0:57:32
Inbound vs. Outbound Traffic: Targeting and Conversion Quality
The speaker argues that high-volume posting across platforms may support visibility but does not by itself guarantee substantial traffic or revenue. He explains that outbound traffic can convert better because it directly targets a suitable audience, while inbound traffic is broader and more uneven in quality; this is his general view, not a documented test result in the excerpt.
- 1:01:01
A Central Assistant for Agent Coordination and Work Monitoring
The speaker explores a central assistant that coordinates specialized agents, reducing the need to address each one directly and potentially producing recurring reports on goals and progress. The assistant clarifies that it cannot currently access company data or retrieve a real organization chart, only explain structures and review proposed ones. The concept also extends to monitoring user-onboarding problems alongside error-tracking tools.
- 1:03:47
Balancing Inbound Marketing and Outbound Outreach
The speaker reassesses a strategy heavily weighted toward inbound content, questioning whether the publishing volume and resource use justify the expected results. Outbound outreach, advertising, and partnerships are discussed as more direct routes. He ultimately treats the choice as a mix rather than a binary: both inbound and outbound can be useful, while the inbound effort may have become oversized. This is presented as a personal strategic reassessment, not a conclusive test result.
- 1:06:35
Planning Audio Treatment Across a Full Track
The speaker requests a plan for applying an earlier treatment across an entire audio track, considering hypnotic-style sounds or a radio-static-like alternative, then asks how many phases remain. The page does not establish that the plan was executed or what result it produced.
- 1:10:44
Smaller Teams with Focused Pipelines
The speaker argues that a large headcount is not always necessary, preferring a smaller team whose members each own a clear pipeline or responsibility, while stressing that the operating plan should not leave critical gaps.
- 1:12:09
Combining Inbound and Outbound Acquisition
The speaker discusses moving from heavier reliance on inbound traffic toward a mix of inbound acquisition and outbound outreach to create a more diversified acquisition strategy.
- 1:16:12
Team Size Should Follow Business Goals and Growth Bottlenecks
Responding to a staffing question, the speaker says the appropriate team size depends on the business target and shares a personal preference for a compact, highly productive team. He also identifies insufficient traffic or customer reach as a common growth bottleneck.
- 1:17:32
SEO Is Slow but an Important Launch Foundation
The speaker says he values search engine optimization but considers its financial results slow, which can make faster channels more attractive. Even so, he stresses that a strong SEO foundation matters when launching new content or a project.
- 1:19:01
Cold Email as an Outbound Channel
In response to a suggestion to rely less on advertising, the speaker says he already uses cold email but has not pursued it deeply. He mentions Apollo as a source of targeted lead data and expresses interest in expanding outbound outreach without claiming proven results.
- 1:20:31
Video Titles May Affect Traffic
An audience comment suggests that sharing video links without descriptive titles may reduce their ability to attract traffic; the page ends before the recommendation is completed.
- 1:21:05
The Challenge of Turning Traffic into Leads
The speaker discusses how some traffic sources may bring visitors but few leads, and argues that solving the traffic-acquisition problem could help many people who get stuck at that stage.
- 1:23:45
Improving Short-Video Presentation and Titles
The speaker discusses improving short videos and checking how their titles appear in scheduled content after an audience member notes that the title may not be displayed as expected.
- 1:24:44
Why a Smaller Team May Be Better
The speaker contrasts managing a large workforce with managing a much smaller team of comparable quality, arguing that a new role should be added only when it is genuinely needed.
Got a question about something in this stream?
Ask in the group