The Automation Engine.

• 1.1

  The workbook and the files

  An HTML workbook that opens in any browser, plus the artifacts it teaches with: the task-map canvas, the tool decision table, two wiring checklists, an RCTF prompt template with an output contract, and the weekly monitoring checklist. All copy-paste ready. No app, no login, no videos to scrub.

• 1.2

  Who it's for

  Solo operators and tiny teams drowning in the same weekly chores — reporting, triage, moving data between tools by hand. No code required: every required step happens in n8n's or Zapier's visual editor. If you want to automate decisions about people, the course will mostly tell you not to, and explain where the line is.

• 1.3

  The guarantee

  30 days, money back, no interrogation. If the Engine doesn't earn its $30, email us and we refund it. We'd rather keep your trust than your thirty dollars.

• 2.1

  Map the task on paper

  Before any tool: frequency, trigger, steps, inputs, outputs, and the current cost in minutes. The "five tasks you hate" inventory, and the filter for picking the first one — recurring, boring, low-risk, at least 30 minutes a week. When to automate versus when to just do it, because some tasks cost more to automate than to keep. You leave with: a one-page task map and a timed baseline you'll re-measure in Module 6.

• 2.2

  Choose the tool honestly

  n8n versus Zapier versus a plain script, decided by your volume and your patience rather than by your feed. Where Zapier's convenience wins (standard SaaS, low volume), where n8n's self-hosting wins (high volume, custom logic, cost per run), and when a 20-line script beats both. The real math: cost per run times runs per month. You leave with: a decision table filled in with your task and your numbers.

• 2.3

  Wire the workflow

  Trigger, steps, branching, and the error branch most people skip. Built around the two patterns that pay for themselves fastest: draft email routed to a triage folder, and a weekly report skeleton assembled from live data. Test with real data — toy inputs pass workflows that break on Tuesday's actual files. You leave with: one working workflow and the two wiring checklists — Checklist A to go live, Checklist B to carry the next ten.

• 2.4

  The LLM step that doesn't hallucinate

  Grounding: fetch the facts into the prompt; never ask the model to recall what you can hand it. Structured output contracts — fixed fields, not essays — so the workflow can fail loudly instead of guessing. The human checkpoint for anything a person will act on, and the honest rule for when the LLM step is allowed to be creative: almost never. You leave with: an RCTF prompt, an output contract, and your checkpoint placed.

• 2.5

  Failure handling and monitoring

  Automations fail quietly, which is worse than failing loudly. Retries with backoff, a dead-letter path for the runs that keep failing, and an alert that pings you — not a dashboard nobody opens. The three numbers to check weekly: failed runs, run duration, volume. You leave with: the failure branch added to your Module 3 workflow and a five-minute weekly health check.

• 2.6

  Measure the hours saved

  Re-time the task. Before and after, in minutes per week and hours per quarter — and what you'll actually do with them, because recovered hours that evaporate into email were never recovered. Kill-or-scale criteria: fix it, keep it, or delete it. You leave with: your measured before/after and the next two task maps, sketched and queued for the next 30 days.

• 3.1

  Order

  The buy button opens a pre-filled email. We reply with a secure payment link, and your course arrives by email within 24 hours of payment. Card checkout is being wired and will replace the email step shortly.

• 3.2

  Work it

  Self-paced; one module per evening is a realistic clip, and the workflow from Module 3 can be live the same week. Each module ends with a finished artifact, and free updates ride the same email channel — when a module improves, the new version lands in your inbox.

• 3.3

  Bring questions

  Reply to any course email with a question about your own setup. A human answers it — usually with a simpler version of the workflow than you were about to build.

Every buy button opens a pre-filled order email — we reply with your secure payment link within 4 business hours (Mon–Fri, CET), and files follow within 24 hours of payment. On a phone? Email hello@upshift-ai.com directly and we'll send your payment link.