Skip to content
LaunchBoxHelp
← Launch & Learn

October 28, 2026 · With Ian McDonald

Let your agent help with the work you already do.

An event becomes an announcement. Everyday work becomes a lesson. A look back at your week reveals a task worth automating. Revisit the examples, then choose one small result to try yourself.

Follow the member questions, course examples and connection walkthroughs, then use the adapted prompts below to try one useful task.

Edited replay · 58 minutes 16 seconds · 14 chapters
Edited session recording · 58 minutes 16 seconds · English captions available with CC
Chapters & searchable transcript ↓

Start with the outcome

One useful task. One clear owner.

You do not need another tool to begin. Start with the assistant and work you already have, check what it can access, and ask for one result you can inspect.

Your practice goal: identify one repeatable task, test it once and decide whether a schedule would help.

Members brought their own examples: a narrated course lesson, a NotebookLM-to-video workflow, a twenty-week course, and agents helping with everyday administration. The common thread was finding the next useful step in work already underway.

The workflow Ian showed

Ask for an event. Check the result. Share it.

Ian revisited a conversation with Grok Bot in which he requested Connect and Create, reviewed the details and approved a one-time event. He then asked for a feed announcement linked to that event.

  1. 01 · AskGive the title, date, time zone, location, audience and recurrence.
  2. 02 · ReviewRead the proposed details before the event is made visible.
  3. 03 · ApproveConfirm the specific action and destination.
  4. 04 · VerifyOpen the saved event and check its details.
  5. 05 · ShareRequest an announcement and review that publication separately.

The example was for October 29 at 9 p.m. Eastern / 8 p.m. Central, public and one-time, in LaunchBox’s built-in live room. It was upcoming when this session was recorded. Normal community and event access rules apply.

Prepare an eventPrepare the details for [event title] on [full date] at [time and time zone], hosted [in LaunchBox / at this meeting link / in person]. Make it [public / members only] and [one-time / recurring]. Write a short description for [audience]. Show me the complete details before saving or publishing, and ask about anything important that is missing.

An event date schedules a gathering. A recurring agent task needs its own trigger, instructions and saved schedule.

Member work and questions

You may already have something worth teaching.

A finished task becomes a lesson.

Ian showed an existing Android home-screen lesson made from work with his assistant. Its chapter structure, prompts and checkpoints turn a completed project into something another person can follow.

Choose work you understand, then ask your agent to help explain the outcome, materials and sequence.

The session revisits a prepared lesson. It does not show the complete lesson-authoring process from scratch.

A course becomes easier to organize.

Annette shared a narrated lesson, Jasheena described moving a slide deck into Google Vids, and Ron asked how new learners could begin his longer course.

The useful structure is course → modules → lessons. Organize the teaching around a learner’s starting point and the next result they need.

The tools and interfaces shown reflect the session date. Use current Help for setup and availability.

Turn existing work into a lessonI have just completed [describe the work]. Help me turn it into a beginner-friendly draft lesson for [audience]. Identify the outcome, required materials, steps and a way to check success. Include prompts people can adapt. Separate what we actually did from optional next steps. Show me the outline before creating or publishing anything.

Ian also requested artwork for a lesson missing its thumbnail. The transcript records an image being prepared; it does not establish that the image was successfully attached to the live lesson.

Your practice path

Look back a week. Find one useful pattern.

Ian’s challenge was to ask the assistant you already work with what it could take off your plate. Use accessible conversations, notes, files or project records. If your assistant cannot see other chats, give it selected material instead.

Inspect my existing automationsCheck the scheduled automations you can actually access. List each task’s purpose, owner, status, schedule and time zone. Show its latest run and delivered result if available. Flag overlapping tasks and missing access. Do not create or change anything yet.

Review my last seven daysReview my last seven days of accessible conversations, notes, files and project records. Tell me which sources you checked and which were unavailable. Find recurring tasks worth automating. For each, show a real example, the inputs needed, suggested timing, the output I would receive and decisions I should keep. Check existing automations to avoid duplicates. Rank the best three suggestions. Do not schedule anything yet.

  1. Choose one. Pick a small task with available inputs and an output you can check.
  2. Define it. Agree on sources, owner, timing, time zone, result, delivery location and approval limits.
  3. Test it. Run it once and inspect the actual result. Correct the instructions if needed.
  4. Schedule it. Save the tested task and confirm the next run. A proposal in a chat or tracker is not a saved schedule.
  5. Check delivery. Inspect the first scheduled run: did it start, finish and produce the result?

A useful first test.

Ask for a private weekly recap from selected project notes: completed work, open items with source dates and up to three suggested next actions.

Keep it private while you test the sources and format. Decide on timing only after the output is useful.

Choose how much help you want.

  • Manual: you make the decision or perform the action.
  • Assisted: the agent prepares a draft for review.
  • Automatic: a defined trigger starts a task within agreed limits.

A schedule marked enabled tells you it is switched on. Its saved result tells you whether it worked.

Test before schedulingUse the task we chose to write a short brief: owner, sources, trigger or schedule, time zone, output, delivery location and approval limits. Explain how to handle missing information and avoid duplicates. Run it once for my review. Wait until the result is useful before creating a recurring schedule.

Schedule the tested taskSchedule this tested task using our agreed brief. Reuse an existing matching automation. Confirm the saved schedule, time zone, delivery location and next run. Explain anything required for it to run. If this app cannot schedule it, identify the setup step. After the first scheduled run, help me check the actual delivered result.

These exercises develop the challenge from the call. The recording does not show an attendee completing the seven-day review or creating a new scheduled automation.

An additional verified workflow

A document can become a community post.

Ian also asked his assistant to turn the Launch & Learn guide into a post. The assistant read the Google Doc through the connected document tools, adapted it for community readers, published through the LaunchBox MCP, and read the saved post back to check the text, author and destination.

  1. 01 · ReadUse the approved document as the source.
  2. 02 · AdaptKeep the useful teaching; leave private notes and internal records out.
  3. 03 · PublishConfirm the community, author and publication instruction.
  4. 04 · VerifyRead the saved post and return its link.
Open the published Launch & Learn post

Turn a document into a postRead this document: [link]. Turn the relevant content into a clear post for my LaunchBox community. Keep verified facts and clearly label pilots. Omit private notes and internal records. Confirm the destination and show me the draft. After I approve publication, publish through the LaunchBox connection, read the saved post back and return its link.

This is a supporting example verified in Ian’s working chat, rather than an additional step claimed to appear in the recording. Reading a document requires access to its source; publishing requires a separate LaunchBox connection and permission.

Connection help

Check the connection before asking it to do more.

Members raised useful questions about reconnecting, choosing the right LaunchBox and discovering available tools. Start with the current guide for your assistant and review the account, community and permissions.

Check my LaunchBox connectionInspect the LaunchBox tools actually available in this chat. Tell me the connected community, my role and the tasks my approved permissions allow. If anything is missing, explain the next setup step. Read only for this check; do not post, reply or change anything.

My agent found a different LaunchBox.

Use the official connection link from launchbox.space or your community’s Bring your AI entry. Review the community name on the consent screen. A similarly named search result is not the same service.

It says I need to reconnect.

Follow the current guide for your assistant, then inspect the tools it can see. An older connection may not include newer permissions. If it disconnects again, save the exact error and the step that failed so support can investigate; do not assume the task succeeded.

Can I give my members the owner link?

Use your community’s member connection link for members. Owner management and member participation have different permissions. A connected assistant still needs the specific access required by the task.

Can my agent join the live call chat?

Ian experimented with this during the session, but it did not work as intended. Treat that part of the recording as an experiment. It is separate from the demonstrated event and community-post workflows.

Take one next step

Bring back a result you can show.

A useful test, a specific question or a screen showing where you got stuck is enough. You can keep work private while you learn.

Your checklist stays in this browser.

Download the prompts and checklist

Revisit the conversation

Chapters and searchable transcript.

Find a demonstration or question by chapter, or search for a word in the transcript. Captions, chapters and transcript timestamps follow the edited replay.

58 minutes 16 seconds · Edited session recording · English captions available with CC
Open recording (791 MB) · Download transcript · Download captions
To save the video, use the player’s download menu.

This replay has been reviewed and trimmed where needed. Teaching, demonstrations and Q&A are retained. Chapters and captions follow the edited recording.

Jump to a chapter

Session transcript

Automatically transcribed from the recording and aligned to this edited replay. Wording and speaker labels may contain errors. Choose any timestamp to play that moment.