aswritten.ai · public perspective

PerspectiveOperatingModelShifts › Narrative DirectVsInfluenceSales

Narrative DirectVsInfluenceSales

6 nodes in this area of the perspective

The sales strategy for demo-call prospects remains anchored in a two-step ladder, moving from a [Publisher tier] (Position_DemoProspectStep1PublisherTier) focused on individual experts to an [Organization tier] (Position_DemoProspectStep2OrgTier) that introduces compliance and on-premise requirements. Enablement efforts have coalesced around providing the prospect with a repeatable process rather than just a deal structure. This includes the development of a [play-by-play playbook] (Position_SalesPlaybookForDemoProspect) featuring visual demonstrations of the knowledge extraction workflow, alongside a [pre-read deck] (Position_PreReadDeckRequest) designed to streamline initial meetings. To improve the user experience, there is a push for [tighter onboarding] (Position_TighterOnboarding) that clarifies the distinction between static documentation and AI-driven features. Additionally, the prospect has requested a [written sales guide] (Position_SalesGuideRequest) to support their own internal sales conversations, ensuring they can effectively communicate the value of the module repository.

Witness phrases

verbatim
Your expertise becomes installable, citable, and generates revenue through the marketplace.
verbatim
The compliance, on-prem, and data sovereignty hooks all apply at this tier.
verbatim
A sales playbook for a demo-call prospect is the critical sales enablement piece this week.
verbatim
New users should not have to figure out which parts are documentation and which are AI-driven.
verbatim
Tension exists between the desire for a simple, approachable 'Publisher' entry point and the complex, compliance-heavy requirements of the 'Organization' tier.