The earlier chapter covered how Opportunity Briefs get made. This one's the log of an actual week running the desk they land on — what I opened, what I built, what I let sit, and the one thing that went sideways.
Monday, 9:10am — six briefs in the queue
First rule of the morning: don't read top to bottom. The page lays a brief out as problem, audience, evidence, scope, confidence — I read evidence first, every time. Open the links before the summary. One of Monday's six cited "growing frustration in the community" and linked two threads, one from 2019 with four upvotes. That's not evidence, that's a search result, and it got closed in about eight seconds.
The second one held up. Freelance video editors losing client feedback across email, Frame.io comments, and text messages, reconciling it by hand before every revision pass. Evidence section had three independent sources — a forty-reply thread in a video editing subreddit comparing workarounds, a G2 review of a competitor complaining about the exact same gap, and a tweet with two hundred likes about a "feedback spreadsheet of shame." Three sources agreeing beats one viral post; virality tells you something's relatable, not that it's common.
Audience: freelance video editors doing client work, one to five clients at a time, active in r/videoediting and the Frame.io community Discord. Specific enough to buy ads against, which matters later. Scope: a single page that ingests a Frame.io comment export and an email thread and spits out one unified revision list. No auth, no team features, no billing. Small enough to build in a day, which is exactly what a scope section should look like — I routinely cut a brief's suggested scope in half in the build prompt, and this one didn't even need that.
Third brief, same run: "freelancers struggle with time tracking across multiple clients." One Reddit thread, six replies. Audience just "freelancers." Scope a full time-tracking SaaS with invoicing. Same morning, same research run, wildly different quality — the underlying signal was just weaker. Closed it. A good run gives you two or three worth reading closely and a handful that aren't sharp enough to act on; that's normal, not a sign the system's broken.
Monday, 9:40am — build prompt, then a decision I almost skipped
The video editor brief was convincing enough that I nearly sent it straight to build. Caught myself — half-convinced still means validate first, not build first. The normal build flow is for when you're actually convinced, not when you're excited. Staged a one-page waitlist instead: the pitch in plain language, and forty dollars of paused ad spend aimed at the Frame.io Discord's obvious neighbors.
Almost made a real mistake here. First draft of the ad targeting was so narrow it would've shown to maybe 200 people total, and a null result off 200 impressions tells you nothing — you can't tell "nobody wants this" from "nobody saw it." Widened the audience before unpausing. Small thing, but it's the kind of thing that ruins a validation run silently if you don't catch it.
Wednesday — checking the number
Four days of ad spend, unpaused Tuesday morning: nineteen signups against roughly nine hundred impressions. Real signal. Would've been a real signal at two signups too, just the opposite one. Either way, I now knew something I didn't know Monday, for the cost of a landing page and forty dollars, instead of a week of build time. This is the brief from the earlier worked example, and it's the one I'd point to if someone asked why validate-first is worth the friction of staging something you're already excited about.
| Action | When |
|---|---|
| Build this | Convinced. Straight to the build prompt. |
| Validate first | Half-convinced. Waitlist + paused ad campaign before committing a week. |
| Let it age | Not convinced. Keep it — the queue is a reading list, not a to-do list. |
My honest ratio across accounts I run this way: about one brief in eight goes straight to build, three or four get staged for validation, the rest age out. If your ratio leans heavier toward build, you're probably not reading the evidence section closely enough.
A brief from March, still sitting there
Not from this week — this one's worth mentioning because it changed my mind about deleting old briefs. Back in March I aged out a brief about a niche inventory tool for small climbing gyms; audience was real but evidence was thin, one forum thread. Left it. Two months later a competitor shipped something adjacent, and going back to reread it, the audience section suddenly looked prescient instead of speculative. Nothing about the brief had changed. The market did. If I'd deleted it to keep the queue tidy, that context would've been gone for free, for no reason.
Friday — tuning the machine instead of reading its output
Fridays I spend less time reading briefs and more time steering the thing that writes them. Two changes this particular Friday. First: scoped the next research run to a specific territory — "tools for climbing gyms" instead of nothing — because an unscoped run tends to surface whatever's loud on the internet that week (there's always a fresh AI-wrapper idea, always a generic productivity complaint) instead of digging into an actual subculture. Scoped runs come back with the exact spreadsheet gym owners share for route-setting rotations. Unscoped runs come back with vibes.
Second change, and this is the one I'd tell anyone to do before anything else on this list: I went back through the last month of rejections and wrote down why, then fed those reasons into the next run's focus. Weak evidence, three times. Oversized scope, twice. Told the next run to lean toward "evidence-heavy" and "narrow MVP." It's a blunt instrument — you're nudging a prompt, not fine-tuning a model — but over a few months of doing this on one account, the acceptance rate climbed from something like one build-worthy brief in twelve to closer to one in five.
What I'd skip next time
I ran Discovery daily for about a week early on, hunting hard, and I'd skip that if I did it again — twice a week is already close to overkill, because the research agent needs real time for signal to accumulate between sweeps. Running it every day mostly produced near-duplicate briefs on the same three trends, which just makes Monday's skeptical reading take longer for no extra signal. Weekly's the right default; I'd only compress it during an active hunt, and even then not past every other day. And I'd rotate the territory sooner than I did — running "climbing gyms" three weeks straight scraped the bottom of the same threads by week three, where two or three territories on rotation would've kept each one fresh.
