AI bootcamps and creative programs for the next 10,000 practitioners across the Gulf.
“We wanted a class-demo cut live in two weekends. Not a course. A working demonstration that the program ships practitioners who can ship.”
Case capture
Education · KSA
proof capture
cohort ops
44
students
14
routes
0
manual deploy
44 students
14 routes
Sunday ops
Year
2026
Stack
Next.js · auth · admin ops · GitHub Actions
Primary buyer
Training operator
Core surface
Cohort and student operations
Launch mode
Class-demo cut
Handoff
Routes, auth, admin, automation
Cut the launch surface
Diagnose
Gulf training markets are saturated with theory courses that produce certificates, not practitioners. Cohort-based bootcamps work — but the operational layer (invites, magic-link auth, submissions, admin) usually takes months to stand up.
proof capture
cohort ops
44
students
14
routes
0
manual deploy
44 students
14 routes
Sunday ops
Cohort operations flow
Next.js · auth · admin ops · GitHub Actions
Two-weekend sprint. Fourteen routes shipped: landing, magic-link login, /me dashboard, cohort detail, lesson body, /admin overview + cohorts + roster + submissions, plus OG/icon. Seed scripts and ops automation followed.
proof capture
cohort ops
44
students
14
routes
0
manual deploy
System diagram
Cohort operations flow
Invite
Student access
Login
Magic link
Cohort
Lesson hub
Submit
Work capture
Admin
Review queue
Ops
Scheduled run
Routes shipped
14
Class demo live for the first 44-student cohort. Sunday ops run from GitHub Actions — no manual deploy steps. Domain bind to gccp.global is the only remaining infra task.
Routes shipped
14
in 2 weekends
First cohort size
44
students
Manual deploy steps
0
GH Actions
Build status
green
since first commit
The actual problem, named.
Gulf training markets are saturated with theory courses that produce certificates, not practitioners. Cohort-based bootcamps work — but the operational layer (invites, magic-link auth, submissions, admin) usually takes months to stand up.
Diagnose first. Build second.
Two-weekend sprint. Fourteen routes shipped: landing, magic-link login, /me dashboard, cohort detail, lesson body, /admin overview + cohorts + roster + submissions, plus OG/icon. Seed scripts and ops automation followed.
Cut the launch surface
The first version did not need a full academy. It needed enough product to run a real cohort.
Mapped the student loop
Login, cohort, lesson, submission, roster, admin review. Every screen had an operator job.
Shipped the class-demo route set
Fourteen routes moved the project from curriculum promise to inspectable platform.
Moved ops into automation
Scheduled scripts keep the Sunday operating rhythm from depending on manual deploy steps.
System diagram
Cohort operations flow
Invite
Student access
Login
Magic link
Cohort
Lesson hub
Submit
Work capture
Admin
Review queue
Ops
Scheduled run
proof capture
cohort ops
44
students
14
routes
0
manual deploy
44 students
14 routes
Sunday ops
Receipt / 01
14
Routes shipped. in 2 weekends
Stack / live
Next.js · auth · admin ops · GitHub Actions
Product capture
A real media surface.
How earns trust with image density. This gives each SirVibez case a loaded, inspectable product still before the page returns to the receipts.
More image, less explanation.
A premium case page needs rhythm: full surface, cropped interface, then close detail. The work should get easier to inspect with every scroll.
Premium case pages need more than claims. These stills turn the operating evidence into inspectable media.
Product still
GCCP
Live surface.
Class demo live for the first 44-student cohort. Sunday ops run from GitHub Actions — no manual deploy steps. Domain bind to gccp.global is the only remaining infra task.
Routes shipped
14
in 2 weekends
First cohort size
44
students
Manual deploy steps
0
GH Actions
Build status
green
since first commit
Numbers we ran weekly. Numbers we own.
- Routes shipped14in 2 weekends
- First cohort size44students
- Manual deploy steps0GH Actions
- Build statusgreensince first commit
Premium case pages need more than claims. These stills turn the operating evidence into inspectable media.
System still
GCCP
System map.
Cohort operations flow
01
Invite
Student access
02
Login
Magic link
03
Cohort
Lesson hub
04
Submit
Work capture
05
Admin
Review queue
More proof per scroll.
The page should feel expensive because the work is inspectable: scope, system nodes, evals, and operating decisions stacked like production stills.
Scope / 01
Training operator
Primary buyer
Scope / 02
Cohort and student operations
Core surface
Scope / 03
Class-demo cut
Launch mode
Scope / 04
Routes, auth, admin, automation
Handoff
Node / 01
Invite
Student access
Node / 02
Login
Magic link
Node / 03
Cohort
Lesson hub
Node / 04
Submit
Work capture
What's in production today.
Class demo live for the first 44-student cohort. Sunday ops run from GitHub Actions — no manual deploy steps. Domain bind to gccp.global is the only remaining infra task.
The artifact layer,
not just the story.
Howe wins by letting visuals carry trust. SirVibez needs receipts that feel like product evidence: interface states, system maps, eval panels, and operating traces.
proof capture
cohort ops
44
students
14
routes
0
manual deploy
44 students
14 routes
Sunday ops
Eval trace
14
Routes shipped
Scope receipt
Training operator
Primary buyer
proof capture
cohort ops
44
students
14
routes
0
manual deploy
Ship trace
01 · Diagnose
Cut the launch surface
02 · Design
Mapped the student loop
03 · Deploy
Shipped the class-demo route set
04 · Defend
Moved ops into automation
View more work