Skip to content
Docs

Opportunities

The scored backlog of candidate pages, and the controls for accepting or dismissing them.

Open in ChatGPTOpen in Claude

App route: /opportunities

Opportunities triage: score, difficulty, accept / dismiss
Opportunities triage: score, difficulty, accept / dismiss

Opportunities are candidate pieces of work, scored and queued. Research agents surface them from your clusters and your own ideas; your job is to triage: accept the ones worth a page, dismiss the rest, and keep the backlog honest.

Doing this rather than looking it up? The Tutorial walks this screen step by step in 4.2 · Generate opportunities.

Reference

Seven states, not all of them visible as columns:

StateMeaning
seedRaw idea you pasted in, not yet developed
developingAn agent is working it up
backlogScored and waiting for triage
consideringShortlisted
acceptedBecame a brief
dismissedRejected
archivedCleared out of the way

seed and developing are the intake path for your own ideas and appear in their own lane. backlog and considering are the only two the system counts as open.

Considering does nothing on its own. Moving an opportunity there is a bookmark, not a commitment: nothing is generated, no brief is created, and no agent starts work. It exists so you can empty the Backlog in one pass without deciding everything at once, then come back to a shortlist you have already thought about. Accepting is the only action that starts production.

The score is a weighted blend of six signals: relevance carries the most weight, then demand, then difficulty and cluster priority, with intent and coverage contributing least. A missing signal is neutral rather than a penalty, so a sparse opportunity isn't pushed down for being sparse.

Badges flag things the score can't express: that your brand already ranks for the term, or that the opportunity likely overlaps a page you've already published.

Overlap is flagged, not resolved. When an opportunity looks like a page you already have, GrowthOS marks it. Deciding whether that means a rewrite instead of a new page is still yours.

Why it works this way

Last updated at October 20, 2018

On this page