The Loop Playbook

20 AI feedback loops you can build today. Each one follows the same pattern: action, signal, adjustment, repeat. The secret to AI that compounds isn't a better model — it's a better loop.

Every loop includes the action the AI takes, the signal it measures, the adjustment it makes, plus implementation tips and guardrails. Organized by function: Marketing, Sales, Operations, Engineering, Finance, and People.

Marketing & Content Loops

Cold Outreach Optimization

Most teams A/B test two subject lines and call it optimization. A real loop tests 20 variants simultaneously, kills the losers every week, and breeds the winners. I've seen this take reply rates from 3% to 18% in eight weeks. The key is measuring meetings booked, not opens. Opens are vanity.

Implementation Tips

Measure meetings booked, not open rates — opens are vanity
Cap send frequency per prospect to avoid spam triggers
Start with 5 variants minimum per cycle to get statistically meaningful signal

Guardrail

Max 2 emails per prospect per week. Automatic pause if unsubscribe rate exceeds 1%.

Content Repurposing Engine

We run this at humAIne. After 12 weeks, the AI writes better LinkedIn hooks than I do. That stings, but it's true. The trick is separating signal by platform — what works on X dies on LinkedIn and vice versa. Let each platform loop independently.

Implementation Tips

Separate loops per platform — what works on X fails on LinkedIn
Track click-throughs to the original post, not just likes
Feed your best-performing hooks back as few-shot examples

Ad Copy Generation

Performance marketers have been doing this manually for years. The loop just runs faster when AI writes the variants. The insight most people miss: don't just look at the winning copy — look at the pattern across winners. Same emotional angle? Same CTA structure? Same word count? That's where the real learning lives.

Implementation Tips

Test emotional angles, not just word choices
Let campaigns run 48 hours minimum before cutting — early data is noisy
Look for patterns across winners, not just the single best performer

Newsletter Subject Line Optimization

"Numbers in subject lines" might work for your tech audience. "Questions" might work for your executive audience. You don't guess — the loop tells you. After 50 sends, the AI has more data on your audience's subject line preferences than any email marketing course will ever teach you.

Sales & Revenue Loops

Meeting Preparation

This loop is deceptively powerful because it personalizes to your judgment, not some generic template. Your CTO colleague might want technical stack details. You might want funding history and decision-maker names. Same meeting, different briefs, each improving independently.

Implementation Tips

Rate every brief immediately after the meeting — the signal degrades fast
Add one line about what was missing, not what was wrong
After 20 rated briefs, the quality jump is dramatic

Recruitment Screening

Job descriptions are aspirational fiction. They list what you think you want. Hire outcomes show what you actually value. This loop closes that gap. After four quarters, the AI is better at predicting who will thrive at your company than the hiring manager — because it has more data and less ego.

Guardrail

AI never auto-rejects. It ranks and recommends. A human always makes the final call.

Sales Call Coaching

Every sales team has a playbook. Almost no sales team has verified that their playbook actually predicts success. This loop does the verification. You might discover that your best closer talks 30% of the time and listens 70% — the opposite of what the playbook says. Let the data rewrite the playbook.

Guardrail

Reps must consent to recording. Scores are coaching tools, never used for punitive decisions without human context.

Document Drafting

Track edit distance per section, not per document. You'll discover the AI nails executive summaries from day one but mangles pricing tables for months. That section-level signal lets you focus improvement where it matters instead of retraining the whole pipeline.

Implementation Tips

Track edit distance per section, not per whole document
Save every human-edited version as a training example
Keep a "never say this" list that the AI checks against before delivering

Operations & Support Loops

Customer Support Triage

The signal most teams miss: repeat contacts. A ticket marked "resolved" that generates another ticket in two weeks was never resolved. Feed repeat contacts back as negative signal and the system learns what actual resolution looks like, not just ticket closure.

Guardrail

Any ticket mentioning legal, billing disputes above $500, or account cancellation always routes to a human.

Inventory Forecasting

The most expensive mistake in retail isn't bad pricing — it's wrong inventory. A 5% improvement in forecast accuracy can mean millions in reduced waste and fewer stockouts. The loop catches things no human can: the correlation between Instagram mentions and demand spikes two weeks later.

Supply Chain Risk Monitoring

The value here isn't prediction accuracy — it's lead time. If the loop gives you 72 hours' warning instead of 24, that's the difference between switching suppliers gracefully and scrambling. Each false alarm is expensive (it cries wolf), so the loop must aggressively prune noisy signals.

Guardrail

Maximum 3 high-severity alerts per week. If the system triggers more, it's being noisy, not helpful.

Product Recommendations

The return rate signal is the one most teams ignore. A product that gets clicked, bought, and returned is worse than one that never got clicked. Feed returns back as strong negative signal and watch the recommendation quality jump. The loop should optimize for kept purchases, not just purchases.

Implementation Tips

Returns are strong negative signal — weight them heavily
Add a cooldown period after purchase to prevent repetitive recommendations
Track recommendation position — slot 1 vs. slot 8 have very different baselines

Internal Knowledge Base Curation

Most company wikis are graveyards. Nobody maintains them because nobody measures whether they're useful. This loop changes the incentive: the AI surfaces which articles are actually solving problems and which are dead weight. The knowledge base gets better through usage, not through a quarterly "wiki cleanup sprint" that never happens.

Engineering Loops

Code Review Assistant

The enemy of AI code review is false positives. Every ignored suggestion teaches the developer to ignore all suggestions. The loop must aggressively prune noise. After 200 reviewed PRs, the system should feel like a senior engineer who actually knows your codebase, not a generic linter.

Guardrail

Never auto-merge. Never block a PR without human confirmation. Security flags always require human review.

Bug Prediction

This isn't about blaming developers. It's about allocating review effort where it matters most. If the system knows that files with more than 400 lines of changes on a Friday afternoon have a 5x bug rate, it can flag those for extra review while waving through the Monday morning one-liners.

Guardrail

Bug predictions are never attributed to individual developers in team-visible reports. Used for review prioritization only.

Finance & Risk Loops

Dynamic Pricing

Amazon has been doing this for a decade. You can do it too, at smaller scale, with an LLM and a spreadsheet. Start with just three price tiers and measure conversion at each. The loop will find the optimal points faster than any pricing consultant.

Guardrail

Maximum 10% price change per 24-hour period. Never price below margin floor.

Fraud Detection

False positives are expensive — they block legitimate customers and create friction. False negatives are more expensive — they lose money. The loop must optimize both simultaneously, which is why you need both signals flowing back. Most fraud systems only learn from confirmed fraud. The best ones also learn from confirmed non-fraud.

Guardrail

Transactions above $10,000 always get human review regardless of AI score. Blocked customers get a fast-track appeal process.

Portfolio Rebalancing

The naive approach: rebalance everything to target weights every quarter. The loop approach: learn that some assets need tighter bands (bonds, cash) and others benefit from momentum (equities, crypto). The AI discovers rebalancing rules that a human portfolio manager would need years of backtesting to find.

Implementation Tips

Factor in tax lots — the cheapest rebalance isn't always the one that moves fewest shares
Set different drift thresholds per asset class, not a blanket percentage
Log every rebalance decision (including "chose not to rebalance") as training data

Customer Churn Prediction

The compounding here is powerful: each churn event makes the model better at predicting the next one, and each successful save teaches the system which intervention works for which type of customer. After 6 months, the system knows that enterprise customers respond to personal calls while SMBs respond to discount offers. You stop guessing and start knowing.

Guardrail

Maximum one retention intervention per customer per quarter. Over-reaching is worse than churning — it damages brand trust.

People & Learning Loops

Personalized Learning Paths

This is where education is heading. Not "AI replaces teachers" but "AI personalizes the path and teachers focus on the human stuff." The loop discovers that Student A learns best from video at 1.5x speed while Student B needs interactive exercises. No teacher can personalize across 30 students simultaneously. The loop can.

Implementation Tips

Combine objective signals (quiz scores) with subjective ones (difficulty rating)
The "productive struggle zone" is where real learning happens — not too easy, not too hard
Build in periodic review loops to prevent knowledge decay