// CASE STUDIES

Five anonymized stories. Five workflows that stopped breaking.

Each one is a real engagement, anonymized for client privacy. Numbers are real. Happy to walk through specifics on a call.

Updated Q2 2026 · 5 of 5 shown
MARKETPLACE·PUBLISHER NETWORK·SERVICES ORG·SALES + SUPPORT OPS·CALL OPERATIONS
GLOBAL SEO PLATFORM · 50K+ PUBLISHER MARKETPLACE

Routing publisher inputs without a human in the loop

Pilot · 6 weeks · Live in production
THE PROBLEM

A two-sided marketplace was processing hundreds of publisher submissions weekly through manual review and routing. The ops team was the bottleneck for every transaction, quality was inconsistent across reviewers, and onboarding new reviewers took weeks. Growth was capped by how many submissions one human could read in a day.

THE BUILD

A Zoom → n8n → Claude pipeline that captured intake calls, transcribed and structured them, scored submissions against a multi-dimensional rubric, routed approved publishers into the right marketplace tier, and flagged edge cases for human review. Wrapped in an eval harness so scoring drift could be monitored and the rubric tuned over time without retraining.

THE STACK
Zoomn8nClaude APIPostgresCustom eval harness
THE RESULT
60%
review-cycle time cut
98%
routing accuracy vs. human baseline
~15h
ops hours reclaimed per week
// anonymized for client privacy
PUBLISHER NETWORK · 8 BRANDS

Editorial intake and routing across eight brands

Pilot · 5 weeks · Live in production
THE PROBLEM

A multi-brand publisher was running editorial intake through a single overloaded editor inbox. Every brief came in via Typeform, got manually triaged, manually tagged, and manually routed to the right desk — averaging 45 minutes per piece before a writer was even briefed. Misroutes were common, writers got dropped acks, and capacity planning was guesswork.

THE BUILD

A form → n8n → Claude pipeline that classifies briefs against a brand-fit rubric, auto-routes to the right desk based on confidence threshold, escalates ambiguous fits to the editor with reasoning, and sends acknowledgement to the writer. Human-in-the-loop kicks in only when confidence drops below 0.85, and a weekly digest surfaces drift patterns to the editor.

THE STACK
Typeformn8nClaude APISlackNotion
THE RESULT
<2 min
routing time vs. ~45 min manual
85%
briefs auto-routed without editor touch
8
brands operating on one shared workflow
// anonymized for client privacy
MID-MARKET SERVICES ORGANIZATION

Standing up an AI transformation function from zero

Strategic engagement · 90 days · Production deploys + team training
THE PROBLEM

A multi-team services company knew they were behind on AI but had no internal capability, no roadmap, and no clear first wins. Leadership wanted real production deployments, not a pilot graveyard, and needed an outside lens to prioritize across competing internal asks.

THE BUILD

90-day audit and roadmap covering 12 candidate workflows, scored on impact and feasibility. Prioritized three for immediate build: client deliverable QA, capacity planning, and contract intake. Shipped all three to production with adoption tracking, change management, and team training so the framework outlives the engagement.

THE STACK
Claude APIn8nAirtableNotionCustom dashboards
THE RESULT
3
production AI workflows shipped in Q1
40%
reduction in deliverable QA cycle time
4
internal teams using the framework
// anonymized for client privacy

Recognize the pattern?

If your workflow looks like one of these, the teardown call is where we figure out what to build.

Book a 30-min teardown →
Free · No prep required · Replies same day
SALES + SUPPORT OPERATIONS

AI call scoring at scale

Pilot · 6 weeks · Live in production
THE PROBLEM

A team handling thousands of customer calls per week had no scalable way to monitor quality. Manual QA covered ~5% of calls; the other 95% were a black box. Coaching was reactive, at-risk accounts surfaced too late, and team leads were spending more time pulling samples than coaching.

THE BUILD

An automated call scoring system using Claude to evaluate every transcript against a multi-dimensional rubric, surface coaching moments in real time, and flag at-risk accounts before they churned. Dashboard for team leads, weekly trend reports for leadership, eval harness to catch scoring drift across the rubric.

THE STACK
Claude APIPostgresCustom dashboardEval harness
THE RESULT
100%
call coverage vs. 5% manual baseline
12x
coaching insights surfaced
6
weeks from kickoff to production
// anonymized for client privacy
CALL OPERATIONS · HIGH-VOLUME SUPPORT

Capacity planning that actually predicts demand

Pilot · 4 weeks · Live in production
THE PROBLEM

A high-volume support operation was staffing reactively. Demand forecasts were built in spreadsheets once a quarter, ignored mid-month, and consistently off by 20–30%. Team leads were either over-staffed and burning margin or under-staffed and burning out the team. No early warning when volume was about to spike.

THE BUILD

A capacity planning system that ingests historical volume, seasonality patterns, and live signal feeds, runs daily forecasts through a structured model, and surfaces staffing recommendations to team leads with confidence intervals. Alert layer flags volume spikes 48 hours before they hit. Dashboard for ops, weekly digest for leadership.

THE STACK
PostgresPythonn8nCustom dashboardSlack alerts
THE RESULT
~7%
forecast error vs. ~25% baseline
48h
earlier warning on volume spikes
4
weeks from kickoff to production
// anonymized for client privacy
// LET'S TALK

Pick a time, or send a few sentences.

// BOOK A 30-MIN TEARDOWN
// OR SEND A NOTE

Replies within 1 business day, usually faster.

Or email hello@opslayr.com directly.