Project research

OCV has scraped high-level information on 28k of all GitHub projects for consideration as of April 2024.

Initial review

Projects with greater than or equal to 20 monthly merged pull requests or 5,000 stars with permissive licensing (MIT, Apache, BSD) will be considered for initial review.

In the initial evaluation of potential projects, pasting the GitHub repository URL into an OCV Slack channel will yield some information and enable the creation of a research document.

Some fields will be pre-populated by the creation of the research document, while others will need to be filled out in an initial review. A reviewer should check the following before putting a project ahead for full research:

1. Source: Where the project came from.

2. Activity: If the project is no longer as active as it once was, it may not be a good fit. Check that it still meets the activity benchmarks above.

3. Existing incorporation: Check if the project has an existing company around it. - -

   1. Websites associated with the project may be a good source of information, and reviewing the LinkedIn profiles of top contributors.

   2. Small companies that are not venture-backed or provide consulting services (and don’t sell software as a service) may be okay to still pursue.

   3. Companies backed by large corporations may still be interesting. For example, if a large company has abandoned it, or if we can recruit talent.

   4. Avoid cryptocurrency and blockchain projects.

4. Business case: If a project is active and doesn’t have an existing company around it, it still may not make sense to start a new company around if there is not a good business case to be made. Checking for large competitors in the same market may provide a barometer for this.

5. Location of key contributors: There are some geographies where we can’t hire.

If there are no outstanding limitations from an initial review, ask an OCV partner if the project seems commercially viable.

A reviewer will mark the project under Status in our tracker as either:

1. Research TODO and add an Assignee to the project for full research or,

2. Mark it Closed Project and provide a Reason Closed.

Full Research

There is a backlog of projects with some initial review completed. By default, they have a P-level of Other.

When an OCV partner recommends a project, it becomes a P-1 and skips ahead of potential research in the backlog. A reviewer is not to get started on P-1 projects. Full research will begin with some information in the research doc from an initial review and build upon it to form a more complete picture and provide actionable next steps.

Starting a new research doc

Researchers should add their names to the assignment in the document along with any notes from partners about a project. Provide and explain the technical background of a project sufficiently to a non-technical reader.

Gather information, including online professional profiles (LinkedIn, blogs), project commit activity, professional information, location, and emails of top contributors to projects. Information on the market should be provided along with a review of the competitive landscape for both companies and other projects. Provide conclusions about the market, project, and top contributors.

Look for contributors who are:

1. The most tenured (contributing for the longest or a long period of time relative to others)

2. The highest or a high-ranking contributor over all time and recently

3. Currently active as a contributor

4. Located in geographic regions where we can hire

Be aware of what may be blockers, indicating that additional time should not be spent on the project. Those where there are potential blockers but are P-1 should be highlighted for review with that partner.

Reviewers should take a look at the full research and discuss any questions about the market, project, or contributors in the #research Slack channel or during a weekly sync call.

Contributor outreach

After a reviewer has checked that the research is completed without blockers, proceed to reach out to the contributor identified.

All outreach notes (date, contributors, their responses, etc.) should be added to the individual research docs. Initial outreach should be marked in our tracker, use messaging of _Template Initial Founder Outreach, and should be sent using a pixel tracker via email. After each week, outreach should be escalated to a follow-up. From Business Operations to COO to partner.

If a meeting is booked, mark this in our tracker, take notes in the research document for that meeting, and mark if the contributor or project closes out based on that meeting. If a meeting is not booked, mark the reason for close in the tracker as non-response and the status as next contributor until another contributor is found (before closing the contributor).

When all viable potential contributors have been exhausted via outreach, close the project if it is P-Other, and check for new contributors later if it is P-1.

Finding contributor emails

To find (non-work) emails for project contributors, try the following:

1. Their online profiles

2. Contactout for LinkedIn

3. Github commit examination

   1. Find a commit on a contributor profile

   2. View commit details

   3. Add .patch to the end of the URL

   4. Review for an email that is not attached to @users.noreply.github.com

Use LinkedIn for initial outreach when no email can be found.

Close out

When a project is not a fit for our criteria, is otherwise not viable, contributors have been exhausted (excluding P-1 projects), or a partner rejects a project, close it out.

Mark the project as closed in our tracker, add - CLOSED OUT to the research document title, and include the reason the project was closed in the document.