Brand & positioning
AuraScore 85/100

Regulatory Tech Category Creation Specification

Build an exhaustive category creation and positioning specification for governance and legal technology platforms.

Use this template when defining a net-new software category or repositioning a legacy compliance solution against entrenched manual workflows. It establishes category boundaries, proprietary mechanics, and distinct narrative pillars for risk-averse buyers.

Template

Role: Principal Brand Strategist specializing in enterprise compliance architecture and regulatory governance.

Context

  • Platform Name: {{firm_name}}
  • Regulatory Sub-domain: {{regulatory_domain}}
  • Existing Workflow Paradigm: {{incumbent_paradigm}}
  • Underlying Technology Engine: {{proprietary_mechanism}}
  • Primary Executive Buyer: {{target_persona}}
  • Core Strategic Thesis: {{strategic_narrative_pillar}}

Task

Generate an exhaustive Category Creation and Brand Positioning Specification that defines an uncontested market category for {{firm_name}}, deconstructs the failures of the {{incumbent_paradigm}}, and translates {{proprietary_mechanism}} into defensible enterprise value for {{target_persona}}.

Method

  1. Analyze the institutional failures and friction points created by {{incumbent_paradigm}} within {{regulatory_domain}}.
  2. Define a distinct, defensible category name that encapsulates the shift from reactive compliance to proactive governance.
  3. Frame the category problem statement, contrasting the cost of inaction against emerging regulatory pressures.
  4. Articulate the category blueprint, positioning {{proprietary_mechanism}} as the foundational standard for this new paradigm.
  5. Formulate three distinct positioning pillars grounded in {{strategic_narrative_pillar}}, mapped directly to the priorities of {{target_persona}}.
  6. Draft an authoritative category manifesto establishing the operational standard for modern enterprise compliance.
  7. Detail a message matrix with tailored value proof points, competitive counter-claims, and proof-of-concept verification criteria.

Constraints

  • MUST anchor all category claims in provable architectural capabilities rather than vague marketing superlatives.
  • MUST NOT mention competitor brand names directly; refer only to structural paradigms and legacy approaches.
  • Positioning statements MUST follow a standardized structural syntax: For [target], who [problem], {{firm_name}} is [category] that [benefit].
  • Content must maintain an executive, authoritative, and policy-informed tone.

Output format

Return a technical brand specification containing exactly these markdown sections:

  1. Category Blueprint (Category Name, Core Definition, Paradigm Shift Analysis)
  2. Enterprise Positioning Architecture (Core Statement, 3 Narrative Pillars with Proof Points)
  3. Executive Category Manifesto (300-400 words)
  4. Stakeholder Messaging Matrix (Tabular or structured format: Persona Pain, Message, Architectural Proof)

Self-review

  • Ensure the category name does not rely on generic suffix additions like '2.0' or 'AI-Powered'.
  • Verify that every narrative pillar directly ties to an operational risk solved by {{proprietary_mechanism}}.
  • Confirm that the message matrix addresses both risk mitigation and operational velocity for {{target_persona}}.
AuraScore breakdown
85/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification10/14 · Adequate

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

marketing
marketing-brand
research-productivity-operations
positioning
category-creation
legaltech