For workshop participants
Build from your own business.
Bring one goal and one example of your work. We’ll use them to create a useful draft for your audience, check it together and plan your next step.
Before the workshop
Seven things to check before you arrive.
- Confirm the exercise with your organizer. What are we building, which AI product will we use, and what counts as a useful result? Use your event-specific instructions to confirm the required plan before buying a subscription.
- Bring a laptop and charger for the hands-on setup lane. Use a laptop for desktop installation steps; a phone can support discussion and public-reference exercises. Tell the organizer about accessibility or device constraints before the event.
- Check your actual account, plan and permissions. Claude, Codex, Cursor and other products have different capabilities and installation routes. Some features need a paid plan or administrator approval. Use the current provider-specific setup guide; confirm the route supported by your product and plan.
- Bring one measurable business goal. For example: prepare one source-backed draft for one clearly defined audience and offer. We use GCT: Goals, Content, Targeting. A new entrepreneur should start with one audience, a specific technique and one offer or package.
- Bring one source asset you may use. A public business URL, an approved recording, a review, an article or a genuine example of your work. Keep source links. Use approved public or synthetic material for a projected demo, and keep passwords, sensitive customer records and private messages off the shared screen.
- Test one bounded task before arrival if you can. If you install a skill, open a fresh task, select it through your product’s supported controls and inspect the saved output. Record the actual instruction/source used, what happened, what failed and what you changed. Keep the completed installation steps and inspected task output as your evidence; a model’s “skills loaded” response alone does not establish installation.
- Prepare a fallback. Save an approved sample and this checklist. If account access, Wi-Fi or an installation is not ready, use the public or synthetic exercise or pair with a prepared participant. Record the exercise you completed and the installation steps still to finish.
After your first exercise
Keep a record of what you built.
Start with a public or synthetic exercise. Installing skills, connecting private accounts and scheduling work each have their own setup and permission checks. Use this table to record the stage you reached and the next step.
| State | Evidence to keep |
|---|---|
| Public exercise | A sourced draft with the goal, audience and unknowns clear. |
| Installed skill | Supported install completed, actual selected instruction identified, new task output inspected. |
| Connected workflow | Scoped account permission plus a safe test with its approved input and output. |
| Recurring operation | Supported trigger, approved scope, an observed execution and a reviewed result. |
Choose the tools your task needs.
Dictation can help you explain the business more naturally. Use a tool you already trust, such as your device’s dictation, or Wispr Flow if it suits your setup. You can also type your brief and use the same framework.
Connect only the services the selected task needs, with the account owner’s approval. Begin with the public-source exercise using approved material. Inbox connections, memory sharing and schedules are separate, optional setup steps for work that needs them.
Download the instructor guide if you are facilitating, or the Hypergrowth review workbook to see a worked teaching edition.
For organizers and facilitators
Rehearse the path you send to attendees.
Before each workshop, confirm the event brief, chosen runtime, plan requirements, example permissions and first-result test. Check the links anonymously on desktop and mobile. Keep one named owner for the event’s resource page and PDF edition. Route current software instructions through the maintained setup guide rather than copying changing menus into every workbook.
After the workshop, use Metrics → Analysis → Action: what was actually completed, where did people get stuck, and what should change? Capture the evidence, update the source instruction, test the correction, then refresh the dependent materials. For recurring work, observe a scheduled run and inspect its output before recording the schedule as active.
Stuck? Tell us the exact step.
Send the product and plan, the step you reached, what you expected, what you saw and a screenshot with private information removed. Your organizer or facilitator can help route it. Keep credentials and private customer data out of your support message.
Product and plan · exact step · expected result · actual result · redacted screenshot. Use the contact supplied with your event instructions.
This checklist is shared across workshop groups, including Hypergrowth. Event dates, venues and participation requirements belong to the organizer’s current event instructions.