Last verified: October 5, 2026
What You Can Now Do
Context Memo's Discovery v5 lets you provide open-ended context during discovery without being prompted for urgency, and the system infers urgency from what you wrote instead of asking for it as a separate field. One free-text question replaces the urgency step. You describe the situation in your own words: the prompts you keep losing, the competitor showing up in the answer, the launch or renewal cycle driving the work. Discovery reads the timing out of that. The practical change is that you stop converting a real deadline into a dropdown value and instead state it once, in context, where the rest of your strategy inputs live.
Where It Is in Context Memo
Discovery, the question set you complete before memo strategy and generation. The open context question appears inside that flow, and the standalone urgency question no longer renders there. Everything else in Discovery stays where it was.
How to Use It
- Open Discovery and start or resume a session. The question set loads in v5 form, with the urgency question absent.
- Answer the open context question in plain language. Name what you want to change in AI answers, which competitor is getting cited instead of you, and any date that matters (a launch, a board review, a renewal quarter). Your text is captured as a single context block rather than split across fields.
- Submit the session. Discovery returns its read of your situation, including the urgency it inferred from your wording.
- Check the inferred urgency against what you meant. If the timing you care about is not reflected, go back to the open context question and say the date or the trigger explicitly, then resubmit. The inference updates from the revised text.
- Carry the completed discovery output into strategy and memo generation as you did before. Downstream steps consume the inferred urgency the same way they consumed the old field.
Why We Built It
Customers kept telling us the urgency question asked them to repeat themselves. They had already written that a competitor was being cited on their top-of-funnel prompts and that a product launch was three weeks out, then the next screen asked them to rate how urgent it was. Two answers for one fact. The cost was a longer discovery flow with a higher drop-off point in the middle of it, and an urgency value stored as a label with none of the reasoning attached, which made the resulting strategy harder to justify to anyone who had not sat through the session.
What It Does Not Do Yet
The inference is only as good as the text. If you write two sentences with no timing, no competitive loss, and no event, Discovery will infer accordingly, and you should expect a lower urgency read than your actual calendar warrants. Write the date if the date matters.
Discovery does not pull timing from your connected systems. Renewal dates in HubSpot and campaign dates in your calendar do not inform the inference, so a deadline that exists only in your CRM needs to be stated in the open context answer.
Review remains a manual step. Context Memo shows you the inferred urgency, and confirming or correcting it is on you. We are not auto-approving a signal that sets strategy priority without a human reading it first.
One note on fit, since Discovery sits at the front of the workflow: the richest discovery sessions come from brands with an existing site and published content, because the open context answer can point at real pages, real positioning, and real competitive comparisons that models are already drawing on. If you are pre-launch with no domain and no content, Discovery will still run, but the strategy it produces has less to work with. Build the foundational content and domain presence first, then come back and run discovery against something models can actually cite.