Clean Cuts Interactive

Sonar —
First-pass triage, #not a pitch generator.

Qualify a prospect. Get one verdict and a drafted response. Sonar decides. It doesn't hand the question back.

The problem

Studios hit your inbox every week. Most aren't right. Screening them by hand takes time you don't have.

Wrong genre. No funding. Wrong moment. A generic AI writes a confident paragraph about all of them anyway.

The duel

Same prompt. Two answers.

Generic AI
"Northwind Studios looks like a strong fit. They're an indie action-adventure studio with a recent title and an active team. We recommend reaching out to explore a partnership."
Sonar
DECLINE.
No funding from any source detected — publisher, raise, or revenue. Can't hire on normal terms.
Score: 58/107 · funding 0 · audio gap 22 · genre 10 · active dev 12
Sonar doesn't profile studios. It screens them.
What it decides

One verdict, every time.

Pursue
Qualified fit, catalyst present. Email drafted and ready to send.
Nurture
Watchlist. Ping on a ship date, audio job post, or a warm reason to reconnect.
Decline
Brief. Professional. Done. No fabrication, no false signal.
Flag
One question a human needs to call. Sonar names it; it doesn't guess past it.
The decision math

Every verdict is traceable.

107
points. Fit score, not a vibe check. Funding is the gating cluster — 30 pts alone.
Funding (gating)
30 pts
Audio gap
22 pts
Active dev
12 pts
Genre fit
10 pts
Platform
10 pts

Output record pastes straight into col-15 of the MASTER sheet — action + warm intro first, score breakdown supporting.

A committed run

Not a demo. A real decision.

PURSUE · primary-vendor
Action:    Email Dana Reyes (Exec Producer) — October ship date, no audio team yet.
The in:    Warm — Dana Reyes, met at GDC 2025 (CRM).
Score:     69/107 · Tier 2 — audio gap 22, active dev 12, horror/narrative 10; PURSUE via live catalyst.
Catalyst:  project — announced October ship window.

Six worked decisions in examples.md — one per verdict, plus a not-found failure. Fire the prompt, get the same output.

Why this build

Built by the person running the workflow.

CCI does BD the same way Sonar does — relationship-driven, ICP-disciplined, no cold-spray. This is the operator built for the workflow I'm already running. Then Shipper — the launch operator built the same day — dogfooded it and produced this deck.

Get Sonar

Drop it in a project. Start qualifying.

github.com/rocleemusic/sonar-operator

Swap the rubric, catalog, and ICP for your own. The verdict logic carries over unchanged.