Loop Public Courses · Entry Class

The QA Director's Guide to Doing More With Less.

One day. One cohort. A practical 90-day plan you can take to your boss on Monday. To reduce low-leverage testing, use AI where it actually compounds, and reposition QA around quality value instead of test execution.

See the syllabus →1 day · Live · Virtual · Cohort · $1,000 per seat
WS-001Entry class · Public

Doing More With Less in QA

A one-day course for QA leaders who need to reduce regression drag, use AI wisely, and prove quality value in 90 days.

Duration

1 day

Format

Live · Virtual · Cohort

Cadence

Last Tuesday monthly

What you'll walk away with

  • QA Access & Permissions Scorecard
  • Test ID Access Request Template
  • QA Operations Maturity Scorecard
  • Current-State / Next-Level Gap Worksheet
  • Test Layer Decision Tree
  • White-Box / Black-Box Testing Map
  • AI Automation Strategy Canvas
  • Automation Constraint Diagnostic
  • QA Output & Quality Metrics Menu
  • Manager's Guide to Spotting Fake AI Productivity
  • 90-Day QA Leverage Plan
  • Boss Justification Memo
  • QA vs. Engineering Ownership Charter
  • Executive Narrative Builder
Read the full syllabus

Beyond the entry class

When you're ready to go further.

The entry class gives you the framework. The next steps apply it to your team, get your org aligned, or implement the new model.

Audit · AUD-001

QA Leverage Review

A private async-first review of where your QA model is losing leverage. And what to do first.

Read the brief →Alignment · ALN-001

Quality Strategy & Leadership Alignment

A leadership workshop that aligns QA, engineering, and product on the new operating model.

Read the brief →Sprint · SPR-001

Quality Transformation Sprint

6–10 weeks. Ship the regression-reduction pilot, the AI pilot, and the executive ROI readout.

Read the brief →

What attendees walk away with

Three QA leaders, three Mondays after the cohort.

Every cohort runs the same curriculum, but the takeaway depends on the conversation each leader needed to be ready for.

01
“I rewrote our QA OKRs the morning after. The Last 20 Bugs exercise alone was worth the seat.”
. SarahQA Director at

Series-B fintech · ~50 engineers

Outcome: Killed two recurring regression flows in 30 days.

02
“I walked into the AI tooling review with the Boss Memo template filled out. Different conversation entirely.”
. MarcusHead of Quality at

Healthcare SaaS · 120 engineers

Outcome: Avoided a six-figure AI vendor commitment.

03
“We presented the 90-day plan in the next exec offsite. Engineering moved three quality activities back left.”
. PriyaQA Director at

E-commerce platform · 200+ engineers

Outcome: Reclaimed 22 engineering-hours per sprint.

Names + companies anonymized at the speakers' request.

Watch · From the desk

Talks behind the cohort

Subscribe on YouTube · @benfellows-dev →
Inside a Real Agentic Pipeline (Step-by-Step Breakdown)

May 4, 2026

Inside a Real Agentic Pipeline (Step-by-Step Breakdown)

Agentic pipelines sound great in clean demos, but what do they actually look like in production? In this video, I break down one of the real AI development pipelines I use almost every day: how it starts from a prompt, creates its own branch and worktree, runs research, builds a plan, gets reviewed by a second agent, writes failing tests, implements until green, runs policy checks, and produces receipts at the end. I also cover what’s worked, what’s been over-engineered, where deterministic checks matter, and why “just run more agents in parallel” is not always the right answer. Sorry for the lower-energy video, I hadn’t eaten all day before recording this one 😅 Links: Newsletter: https://tinyideas.ai/#newsletters QA work at Loop: https://www.workwithloop.com/ LinkedIn: https://www.linkedin.com/in/ben-f-44778426/ X: https://x.com/FellowsBen

Watch on YouTube →
Are Agentic Pipelines Actually Worth It?

May 1, 2026

Are Agentic Pipelines Actually Worth It?

Are agentic pipelines actually worth the extra time, tokens, and complexity? My honest answer: it depends. Agentic pipelines can improve accuracy, visibility, governance, and control, but they also add real cost. They often take longer to run, use more tokens, introduce more orchestration, and create another layer of abstraction around your development process. So the question is not “do pipelines work?” The better question is: did this pipeline earn its cost? In this video, I walk through the framework I’m using to evaluate whether an agentic pipeline is actually worth running. That includes measuring the pipeline tax, tracking run receipts, comparing quality improvements, and using a ledger system to understand whether a pipeline is making the work better or just making it more complicated. I also share an example of a pipeline that looked good on paper but probably wasn’t worth it in practice. That’s an important part of the lesson: not every task needs a pipeline. Sometimes a single Claude Code or Codex session, guided by a strong engineer, is enough. The goal is to use pipelines surgically. Start simple. Measure what happens. Add complexity only when the pipeline is solving a real problem. And when a pipeline gets too large, use the data to make it smaller. If you’re experimenting with agentic development, this video is about how to think about ROI, accuracy, governance, and cost before building complex AI workflows everywhere.

Watch on YouTube →
Stop Doing AI “Factory Work” - Own Your Agentic Pipeline #agenticai #agentic #agenticcoding #coding

Apr 30, 2026

Stop Doing AI “Factory Work” - Own Your Agentic Pipeline #agenticai #agentic #agenticcoding #coding

Stop treating AI like factory work. Rigid, assembly-line workflows break down with complex codebases. Owning your agentic pipeline means customizing every step and refreshing context each time—leading to better accuracy, flexibility, and scalability where it actually matters. #agenticai #agentic #agenticcoding #coding

Watch on YouTube →

Common questions

Before you reserve a seat.

Is this for me or my team?
It's designed for the QA leader. Most attendees come solo. If you'd rather run it for your team, ask about the private cohort below.
Will my boss approve $1,000?
Use the boss-justification memo from the resources hub. Most leaders frame it as the cost of preventing one bad AI tool decision. The bar is low.
What if I miss the cohort I signed up for?
We'll move you to the next month at no additional cost, twice. After that we'd ask you to send a colleague.
Is there a refund policy?
Full refund up to 7 days before the cohort. After that we'd swap you to a future date or send the recordings + worksheets.

Past sessions library

Replays of every workshop Loop has run.

Recordings live on the YouTube channel. Worksheets and slides are linked off each replay card.

Replay · 60 min

Why QA Teams Become Cost Centers. And How to Avoid It

The four moves that turn QA back into leverage. Recording + the framework worksheet are linked from the YouTube description.

Watch on YouTube →

Want every replay

Subscribe to the Loop YouTube channel. Every workshop replay lands there as soon as the cohort wraps. @benfellows-dev →

Private team workshop

Run the entry class privately for your team.

Same curriculum, your team only. Tailored exercises, pre-work against your actual regression suite, and an executive readout at the end.

Inquire about a private workshop →
Template

90-Day QA Leverage Plan

Coming soon