How to win an Overclock Ultra subscription.
We're giving away 5 Ultra subscriptions — 3 months each, the top plan, on the house. But it's not a raffle or a form: it's a championship. Hit the goal — 4 YouTube videos showing what you build with Overclock, each with 1,000+ views (or 10,000+ on a Short) — and be among the first 5 to prove it. After that, 1 new video a week renews another 3 months.
The race has three steps.
Record what you build
Open Overclock, build something real — a site, a squad, an automation — and record your screen. No studio needed: you need a real build happening.
Hit the view goal
4 videos on your public YouTube channel: 1,000+ views on a long video, 10,000+ on a Short. Cut, livestream, devlog — the format is yours. So is the pace.
Prove it before the others
One click opens the chat with the message ready — paste your 4 links and your account email. Made the first 5? The team checks and activates your 3 months of Ultra.
There are three. Just three.
No hidden step, no fine print — what's here is the whole championship.
| The rule | In practice |
|---|---|
| The goal: 4 videos, each hitting the view count | 1,000+ views on a long video or 10,000+ on a Short — each one showing what you build with Overclock, on your public channel. |
| The podium: the first 5 win 3 months of Ultra | Order of arrival counts, once checked on WhatsApp. The 5th spot fills up? The championship closes. See what's in Ultra → |
| 1 new video a week renews it | Won and kept building in public — 1 new video a week during those 3 months? You get 3 more. Rolling cycle for as long as you keep posting. |
Real Overclock on screen
The videos need to show you actually building with Overclock — screen open, panes running. A mention in the title with no product on screen doesn't count.
Long or Shorts, public views
A long video qualifies with 1,000+ views; a Short, with 10,000+. Always the public YouTube counter, on a public video on your channel — no private metrics, no studio screenshot.
Subject to review
The championship is new and may be adjusted. The rules are whatever's on this page — if it changes, it changes here first.
The lineup's ready: 20 scripts waiting for you
Video formulas that already pull tens of thousands of views in AI content — click a topic to open the full script, block by block, ready to record.
Claude + Codex + Gemini working together
A real task split across panes in parallel — with a stopwatch running against doing it with a single agent.
insane comboI ran an AI team by voice
Hands off the keyboard: you talk, the panes obey, the task ships.
insane comboOverclock + Ollama = 100% local agents
Live setup, plus the honesty of saying where the local model falls short.
money and timeA squad built a real business's site
Ugly baseline → squad running → site live, with an honest stopwatch. It's the BUILD from module 4 of the course, on camera.
money and timeHow much does running 6 agents in parallel cost?
The token-and-cost meter per pane, visible the whole session — with the final number on screen.
money and timeI rebuilt a client's site — before and after
The old site, the new one live, and the sped-up middle. A concrete contrast holds the view.
levels and conceptsEvery Overclock level explained
From the first pane to hero mode, each level with a demo and the time it hands back to you.
levels and conceptsVibe coding explained for regular people
Pane, squad, maestro, skill, recipe — 1 short definition + 1 demo per concept.
levels and conceptsFrom zero: I installed and built in 1 hour
The honest beginner video — follows the public course and shows every stumble.
launch"Overclock's update X changed everything"
Every release: what changed, a demo of the new feature, and what you'll actually use. An endless topic.
launchI tested Overclock for 30 days
A review with the limitations said upfront — the format that builds the most trust.
squadsCINEMA SITE: I stole the DNA of a reference
"Steal the reference's DNA. Ship a cinema-grade production." — 9 panes, styleboard, 1 agent per image. Record the gates.
squadsAPP FACTORY: backend and frontend in parallel
"Against the contract, not against each other." — 8+ panes building both sides of the app at the same time.
squadsSAAS 10K: 4 auditors attacking my app together
"The whole app from APP FACTORY. And above it, the vault." — the simultaneous security pass is a cinema-grade scene.
squadsAUTOPILOT: I left it running overnight
"Runs overnight. Only wakes you if it breaks." — record the before-bed moment and the result at breakfast.
squadsARCADE: a playable game in one session
"With a video of the bot playing to prove it." — the clip of the bot playing your game is already the cut ready to go.
only hereI found a bug — and the fix shipped with my name on it
Report it on Discord, follow the queue, show the changelog. No other product gives you that arc.
only hereThe app that was born on a livestream
Tell the origin using the journey as the source, with the product's screen today.
only hereI entered the Builders championship
Document your own run as a series — every episode counts toward your goal and pulls the next one. The journey is the precedent.
only hereNot an IDE: understand what an ADE is
The category education piece — parallelism and the maestro demonstrated in practice.
The formula that holds the view: live demo the whole video · one concrete proof number · before/after · one limitation said upfront · a close that pulls the next video — which is exactly the pace that renews your Ultra.
What's stopping you from hitting record?
Is 1,000 views a lot for someone just starting out?
It's less than it sounds: it's not a viral video, it's a useful video with a clear title about something people search for. Shorts with 10,000+ views count too, and your footage is an AI team building on screen — the hook is already built in. Just remember: it's a championship, first to prove it wins.
I don't know how to edit video.
You don't need to. Build in public works raw: screen recorded, your voice explaining what's happening. What holds attention is the thing actually being built — not the intro animation.
I don't have a channel or an audience.
The championship is exactly the excuse to start. A brand-new channel competes the same — the rule is the public view count, not the channel's age. And every video stays yours: the audience you build now is yours for good.
How do I know if there's still a spot on the podium?
Checks happen in the order proofs arrive on WhatsApp. Message in and ask — the team will tell you on the spot how many of the 5 spots are still open.
What if I come in 6th?
You lose nothing — there's no sign-up, no fee. The videos, the channel, and the audience stay yours, and your published material still counts if a next season opens (no date yet).
Isn't 1 video a week to renew a lot?
It's the pace of anyone building a channel anyway — and recording your screen while you work is one button press. Made 1 new video a week during the 3 months? You get 3 more. The same video that renews your Ultra is the one that grows your channel.
A lot of people will discover Overclock once it's huge. Few will be able to say they were here.
Overclock started this way: an internal SaaS tool, shown in public, live — until the community asked for access and it became an ecosystem. It's all recorded in the journey. The Builders championship is the same bet, in your hands: build in public, get out ahead — and leave it on record that you were building here from the start.
The chat opens with the message ready — just paste your 4 video links and your Overclock account email.