SolCrys Logo

How SolCrys Works

Signal: a weekly market brief tied to the prompts you are losing

Content calendars usually get filled from whatever is trending. Signal fills them from what is trending and measured: it scans the sources you configure plus the communities your targeting playbook already watches, ranks what changed this week, drops anything the last four briefs already covered, and binds each surviving idea to a specific tracked prompt. Each idea then carries a coverage verdict - covered, uncovered, or not yet measured - and only an idea aimed at a prompt you are demonstrably losing is promoted as high-priority work. It is the answer to the question a content team actually has on Monday morning, which is not "what is happening" but "which of the things happening is worth my week."

Updated

Questions this guide answers

  • What is SolCrys Signal?
  • How do I decide what AEO content to write this week?
  • How do I connect market news to AI visibility gaps?
  • What should go on an AEO content calendar?

Direct answer

Signal produces one brief per workspace per week. It reads the sources you configure - RSS feeds, sites you want watched, LinkedIn accounts - plus the communities your Reddit targeting playbook already tracks, then ranks what changed, writes each item up, and binds every idea to a tracked AEO prompt.

That binding is the whole point. An idea with no prompt behind it is a hunch. An idea bound to a prompt you are currently losing is a piece of work with a measurable outcome attached before anyone starts writing.

Why a trend feed is not a content plan

Every marketing team already has more inputs than it can act on. The scarce thing is not awareness of what is happening; it is a defensible reason to pick one item over the other nine.

Ranking by novelty or engagement does not supply that reason - it supplies the same list your competitors are reading. Ranking by whether the topic touches a question your buyers ask an answer engine, and whether you currently lose that question, does. It also makes the decision auditable after the fact: you can say why the week was spent the way it was, and re-measure whether it worked.

How a brief is built

Four steps, one scan.

1. Read the sources you chose

Sources are configured per workspace and the configuration is the feature gate - a workspace with no sources has no Signal. That is deliberate: a generic industry feed produces generic briefs, and the value comes from watching the specific publications, sites and communities that shape your category.

2. Rank, and drop what you already covered

A single pass ranks the candidates and de-duplicates against the topics of the previous four briefs. Without that memory a weekly brief degenerates into the same three evergreen themes restated, which is how most automated content calendars quietly die.

3. Bind each idea to a prompt, and say what you know

Each surviving item carries a topic, a short brief, a suggested angle and channel, its sources with dates, and the tracked prompt it is aimed at. The prompt binding is stored as an identifier rather than as text, and the wording is re-resolved from your prompt set on every read - so an edited or deactivated prompt cannot leave a card quietly claiming coverage that no longer exists.

Each binding carries one of three verdicts, and the distinction matters more than it looks: covered means your brand appeared for that prompt in the latest completed run; uncovered means it measurably did not; not yet measured means there is no completed run to judge against - a normal state for a new workspace rather than an error. Only *uncovered* is proven upside, and only *uncovered* earns a high-priority action.

4. Promote what you decide to do

An idea you accept becomes an action in the Action Hub, with the brief, the sources and the prompt binding attached. Promotion is idempotent - a reload or a second browser tab cannot file the same idea twice - and the action body is assembled server-side from the stored item rather than from whatever the page happened to be showing.

What Signal deliberately does not do

Two boundaries.

  • It does not write the content. A brief is a decision aid with an angle and sources, not a draft. Drafting happens later in the loop, grounded in Corporate Context and reviewed by a person.
  • It does not invent coverage it has not measured. An unmeasured prompt is labelled unmeasured. The temptation to present every idea as a gap is exactly the behaviour that makes trend tools untrustworthy after the third week.

How it fits the rest of the loop

Signal is the input end of the same loop everything else runs on. The prompt set it binds against is your Golden Prompt Set; the coverage verdict comes from the same measurement that drives your dashboards; the accepted idea lands in the same queue as an audit finding or a citation gap, and is re-measured the same way after it ships.

That is the reason it is built into the platform rather than sold as a separate trend tool: a market signal is only actionable when you already know which questions you lose.

FAQ

How is this different from a trend or social listening tool?

A listening tool ranks by what is happening. Signal ranks by what is happening that touches a question your buyers ask AI engines - and tells you whether you currently lose that question. The output is not a list of topics but a shortlist with a measurable outcome attached to each item, which is what makes it possible to review the decision later.

What sources can Signal read?

RSS feeds, specific sites you want watched, and LinkedIn accounts, configured per workspace - plus the communities your Reddit targeting playbook already tracks, so the two features share one map instead of maintaining two. A workspace with no configured sources simply has no Signal; the configuration is the switch.

What does it mean when an idea says a prompt is 'not yet measured'?

That there is no completed measurement run to judge coverage against - normal for a new workspace, and deliberately not collapsed into 'uncovered'. Treating 'we have not measured yet' and 'we measured and lost' as the same state would let a brand-new workspace present every idea as a proven gap, which would be false.

Does a brief expire if I do not act on it?

It stays as the record of that week, and a rescan merges new items into the same week's brief rather than replacing it, so you can see which scan surfaced which idea. What ages is the coverage verdict - it is a snapshot of the latest completed run at scan time, so an idea you revisit a month later should be re-checked against current measurement before you treat its gap as still open.

Free ChatGPT visibility check

See where AI answers skip your brand — then fix it, free

Start a free workspace with your domain: 10 buyer-intent prompts through ChatGPT show where you are mentioned, cited, or skipped, and who gets recommended instead. A free content audit in the same workspace hands you the first fix to ship.

Start Free

Free · No credit card · About 5 minutes

Related guides

How SolCrys Works

Inside the Action Hub: From Gap to Verified Lift

What SolCrys does after the dashboard surfaces a gap: the closed-loop workflow from detection to draft to review to ship to re-measurement, plus the task layer a team actually runs it on - owners, review handoffs, comments, checklists and reminders.

How SolCrys Works

Golden Prompt Set Methodology

We ground every AEO prompt set on real intent volume, public community questions, AI query signals, and live engine follow-ups - not synthetic keyword lists. Here's how we build it.

How SolCrys Works

Don't delete 0-visibility prompts: a four-state lifecycle for AEO prompt sets

Most teams delete prompts that show 0 visibility. Eason Wang, SolCrys CPO, on why that's the wrong heuristic — a 0-visibility prompt with real buyer intent is a gap to fix, not a prompt to remove — and the four-state lifecycle (Keep + Act, Rewrite, Archive, Add) we ship to enforce it.

How SolCrys Works

AI Visibility Measurement Methodology

How we capture your AI visibility data across supported engines, with each response traceable to a prompt, engine, capture method, available model or surface signal, and timestamp. Consumer-surface and retail-assistant validation are scoped where technically reliable.