01 / The course / Week 1
Build something that works
Set up your own laptop with us, then build a briefing from one approved source. You leave with something that runs.
- 1A
Set up together, then build
Set up your own laptop with us. Build a first working automation: a briefing that reads one approved source.
Practice Run it again tomorrow and check it against the source.
- 1B
Change it, break it, fix it
A repeatable way to build: brainstorm, plan, build, verify. Make a change on purpose and recover from it.
Practice Add one thing you want and keep the version that works.
You learn what you need when you need it, on something you actually want to work.
02 / Your project
Two months. Your workflow.
Twice a week, one-on-one with a builder, working from the brief you wrote in the course until the workflow is in use.
One-on-one sessions for each participant, with a builder.
Continuation can be agreed as needed.
One workflow, its users, and the approved sources it needs.
Parts that need a dedicated developer are scoped as Build and care.
The pattern from the course, read approved sources, summarize, schedule, verify, stop, is the skeleton of every workflow you build here.
03 / Build and care
The parts that need a builder
Dedicated development and ongoing care, agreed apart from the course and the project sessions.
Ask us to deliver an agreed workflow, with clear checks and an owner who knows how to use it.
Your people build with help in their sessions. We take the parts that need a dedicated developer.
Access controls, credential handling, and connections to company systems.
Audits, security hardening, and fixes for the code and connections we own.
Agree which parts we own, the checks required, and the maintenance terms. Every project uses company-approved access.
