TOFU Acquisition Strategy
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 wide-ranging practical work on Burnish, a GEO application for Shopify merchants intended to measure store and product visibility in AI answers and recommend catalog improvements. The session focused on rebuilding and simplifying onboarding, polishing the scan page, report-wait experience, and mobile UX, and reviewing plan selection, Shopify billing, and data-processing consent. In parallel, it developed a Meta/Facebook acquisition funnel built around a free report and signals such as scan started, scan completed, and lead, with a recurring view that the mid-funnel and user journey should be improved before ads run. The work also covered clean-state testing and troubleshooting 500 errors, scan failures, deployments, Turnstile, tracking events, Stripe redirection, and Supabase, Cloudflare, Railway, and GitHub integrations; several causes and outcomes remained unresolved, and end-to-end verification was not shown as complete. Performance testing found that reducing sampling depth did not deliver the expected speedup in one attempt, leading to discussion of progressive results and a clearer waiting experience. Audience questions and broader discussions covered home-hosted databases, building Shopify apps through vibe coding, learning programming with AI, GEO versus SEO and AEO, dropshippers as a possible audience, and personal comparisons of Codex, Claude, and agent workflows. The indexed topics also cover separate discussions of Shopify-app market economics and saturation, D2C and Egyptian market strategy, cash flow and AI-tool spending, internet and OBS troubleshooting, digital-access constraints, digital-nomad visas, and asynchronous communication. The supported conclusion is that clear value, low-friction onboarding, reliable funnel behavior, and sound measurement should precede advertising scale; final product readiness, several bug causes, and the best landing-page and consent structure remained open.
183 moments from the stream
- 4:29:52
Reviewing Hostname Configuration in Cloudflare Turnstile
The debugging shifted to Cloudflare Turnstile configuration, with a suggestion to add the required hostnames to the Turnstile widget and a request for more precise, screenshot-based guidance. The speaker had first said the error was not a general Cloudflare problem, so the exact cause remains unresolved on this page.
- 4:50:14
Running localhost in the Codex in-app browser
A discussion of a localhost environment working in a regular browser but not in the Codex in-app browser, including whether to use LVH.me or another workaround that keeps the full workflow inside the app. The captions do not establish a successful solution.
- 4:57:54
Resetting an AI report to test the user journey
A request for an on-demand reset of AI report generation so the experience can be tested as if it were the first run and the complete flow viewed from the user's perspective. The discussion then begins examining what was patched and the transition to the plan-and-usage page, but the details and outcome are incomplete on this page.
- 5:00:27
Plan Selection and Shopify Billing Flow
The proposed flow shows the plan and usage limits after the initial step, then sends the user to Shopify’s billing-request page once a plan is selected.
- 5:02:09
Report Generation Time and Funnel-Page Readiness
While waiting for a deep report to build, the speaker observed that the process took several minutes rather than the shorter duration he expected. He also described the page as visually static and central to the funnel, with further polish needed before advertising continues.
- 5:10:58
Polishing the Scan Page with Reused Design Effects
The polish plan starts with desktop before moving to mobile: reuse an existing homepage card’s background and sweep effect on the scan page, and replace the current logo treatment with a 3D glyph already used elsewhere. The instructions also call for restating the requirements before execution to confirm understanding.
- 5:15:46
Acquisition Channels and Conversion Tracking Setup
The speaker described reaching the stage of setting up Burnish’s social presence and Meta Pixel infrastructure, including page-view tracking and a conversion when a store URL and business email are submitted, alongside additional custom conversions.
- 5:16:39
Why Optimize the Middle of the Funnel Before Purchase?
The speaker argues that improving the middle of the funnel currently matters more than optimizing directly for purchase, because stronger signals and data are needed before attempting to scale.
- 5:19:02
Using a Second Model to Review a Coding Assistant’s Diagnosis
The speaker recounts a coding assistant getting stuck on a localhost-accessibility issue. He asked Claude to explain the mistake and next steps to that assistant and, by his account, the review helped it reach a fix within minutes.
- 5:19:55
Polishing Mobile and the Scan Flow Before Running Ads
The speaker says the desktop experience is stronger than mobile and that Burnish’s site and scan flow still need polish. He treats the site as part of market validation rather than the final destination and wants the funnel’s process, presentation, and purpose clear before ad spend.
- 5:22:25
Anticipating Pre-Q4 E-commerce Demand
Based on a pattern he observed in 2025, the speaker expects demand in this domain to rise from late August into September 2026 ahead of Q4, when more merchants begin considering SEO and GEO. He presents this as an expectation, not a certainty.
- 5:30:06
Turning Fragmented Onboarding Issues into a Parallel Plan
After a plan-switching check showed the flow was not working, the speaker identified design, logic, and bug issues across the onboarding steps. He proposed entering planning mode and using multiple agents in parallel to address the system more comprehensively and quickly.
- 5:31:42
Can a Supabase-like Service Be Hosted at Home?
Answering an audience question, the speaker says he has not tried running a home server that behaves like Supabase and suspects it may require powerful hardware. The answer remains an untested impression.
- 5:31:55
Why the Database Needs Reliable Cloud Hosting
He explains that running a server at home could make a customer-facing database unavailable during a power outage, so he considers cloud hosting more suitable for the data.
- 5:34:39
Voice Notes for Asynchronous Communication
He describes preferring voice notes to calls because, in his experience, they support careful listening, detailed responses, and more efficient communication.
- 5:37:50
Stabilizing and Polishing the Onboarding Experience
The discussion prioritizes stabilizing onboarding and deciding what merchants should choose. UI directions include removing a glyph’s dark background, matching its motion effect to another page, moving it into the merchant-view card, and creating a separate first-time plan-activation page with dedicated copy and a CTA outside settings.
- 5:45:22
Comparing Warp, Claude Desktop, and Codex
A practical, qualified comparison of work environments: Warp felt faster for some tasks, while Claude Desktop and Codex were considered better in several respects and more accessible, with terminal-based work described as potentially consuming tokens faster.
- 5:50:28
Structuring Shopify App Onboarding and Using the Right Reference
A proposed onboarding sequence covers Shopify consent, activating the app embed, confirming the website and the AI's understanding of the brand, then choosing a plan. The discussion also stresses using the correct internal app-analysis documents before drawing conclusions from earlier onboarding experiences.
- 5:52:32
Detailed Onboarding Interface Feedback
A visual review of the onboarding interface covers enlarging a glyph while preserving its placement, improving alignment, positioning a testimonial, and using the “Activate and continue” CTA, alongside a review of the activation, confirmation, and plan-selection step labels.
- 5:58:09
Deriving an Onboarding Pattern from App Examples
The discussion proposes analyzing multiple app examples to derive a rational onboarding pattern for Burnish, treating onboarding as an important product decision that merits explicit discussion rather than copying one example.
Got a question about something in this stream?
Ask in the group