Smart MarketerSMART MARKETER LIVE

SMART MARKETER LIVE 2026 · VIP DAY TAKEAWAYS

The Rise of the One-Person Creative Team

Alex Cooper

Updated 2026-10-27 · 1 processed session

Alex Cooper shows how a marketer can direct AI-assisted research and creative production while keeping control of the message, judgment and quality. Start with customer evidence, delegate deliberately, and turn the team’s decisions into reusable skills. The delivered talk and Q&A add practical guidance on templates, creator sourcing, real creator footage and sharing context across a team.

01 / Alex CooperThe Rise of the One-Person Creative Team

2026-10-19 · AI creative · customer research · ad messaging · reusable skills · creator sourcing · video editing

Alex Cooper shows how a marketer can direct AI-assisted research and creative production while keeping control of the message, judgment and quality. Start with customer evidence, delegate deliberately, and turn the team’s decisions into reusable skills. The delivered talk and Q&A add practical guidance on templates, creator sourcing, real creator footage and sharing context across a team.

Download slides (PDF)

PUT THIS SESSION TO WORK

Welcome to Alex Cooper’s One-Person Creative Team session.

Let’s turn customer insight into better creative, with AI doing more of the production and you making the important decisions.

01

Research the message before choosing the format.

Look for buying triggers, unexpected use cases, emotional phrases, objections, failed alternatives and words only customers use. Alex argues that a strong story can work across animation, static and creator-led ads; the fashionable format is not the underlying strategy.

02

Choose AI’s role one task at a time.

Alex uses AI as a research assistant and remains cautious about original scriptwriting. He delegates more of creator operations, production and analysis. These are his working preferences, not universal reliability scores: choose the task, inputs and review requirements before automating it.

03

Document decisions, not just the steps.

Record a real task while explaining why you selected an idea, hook, clip, cut or creator. Turn that explanation into a reusable skill with inputs, decision rules, quality checks and examples. Alex sees the team’s accumulated context and expertise as the differentiator.

What would you like to put into action?

Open a choice to see the first question and what you’ll create. Continue the work in your connected Coach.

Find my next ad messageA message brief with audience, customer evidence, core message, three proposed angles, one selected angle and the next test.

Turn customer feedback into a focused message and a few ad angles to test.

Useful inputs

  • Product, customer and desired action
  • Available reviews, surveys, support tickets or ad comments
  • Current messages, brand constraints and available proof

Work through it

  1. Reuse business context already supplied. Ask for relevant customer reviews, comments, survey responses or other available customer evidence.
  2. Identify use cases, buying triggers, objections, failed alternatives and distinctive customer wording. Link each finding to its source; distinguish repeated patterns from isolated comments.
  3. Propose three angles as Coach suggestions. Help the attendee choose one and turn it into a creative brief.

If inputs are missing: If customer evidence is unavailable, make a collection plan and mark any proposed angles as hypotheses. Do not invent customer quotations or claim research is complete.

Your working document

  • Product and audience
  • Customer evidence with source references
  • Buying triggers, objections and useful language
  • Three proposed message angles
  • Selected angle and creative brief
  • Next test and success measure
  • Missing evidence and assumptions

Complete when: The attendee has chosen one angle, can see the evidence or stated hypothesis behind it, and knows the next test.

Map my AI creative teamA workflow table with steps, inputs, AI responsibilities, human responsibilities, review gates and one measurable pilot.

Break down a creative workflow and decide what AI can do, what you own and where review belongs.

Useful inputs

  • One creative bottleneck and today’s workflow
  • Available tools, assets, people and budget constraints
  • Examples of acceptable work and decisions requiring approval

Work through it

  1. Choose one bottleneck and map how that work happens today. Ask about available inputs and tools only when they affect the recommendation.
  2. Assign each step to a person, AI assistance or a combination. Specify the input, expected output and human review point.
  3. Choose one small pilot, its owner and a way to judge quality, time saved or rework before expanding.
  4. For creator sourcing, design a small reviewed sample before scaling. Draft outreach and budget rules; sending messages or committing spend requires a separately authorized action in a tool that supports it.

If inputs are missing: If the attendee is starting from scratch, draft a simple workflow and label it as a proposed starting point. Never imply the Coach has connected accounts or begun running agents.

Your working document

  • Selected bottleneck and current workflow
  • Step-by-step division of AI and human responsibilities
  • Required inputs and tool access
  • Review points, spending limits and escalation rules
  • Small pilot, owner or TBD, and success measure
  • Feedback and next decision

Complete when: One workflow has a clear task split, review gates, an owner and a first experiment.

Build my first reusable skillA reusable instruction document with purpose, trigger, required inputs, steps, decision rules, output format, quality checklist, review points and a worked example.

Capture your steps and judgment so AI can repeat a task your way.

Useful inputs

  • One repeatable task and a real example
  • A narrated walkthrough, existing instructions or description of decisions
  • Required inputs, output format and examples of good and bad results

Work through it

  1. Start with one task. Use a narrated walkthrough, existing procedure or the attendee’s description; ask for a concrete example of good output.
  2. Capture the inputs, steps, reasons behind decisions, quality checks, exceptions and points that need the person’s judgment.
  3. Write a platform-neutral skill draft. Walk it through an example, record corrections and define what would count as a successful first use.
  4. Choose a place to store and share the approved instructions. Identify who will review feedback and update the skill; do not claim installation or automatic synchronization without a verified action.

If inputs are missing: If the process is still implicit, guide a walkthrough one question at a time. Mark missing decisions; do not claim the skill is installed, shared or automated.

Your working document

  • Purpose and when to use this skill
  • Required inputs and examples
  • Workflow and decision rules
  • Human approvals and exceptions
  • Output format
  • Quality checklist
  • Worked example and corrections
  • Feedback process and version owner
  • First real-world test

Complete when: The attendee has a usable instruction draft, has checked it against an example, and knows what still needs testing.

Reuse business context you have already shared. Start with one useful workflow; these paths help you create a working draft and a practical next step. Coaching paths and output templates are Coach-designed applications. This guide does not submit or store answers.

Read all takeaways ↓ · Open session resources ↓ · You can also ask the Coach a question about the session.

Questions about the session

Where should I start if I cannot build the whole system?

Choose one strong marketer as the AI champion, have people capture how and why they work, and build one small reusable workflow. Alex advises against stopping the whole team’s work to make everyone an advanced tool user at once.

Talk · 43:01–49:28; Slide · 54

How do I explain this to the team without making it threatening?

Alex frames the change as an opportunity to upskill people into orchestration and quality control. He says his agency had not let people go because of AI that year and describes investing in their ability to build and improve skills.

Talk · 37:37–49:28; Slides · 45–54

Were the video examples AI-generated people?

No. Alex clarifies that the three edited examples used human creators and that most of his agency’s creative still does. He favors real creators and also sees promise in animation; he reports limited use of AI UGC avatars.

Talk · 57:11–59:22

Which video generation platform does Alex recommend?

He says his team uses Higgsfield, but he had not compared the alternatives closely enough to give an informed cost ranking. His advice in Q&A is to pay attention to the underlying model and whether the interface fits the workflow.

Talk · 59:22–1:00:04

How should I start creator sourcing with Apify?

Specify the creator demographic, niche, examples, keywords and budget. Alex recommends reviewing roughly 100 candidates first, giving feedback and expanding only after the results fit. He describes Apify scrapers connected through an MCP; the Coach can help draft the brief and review criteria, but it does not already have those accounts connected.

Talk · 1:04:53–1:08:17; Slide · 32

Can the Coach build the video review app Alex showed?

The Coach can help define the workflow and prepare a build brief for a coding assistant: brief and footage in, an edited draft, timestamped comments, revisions and a saved feedback loop. Alex says the exact prompt is near the end of his linked video-editing tutorial. That prompt is not reproduced in this session transcript, and his app was local to his own computer rather than a finished shared service.

Talk · 34:54–37:37; Slides · 43–44

How did Alex use Trybe, and what did creators get paid?

He describes Trybe as an amplifier for his agency’s performance model, but says he does not personally run the program. He explains tiered agency pricing based on ad spend and caps, while qualifying his account of the creator arrangement. Do not treat his agency pricing as a verified universal Trybe payout formula.

Talk · 1:01:28–1:04:53

Do I need Parker to use these ideas?

No. Alex explicitly says the method can be implemented without paying Parker. He offers Parker as a way to bring research, shared context and skills together, mentions GitHub as an alternative, and says attendees can ask him for the public skills repository. The transcript does not supply an exact repository URL.

Talk · 43:01–53:34; Slides · 50–64

What was the Parker event offer?

Alex announced 30% off using SML2026; slide 64 specifies the first three months. Treat this as the offer presented at the event, and confirm eligibility, plan availability and final terms with Parker before purchasing.

Talk · 49:28–53:34; Slide · 64

Explore the full session index · 86 entries

The index covers all 64 prepared slides and the complete 156-paragraph transcript in 22 sections. Transcript timestamps include the host introduction. Private and incidental audience details are omitted; demo gaps are identified rather than reconstructed.

Slide 1 — Title and speaker

Title: The Rise of the One-Person Creative Team, presented by Alex Cooper of Parker.

Slide · 1

Slide 2 — Earlier talk / visual reference

Image reference to Alex’s earlier talk. The delivered opening explains the shift toward a person supervising specialist agents.

Slide · 2

Slide 3 — One-person team premise

Frames the move toward a person supervising agents as inevitable; this is the speaker’s outlook.

Slide · 3

Slide 4 — AI roles around a paid-media specialist

Maps research, scripting, static production, video production, media buying and performance analysis around a paid-media specialist.

Slide · 4

Slide 5 — Supplement-brand anecdote

Supplement-brand anecdote about doing more creative work without replacing departed creative staff; it is a speaker-reported example.

Slide · 5

Slide 6 — One operator connected to existing tools

Shows a person connected to existing business tools through an agent environment.

Slide · 6

Slide 7 — Concern about more volume

Introduces the concern that greater output might reduce quality.

Slide · 7

Slide 8 — Ad-performance screenshots

Ad-performance screenshots used as examples. Do not infer a general performance guarantee from the visual.

Slide · 8

Slide 9 — Intentional volume: message, execution, human judgment

Defines intentional volume as researched customer messages, agent execution and human judgment.

Slide · 9

Slide 10 — Intentional volume and team capacity

Connects intentional volume with the capacity of a smaller creative team.

Slide · 10

Slide 11 — Three lessons introduction

Introduces three lessons: the message, delegation and reusable skills.

Slide · 11

Slide 12 — Lesson 1: message first

Lesson one begins with finding the message before making the ad.

Slide · 12

Slide 13 — Ad examples; media areas blank in PDF

Introduces ad examples. Embedded video playback is not preserved in the source export.

Slide · 13

Slide 14 — Same story across creative formats

Explains that the same underlying story can be expressed in animation, native ads and creator-led video.

Slide · 14

Slide 15 — Output volume without message

Warns against producing volume without a grounded message.

Slide · 15

Slide 16 — What focusing on the message means

Transitions into the practical meaning of message-led research.

Slide · 16

Slide 17 — Research agent: research, data processing, external inspiration

Research diagram groups research, customer-data processing and external inspiration; the visual was inspected in the earlier deck review.

Slide · 17

Slide 18 — Seven deeper customer-research questions

Lists seven research questions about use cases, emotional language, objections, triggers, failed alternatives, insider phrasing and metaphors.

Slide · 18

Slide 19 — Shapewear use-case example; reported ad spend

Shapewear example: post-purchase feedback revealed a mother-focused use case. The slide’s $500K+ figure is ad spend, not revenue or profit.

Slide · 19

Slide 20 — Message discovery versus changing format

Argues that useful customer insights matter more than chasing a new creative format.

Slide · 20

Slide 21 — Research and customer-data processing highlighted

Highlights internal research and customer-data processing within the research framework.

Slide · 21

Slide 22 — External creative inspiration highlighted

Highlights external inspiration within the research framework.

Slide · 22

Slide 23 — Organic research report example

Shows an organic-content research report as a source of ideas.

Slide · 23

Slide 24 — Competitor research report example

Shows a competitor research report as another source of context.

Slide · 24

Slide 25 — Weekly research pack and ranked actions

Weekly research pack combines performance, customer voice, competitor and organic research, team discussion and ranked actions.

Slide · 25

Slide 26 — Research output into an ideas bank

Moves selected research ideas into an organized ideas bank.

Slide · 26

Slide 27 — AI research assistance with human judgment

Positions AI as research assistance while people retain critical judgment.

Slide · 27

Slide 28 — Parker research product overview

Describes Parker’s research capabilities as the speaker’s product context, not capabilities already connected to the Coach.

Slide · 28

Slide 29 — Lesson 2: choose what to delegate

Lesson two begins with choosing which work to delegate and which decisions to retain.

Slide · 29

Slide 30 — Task-dependent AI strengths

Notes that AI capability varies substantially by task.

Slide · 30

Slide 31 — Speaker’s personal trust ratings by task

Shows Alex’s personal trust ratings, with low trust in original scripting and more confidence in several execution tasks.

Slide · 31

Slide 32 — Creator-sourcing workflow example

Creator-sourcing example uses a defined brief, budget and scraping tools. Q&A adds the recommendation to review a small sample first.

Slide · 32

Slide 33 — Creator outreach and reply-tracking workflow

Creator operations cover outreach, reply checks and tracking. The delivered talk also describes budget parameters, feedback and escalation.

Slide · 33

Slide 34 — Footage review against a brief and handoff

Footage is checked against the creative brief before moving into editing.

Slide · 34

Slide 35 — Static-ad inputs, copy approval, batches and feedback

Static-ad production starts from strong templates, uses customer language and includes approval and feedback.

Slide · 35

Slide 36 — Static-ad roles and review points

Separates agent work from human approval, launch and learning in the static-ad workflow.

Slide · 36

Slide 37 — Static skill label; demo not visible in export

Shows the Black Friday static-ad skill label. The source export does not preserve its complete live demonstration.

Slide · 37

Slide 38 — Static-ad tutorial reference

Links Alex’s full static-ad walkthrough on YouTube; its QR destination is included in this guide.

Slide · 38

Slide 39 — Landing-page assets, template, persona and QA

Landing-page workflow uses brand assets, a template and persona, approved copy, review and saved feedback.

Slide · 39

Slide 40 — Landing-page roles and review points

Separates choosing a layout, drafting copy, approving the build and authorizing publication.

Slide · 40

Slide 41 — Video-editing examples; media areas blank in export

Introduces video-editing examples; Q&A clarifies that the highlighted edited examples use human creators.

Slide · 41

Slide 42 — Agent-assisted video assembly and editor judgment

Presents agent-driven video assembly and human quality review. Timing and model claims describe Alex’s setup at the event.

Slide · 42

Slide 43 — Video-editing tutorial reference

Links the Emergency Office Hours video-editing tutorial on YouTube; its QR destination is included in this guide.

Slide · 43

Slide 44 — Timestamped review and quality feedback

Shows timestamped feedback and iterative video review. The delivered talk clarifies that Alex’s app is local and not yet shared team-wide.

Slide · 44

Slide 45 — Human responsibilities: ideas, copywriting, taste

Keeps idea prioritization, copywriting and taste with people.

Slide · 45

Slide 46 — Lesson 3: turn processes into skills

Lesson three begins with turning repeated processes into skills.

Slide · 46

Slide 47 — Example reusable skills

Lists reusable skills for sourcing, reports, delivery checks, statics, landing pages and editing.

Slide · 47

Slide 48 — Skills throughout the process; placeholder/demo gap

Shows the idea of skills throughout the process; the export does not preserve every demonstration detail.

Slide · 48

Slide 49 — Record work and explain decisions

Asks strategists, editors and creator sourcers to record work while explaining their decisions.

Slide · 49

Slide 50 — Share skills across the team; placeholder/demo gap

Introduces sharing skills across the team; use the delivered explanation rather than treating a demo placeholder as evidence.

Slide · 50

Slide 51 — Company knowledge folder and synchronization

Shows a synchronized company knowledge folder that sits on team members’ devices.

Slide · 51

Slide 52 — Creative strategy context; placeholder/demo gap

Describes creative strategy context supporting the shared skills. Private client folders are not reproduced.

Slide · 52

Slide 53 — People and agents use shared context

Positions shared context as the working base for people and agents.

Slide · 53

Slide 54 — Choose champions, document decisions, share skills

Action plan: choose AI champions, document decisions, build skills and share them.

Slide · 54

Slide 55 — Marketing expertise and agentic capability diagram

Argues that marketing expertise sets the ceiling and tool fluency amplifies it.

Slide · 55

Slide 56 — Same diagram with product positioning

Positions Parker as assistance with the tool and workflow side of that capability.

Slide · 56

Slide 57 — Product feature list: account analysis

Product feature overview emphasizes account analysis; these are speaker-presented product claims.

Slide · 57

Slide 58 — Product feature list: advertising library

Repeats the product feature overview with emphasis on the advertising library.

Slide · 58

Slide 59 — Product feature list: swipe files

Repeats the product feature overview with emphasis on saving and adapting examples.

Slide · 59

Slide 60 — Product feature list: customer evidence

Repeats the product feature overview with emphasis on customer evidence.

Slide · 60

Slide 61 — Product feature list: connector access

Repeats the product feature overview with emphasis on connector access.

Slide · 61

Slide 62 — Product feature list: shared skills

Repeats the product feature overview with emphasis on shared skills.

Slide · 62

Slide 63 — Product feature list: synchronized context

Repeats the product feature overview with emphasis on synchronized context.

Slide · 63

Slide 64 — Parker event offer

Displays SML2026 for 30% off the first three months. The talk announces the discount; current eligibility and availability require confirmation with Parker.

Slide · 64

Host introduction

Event reminders, speaker introduction and opening conversation. These are not Alex’s teaching.

Talk · 0:00–5:24

The one-person creative team

Alex describes people directing agents and a supplement-brand anecdote illustrating the approach.

Talk · 5:24–8:20

Intentional volume

Maintain a quality bar, start from customer language and avoid ungrounded mass production.

Talk · 8:20–10:46

Message, formats and customer research

Explains message versus format, deeper research questions, the shapewear use case, internal and external inspiration, weekly reports, ranked ideas and human judgment.

Talk · 10:46–19:42

Where to use AI

Personal preferences by task, including caution about original scripting and greater confidence in operational execution.

Talk · 19:42–21:42

Creator operations and static workflows

Sourcing, budgeted outreach, feedback, footage checks and template-based statics. Reported sourcing costs are corrected during the talk.

Talk · 21:42–25:59

Static-ad templates and tutorial

Customer research is applied to curated templates, with example batch economics and a linked YouTube walkthrough.

Talk · 25:59–27:45

Feedback, landing pages and video editing

Explains specific corrections, copy approvals, template-based pages, editing skills, the video tutorial and a local review interface.

Talk · 27:45–34:54

Where to find the review-app prompt

Alex says the prompt is near the end of his video-editing tutorial; he does not recite it in this transcript.

Talk · 34:54–35:43

Local app limits and Frame.io

Discusses the Coach handoff, the local-only app, team-sharing challenges and Frame.io as an alternative. Beta timing is an event-time claim.

Talk · 35:43–37:37

Human judgment and reusable skills

Rejects a layoff interpretation, explains the role of taste and defines skills as reusable processes supported by context.

Talk · 37:37–42:02

Document the reasoning

Capture the choices made by strong team members so repeated workflows can incorporate their expertise.

Talk · 42:02–43:01

Team adoption and shared context

Answers the team-threat question, explains shared company context and skills, mentions an available repository, and recommends AI champions.

Talk · 43:01–49:28

Marketing expertise and Parker offer

Prioritizes strong marketers, explains optional Parker capabilities, announces the event discount and says the method can be used without Parker.

Talk · 49:28–53:34

Host recap and transition

Recaps the broader role of documentation and transitions into audience questions; incidental personal conversation is omitted from takeaways.

Talk · 53:34–55:59

Q&A: human creators and AI avatars

Alex clarifies the source of the footage and discusses real stories, human creators and animation.

Talk · 55:59–59:22

Q&A: generation tools

He uses Higgsfield but does not claim a definitive comparison of platforms or prices.

Talk · 59:22–1:00:04

Host interlude

Fundraiser reminders and audience conversation; no additional creative framework is introduced.

Talk · 1:00:04–1:01:28

Q&A: Trybe and creator economics

Describes the performance model, its effect on risk allocation and his expectation of a more balanced arrangement; he does not run the program personally.

Talk · 1:01:28–1:03:31

Q&A: incentives and pricing

Discusses tiered agency fees and caps while qualifying the exact creator arrangement.

Talk · 1:03:31–1:04:53

Q&A: a practical sourcing pilot

Define the creator brief, connect a sourcing tool, review about 100 candidates, refine the instructions, then expand with budgets and exception handling.

Talk · 1:04:53–1:08:17

Closing

Thanks, break announcement and a reminder that the session will be available through the Coach.

Talk · 1:08:17

Key takeaways

  1. Make more of a message worth hearing.

    Alex calls this intentional volume: start with your customers’ language, let AI produce more executions, and keep a person responsible for quality. Increasing output without a researched message does not create a useful creative strategy.

    Talk · 8:20–10:46; Slides · 9–15

  2. Research the message before choosing the format.

    Look for buying triggers, unexpected use cases, emotional phrases, objections, failed alternatives and words only customers use. Alex argues that a strong story can work across animation, static and creator-led ads; the fashionable format is not the underlying strategy.

    Talk · 10:46–19:42; Slides · 14–20

  3. Turn research into a weekly decision brief.

    Combine account performance, customer voice, organic and competitor research, team observations and ranked next actions. Let AI assemble evidence and suggest ideas; use human judgment to choose what enters the ideas bank.

    Talk · 10:46–19:42; Slides · 23–27

  4. Choose AI’s role one task at a time.

    Alex uses AI as a research assistant and remains cautious about original scriptwriting. He delegates more of creator operations, production and analysis. These are his working preferences, not universal reliability scores: choose the task, inputs and review requirements before automating it.

    Talk · 19:42–21:42; Slides · 29–31

  5. Review a small creator sample before sourcing at scale.

    Define the audience, niche, keywords, examples of good creators and spending limit. In Q&A, Alex recommends starting with about 100 candidates, reviewing the fit and correcting the instructions before expanding. His large sourcing example is not a reason to begin with 20,000 unreviewed contacts.

    Talk · 1:04:53–1:08:17; Slides · 32–34

  6. Build static ads and pages from strong templates.

    Use a curated swipe file, brand assets and customer evidence to produce variations. Alex’s static workflow rewrites template copy from research; his landing-page workflow combines a template and persona with approved copy. Template quality sets an important limit on output quality.

    Talk · 25:59–34:54; Slides · 35–40

  7. Keep people responsible for ideas, words and taste.

    Alex prefers approval points for headlines, copy and final creative. He describes people moving toward orchestration and quality control, and explicitly rejects interpreting the talk as an instruction to dismiss the team. Review should evaluate the actual result, not merely whether the agent finished.

    Talk · 27:45–42:02; Slides · 36–45

  8. Explain corrections so the next run improves.

    Record what is wrong and why: an unsuitable template, changed font, misplaced text, weak cut or poor creator choice. Feed approved corrections back into the reusable instructions. Alex’s improvement loop depends on recording feedback; it is not a promise that any AI tool remembers every correction automatically.

    Talk · 27:45–37:37; Slides · 35–44

  9. Pilot AI-assisted editing with real footage and a review loop.

    Alex describes skills that turn a brief and raw footage into edits, then revise them from timestamped notes. His examples mostly use human creators. He presents simple advertising edits as a useful starting point and distinguishes them from more complex productions; his local review app was not yet a shared team service.

    Talk · 27:45–37:37; Slides · 41–44

  10. Document decisions, not just the steps.

    Record a real task while explaining why you selected an idea, hook, clip, cut or creator. Turn that explanation into a reusable skill with inputs, decision rules, quality checks and examples. Alex sees the team’s accumulated context and expertise as the differentiator.

    Talk · 37:37–43:01; Slides · 46–49

  11. Share the skills and their supporting context.

    Give the team a common place for customer evidence, brand context and approved skills, plus a way to contribute corrections. Alex demonstrates Parker’s shared company context and also mentions GitHub as an option. The method does not require buying Parker.

    Talk · 43:01–49:28; Slides · 50–54

  12. Start with a capable AI champion.

    Choose a strong marketer who is curious about the tools to build and test the first workflows. Have the wider team document its work and contribute expertise without requiring everyone to master the tooling at once. Alex frames this as upskilling, with marketing judgment remaining central.

    Talk · 43:01–53:34; Slides · 54–56

  13. Separate AI editing from AI-generated creators.

    In Q&A, Alex clarifies that the edited examples used real creators and that most of his agency’s creative still does. He favors real people telling real stories and sees animation as another useful way to express a message. His limited enthusiasm for AI avatars is a personal practice, not a blanket rule for every brand.

    Talk · 57:11–59:22; Slides · 41–45

Resources from the session

WATCH THE WORKFLOW

How to Make 100 Static Ads/Day in Claude Code (Full Step-by-Step Walkthrough)

Use Alex’s walkthrough to turn a swipe file, customer language and brand context into a repeatable static-ad workflow.

Why use it: Watch this when you want to build your first static-ad skill, including a Black Friday variation. Start with a small batch and review the copy and final ads.

Get started: Gather a few suitable templates, your brand assets and customer evidence. Watch the walkthrough, then use Build my first reusable skill to adapt the process to your business.

Watch on YouTube →

Alex Cooper · shared on slide 38. Examples and tool details reflect the tutorial; results depend on your inputs and review.

Scan to watch How to Make 100 Static Ads/Day in Claude Code (Full Step-by-Step Walkthrough)
Scan to watch on YouTube.

WATCH THE WORKFLOW

Emergency Office Hours: AI Video Editing Workflow

Alex’s longer walkthrough of AI-assisted video editing, referenced during the session.

Why use it: Watch this when you want to move from a brief and raw footage to a reviewed video draft. Alex also points to a prompt near the end for building his local review interface.

Get started: Have one brief and a small set of footage ready. Watch the workflow, then use Map my AI creative team or Build my first reusable skill to plan a reviewed pilot.

Watch on YouTube →

Alex Cooper · shared on slide 43. Examples and tool details reflect the tutorial; results depend on your inputs and review.

Scan to watch Emergency Office Hours: AI Video Editing Workflow
Scan to watch on YouTube.

FROM THE SPEAKER

Parker — research and shared marketing context

The platform Alex demonstrated for bringing customer research, creative context and reusable skills together.

Why use it: Explore it if you want the research and shared-context approach Alex demonstrated. You can also apply the method with other tools.

Get started: Review the current product and plans. Alex announced SML2026 for 30% off; slide 64 specifies the first three months.

Visit website →

The offer is attributed to the event presentation. Confirm eligibility and final terms with Parker; using this Coach does not require buying Parker.

Examples from the session

Shapewear: customer feedback revealed a mother-focused use case that became an advertising angle. Alex reports substantial spend behind it; the deck labels $500K+ as spend, not revenue or profit. Talk · 10:46–19:42; Slide · 19

Static-ad batches: Alex illustrates using customer language across a set of curated templates, reviewing the results and feeding corrections into the next run. His generation-cost and usable-output examples are illustrative, not a forecast. Talk · 25:59–34:54; Slides · 35–38

Video review: his local app accepts timestamped comments, applies requested changes and brings back another draft. During the talk he says team-wide sharing was not yet solved. Talk · 27:45–37:37; Slide · 44

Creator sourcing: the large-list story is followed by a smaller starting recommendation in Q&A—review roughly 100 candidates, correct the brief and expand only once the fit is useful. Talk · 21:42–25:59; Talk · 1:04:53–1:08:17; Slide · 32

Context to keep in mind

  • Performance, cost and time examples are speaker-reported. The creator-sourcing cost is corrected and expressed differently during the talk and Q&A; do not quote one precise figure as a universal budget.
  • AI trust ratings, model names, editing forecasts and beta timing describe Alex’s views and setup at the event. Check current tool requirements before implementing a workflow.
  • The transcript contains transcription errors in product and model names. Brand spellings are reconciled with the slides; model-specific claims remain attributed rather than treated as universal capability promises.
  • Prepared slides and the delivered talk are indexed separately. Embedded video playback is not preserved in the source export; the two linked tutorials have not been separately transcribed into this library.
  • Alex’s local review app was not a released team product. The transcript mentions a build prompt in the video tutorial but does not include the exact prompt.
  • A public skills repository is mentioned without its exact URL. Ask Alex for it rather than assuming a similarly named repository is his.