- Buying an A/B testing tool in a larger company runs through three reviews in parallel: legal (contract and DPA), security (questionnaire and evidence) and procurement (commercial terms).
- The checklist below lists every document and clause to request, with the phase in which you need it: first contact, evaluation, security review, legal review and procurement.
- Vendor approvals stall most often when the DPA arrives late or the security questionnaire is sent at the very end. Request both in the first conversation.
- Varify includes a standard DPA and a standard SLA in every plan. On the Enterprise plan, Varify signs your own DPA, SLA and NDA and completes your security and privacy questionnaires.
Before procurement signs with an A/B testing vendor, it needs a complete file: the main contract, the data processing agreement (DPA) with its annexes, the answers to the security questionnaire, and the commercial terms. A missing document regularly delays a purchase by weeks.
This checklist lists the documents and clauses to request, sorted by area and by the phase of the buying process. A second table shows what Varify provides on each plan, with a link to the source. Feature, price and support criteria are covered in the guide on how to choose a CRO platform.
How enterprise teams buy an A/B testing tool
In a small company, the person who wants the tool often signs the contract. In a larger company, three functions review the same vendor at the same time:
- Legal and data protection review the main contract and the DPA: data categories, sub-processors, transfers, liability, deletion and governing law.
- IT security reviews how the tool is accessed and delivered: account security, roles, audit trail, the script on the website and the evidence the vendor can provide.
- Procurement reviews the commercial side: order form, term, billing, service levels and what happens when the contract ends.
The three reviews depend on the same documents. If they run one after the other, every document request starts a new waiting period. If they run in parallel and every team gets its documents in the first week, the review takes as long as the slowest team, and no longer.
That is why the checklist below assigns each document to a phase. The phase says when the document should be on the table.
The checklist
Copy the table into your vendor file. Each row has one check that the document must pass.
| Document or clause | Check | Phase |
|---|---|---|
| Contract | ||
| Main agreement or terms | Scope of service, term and termination are defined. | Legal |
| Order form | Plan, quantities and price match the offer. | Procurement |
| NDA | Your template or the vendor's template is agreed before confidential information is shared. | First contact |
| Service level agreement (SLA) | Availability, response times and remedies are defined. | Legal |
| Liability | Liability for intentional, grossly negligent and negligent breaches is defined. | Legal |
| Governing law | The applicable law is named. | Legal |
| Data protection | ||
| Data processing agreement (DPA) | Data categories, purpose and data subjects are listed. | Evaluation |
| Technical and organizational measures (TOMs) | The TOMs are part of the DPA or referenced by it. | Evaluation |
| Sub-processor list | Every sub-processor is named with purpose, place of processing and transfer basis. | Evaluation |
| Change procedure for sub-processors | Notice and objection deadline are defined. | Legal |
| Return and deletion | Data and backups are returned or erased at contract end, with evidence on request. | Legal |
| Security | ||
| Security questionnaire | Your questionnaire is answered in writing. | Security review |
| Certifications and attestations | The current status of each certification is stated in writing. | Security review |
| Account security | Multi-factor authentication, roles and an audit trail are described. | Security review |
| Script and delivery | Content Security Policy requirements and delivery domains are documented. | Security review |
| Operations | ||
| Status page | A public status page exists. | Evaluation |
| Support and escalation | Contact channels and escalation path are named. | Procurement |
| Exit | Data export, return and deletion at contract end are described. | Procurement |
The following points belong in every file, but they depend on your contract with the vendor and are not answered on this page:
- Order form with plan, quantities and price
- Costs at the end of the contract
- Minimum term and billing cycle
- UK Addendum or IDTA, if your legal team requires one for UK data
- Proof of insurance, for example cyber and liability insurance
- Company policies such as Modern Slavery, Anti-Bribery and Environmental policies
For the security rows, the security checklist for A/B testing tools goes into detail.
What to request in which phase
The same documents, sorted by time. Requesting them in this order keeps legal, security and procurement working in parallel.
- First contact: NDA, a sample of the DPA, the sub-processor list and a note on which certifications are in place or in preparation. Ask whether the vendor completes customer questionnaires and which plan that requires.
- Evaluation: the signed DPA version with all annexes, the TOMs, the status page and a description of the optional features that involve further sub-processors.
- Security review: your security questionnaire, the vendor's answers, and the documentation for account security and script delivery.
- Legal review: the main agreement, the SLA, the liability and deletion clauses and the governing law. If your company uses its own DPA or NDA, send it here at the latest.
- Procurement: the order form, term, billing, and the exit terms.
A vendor that can hand over everything from phases 1 and 2 in the first meeting shortens the whole process, because legal and security can start on the same day.
What Varify provides on every plan and on Enterprise
The table lists the documents Varify provides and where to find the source for each one.
| Document | Plan | Source |
|---|---|---|
| Standard DPA | Growth, Pro, Enterprise | Plans |
| Order processing contract including the TOMs, for download | Public download | DPA (PDF) |
| Sub-processor list (DPA Annex 5) | Part of the DPA | Sub-processors |
| Standard SLA | Growth, Pro, Enterprise | Plans |
| Your own DPA, including your sub-processor requirements | Enterprise | Plans |
| Your own SLA | Enterprise | Plans |
| Your own NDA | Enterprise | Plans |
| Completed security and privacy questionnaires | Enterprise | Plans |
| Account history (who changed what) | Pro, Enterprise | Plans |
| Public service status page | Public | status.varify.io |
The Enterprise lines in Varify's own words:
- "Your own DPA: We sign your data processing agreement, including your sub-processor requirements."
- "Your own SLA: Agree availability, response times and penalties on your own terms."
- "Your own NDA: We sign your non-disclosure agreement instead of our standard template."
- "Questionnaires on cyber security or data protection: We complete your security and privacy assessments during procurement."
And the contract clauses from Varify's DPA that procurement usually asks about:
- Sub-processors: All sub-processors are listed in Annex 5 of the DPA. "An objection to the intended addition or replacement of a sub-processor must be raised within 2 weeks of receipt of the information about the change."
- Liability (§ 10 (2)): "The Processor is liable without limitation for damage to the extent that the cause of the damage is based on an intentional or grossly negligent breach of duty by the Processor, its legal representatives or vicarious agents."
- Contract end (§ 11): Upon termination, data are returned or erased, including backups, with documented evidence of erasure on request.
- Governing law (§ 12 (4)): "This Agreement is governed by German law."
Where vendor approvals stall
Two points in the process cause most of the delays:
- The legal review after the DPA is sent. The DPA often arrives only once the commercial terms are agreed. Legal then starts its review from zero, finds a question about sub-processors or transfers, and the vendor needs time to answer. The purchase waits for every round.
- The security questionnaire at the end. Many companies send their questionnaire only when the decision is already made. The questionnaire then becomes the last step before signing, and any open answer stops the contract.
The remedy is the same for both: request the DPA, the sub-processor list and the questionnaire answers in the first conversation, and hand them to legal and security on the same day. Ask the vendor up front which documents it signs in your format and which it provides as a standard document.
Once the documents are in, the open question is usually what to ask the vendor in a structured way. A list of the documents tells you what to collect; a question catalog tells you what to compare.
Get Varify's procurement documents in the first call
DPA with TOMs and sub-processor list on every plan. On Enterprise, your own DPA, SLA and NDA, and completed questionnaires.