Louise de Sadeleer used to sit down to edit a one-minute video and lose time trying to find the post or screenshot she wanted on screen. Now she sends the reference to Grok Bot from her phone when she finds it. It goes into the right video project, so when she sits down to edit, the material is already there.
In her conversation with Greg Isenberg, the Tella team member shows how she applies the same idea to the rest of her week. She delegates collecting, sorting and first-pass edits. She still picks the creators, writes her own scripts and decides what goes live. Louise says she gained 6,500 Instagram followers over three months while using this workflow. That's her reported result, not a measurement of how much growth the bot caused.
Watch the Episode
Source Note: The 18 November 2026 episode and transcript are the sources for Louise's workflow and performance claims. We checked the product documentation on 19 November. Louise works at Tella, whose editor she demonstrates. The starter prompts below are JQ AI SYSTEMS adaptations, not exports of Louise's or Miranda's instructions.
Louise's Workflow at a Glance
- CaptureSend ideas, hooks and B-roll from your phone.
- ResearchGather outliers, trends and keywords weekly.
- PlanPolly and Trend Steady pitch ideas. Louise picks one.
- Script & editLouise writes. Skills critique. Tella applies edits.
- PublishYuri drafts metadata. Louise reviews and publishes.
Four Weekly Research Routines
Louise curates her own list of creators in Notion. The work she hands off is scanning that list and filing useful examples. Weekly runs are enough for her planning rhythm, and less demanding on usage than running each routine daily. The Grok Bot docs recommend testing a task once before scheduling it.
| Routine | What Louise collects | What to check before using it |
|---|---|---|
| Creator outliers | Unusually strong posts, with the link, topic, hook and performance against the creator's usual range. | Compare like with like. One creator's average is more useful than a universal view threshold. Don't call the hook the cause just because the post did well. |
| Saved hooks | Opening lines from her saved TikToks, grouped by format such as a question, a contrast or a relatable observation. | Borrow the structure, not the wording. Use links or your own notes where direct collection access isn't available. |
| Trend digest | Signals from newsletters, X and news outlets. Miranda wrote the original instructions; Louise added sources. | Count independent evidence, not five accounts repeating one story. Limit access to the sources you need, and keep private or paid material out of public drafts unless cleared. |
| Rising search terms | YouTube Yuri checks vidIQ's Rising Keywords for ideas. | A rising term is a lead, not an assignment. Make the video only if you can answer a real viewer question or show something useful. |
Give Two Bots Different Inputs
Every Monday, Louise plans with Production Polly, the bot that manages her Notion calendar and knows the ideas and hooks she's already saved. Trend Steady tracks what's being discussed. In a Grok Bot group chat, the two combine her backlog with the week's research and pitch three ideas. Grok Bot's collaboration guide documents working with bots in chat.
The split is worth copying even without two bots. Read the research first, then judge which ideas your audience actually needs and what you can show on camera. Pick one, and reserve time to script, record and edit it. Let the bot propose time blocks; confirm changes to your real calendar yourself.
Use Skills as Script Editors, Not Ghostwriters
A bot has a job and its own working context. A skill captures a repeatable method, such as reviewing a hook or filing a link. A routine decides when to run the work. In practice, you can put several skills in one production bot and add a specialist only when it has different sources or a distinct job.
Louise writes her script and then uses three different reviewers: the idea advisor checks whether there's anything worth saying; the hook advisor checks the opening against saved formats and her own templates; the script advisor checks structure. Her Miranda Feedback skill draws on feedback from her short-form course mentor. The reusable part is the reviewer rubric. Use notes you have permission to share, and treat the output as an approximation, not something the mentor said.
Collect B-Roll Before You Open the Editor
At 33:18, Louise shows the link between her phone and the edit: Production Polly uses the Tella MCP connection to add a screenshot to a named project's media library. Grok Bot takes the instruction; Tella performs the edit. That distinction matters if you're using another editor: you need a way to deliver the assets to the project, not just a smarter chat model.
Once Tella is connected, attach a photo, screenshot or clip you have permission to use in Grok Bot on your phone. Paste this prompt with the exact project title or link. It files the asset without placing it on the timeline.
Send B-roll to the right Tella project
Send B-roll to the right Tella project
Give each video one home for footage, screenshots, candidate cutaways and source links. Include where you'd use a visual and whether it's cleared for use. After recording, try a first pass that removes obvious retakes or long pauses from a duplicate project. Review whether a cut changed the meaning or made the speaker sound rushed before adding effects.
Louise's editing model preference is Claude Opus 5.5 at medium effort for most work, with Fable 5.2 reserved for demanding 3D or Blender work. That's her experience with her tools, not a Grok Bot model-picker instruction or a benchmark. Better references and narrower edit instructions are worth testing before paying for more reasoning.
Watch Louise's separate Claude and Remotion example
In this companion video from Will Leatherman, Louise explains how she uses a timestamped transcript to choose where motion graphics would help an educational video. It's a separate workflow from the Tella MCP demo above.
Draft the Upload, Keep the Publish Button
YouTube Yuri checks the transcript and keyword ideas, then drafts title options, a description and chapters. Louise says she publishes from Tella; Tella documents that handoff. Drafting metadata and making a video public are separate actions. Review the exact video, title, thumbnail, channel and visibility before approving any upload or publication. Use Ask first rules where supported, and leave publishing disconnected during the pilot.
Check chapter timestamps against the final cut, after edits and retakes. YouTube's chapter rules require an opening timestamp of 00:00, at least three ascending timestamps, and sections of at least 10 seconds. Louise's example of a Remotion video drawing around 50,000 views illustrates why she looks for rising terms. It doesn't establish that using vidIQ guarantees a ranking or that search drove all those views.
A One-Video Pilot and Four Starter Prompts
Start with one video, five hand-picked creators and one place to collect references. Run the research by hand with the bot once, pick a pitch, and use one script critique and one metadata draft. Track how many references you actually use, how much time you spend fixing the output, and whether you made it to a finished cut. Schedule only the parts that saved time.
Find outliers from my creator list
Find outliers from my creator list
Turn trend evidence into three video pitches
Turn trend evidence into three video pitches
Review an opening without rewriting my voice
Review an opening without rewriting my voice
Draft the YouTube package from the final cut
Draft the YouTube package from the final cut
Video Chapters
| Time | Topic |
|---|---|
| 00:00 | Intro |
| 02:32 | Why Grok Bot fits video creation |
| 07:26 | Research routines: creators, outliers and hooks |
| 15:14 | Trend digests and rising keywords |
| 20:04 | Planning your content week |
| 24:25 | Scripting and bot group chats |
| 26:29 | Advisor skills for ideas, hooks and scripts |
| 29:25 | Bots vs. skills |
| 33:18 | Editing video from your phone |
| 41:43 | Publishing to YouTube |
| 43:50 | Why video, and owning a search term |
| 46:40 | Picking a model for video editing |
| 49:39 | Wrap |
Louise de Sadeleer on X
Posts by @LouiseDSadeleerFrom her feed: why Louise moved her video editing to the cloud.
Louise's post on switching to cloud editing