Atlas of Work
← All sectors

DATA PARTNERSHIPS / SOFTWARE

The work behind your software has value.

Explore licensing opportunities for the decisions, iterations, and expertise behind the software you build.

Explore a partnership Contact us ↓See the possibilities ↓

No uploads. No account. Start with what you know.

THE RECORDS BEHIND THE WORK

You may already have
more than you think.

Illustrative starting points for a conversation. Suitability depends on the records, the proposed use, and available rights.

01

Code & changes

Repositories, pull requests, review discussions, and release histories.

02

Problems & resolutions

Bug reports, support tickets, incident reviews, and the fixes that followed.

03

Product decisions

Specifications, technical documentation, and architectural decisions.

CONTEXT MAKES THE CONNECTION

More than a collection of files.
A record of how work happens.

  1. A reported bug
  2. The investigation
  3. A reviewed fix
  4. The resolved issue

Illustrative workflow for software.

A CONSIDERED PROCESS

Start small.
Define the opportunity.

A clear scope comes before a data transfer. Here’s the path we would work through together.

  1. Tell us what you have

    Describe your company, the systems you use, and the history behind your records.

  2. Explore the fit

    Discuss potential uses, data quality, available rights, and the records you would consider.

  3. Agree the terms

    Define the scope, permitted uses, handling requirements, and commercial terms before sharing data.

  4. Prepare, review, and deliver

    Follow the agreed preparation and acceptance process, with payment on the terms of your partnership.

YOUR DATA. A DEFINED SCOPE.

Clarity before
commitment.

Exploring a partnership starts with a description of your records. It does not grant access to your systems or permission to use your data.

What is included
Identify the records you can consider, and the customers, projects, or fields that need to be excluded.
How it could be used
Discuss the intended use, recipients, and licensing boundaries before agreeing to a partnership.
How it would be handled
Agree requirements for preparation, access, sensitive information, retention, and deletion.

A FEW THINGS TO KNOW

Before we begin.

Can we explore this without licensing our source code?

Yes. Start by describing the documentation, issue histories, or other records you would consider. The assessment does not commit you to including a repository.

What about code written for clients?

Flag client work and third-party dependencies separately. The next conversation should establish what your company can license and what needs to be excluded.

LET’S START A CONVERSATION

Contact us.

Tell us a little about your business and what you have in mind. We’ll help you explore the possibilities.

No files or system access needed.
No commitment to license your data.

Prefer a guided assessment? →