Code, tickets and chat: are you pricing the wrong asset?
The Price Index puts a private repository at an estimated $150 to $1,500 per sale and an operating-company archive at $185,000 to $1M+ per company. They price different things. If you own the tickets, discussions and decisions around your code, establish that broader scope before deciding which comparison fits.
You have years of private code. You also have the support desk that recorded what broke, the engineering conversations that explained the choices, and the work tracker that followed a fix. When you ask what the code is worth, do those records belong in the appraisal?
That decision matters before you negotiate a number. A repository license buys access to code and its history. A company archive can include the record of work across several systems, teams and years. Its appraisal asks different questions and may involve different license terms.
A current Rightmark listing makes the distinction concrete: 30 repositories, about 4.2 million original lines and about 70,000 support tickets, with engineering chat, work tracking and error-monitoring data in the same proposed package. The missing evidence is whether those records can actually be followed from a reported problem to a change and its outcome.
For an owner, the useful next step is to map that connection. The larger archive benchmark does not establish this package's price, and adding a chat export does not by itself qualify a code collection for it.
First establish what you are offering
The listed code-and-records package brings together a selected code collection and the surrounding operational records. Its scope describes what is available for review; it does not establish that every ticket can be matched to a change.
| What the listing puts in scope | Recorded amount or status |
|---|---|
| Combined code selection | 30 repositories |
| Original code in that selection | About 4.2 million lines |
| Support desk in the proposed package | About 70,000 tickets |
| Additional systems | Engineering chat, work tracking and error monitoring |
| Ticket-to-commit links | Not checked yet |
Scope and calculation: the two code selections overlap, so 14 + 19 - 3 = 30 unique repositories in this selection. Code measurements are dated October 20, 2026; the owner's record description is dated October 21. The live listing was checked October 23. Large figures are rounded. These are one owner's listed records, not a market sample or proof of completed delivery.
The 70,000 tickets are relevant because they may contain the requests and resolutions around the software. They are not 70,000 verified coding tasks. Some could concern configuration, billing or a duplicate report. A repository can also address many tickets, and one ticket can require changes in several repositories.
The code count answers how much code is in this selection. It does not answer how much of the company's work can be reconstructed. Those are separate measurements, so they should stay separate in the appraisal.
The money question: a repository price or an archive price?
The current Rightmark Price Index, Q3 2026 provides two relevant reference points. Read the dollar amount together with its unit and license scope.
| Price reference | What is priced | Evidence and commercial stage |
|---|---|---|
| $150 to $1,500 per repository, per sale | A non-exclusive private-code license with full git history | Medium confidence. Rightmark's September 2026 summary of public-program pre-sale estimates. |
| $185,000 to $1M+ per company | An operating-company archive from a team of 30 or more, with mostly English records across company systems | Medium confidence. Rightmark's 2026 summary of published program calculators and stated ranges for exclusive lump sums. |
All amounts are US dollars. Index published September 30 and updated October 10, 2026; checked October 23. These are published estimates and program reference ranges, not verified offers or completed payments for the listed package. The rows do not establish the owner's net proceeds, preparation costs, tax or final contract terms.
The commercial insight is about which asset and agreement you are pricing. Multiplying 30 repositories by a standing rate would model a code-license scenario. It would not value the support desk or the company's operating history. Applying the company band to those same repositories would be equally unsupported: the broader archive has its own qualification and scope requirements.
The company row describes substantially more than a bundle of files. Rightmark's published program summary identifies team size, years retained, region, English-language coverage and connected tools as appraisal inputs. Several years of records are commonly required. A collection must be reviewed against those inputs before the benchmark is useful for its owner.
The rights being licensed also differ. The code reference is per non-exclusive sale. Company-archive lump sums usually involve exclusivity over an agreed term and scope; a non-exclusive revenue-share route is a separate option. An exclusive quote and a non-exclusive quote are different commercial proposals even when they concern the same records.
Owner insight: ask for the proposed scope, permitted use, exclusivity and payment basis beside the amount. The first question is whether you have a code asset, a broader operating archive, or both. The next is which licensing route fits what you are willing and able to supply. Neither range supplies a price premium for linking one additional tool.
Indicative estimate, not an offer. Final offers depend on the systems you connect, data size and quality, access terms and due diligence.
Show the work between the files
The company operating archive lot describes the intended use: teaching agents how office work gets done across tools, including coordination, follow-up and escalation. Its preparation criteria call for several years of linked records, with identifiers masked while useful connections are retained.
An owner can begin with one real chain of work:
- A customer reports a problemThe original ticket, its date and stable reference
- The team chooses a responseThe relevant discussion and its connection to that ticket
- An engineer changes the productThe issue or pull request and the exact code revision
- The change is checkedA test or other recorded check tied to that revision
- The outcome is recordedThe resolution or follow-up linked to the original problem
This is an editorial preparation framework, not an observed completed workflow in the listed package or a universal requirement for every buyer. No completed-chain count or archive-wide linkage rate has been established here.
Preserve the references that make a relationship inspectable. A conversation and a commit happening on the same day do not prove they describe the same work. If the original records link them, retain that connection in the proposed review sample. If the relationship is uncertain, mark it as uncertain.
This also explains why preparation should happen before a large export. If separate masking steps remove every shared identifier, a reviewer may receive readable files but lose the relationship between them. The target is a reviewable, appropriately de-identified connection, with the original private material kept under controlled access.
Spend preparation effort on the gaps that change the decision
Start with a short map of the systems you can include: the period retained, approximate volume, available linking fields, export state and exclusions. Confirm that the systems cover overlapping teams and years. Ten years of code and three months of unrelated chat should not be described as ten years of connected company history.
Next, prepare a small, reviewable example that shows the references at each handoff. Record missing discussion, missing attachments or an unverified outcome instead of filling the gap with a new explanation. One complete example demonstrates a possibility; it does not establish how often that chain exists across the archive.
Then separate the questions that change commercial scope. Does the company control the relevant material? Which client-confidential records must stay out? Can the required exports be used for the proposed purpose? What portion would an exclusive license cover? The listed package itself requires a rights and privacy review before delivery.
The result does not assure a higher offer. It is a clearer basis for an appraisal: what the owner can supply, what a reviewer can verify, what still needs work, and which commercial route merits further discussion. That clarity helps an owner decide whether to prepare a broader archive or continue with the code-only route.
What this note establishes
This is a scope analysis of one public, owner-approved listing, supported by Rightmark's published Price Index and current lot criteria. The listed code and record volumes were rechecked on October 23. The source does not supply a package estimate, completed payment, measured linkage rate or a price uplift caused by linked records.
The operating-company band is Rightmark's aggregate summary of published programs; the index does not provide the underlying calculator links. We therefore retain it as an attributed benchmark rather than claiming an independently verified buyer offer. No private buyer terms are used in this note.
The conclusion for owners is practical: describe the work your records preserve before choosing the price unit. Code volume helps price code. A company-archive assessment also needs the systems, history, relationships and license scope around it.
The data we are looking for
Rightmark is assembling company operating archives from agencies and software companies: owned chat, documents, tickets and wikis, with several years of records across tools and useful connections preserved. The lot was in preparation on October 23; the Wanted board showed no active requests. The separate listed code-and-records round was scheduled to open October 27. Neither status is an offer to this reader.
The relevant company-archive reference is $185,000 to $1M+ per company, Medium confidence, under the scope and program-estimate limits above. It is a reason to establish whether your archive fits the route, not an earnings forecast. Code alone has the separate $150 to $1,500 per-repository, per-sale standing-rate reference.
Appraise your company archive. Start with the systems, years, team size and rights you can describe; the initial appraisal asks for no files or system access. It provides an indicative range and route assessment, followed by a separate review if you request one.
For a package that spans several systems, talk to Rightmark about the scope. For the code component, run Repo Check locally. Bring the map of your archive and the gaps you know about. That is the next useful step toward finding out what can be licensed and on which terms.