TRADITIOtrah-DIT-ee-oh
Direct-Sale Enablement
Traditio is Latin for handing something over. In Roman law it was the delivery that completed a transfer. You hold the relationship and the agreement; we handle the technical delivery.
Keep the buyer relationship. Bring us in for the data work.
Billed for defined services, not a brokerage commission. Any new brokerage appointment requires a separate written agreement.
You lead the buyer relationship and approve the commercial agreement with your counsel.
Is this for you?
- Companies already in discussion with an AI developer that has sent data requirements
- Data owners who want to keep the relationship and the commercial terms in-house
- Teams that need samples, documentation, and technical diligence answered on a deadline
The problem
You have a buyer. Now come the requirements.
A developer has asked for your data and sent a list: a sample, a schema, quality thresholds, provenance documentation, diligence questions, and a delivery format. The relationship is going well, and you want to keep it.
What you need is not a broker. It is a data team that can translate the buyer’s requirements into a defined project and deliver against them on time.
How we work
Defined packages. Fixed or capped fees.
We start with a requirements sprint that turns the buyer’s list into a matrix, a gap analysis, and an estimate. Then you choose the packages you need: preparation and diligence, technical closing support, and ongoing refresh.
You lead the relationship and the commercial terms with your counsel. Our staff do not issue legal opinions, promise acceptance, or introduce other buyers without your authorization.
Typical requests
What buyers usually ask for.
Typical requests in a direct sale, not past client work.
- Requirements
A requirement matrix
Every buyer requirement mapped to your data, with gaps named.
- Samples
An approved sample
A representative sample, prepared and released through an agreed process.
- Schema
A proposed schema
Fields, formats, and units in the buyer’s preferred structure.
- Quality
Acceptance criteria
Measures and thresholds both sides can test.
- Provenance
Provenance documentation
Where each source came from, and the rights questions register.
- Diligence
Technical Q&A
Approved answers to the buyer’s technical questions, within scope.
- Delivery
Transfer and manifest
Release validation, transfer configuration, and checksums.
- Refresh
Ongoing updates
Scheduled refreshes, drift checks, and version documentation.
What you receive
Buyer Requirements Sprint
A requirement matrix, gap analysis against your data, a sample plan, a proposed schema, acceptance criteria, and a preparation estimate.
Preparation & Diligence Pack
A prepared sample and dataset, quality report, dataset card, provenance documentation, data dictionary, and approved diligence responses.
Technical Closing Support
Technical Q&A within scope, release validation, transfer configuration, a manifest, and acceptance testing.
Refresh & Maintenance
Separately scoped recurring updates, drift checks, validation runs, and version documentation for ongoing delivery obligations.
How it works
Share the requirements
Send the buyer’s written requirements, if you have them, and describe the data at a high level.
Scope the packages
Choose the packages you need. Each has defined deliverables and a fixed or capped fee.
Prepare and document
We organize samples, improve the agreed quality measures, and prepare the documentation.
Support diligence and delivery
We answer technical questions within scope, validate the release, and support acceptance testing.
Completion
Done means the agreed specification is met.
Each package has its own deliverables and completion criteria, set before work begins.
- Requirements covered
- Each buyer requirement marked met, partly met, or out of scope.
- Acceptance tests
- The agreed tests run on the delivered release, with results.
- Diligence answered
- Technical questions answered and approved by you.
- Delivery validated
- Manifest, checksums, and transfer confirmed.
Common concerns
What data owners ask before they sign.
- Changing requirements
- New buyer requests are compared with the agreed specification and handled by written scope change.
- Commercial terms
- You negotiate the agreement. We never negotiate or take an undisclosed commission.
- New introductions
- Any introduction or representation beyond this scope needs a separate decision and agreement.
Who does what
Who decides, who advises, and who does the work.
Your team
- Lead the buyer relationship
- Approve every release and answer
- Negotiate and sign with counsel
Copia
- Translate requirements into a project
- Prepare samples, data, and documents
- Support diligence and delivery
Afterward
Where clients go next.
Each route stands on its own. You choose, and nothing starts without your approval.
Refresh and maintain
If the license includes updates, scope a recurring package.
Represent the next asset
For a dataset without a buyer, a brokerage mandate can run a full process.
Before the first call
What to have ready.
- The buyer’s written requirements, if you have them
- Your timing and any deadlines in the term sheet
- Who on your side approves releases and answers
Related services
What “accepted” means
Measured against criteria you agree to in advance.
- Each package lists its deliverables, dependencies, and fee before work begins.
- Technical staff do not issue legal opinions, promise acceptance, or introduce buyers without your authorization.
- Changes in buyer requirements are compared with the agreed specification and handled through a written scope change.
- Any introduction or representation beyond the direct-sale scope triggers a scope decision, never an automatic fee.
Scope direct-sale support
Tell us about the buyer and the data.
You keep the buyer relationship. We reply with a scoped technical project, billed for defined services.
- An engineer reads every request
- A reply by email within two business days of receipt
- No obligation until scope and price are agreed
Not ready to scope this? Discuss data licensing first: a free conversation about which route fits your dataset.
Where this fits
- Check Dataset readiness check
- Describe Fit discussion
- License Managed Data Licensing
- Prepare Data Quality & Packaging
- Sell direct Direct-Sale Enablement
Not ready yet? Dataset readiness check. After this: Data Quality & Packaging.
Questions
Does this make Copia our broker?
No. Direct-sale support is billed for defined services. A separately signed brokerage mandate, if one exists, remains governed by its own terms.
What happens if the buyer changes its requirements?
We compare the request with the agreed specification. New work is handled through a written scope change, rather than an open-ended promise to obtain buyer approval.
Can we use the outputs with another provider?
Your agreement specifies your rights to the prepared deliverables and any tooling restrictions.