Quill

Suggests what to write next, based on what actually scored well in your real Scorecard data.

Suggest Ideas

Works from real Scorecard data — what actually scored well and why, not generic advice.

A second customer case study (different Anomali customer) following the same Customer Background / Challenge / Solution / Results and Impact structure as the Brianna Blacet case studyCase Study

The Brianna Blacet case study scored 86-95/100 specifically for strict adherence to real facts (no invented stats/quotes/names), the four-part structure, consistent use of the customer's real name/role, and factual tone without embellishment. This pattern is clearly repeatable and rewarded highly whenever followed precisely, so applying the identical structural and factual-fidelity discipline to a new customer story is a low-risk, evidence-backed idea rather than a stretch.

A follow-up vendor-neutral blog post debunking another AI security/SOC industry myth (e.g., 'Why your SOC's automation playbooks are just decision trees with a UI'), styled after 'Why most AI agent demos are actually just chatbots with extra steps'Blog Post

This exact blog_post title was scored 85-93/100 across six separate evaluations, consistently praised for: a non-cliché opening, real headings (never literally 'Introduction'/'Conclusion'), staying vendor-neutral for ~90% of the piece with the pitch only at the end, avoiding marketing buzzwords like 'revolutionize'/'thrilled'/'cutting-edge', ending on a single imperative CTA, and having zero fabricated stats or quotes. Because this exact formula repeatedly hit high scores across multiple runs, a new topic using the same contrarian-debunking angle and structural rules is directly justified by the data, not just loosely related.

A second landing page for a related Anomali product capability (e.g., automated threat intel triage), reusing the exact structure of 'Content That Grades Its Own Work'Landing Page

The landing_page piece scored 94-95/100 for a very specific, reproducible formula: title/2-3 sentence intro/bullets/CTA structure, the bullet format '- [point]. [explanation]', the exact CTA text 'Request a demo' as the literal final line, no bracketed placeholders, second-person 'you' address, never 'we'/'our' for the company, avoidance of banned phrases and terms like 'on-prem'/'3rd party', and consistent Oxford comma use. Since this precise checklist earned near-perfect scores twice, extending it to a new product/feature landing page is a direct, evidence-based extrapolation rather than a generic suggestion.

A second customer success case study (different named customer, role, and results) following the exact Customer Background / Challenge / Solution / Results and Impact structureCase Study

The Brianna Blacet case study scored 95, 90, and 86 across three runs specifically because it used only source facts (no invented stats/quotes), kept the required four-part structure, used the real name/role consistently, and avoided banned phrases like 'we,' 'our,' 'on-prem,' and ALL CAPS. This pattern is proven and repeatable, so applying the same disciplined, fact-only, structure-locked approach to a new real customer is a directly evidence-backed idea rather than a generic case study suggestion.

A landing page for Anomali's threat intelligence or detection engineering capability, built with a 2-3 sentence intro, dash-bullet list, and a closing 'Request a demo' CTALanding Page

Both scored landing_page entries (95 and 94) explicitly credited the exact structure (title, short intro, '- [point]. [explanation]' bullets, verbatim 'Request a demo' CTA as the final line, no placeholders), plus strict style rules (no 'we'/'our', Oxford comma, active voice, no banned terms like 'on-prem'). Since this exact template scored consistently in the mid-90s, reusing it for another product/capability page is a data-supported extension, not a new untested format.

A vendor-neutral blog post debunking another overhyped AI/security buzzword or claim (e.g., 'Why most SOC automation is just alert routing with a new label'), ending in a single imperative CTABlog Post

The 'chatbots with extra steps' blog_post scored 93/93/93/85/85 consistently, with evaluators praising the non-cliché opening, real headings (never literally 'Introduction'/'Conclusion'), ~90% vendor-neutral tone before a brief pitch, avoidance of hype words like 'revolutionize'/'cutting-edge', and a single clear imperative CTA at the end. This idea directly reuses that exact contrarian-debunk structure and tone on a new but analogous industry claim, which the data shows this content mode/style handles reliably well.

A case study on a second customer's implementation, following the exact same structure as the Brianna Blacet case study (real name/role, stated results only, no embellishment)Case Study

The Brianna Blacet case study scored 95/100 specifically for using the customer's real name/role consistently, presenting results as stated without embellishment, no invented stats or quotes, and following required structure. This is a repeatable template — applying the same disciplined, fact-only approach to another customer story should replicate the success.

A landing page titled 'Stop Demoing Chatbots and Call Them Agents' that turns the blog post's core argument into a persuasive product pitchLanding Page

The blog post 'Why most AI agent demos are actually just chatbots with extra steps' repeatedly scored 85-93 for its vendor-neutral, non-generic argument and clean structure, while 'Content That Grades Its Own Work' (94/100) showed landing pages succeed with strict structure (title/intro/bullets/CTA), the exact bullet format '- [point]. [explanation]', and a verbatim final CTA 'Request a demo'. Combining the blog's proven argument/topic with the landing page's proven structural formula is a direct, evidence-based extension rather than a new theme.

A follow-up blog post on 'Why vendor-neutral content outperforms sales pitches (and when to break that rule)'Blog Post

Every scored instance of the AI-agent-demos blog post was praised for being vendor-neutral for ~90% of the piece with the pitch only at the very end, avoiding marketing clichés, and ending with a single imperative CTA. This pattern is strong and consistent enough (appearing in all 6 blog_post entries) to justify a new post that explicitly explores and reinforces that same structural/tonal formula, rather than proposing an unrelated topic.