A vetted community lab for experienced software engineers

Produce more quality AI engineering work within 2 months

Weekly live accountability & focus sessions to hit your goals faster and be on the edge of the AI transition.

Lab Notes · Entry PassLoop Labs 🧪

Join the live sessions

WhoSenior-plus engineers

WhatCommunity · Career Chats · Kits

When1/w newsletter; Wd/St live

No spam. No hype hand waving. Software Engineering, but new. Next step: Get the invite.

$97

Per month, cancel anytime

30d

No-questions refund

1×/wk

Live session loop with peers

Engineers max per live session

100%

Senior Engineer members

House scientist bot

AI rewrites our work mechanics every few months right now. We go with the flow and stay on the edge together.

Loop Labs Vision

How it works

A Loop Labs week, start to finish.

Not another sprawling community platform. One session a week, your real work on the bench, and a room that remembers what you said you would do.

Open the weekAll four steps

Book your slot

Wednesday or Saturday, five session times across US, EMEA and SEA hours. Pick the one that fits your week, every week.

Bring one real thing

The loop that is actually breaking on your production work. Not a hypothetical, not a tutorial repo.

Take your turn

Eight engineers max, random order, everyone gets the floor. What you shipped, what the agents got wrong, what you want done by next week.

Leave it written down

A personalized recap email, the focus topic's notes, and a room that asks about your commitment next session.

The session format

One hour. Everyone takes a turn.

A format Rich has run for over a year across 5 Rails.Builders cohorts. Press the loop and watch it run.

🧪 Weekly live accountability & practice session. Eight engineers max, so everyone actually gets the floor.
⏱️ About 60 minutes. Random order, one turn each, nobody presents at anybody.
🎯 Your turn: what you shipped, where the loop broke, and the one thing you want done by next session.
📌 One focus topic per session that we all learn from. Token efficiency one week, AI-native IDEs and setup the next.
🛋️ (optional) Another 30 minutes to go deeper on anything, or just to hang out.
💌 (optional) Personalized recap email, so next week starts where this one ended.
📈 (optional) Periodic progress trends from Otto and Rich.
📚 (optional) Biweekly book club from month two. Commit to it and the current book arrives on us, shipping permitting.
💬 Paid Slack with retained history. Ping @Otto, our resident scientist bot, any time and stretch his abilities.

I love it 🤝 Show me the plans →

What to expect

What two months in the loop actually changes.

No testimonial wall yet: the founding cohort just started. So here is what the format is built to produce, and the 30-day refund is what happens when it does not.

Read the expected outputSix things, no promises

More shipped, not fewer hoursMembers do not save time. They put the same hours in and more comes out the other end. You will not find a time-saving claim anywhere on this site.
Your setup reviewed by people who run oneSenior peers look at your actual harness, your actual eval, your actual review gate. Not a screenshot of one.
A week that does not resetThe recap email and the room's memory mean the thing you said you would do on Wednesday gets asked about next Wednesday.
The edge, well before the conference talkWhat works right now, from engineers running it in production this week. Evidence over visionary videos.
Fewer dead experimentsThe agent setup you would have abandoned on a Sunday survives, because somebody is expecting a result from it.
It gets fun againHard to put a number on. It is the thing people mention first anyway.

What you get out of it depends on the work you put in. These are the outcomes the format is designed for, not guarantees.

Engineers Today

There are mostly two kinds of engineers now when it comes to working with AI. We want to be the third one.

Click where you are!

Outside the Loop

For one reason or another, some engineers don't use AI for coding at all yet.

Honest answer: We don't have the infrastructure to help you yet, but keep tuned and let us know what you would be interested in! In the meantime, get AI writing a real share of your code first, then come back. Use the Loop Labs Notes newsletter and our other free offerings to level up in the meantime!

In the Loop

AI already writes a serious share of the code (~100%), but code edit approvals, preparing reviews, reviewing and QAs still take up time. Faster than before, and capped all the same: you are the bottleneck in your own pipeline in various spots. This is still the most engineers today and some projects need this care.

Welcome to the club and let's get our agents more autonomous!

On the Loop

Understands the product, manages priorities, sets the goal, hands the execution to agents, watches results, and steps in where judgment matters. Runs several agents at once and signs their name on the final product. Keeps watching quality post-deploy.

Then you are here to compare notes, not to learn fundamentals. There will be a mastermind group twice a week to discuss the edge.

Loop Labs engineers go from In the Loop to On the Loop, on real work, with senior peers and the Loop Lab folks and bots checking the evidence.

The questions everyone asks

Four answers before you pick a plan.

01What changes can I expect?

Your week, before and after.

Now

You write the code, alone, tab by tab
Your agent experiments die on weekends
Nobody senior ever reviews your AI setup
Or you already run stuff in parallel but want to scale

With the loop running

Agents push your code through the pipeline while you're in a meeting
You review the critical parts, not every line
Senior peers review your workflow every week
You ship more, it's fun again, and you're the one who knows why it works

02What is Loop Labs?

Fair question, everything calls itself a community these days. Here is what it actually is.

A course?No. Nothing expires after lesson eight. You bring real work, every week.

A sleepy Discord?No. A vetted room where every member is a senior peer, plus live sessions and Professor Otto Labot as our in-house scientist showing us how to ship things in the "Slack IDE".

Coaching?Partly. Weekly accountability sessions for everyone with a proven format; 1:1 career coaching on the Career plan (coming soon). Each session has a focus topic where we learn from each other, like for example "token efficiency" or "AI-native IDEs and setup".

A mastermind?Separate Mastermind sessions coming soon for folks already closer to "on the loop".

03What is the bar for entry?

Senior-plus title or the equivalent experience, and AI already writes a serious share of your code. Not starting from zero.

Join

Pick a plan on the next page. Payment first keeps the room serious.

20-minute intro chat

We meet. You tell us where your loop breaks. We tell you honestly whether this room will move you.

Fit or refund

If the room isn't right for you, you or we say so and refund you. And the first 30 days are refundable anyway. No reason needed, no questions asked.

04Who runs this?

Rich runs the sessions and the technical bits. Professor Otto Labot is the second pair of hands, and he asks everyone for evidence.

Rich Steinmetz — **Rich**Engineering · facilitator

Professor Otto Labot, a boxy blue robot head wearing a monocle, a bow tie, and a lab coat with a name badge — **Prof. Otto Labot**Resident scientist · bot

The Long Game

Why does this matter economically?

AI might also rewrite the economics. The 2026 numbers are real and sourced. Everything after that is a guess you can drag, so drag it and decide whether you believe it.

Year 2026

Average Engineer Technical, works on tickets.

$195,000 Median total comp

Top Operators Multi-hat, understands the business.

$283,000 Top quartile total comp