Intermediate cohort
GHS 750
Standard rate GHS 1,000–1,200
The five-week training only.
Stage 2 training · live online
Intermediate cohort — five Saturdays, live online
Five weeks for builders who can already make workflows and now need to design them professionally, diagnose systems they did not build, and handle the client work around them.
The cohort
- Length
- Five Saturdays
- Live time
- Two hours each week
- When
- 11:30–13:30 GMT
- Format
- Live online
- Places
- 25
What a buyer needs to know
- Starts
- Revised date being confirmed
- Founding Cohort Rate
- GHS 750
- With BCAB assessment
- GHS 1,050
- Assessment-only route
- Available separately through Path B
Want the assessment without the training? Path B remains open to working practitioners. Use the readiness-review route on the certification page.
Who this is for
This is the next taught step for Foundations graduates. It is also for working builders who already know how to get a workflow from trigger to output without being shown every click.
You should already be comfortable reading workflow data, using expressions, connecting an application or API, branching logic, and basic error handling. You should be able to explain what a workflow is doing and test whether it actually produced the intended result.
Check your readiness first
The readiness self-check is eight practical things you should be able to do without looking anything up. It is for your own judgment; nobody marks it and you do not submit it.
You do not need to have decided that you want a professional credential. The cohort is training. The BCAB assessment is a separate product and a separate decision.
What changes from Foundations
Foundations teaches you to build a workflow. Intermediate changes the standard of the work.
| Foundations | Intermediate |
|---|---|
| Follow a build and understand what each step does | Receive a requirement and decide the approach yourself |
| Build your own workflow from scratch | Diagnose workflows you did not build, including broken and half-built systems |
| Handle ordinary data and failures | Design for incomplete data, duplicate work, partial failure and wrong-but-valid output |
| Connect an application or API | Work from unfamiliar API documentation without a walkthrough |
| Build the technical solution | Scope, price, communicate and support the work as client work |
Scroll the table sideways to see every column.
The five weeks
One project grows across all five weeks. There is no final-week capstone crunch. The structure shifts from “follow me” to “here is the requirement, you decide” — you will not all be building identical workflows.
-
Week 1
Complex data
You work with nested objects, arrays, multi-item data and missing fields rather than clean examples. Split, Aggregate and Merge become tools for shaping real workflow data instead of nodes you have merely seen before.
You also decide when the Code node has earned its place and when ordinary nodes are clearer. Pinned data is used as a testing tool so you can isolate behaviour without repeatedly running an entire workflow.
-
Week 2
Real API integration
You move beyond simple GET requests into POST, PATCH and DELETE, and deal with authentication patterns, pagination, rate limits and status-code literacy.
You are given an unfamiliar API and its documentation, with no walkthrough. The task is to work out what the API expects, what it returned, and what the workflow should do when that answer is not the one you hoped for.
-
Week 3
Workflow architecture
You break larger automation work into sub-workflows and reusable components, with naming and configuration that another builder can understand. Values that belong in configuration stop being buried in nodes.
State and persistence become deliberate design choices. You work through deduplication and idempotency so the system can recognise work it has already done and behave predictably when requests repeat.
-
Week 4
Troubleshooting and reliability
This is the centrepiece. You deal with silent failures, partial failures and workflows that execute successfully while producing the wrong business result. Observability, run IDs, dead-letter patterns and recovery workflows give you evidence instead of guesswork.
The diagnostic lab gives you a broken workflow you did not build. You are not told how many defects it contains. The work is to find what is actually wrong, distinguish causes from symptoms, and recover it without making the system harder to trust.
-
Week 5
Production AI and automation design
You decide where AI should and should not make decisions inside an automation. Structured output, validation, confidence, fallback and human-in-the-loop controls are treated as design requirements, not optional polish.
You also judge an agent against a workflow. The question is not which approach looks more advanced. It is which one gives the business the control, reliability and explanation the requirement actually needs.
The business thread
Every week pairs the technical subject with one part of doing client work.
- Week 1: Positioning, and where client work actually comes from.
- Week 2: Discovery and scoping: interviewing a client, and writing down what is not included.
- Week 3: Pricing models and the one-page proposal.
- Week 4: Customer service and incident communication: telling a client something broke before they notice.
- Week 5: The monthly maintenance retainer: what is included, what is excluded, and what to charge.
Most builders ship a workflow and walk away. A maintenance retainer is how one build can become recurring income when both sides know what support includes, what it excludes, and what it costs.
This is not part of the BCAB assessment
The BCAB assessment measures technical competence against the seven published competency domains. Positioning, scoping, pricing, proposals, customer service and retainers are taught alongside that work, but they are not assessed or credentialled.
What a Saturday looks like
The live session is two hours. It is not designed to contain all of the building.
- Homework debrief — what worked, what failed, and what needs to be understood before moving on.
- Business thread — the week’s client-work topic and the decisions around it.
- Concept framing — the technical idea, why it matters, and the failure modes to look for.
- Hands-on clinic — focused work on the hard parts rather than a two-hour follow-along build.
- Pairing — rotating partners are set for the week’s work and the requirement is handed over.
- Portfolio checkpoint — what evidence you need to keep, explain and be able to defend.
Between sessions
Substantial building happens between Saturdays. The shorter live session does not reduce the weekly commitment.
You work in pairs, with partners rotating across the five weeks. The aim is to make you explain decisions, read someone else’s work and deal with approaches that are not identical to your own.
Not every assignment starts with a blank canvas. Some weeks use supplied broken or half-built workflows so that troubleshooting, recovery and professional judgment get the same amount of practice as building from scratch.
Plan for the two live hours plus midweek paired homework. The exact amount of homework varies with the requirement and with how quickly your pair can diagnose what is in front of you.
Before Week 1
- A setup clinic runs before the first session. It is recorded, and comes with a written guide.
- A short proof-of-setup task is due 48 hours before the cohort starts — create a table, insert a row, call the REST endpoint, and screenshot the JSON.
- You will need a Supabase account (the free tier is enough).
- By Week 2 your webhooks must be reachable from the internet. Localhost is not enough. We will confirm the method before the setup clinic.
Who this is not for
- People who have never built a workflow. Start with Foundations — it is free.
- Anyone who cannot commit two live hours a week plus paired midweek homework for five weeks.
- Anyone who wants only the technical training and has no interest in client work. Client positioning, scoping, pricing and support are part of this cohort.
- Anyone expecting the credential to produce a job. It does not.
Where certification fits
The Intermediate cohort is training. Completing it qualifies you to attempt the BCAB assessment; it does not award the credential.
The assessment is a separate product and can be taken without buying this training through Path B. It measures technical competence against the published standard.
Pricing
These are Founding Cohort Rates. Future cohorts are priced at the standard programme rate.
Most complete
Intermediate cohort + BCAB assessment
GHS 1,050
Standard rate GHS 1,500–1,750
- Intermediate cohort training
- GHS 750
- BCAB certification assessment
- GHS 450
- Pathway bundle
- − GHS 150
- Total
- GHS 1,050
Training and the assessment opportunity are line-itemed separately, because they are separate things.
Path B readiness review
GHS 150
Standard rate GHS 200
Credited against the assessment fee if you proceed.
Payment plans
- Intermediate only — GHS 400 at enrollment, GHS 350 before Week 3.
- Cohort and assessment — GHS 400, then GHS 350, then GHS 300.
- Payments do not extend beyond the five-week programme.
- A missed instalment pauses access until it is paid.
Foundations Cohort 1 graduates keep the Ghana rate wherever they now live. We confirm that against the cohort roll before payment.
Read the Refund and Cancellation Policy — cancellations, transfers, payment plans, and what happens if we cancel.
Facilitator
Johnathan Lightfoot is the founder of Bulletproof Automations and creator of the Bulletproof Automation Builder Pathway. His approach comes from more than three decades around technology leadership, systems integration, application development and business systems where the work has to hold up after the demonstration ends.
Questions
What if I miss a session?
Tell us as early as you can and we will work it out with you. This is a paid cohort of 25 people, not a lecture hall — a missed week is handled individually rather than by policy.
What is the real time commitment?
Two live hours on Saturday plus paired midweek homework. Substantial building happens between sessions, and the amount varies with the requirement and how quickly your pair can diagnose and complete the work.
Are the sessions recorded?
The setup clinic is recorded and comes with a written guide. The five Saturday sessions are live working sessions; recordings are not promised as a replacement for participation.
What software do I need?
You need access to n8n, a laptop, a working internet connection and a Supabase account; the free Supabase tier is enough. By Week 2 your webhooks must be reachable from the internet rather than only from localhost.
What is the refund policy?
Cancellations, transfers and refunds are covered by the Refund and Cancellation Policy. Read it before you pay rather than after.
Enroll
The enrollment form remains on the certification page because the same form handles the cohort, the cohort-and-assessment bundle, and the Path B readiness review.
The cohort’s revised start date is being confirmed. There are 25 seats.