FOR SOFTWARE COMPANIES

Your repo history is an argument about why the product is shaped this way

Design docs, RFCs, pull request discussion, incident post-mortems and years of support threads. Engineering culture forces reasoning into writing, and that written reasoning is the scarce part.

Check your data Six questions, roughly two minutes.
Reasoning is already written downIncidents and post-mortems are dense materialNo equity, no debt, no board seat

WHAT ABOUT OUR CUSTOMERS

Scope first, anonymization before anything moves

  1. 01

    Establish what exists

    Six questions about your stack. No systems are touched and nothing is shared at this stage.

  2. 02

    You set the boundary

    The licence covers a defined slice. Anything you are contractually unable to license stays outside it.

  3. 03

    Identifying fields stripped

    Anonymization is part of preparing the data, handled before anything is shared onward.

  4. 04

    Paid on completion

    Typically $100K to $2M, Net 30 to 60, once the data has been approved, shared, and anonymized.

SPEAK WITH A MANAGING PARTNER

Price the decisions your team already documented

Six questions and one short conversation will tell you whether there is a deal here. Nothing you tell us leaves Polyshares.

Check your data