← Back to the deck

References & working notes

Video selections and rejected sections

Audience direction

Owner direction, 13 October: adults with a Chinese-speaking partner or Chinese heritage have a personal reason to learn. Repeatedly stopping is the shared problem. Other restarting learners are an adjacent audience.

This is a working hypothesis, not a validated customer segment. Auntie Lin is a created hook, not proof of audience fit.

Auntie Lin door video — version C · Avatar studio

Joseph Choi · 13 October

Start with a specific customer problem. Work closely with a few credible creators. Test formats systematically. Separate creator performance from format performance. Use customer results to judge the work, alongside views. Increase spend after a format converts repeatedly.

The deck’s 2–5 creator test and Content Rewards sequence are our proposal based on these lessons. They are not a campaign commitment or a direct instruction from Joseph.

Open the detailed workshop notes

Brain source: references/marketing/joseph-choi-organic-ugc-workshop-2026-10-13. The original transcript contains repetitions and local timestamp resets.

Content Rewards rep · 8 October

The rep recommended self-service and building our own operation for the proposed starting budgets. The rep said the existing brief was suitable. The rep advised an active Discord community and close work with creators. Agency work includes ideas, formats, sourcing, and submission review.

The earlier plan covered several app campaigns. The revised deck proposes a focused Lock In Chinese test first. We want Kaitlin’s advice on the right place for Content Rewards in that test.

Open Content Rewards

Brain source: meetings/2026-10-08-content-rewards-rep-call. This is a summary of the recorded call, not a current platform pricing claim.

Existing UGC work

The herdr UGC workspace contains work on the “Study with me” creator guide. It includes real app clips, three edited examples, recording instructions, and a post check. A separate discussion covers the wider agency plan and naming.

The introduction uses the 3.3-second Dynamic Island section. The quiz is an alternate example. The owner rejected the Lock Screen and word-walk selections. The audience slide uses a silent 3.65-second door hook. The audience slide uses lin_peep_C.mp4 from the archived creative assets.

App video · Creator portal · Slide maker

Tool status

The research slide uses the owner’s screenshot of the live feed, supplied on 13 October. The feed contains 2,456 posts. Lab analysis is separate from collection and review. A batch of 12 previously liked or shortlisted language-learning posts is requested for analysis. Completion must be checked separately.

The outreach rollout records the core work as built. Preparation and live checks remain before the first send. Dash owns creator records, drafts, and reply review. Instantly is the selected delivery service.

Dash links require an authorized sign-in.

Attention Lab · Creator outreach

Repo sources: docs/playbooks/creator-outreach-rollout.md; docs/superpowers/specs/2026-10-09-attention-lab-design.md; docs/superpowers/plans/2026-10-12-attention-lab-phase-4-lab-pages.md.

Ideas to test later

Owner update: a small farm at home is being set up. Its scale, equipment, and operating status are not specified.

Owner clarification: the idea behind slide 3 comes from seeing formats repeated across large UGC campaigns. A generator could help many creators make variations after we identify a winning format.

The supplied links identify Hevy, not Strong: Hevy Clipping [Slideshow] by Clipvex and Hevy CTA Slide Generator. The generator offers leaderboard, workout history, gym comparison, PR tracking, and streak formats.

These are external references. Their existence does not prove conversion performance. Our proposed sequence is to validate a format first, then explore templates and wider creator production.

Founder network and the wider plan

The 8 October Content Rewards meeting records Neco’s intention to build an operation focused on mobile app distribution. The plan starts with his own apps, then extends to founders in Hacka Network. The owner corrected the network name from the meeting transcription.

Owner clarification for the Kaitlin call: “I want to be the one who solves distribution. Once I get this going, I will bring more apps and projects.” This describes the intended next step after proving the process, not committed customers.

The meeting also names Pretty Progress and other possible projects. The deck keeps the first campaign focused on Lock In Chinese.

Source: meetings/2026-10-08-content-rewards-rep-call, plus the owner’s current direction.

Review against gbrain · 13 October

The gbrain review covers the original eight slides. A ninth slide now adds research-based content proposals. The revisions make the product mechanism, creator test, outcome measures, and requested call decisions more specific.

Gbrain sources: references/marketing/joseph-choi-organic-ugc-workshop-2026-10-13; meetings/2026-10-08-content-rewards-rep-call; playbooks/consumer-app-growth/promise-continuity; docs/playbooks/creator-outreach-rollout; playbooks/creator-cold-email-outreach-learnings; playbooks/creator-research-and-outreach-workflow.

Latest owner corrections govern: Hacka Network is the correct name; the rejected Lock Screen and word-walk extracts stay excluded. The phone farm is an early setup, not a proven distribution channel. Network size and prospective projects are not presented as committed customers.

New format selection · replaces the first examples

The owner rejects the first selection as insufficiently repeatable. The new search requires videos under 30 seconds, a clear opening, and a real product mechanism that fits Lock In Chinese. See seven formats, timings, variation rules, and local video examples.

The earlier selection below remains a research record. It is no longer the recommended deck content.

Product–content fit · Dash evidence

Added 13 October. These three proposals combine saved Dash examples with the current audience direction and Joseph’s test approach. They are adaptations, not proven conversion formats. Draft openings are our proposed copy, not quotes from creators or customer testimonials.

  1. Personal reason. @cantowitheunice is owner-liked. Completed Lab analysis identifies a partner-specific opening followed by useful phrases. The source teaches Cantonese. Our adaptation concerns Mandarin and the habit of reviewing words, not a promise of fluent family conversation. Use a creator whose partner story is true. Test heritage separately.
  2. Question reply and routine. @thisrromericanlife is owner-shortlisted; the owner specifically likes the question widget. @learningwithsirine is owner-shortlisted. Completed Lab analysis identifies numbered tips, a product recommendation, and an app overlay. Borrow that sequence, not the source’s four-month fluency claim. A genuine user can show how Lock In fits their routine. Label a drafted question as a question, rather than fabricating a viewer comment.
  3. A visible rule. @freya.loren is owner-shortlisted with “Format we can copy” and “Fits Lock In.” @christinewrutzen is agent-shortlisted for the sequence of long avoidance, short action, and completion. The latter has no completed Lab analysis. Our proposed adaptation shows the actual restriction, quiz, and app access. It is not a claim that either reference uses Lock In Chinese.

Suggested first test: choose the partner audience and compare the personal-reason opening with the question reply. Keep the creator, product proof, and call to action consistent. Test the visible-rule version next. Measure installs and useful app activity alongside views; assess purchases when attribution is available.

Saved research feed · Lab analysis

Evidence: Dash shortlist records and current source analysis, read 13 October. Automated Lab observations describe sampled video frames and available audio; they do not establish effectiveness. Public engagement counts are omitted because they do not demonstrate product–content fit.

Existing campaign brief and research · 13 October review

Live creator page · Full creator brief · Recruitment kit · Campaign research

What is already written

Where it differs from the current direction

What the campaign research contributes

The saved study compares Lorcana Scan, Trepa, Bluffs, Keymagine, Takeback, and Hevy. Its main operational lesson is to separate the recruitment page, governing brief, format examples, and resources. Takeback is the closest recorded reference for real use and original footage. Hevy supplies the reference for a repeatable slideshow recipe and generator.

For our smaller initial test, retain clear approval and payment rules, specific filming instructions, two or three finished examples, and one resource index. The historical checklist is not a current completion report: for example, the current brief already includes the day-seven bonus rule that the older research lists as missing.

Proposed revision: keep the useful operating material; replace the broad audience and mandatory 30-day format with the focused learner test. Resolve the face rule, product details, and distribution requirements before sending a revised creator pack. This review does not change the public campaign, payment terms, or Dash standing brief.

Sources read: current local creator brief and recruitment material, live creators.nokta.dev page, Dash UGC research brief v1, and the saved campaign-material study in gbrain. Historical external campaign counts and rates are not treated as current.

Technical approach: own the operating system

Owner direction: use a technical product-building background to solve individual marketing and UGC operating problems quickly, automate repeat work, and design for scale. The purpose is more useful tests and evidence. Audience, creative, and customer acquisition still require validation.

The deck overlays the actual Dash interface and a rendered image of the supplied outreach blueprint. A comparison slider reveals the two layers. The interactive original remains available through a separate link. Open the portable blueprint. Source: creator-outreach-p2 worktree, docs/superpowers/specs/2026-10-09-creator-outreach-blueprint.html.

The blueprint is a dated architecture snapshot, not a fresh production audit. It marks checks, dispatcher, API integration, event processing, and scheduled operations as built. It marks mailbox setup and the main switch as pending. Import, verification, drafting, reply options, and later automation stages remain planned in this snapshot. The original links to implementation PRs remain clickable. No email is sent by this deck.