Legaltech Enterprise Discovery Specification
Design a tailored discovery specification for enterprise legal operations and compliance leaders.
Use this template when preparing discovery sessions with corporate legal departments and General Counsels. It structures technical, workflow, and compliance qualification into a reusable spec.
Role: Senior LegalTech Enterprise Account Executive specializing in contract lifecycle management and risk governance.
Context
- Target organization scale: {{target_firm_size}}
- Primary practice scope: {{practice_areas}}
- Legacy tech footprint: {{current_clm_tool}}
- Regulatory governance: {{regulatory_mandates}}
- Workflow bottleneck: {{primary_operational_bottleneck}}
- Buyer committee structure: {{buying_committee_roles}}
Task
Generate a comprehensive discovery specification document that equips sales teams to uncover hidden operational risks, quantify manual review costs, and validate technical prerequisites during enterprise legal consultations.
Method
- Analyze {{practice_areas}} and {{regulatory_mandates}} to isolate regulatory audit triggers and contract turnaround exposure.
- Formulate diagnostic inquiry tracks targeting root causes of {{primary_operational_bottleneck}} across legal and business users.
- Map technical discovery parameters to audit integration viability with {{current_clm_tool}} and existing ERP systems.
- Draft role-specific qualification questions tailored to each stakeholder in {{buying_committee_roles}}.
- Establish quantitative metric baselines for contract review cycle times, outside counsel spend, and clause deviation rates.
- Detail high-probability red flags, security clearance hurdles, and data residency criteria tailored to {{target_firm_size}}.
- Construct an evidence capture matrix to map observed client pain directly against specific platform capabilities.
Constraints
- MUST express all qualification metrics in quantifiable business indicators (hours, risk exposure, dollars).
- MUST NOT prescribe product solution demonstrations within the discovery phase spec.
- Must adapt questioning depth specifically for {{target_firm_size}} enterprise procurement protocols.
- Must keep every discovery track to a maximum of four targeted diagnostic questions.
Output format
Provide the specification organized in these exact sections:
- Executive Context & Hypothesis (1 paragraph)
- Diagnostic Question Tracks (4 categorized tracks, max 4 questions each)
- Technical & Security Clearance Criteria (bulleted list of 5 requirements)
- Economic Impact Baseline Spec (table mapping 3 friction metrics to financial impact)
- Red Flag & Disqualification Triggers (bulleted list of 4 conditions)
Self-review
- Verify all 6 context variables are actively utilized in the diagnostic tracks.
- Confirm no solution pitching or feature selling appears in the discovery questions.
- Check that financial impact baselines are concrete and relevant to corporate legal teams.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.