$49 Reservation 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 documents Burnish’s preparation before market entry, including practical reviews of the website messaging, mobile experience, and the “scan my store” journey intended to measure a Shopify store’s visibility in AI-platform answers and email a useful report. Work focused on outcome-led copy, reframing the product loop as “research, monitor, action, measure,” and experimenting with sections, ambient video, and visual effects whose impact on site speed still needs measurement. Refundable early reservations and a waitlist were discussed as possible demand-validation signals, while fabricated social proof was rejected and actual uptake remained uncertain. Technical discussion covered the Polaris migration, dividing work between Codex and Claude, deployment and environment-configuration complexity, and adding model providers; however, the migration audit, compliance requirements, and some sensitive backend integrations remained unresolved. Side discussions answered audience questions about learning English, stream-music permission, the current preference for YouTube, and a multi-agent command-center architecture. The recording is presented as documentation of an unfinished build journey—not a course or a claim of product success.
50 moments from the stream
- 0:03:46
Preparing Burnish Before Marketing
The priorities include finishing desktop and mobile experiences, migrating from Polaris React to Shopify-recommended Polaris Web Components, and building the backend for a funnel that assesses a merchant store’s visibility on AI platforms. Once these foundations are in place, marketing preparation can begin even before the entire product is finished.
- 0:07:09
Product Results Come Before Marketing
The speaker explains that market entry can combine paid and organic channels, but marketing cannot compensate for a B2B product that fails to deliver tangible value or results. If the product is not yet effective, the priority is to return to its engineering and improve it before confidently expanding into the market.
- 0:11:47
Reviewing Burnish’s Homepage Message and Experience
The discussion reviews a homepage coded with assistance from Claude and Codex, emphasizing that the hero should quickly communicate that Burnish serves Shopify merchants and addresses weak store visibility across AI platforms. It also presents the proposed visibility-improvement solution and notes unfinished design work, including a missing 3D logo element whose root cause needs investigation.
- 0:14:46
Marketing Foundations Are Not Yet Go-to-Market
The speaker distinguishes preparing for market entry from actively executing a go-to-market phase. Current work focuses on establishing the marketing foundations while the product remains incomplete, with debugging potentially requiring additional time.
- 0:15:27
Pre-Launch Reservations as a Market-Validation Signal
Before the app becomes available on Shopify, the funnel proposes an early reservation option with a plan-linked deposit that is returned at launch, followed by an installation link and an initial review of the store’s AI visibility. The stated purpose is not to spend the deposit but to measure customers’ willingness to pay before launch as a stronger demand signal, alongside collecting email addresses and store URLs through a waitlist.
- 0:17:39
Sequencing Website Completion and Conversion Funnels
The speaker sequences the work by finishing and polishing the homepage first, including addressing the logo issue, before moving to the store-scanning funnels. He also briefly mentions warming up the email domain through the terminal as preparatory work, while postponing a fuller explanation.
- 0:20:45
Agent Task Execution with a Careful Migration Audit
The workflow has Codex execute several tasks, while sensitive work such as migrating from Polaris React to Polaris Web Components receives closer supervision and a final audit by Claude.
- 0:21:55
Why Would a Customer Pay an Early Reservation Deposit?
An early refundable reservation for a beta cohort is framed around priority onboarding, a personal founder review and locking an early pricing tier. The goal is to create launch-day traction and cash flow, while explicitly acknowledging that reservation uptake is uncertain and depends on the marketing funnel and reach.
- 0:23:58
Preparing for Day-One App Traction
The pre-launch phases are used to build early interest so installs, reviews and market attention can begin when the Shopify app is approved, instead of relying only on organic adoption. The speaker notes that early incentives may reduce later margins in exchange for stronger initial traction.
- 0:26:01
Writing Product Education Around Outcomes
A merchant-facing education page is reviewed with an emphasis on benefits and outcomes rather than implementation details. The messaging should balance the product promise with an explanation that Burnish measures visibility and improves product information for better representation in AI answers.
- 0:28:13
Testing an Embedded Product-Page Video
The speaker requests an experiment placing an optimized, dimmed video within a page section so its visual effect can be assessed. He rejects effects without a clear purpose and says the section still needs refinement.
- 0:32:34
Vibe Coding for Non-Developers
The speaker says the website was built through vibe coding despite lacking a traditional web-development background, presenting it as evidence that people can build products without deep programming expertise while acknowledging that professional developers can often produce better work faster.
- 0:34:01
Reframing the Product Workflow Loop
The review finds the “measure, fix, prove, re-measure” sequence confusing and repetitive. The speaker asks to replace it with a clearer ‘research, monitor, action, measure’ loop across the relevant website pages and to remove the unsuitable background video.
- 0:45:52
Redesigning a Burnish Section and Its Interactive 3D Logo
Luqman discussed rebuilding a page section with a simpler approach and testing whether Claude could work from a visual example. He also demonstrated a coded GLTF 3D logo that follows the user, snaps into a specific section, and returns to the footer, while acknowledging that the effects may be over-polished.
- 0:48:46
Dividing Work Between Codex and Claude Using a Reference Interface
Luqman explained that Codex helped create the structure while Claude was more responsive when tuning the desired effects. He directed the workflow to analyze how a reference landing page presents its closed-loop section and use that as inspiration for Burnish, while keeping one command-center milestone partly manual.
- 0:52:51
Environment Configuration Complexity After a Deployment Failure
After a Railway deployment failure, Luqman discussed how environment variables and keys accumulate as a project grows and must be coordinated across the project, worker, and services such as Cloudflare. He also noted that adding multiple model providers increases configuration and manual dependency complexity.
- 0:57:47
Adding AI Providers and Tracking Compliance Requirements
Additional API integrations were configured so AI-visibility measurements could also be run with DeepSeek. DPA, ZDR, and public compliance-link requirements for XAI and DeepSeek were still unverified and were to be recorded as follow-up work. Creating a DeepSeek API was described as easier than XAI, as an impression during the work.
- 1:05:28
Building a Section in Two Phases: Mechanics, Then Content
The proposed approach was to lock in the section’s mechanics first, then add its content in a later phase, splitting the work into clearer steps.
- 1:05:46
A Practical Daily Routine for Improving English
The advice was to combine courses, English-language content, and daily Duolingo practice. The app was described as initially game-like but potentially enjoyable and useful with consistency, without promising a fixed time to master the language.
- 1:08:53
Why Mobile Design Should Take Priority
The discussion prioritizes the mobile experience because traffic often skews toward phones, even when desktop is used first to establish the page layout. This requires image optimization and responsive restructuring; a six-item desktop grid might become a carousel on mobile. The actual traffic mix was qualified as depending on the site’s niche.
Got a question about something in this stream?
Ask in the group