Company data has no standard price. Assess a specific offer against its scope, requested rights, preparation work, delivery requirements, and payment conditions.
Employee count is not a quote.
A useful price discussion needs defined material, an interested buyer, the rights requested, and the obligations involved. Company size and retained history only frame the conversation.
Origin does not provide valuations. These factors are questions to investigate, not scoring weights or promises of a higher offer.
What should a price discussion cover?
Start with the records, their context, and the proposed use. Ask how quality, volume, connected workflows, and preparation work affect the offer.
Ask the receiving company to explain its assumptions. A preliminary estimate is not a payment commitment. Review licensing requirements separately from the offered price.
Scope and quality.
Define teams, workflows, dates, categories, and exclusions. Counts can include duplicates, gaps, inaccessible links, or material that must be excluded.
Can records be sequenced? Are decisions and outcomes connected? What preparation is required? Ask whether a company-level description is enough for the initial evaluation.
Continuity and uniqueness.
Investigate what the history explains across a process and what may be distinctive. Being internal does not itself establish uniqueness or value.
Compare an archive of closed tickets with one that also retains investigation notes and verified fixes. Describe those differences before discussing price.
Rights, demand, and permitted use.
Ask what the buyer wants to accomplish and which permissions it needs. Investigate whether your company can grant them and whether the proposal fits its priorities.
Compare offers for the same scope. A license can grant exclusive or nonexclusive rights. Clarify those rights alongside ongoing work and termination conditions.
| Factor | Question to resolve |
|---|---|
| Scope | Which records, dates, and exclusions does the offer cover? |
| Rights and uses | Who can use it, for what, and for how long? |
| Company effort | What preparation, delivery, updates, or support are required? |
| Payment | What triggers acceptance and payment? Which costs or conditions apply? |
Compare the whole proposal.
Record scope, rights, deliverables, dependencies, payment triggers, and unresolved questions. Have finance, operations, and specialist reviewers assess the same terms.
Confirm the payment amount, acceptance criteria, and payment date in the agreement.
Use the diligence guide before committing. Read how it works for Origin’s initial role.