ai-demo-request

Drafting an AI demo brief involves aggregating context across seven data sources like Obsidian, Salesforce, and Slack to produce a form-ready Part 1 request and a Part 2 demo strategy.

Multi-source research works by aggregating account context from Obsidian files, transcripts, Salesforce, Slack, Gmail, company websites, and public web sources to inform a precise demo brief.

The Part 1 output is a form-ready demo request draft, while the Part 2 output provides a demo strategy for builders, including Salesforce opportunities, transcript summaries, and targeted questions.

Yes, you can use Obsidian and Salesforce data. The Skill aggregates context from these sources alongside Slack, Gmail, and web data to generate a tailored demo strategy for the builder.

To ensure compliance, the Skill generates outputs using Regal-native syntax and variables while avoiding internal timelines and strategic language to adhere to required fields, formats, and field constraints.

A key constraint is avoiding internal timelines and strategic language in the draft. The approach strictly adheres to required fields and formats, producing targeted questions to guide Tier 2 and Tier 3 research.