Legal Technology RFP
When to use this
Use this skill to draft a formal request for proposal for a legal technology product or service. The RFP structures the selection process, ensures vendors address the department's specific requirements, and creates a documented basis for the final vendor selection decision.
Triggers:
- "We need to select a contract lifecycle management system — draft us an RFP."
- "Issue an RFP for an e-billing platform."
- "We're buying a matter management system — what should the RFP cover?"
- "We need a legal research platform for our regional offices in the UAE and KSA."
Required inputs
| Input |
Why it matters |
Default |
| Technology category |
Scopes the functional requirements (CLM, e-billing, matter management, legal research, e-discovery, AI legal assistant) |
Ask user |
| Company name and department |
Names the RFP and contextualizes the requirements |
Ask user |
| Current systems / integrations needed |
Determines technical compatibility requirements |
Ask user |
| Timeline for selection and deployment |
Enables vendors to plan response and implementation |
Ask user |
| User base size |
Affects pricing; enterprise vs mid-market requirements |
Ask user |
Optional inputs
- Budget range (including for RFP anonymity — many organizations do not disclose budget in RFP)
- Geographic scope of deployment (single-country vs multi-region — important for MENA multi-language requirements)
- Data residency requirements (sensitive for government-linked entities in UAE/KSA with local data residency obligations)
- Existing vendor relationships to preserve or eliminate
- Diversity / ESG requirements for vendors
RFP structure
Section 1: Introduction and Background
- Brief description of the issuing organization and legal department
- Purpose of the RFP: selecting a [solution type] to support [business objectives]
- Current-state description: existing tools, pain points, reason for change
- Timeline: RFP issue date, questions deadline, response deadline, shortlist announcement, demonstrations, final selection
Section 2: RFP Process
- Submission instructions (format, file type, contact details)
- Confidentiality: vendor responses treated as confidential
- Reservation of rights: company may reject any or all proposals, negotiate with multiple vendors, request additional information
- Conflict of interest disclosure requirement
Section 3: Functional Requirements
List requirements by priority: Required (must-have) vs Preferred (nice-to-have).
For a Contract Lifecycle Management (CLM) system, example requirements:
| Req. ID |
Requirement |
Priority |
Vendor response (Meets / Partial / Does not meet) |
| F01 |
Self-service contract request intake by business users |
Required |
|
| F02 |
AI-assisted contract drafting from approved templates |
Required |
|
| F03 |
Clause library with pre-approved alternative positions |
Required |
|
| F04 |
Automated routing for approval workflows |
Required |
|
| F05 |
E-signature integration |
Required |
|
| F06 |
Contract repository with full-text search |
Required |
|
| F07 |
Obligation tracking and deadline alerts |
Required |
|
| F08 |
Reporting: contract volume, cycle time, risk profile |
Preferred |
|
| F09 |
Multilingual interface (Arabic / English) |
Required for MENA deployment |
|
| F10 |
Support for Arabic right-to-left text in contracts |
Required for MENA deployment |
|
Adapt the requirements table to the specific technology category (e-billing, matter management, AI assistant, etc.).
Section 4: Technical Requirements
| Req. ID |
Requirement |
Priority |
| T01 |
Cloud-hosted (SaaS) with [SOC 2 Type II / ISO 27001] certification |
Required |
| T02 |
Single sign-on (SSO) via [SAML 2.0 / OAuth 2.0] |
Required |
| T03 |
API availability for integration with [ERP / HRIS / existing tools] |
Required |
| T04 |
Mobile application (iOS and Android) |
Preferred |
| T05 |
Data export in standard formats (CSV, JSON, PDF) |
Required |
| T06 |
Uptime SLA ≥ 99.5% |
Required |
| T07 |
Data residency: option to host data in [UAE / GCC / EU / US] region |
Required / Preferred |
| T08 |
Multi-tenant or dedicated instance |
Specify per company requirement |
Section 5: Security and Data Protection
- Data encryption in transit and at rest (AES-256 standard or equivalent)
- Access control: role-based permissions; principle of least privilege
- Audit logs: full activity logging, exportable for compliance review
- Data retention and deletion policies
- Penetration testing: frequency and most recent report availability
- Compliance: GDPR, UAE Personal Data Protection Law, KSA PDPL compliance confirmation
- Incident response: defined SLA for notification of data breaches
Section 6: Integration Requirements
List all systems the solution must integrate with:
- ERP (SAP, Oracle, etc.)
- HRIS (Workday, SAP SuccessFactors)
- E-signature (DocuSign, Adobe Sign, or local alternatives)
- E-billing platform (if separate)
- Document management (SharePoint, NetDocuments)
- Identity provider (Azure AD, Okta)
Section 7: Implementation and Support
- Implementation timeline: expected go-live date and milestone schedule
- Implementation methodology: vendor-led vs customer-led; professional services available?
- Training: type (live, on-demand, documentation) and scope
- Support model: SLA for support tickets (P1 critical, P2 major, P3 minor); named account manager?
- Maintenance windows and patch notification process
- Roadmap visibility: how does vendor share upcoming feature releases?
Section 8: Pricing
Request:
- Per-seat / per-user pricing model with volume tiers
- Module pricing if the solution is modular
- Implementation and professional services costs
- Annual maintenance and support fees
- Multi-year pricing options (3-year commitment discount)
- Payment terms
Do not disclose the company's budget in the RFP; allow vendors to propose pricing based on requirements.
Section 9: Evaluation Criteria
| Criterion |
Weight |
| Functional fit to requirements |
30% |
| Technical architecture and security |
20% |
| Vendor stability and references |
15% |
| Implementation plan and timeline |
15% |
| Total cost of ownership (3 years) |
15% |
| MENA / Arabic language support |
5% |
Section 10: Vendor Information Required
- Company overview, ownership, financial stability, years in operation
- Client references: 3 clients of similar size and in similar industry
- Current client count and retention rate
- Subcontractors / hosting providers
- Litigation and regulatory proceedings (if any)
MENA-specific requirements to include
- Arabic language support: full RTL (right-to-left) interface and document support is essential for UAE, KSA, Egypt, Lebanon deployments where Arabic-language contracts must be drafted and managed.
- Data residency: UAE and KSA government-linked entities may be required to store data locally. Confirm whether the vendor can offer UAE or KSA data centers.
- Local customer references: ask for references from existing MENA or GCC clients.
- VAT / e-invoicing compliance: e-billing platforms must support VAT in UAE and KSA (including KSA Phase 2 e-invoicing ZATCA compliance).
Common mistakes
- Issuing an RFP without internal alignment on must-haves: results in conflicting feedback during demos and inability to make a decision.
- Not specifying integration requirements: vendors will assume standard integrations; non-standard integrations discovered post-contract cause cost overruns.
- Omitting data residency and privacy requirements: critical oversight for MENA-region entities subject to local data protection laws.
- Accepting vendor SaaS terms without review: standard SaaS agreements favor vendors; negotiate data ownership, exit rights, and SLAs before signature. Use [[prompt-pack-master-services-agreement]] as a negotiation starting point.
Related skills
- [[prompt-pack-outside-counsel-guidelines]]
- [[prompt-pack-legal-department-kpi-dashboard]]
- [[prompt-pack-legal-budget-forecast]]
- [[prompt-pack-master-services-agreement]]
1---2name: prompt-pack-legal-technology-rfp3description: Use when a legal department or law firm is issuing a request for proposal (RFP) for a legal technology solution such as a contract management system, e-billing platform, matter management system, or legal research tool. Produces a structured RFP covering functional and technical requirements, security standards, integration needs, evaluation criteria, and pricing. Applicable to corporate legal departments and law firms of all sizes.4license: MIT5metadata:6 id: prompt-pack.legal-technology-rfp7 category: prompt-pack8 practice_area: legal-ops-billing9 priority: P210 intent: [drafting, legal-technology-rfp]11 related:12 - prompt-pack-outside-counsel-guidelines13 - prompt-pack-legal-department-kpi-dashboard14 - prompt-pack-legal-budget-forecast15 - prompt-pack-master-services-agreement16 source: https://skillmd.com/skills/sboghossian-mini-claude-for-legal/prompt-pack-legal-technology-rfp17 upstream: Louis — HAQQ Legal AI (github.com/sboghossian/mini-claude-for-legal)18 version: "1.0"19---2021# Legal Technology RFP2223## When to use this2425Use this skill to draft a formal request for proposal for a legal technology product or service. The RFP structures the selection process, ensures vendors address the department's specific requirements, and creates a documented basis for the final vendor selection decision.2627Triggers:28- "We need to select a contract lifecycle management system — draft us an RFP."29- "Issue an RFP for an e-billing platform."30- "We're buying a matter management system — what should the RFP cover?"31- "We need a legal research platform for our regional offices in the UAE and KSA."3233## Required inputs3435| Input | Why it matters | Default |36|---|---|---|37| Technology category | Scopes the functional requirements (CLM, e-billing, matter management, legal research, e-discovery, AI legal assistant) | Ask user |38| Company name and department | Names the RFP and contextualizes the requirements | Ask user |39| Current systems / integrations needed | Determines technical compatibility requirements | Ask user |40| Timeline for selection and deployment | Enables vendors to plan response and implementation | Ask user |41| User base size | Affects pricing; enterprise vs mid-market requirements | Ask user |4243## Optional inputs4445- Budget range (including for RFP anonymity — many organizations do not disclose budget in RFP)46- Geographic scope of deployment (single-country vs multi-region — important for MENA multi-language requirements)47- Data residency requirements (sensitive for government-linked entities in UAE/KSA with local data residency obligations)48- Existing vendor relationships to preserve or eliminate49- Diversity / ESG requirements for vendors5051## RFP structure5253### Section 1: Introduction and Background54- Brief description of the issuing organization and legal department55- Purpose of the RFP: selecting a [solution type] to support [business objectives]56- Current-state description: existing tools, pain points, reason for change57- Timeline: RFP issue date, questions deadline, response deadline, shortlist announcement, demonstrations, final selection5859### Section 2: RFP Process60- Submission instructions (format, file type, contact details)61- Confidentiality: vendor responses treated as confidential62- Reservation of rights: company may reject any or all proposals, negotiate with multiple vendors, request additional information63- Conflict of interest disclosure requirement6465### Section 3: Functional Requirements66List requirements by priority: **Required** (must-have) vs **Preferred** (nice-to-have).6768**For a Contract Lifecycle Management (CLM) system, example requirements:**69| Req. ID | Requirement | Priority | Vendor response (Meets / Partial / Does not meet) |70|---|---|---|---|71| F01 | Self-service contract request intake by business users | Required | |72| F02 | AI-assisted contract drafting from approved templates | Required | |73| F03 | Clause library with pre-approved alternative positions | Required | |74| F04 | Automated routing for approval workflows | Required | |75| F05 | E-signature integration | Required | |76| F06 | Contract repository with full-text search | Required | |77| F07 | Obligation tracking and deadline alerts | Required | |78| F08 | Reporting: contract volume, cycle time, risk profile | Preferred | |79| F09 | Multilingual interface (Arabic / English) | Required for MENA deployment | |80| F10 | Support for Arabic right-to-left text in contracts | Required for MENA deployment | |8182Adapt the requirements table to the specific technology category (e-billing, matter management, AI assistant, etc.).8384### Section 4: Technical Requirements8586| Req. ID | Requirement | Priority |87|---|---|---|88| T01 | Cloud-hosted (SaaS) with [SOC 2 Type II / ISO 27001] certification | Required |89| T02 | Single sign-on (SSO) via [SAML 2.0 / OAuth 2.0] | Required |90| T03 | API availability for integration with [ERP / HRIS / existing tools] | Required |91| T04 | Mobile application (iOS and Android) | Preferred |92| T05 | Data export in standard formats (CSV, JSON, PDF) | Required |93| T06 | Uptime SLA ≥ 99.5% | Required |94| T07 | Data residency: option to host data in [UAE / GCC / EU / US] region | Required / Preferred |95| T08 | Multi-tenant or dedicated instance | Specify per company requirement |9697### Section 5: Security and Data Protection9899- Data encryption in transit and at rest (AES-256 standard or equivalent)100- Access control: role-based permissions; principle of least privilege101- Audit logs: full activity logging, exportable for compliance review102- Data retention and deletion policies103- Penetration testing: frequency and most recent report availability104- Compliance: GDPR, UAE Personal Data Protection Law, KSA PDPL compliance confirmation105- Incident response: defined SLA for notification of data breaches106107### Section 6: Integration Requirements108109List all systems the solution must integrate with:110- ERP (SAP, Oracle, etc.)111- HRIS (Workday, SAP SuccessFactors)112- E-signature (DocuSign, Adobe Sign, or local alternatives)113- E-billing platform (if separate)114- Document management (SharePoint, NetDocuments)115- Identity provider (Azure AD, Okta)116117### Section 7: Implementation and Support118119- Implementation timeline: expected go-live date and milestone schedule120- Implementation methodology: vendor-led vs customer-led; professional services available?121- Training: type (live, on-demand, documentation) and scope122- Support model: SLA for support tickets (P1 critical, P2 major, P3 minor); named account manager?123- Maintenance windows and patch notification process124- Roadmap visibility: how does vendor share upcoming feature releases?125126### Section 8: Pricing127128Request:129- Per-seat / per-user pricing model with volume tiers130- Module pricing if the solution is modular131- Implementation and professional services costs132- Annual maintenance and support fees133- Multi-year pricing options (3-year commitment discount)134- Payment terms135136Do not disclose the company's budget in the RFP; allow vendors to propose pricing based on requirements.137138### Section 9: Evaluation Criteria139140| Criterion | Weight |141|---|---|142| Functional fit to requirements | 30% |143| Technical architecture and security | 20% |144| Vendor stability and references | 15% |145| Implementation plan and timeline | 15% |146| Total cost of ownership (3 years) | 15% |147| MENA / Arabic language support | 5% |148149### Section 10: Vendor Information Required150151- Company overview, ownership, financial stability, years in operation152- Client references: 3 clients of similar size and in similar industry153- Current client count and retention rate154- Subcontractors / hosting providers155- Litigation and regulatory proceedings (if any)156157## MENA-specific requirements to include158159- **Arabic language support**: full RTL (right-to-left) interface and document support is essential for UAE, KSA, Egypt, Lebanon deployments where Arabic-language contracts must be drafted and managed.160- **Data residency**: UAE and KSA government-linked entities may be required to store data locally. Confirm whether the vendor can offer UAE or KSA data centers.161- **Local customer references**: ask for references from existing MENA or GCC clients.162- **VAT / e-invoicing compliance**: e-billing platforms must support VAT in UAE and KSA (including KSA Phase 2 e-invoicing ZATCA compliance).163164## Common mistakes165166- **Issuing an RFP without internal alignment on must-haves**: results in conflicting feedback during demos and inability to make a decision.167- **Not specifying integration requirements**: vendors will assume standard integrations; non-standard integrations discovered post-contract cause cost overruns.168- **Omitting data residency and privacy requirements**: critical oversight for MENA-region entities subject to local data protection laws.169- **Accepting vendor SaaS terms without review**: standard SaaS agreements favor vendors; negotiate data ownership, exit rights, and SLAs before signature. Use [[prompt-pack-master-services-agreement]] as a negotiation starting point.170171## Related skills172173- [[prompt-pack-outside-counsel-guidelines]]174- [[prompt-pack-legal-department-kpi-dashboard]]175- [[prompt-pack-legal-budget-forecast]]176- [[prompt-pack-master-services-agreement]]