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
- 1:43:58
Checking a Subscribe Event and Network Errors
After a test scan, a subscribe-button click event appears, while network errors and an unclear verification problem are mentioned. The speaker asks for the cause to be investigated and the fix moved into the main code quickly; the available captions do not confirm the outcome.
- 1:47:45
Shopify App Saturation and the Importance of Marketing
Citing a reported influx of new applications, the speaker predicts that the Shopify app market will become saturated with AI-created apps sooner than many expect. In his view, success will depend on balancing product value with strong marketing.
- 1:51:30
Marketing Economics for Shopify Apps in a Crowded Market
The speaker argues that a Shopify app needs both genuine product value and strong marketing because customer acquisition can be expensive. In his view, high margins create more room for marketing spend, while AI has made an already competitive market feel more saturated.
- 1:52:23
Diagnosing a Post-Deployment Scan Failure and Improving AI Collaboration
Although deployment reported success, the scan still failed despite the public Turnstile configuration being present, suggesting a deeper issue than a page refresh. The work also raised consent-copy and checkbox-gate changes, while the speaker asked the AI assistant to give one step at a time instead of a long sequence; the accessibility remark remains unclear.
- 2:02:17
Tracing a Repeated Cloudflare and GitHub Actions Setup Loop
The speaker traces a deployment setup involving GitHub Actions and Cloudflare, asking how to create an API token and insisting on understanding Git commands and branches before running them. At the repository-secrets stage, he finds that the requested configuration had already been added, exposing a troubleshooting loop that repeats setup steps instead of isolating the root cause. No private tokens or identifiers are included.
- 2:09:49
Two Coding Assistants Stall While Public Meta Settings Remain Missing
The speaker remarks that Codex and Claude have both stalled during the troubleshooting session, then encounters a warning that required public Meta settings are still missing. The excerpt ends with the question and does not establish either the cause or a fix.
- 2:12:22
Deploying and Testing Consent-Page Fixes
The work deploys consent-page changes to Railway and then refreshes the page to verify them. The changes include disabling Continue until the customer accepts the terms, improving the presentation of data-processing agreements, and repairing a link that returned a 404 before debugging inside the application.
- 2:13:40
Diagnosing a Deployment That Shows Stale Changes
The discussion describes using Codex for earlier work and Claude for marketing-front-end tasks while noting deployment, API, and environment-configuration complexity. After a redeploy and a wait, the consent page still showed its original version, prompting a request for a deeper investigation to identify and fix the root cause.
- 2:19:00
Testing a Shopify Store and Reviewing Pixel Events
The discussion mentions creating a Shopify testing store, then reviews a page that needs improvements such as a loading state during a scan. It also inspects Shopify Pixel events and custom conversions, including scan-started and lead events, while waiting for the scan to finish to verify the behavior.
- 2:23:14
Integrating an App with Google Merchant Center
A discussion of why the app needs a verified store and Google Merchant Center API access, with clarification that it receives issues shown in the merchant’s Google Merchant Center account. The product scope was initially uncertain, prompting a question about whether it focuses on product optimization for ads.
- 2:24:47
Diagnosing Funnel Events Before Running Ads
The scan was considered broken in its design rather than its result, and it needed polishing before any ad spend. The review covered events such as page view, scan started, scan completed, and lead, emphasizing the need to define each trigger, verify event order, and confirm that any assigned monetary values are intentional.
- 2:31:22
Merchant Center Violation Diagnosis and Product Expansion
An app concept combining AI with the Google Merchant Center API to identify policy issues, help merchants resolve them, and run recurring preventive scans. The discussion suggested beginning with this focused use case and potentially expanding later into broader product-catalog optimization. The speaker also observed, based on prior experience, that a tool embedded deeply in catalog operations can become difficult to replace, which may strengthen retention.
- 2:34:29
Choosing Optimization Goals and Designing CTAs
A review of optimization goals across funnel stages, noting that a registration step centered on GMV questions needs a clearer value exchange. Important result-page CTAs were also identified, including opening the full report, downloading it, and proceeding to a reservation, with the reservation CTA still needing refinement.
- 2:36:22
Reservation CTA Fails to Reach Checkout
Testing showed that the reservation button did not redirect to Stripe as expected; the report disappeared and a message then indicated that a reservation was already in progress. The behavior was identified for further diagnosis without claiming a confirmed cause.
- 2:41:36
Planning End-to-End Funnel Verification in an Isolated Branch
A plan to review the funnel end to end, including design, copy, and a smoke test, while keeping the work in a separate branch or worktree until approval and integration into main. After setup difficulties, the speaker requested a clear explanation and step-by-step resolution; the proposed first step was a clean branch from origin/main with the needed commits applied, without deploying yet.
- 2:46:14
Why Dropshippers May Be the Best Audience for a Google Shopping Compliance Tool
The discussion distinguishes product-sync tools from a compliance-focused solution and argues that dropshippers are likely the strongest target persona. The speaker associates their typically larger catalogs with more Google Shopping compliance challenges, contrasting them with private-label stores that may maintain smaller, more curated catalogs.
- 2:53:32
A Repeatable Workflow for Testing the Onboarding Funnel
A workflow was proposed to reset test data on demand through Supabase, run a local preview, and review the customer journey from the beginning while establishing what should happen at each step. Stripe was mentioned as part of the setup, though the page does not provide the complete workflow details.
- 2:58:37
Reducing Onboarding Friction with Scan-Derived Data
The speaker argues that heavier onboarding can increase churn and criticizes asking merchants for brand, product-category, priority-product, and competitor data when the application could infer it from a website scan. The scan step is presented as central to onboarding, while a general churn benchmark is offered as an opinion rather than a documented test result.
- 3:02:57
Choosing a Conversion Signal for Top-of-Funnel Optimization
Opening an answer about top-of-funnel strategy, the speaker explains that Facebook campaign optimization needs sufficient data points and signals. He argues that optimizing immediately for a final conversion may be impractical, suggesting an upper- or middle-funnel conversion event instead. The excerpt ends before he identifies the event for his case.
- 3:04:39
Tracking Scan Starts and Completions as Qualification Signals
A surface-level measurement strategy: the pixel records a page view, a scan-start event represents clicking to generate a report, and the lead event indicates remaining through scan completion. These signals are used to identify qualified leads and route them into follow-up systems.
Got a question about something in this stream?
Ask in the group