• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
Orange DAO Orange DAO by0x4558e88C5a972244c995AE4DD95a84fc790355f9huh.eth

OIP-18: Orange Fund Portfolio Support System v1

Voting ended about 4 years agoSucceeded

Full Details https://docs.google.com/document/d/1pzQa85vUKLENXPG_Pd1OwNYIMQ88ktQQv8HuOC2XtiM/edit#heading=h.jihimw60zxbi (This proposal contains detailed indented lists of token distribution and rewards. Snapshot's formatting does not reflect this. Please use the Google Doc instead to review.

Goal Create v1 of a working system to enable Orange Fund Portfolio Companies to receive support from Orange DAO members and Orange Fund LPs

Point of Contact @Byron#4552

Sponsors @JeremiahSmith#5560, @tilde#2915, @pineapple#5176, @annapinol#3471, @Byron#4552

Description Background

Orange DAO is uniquely qualified to provide massive value to Fund Portfolio Companies (“PortCos”) because of the broad network of talent within its Members. We seek to unlock the free flow of value between the Fund and the DAO such that they may help each other in mutually beneficial ways.

This is the first step forward in creating systems that can provide structural long-term value for the DAO and Fund. Similar to how YC has bookface, office hours, etc that makes it easier for us to share value with each other, if we can establish the processes and cultural norms, it helps the value-flow happen. Inversely, when funds are just like "tell us how we can be helpful" - often that doesn't go anywhere. because it's just too broad. Instead, we will give PortCos a "menu" of ways that we can help, that makes it easy for them to say yes. Then we need the systems to meet those needs scalably.

Deliverables For this initial v1 of the Portfolio Support System, we will create the core infrastructure for PortCos to start receiving the help they need.

The plan is to create: PortCo Onboarding document + experience An onboarding [Notion] document for PortCos which includes a suggested process and tips to get started with Orange DAO PortCo Support System A database of PortCos [ie a form to create and update profiles that we work with the Fund to ask all PortCos to complete] A way for PortCos to post and easily update their current needs for help. [ie a secure form to update current needs per PortCo] A way for help requests to get channeled to the best destinations [ie Zapier automations to send different types of requests to specific Discord Channels, people who will take action, or other content databases] A gated way for Members and LPs to browse PortCos needs, to assess where they can help then volunteer [ie a gallery where all current needs can be viewed with token gating] A way for Members and LPs to volunteer to help meet these needs.
[ie the above gallery containing contact info and Cal links for booking] Assistance + Compensation Tracking System A way to track when Members volunteer to help serve PortCo requests or otherwise provide value A simple way to track the status of their $ORANGE compensation
Establish a team (Portco Support Committee) until the end of Season 1, which will: Act as Point-of-Contact to receive requests from PortCos, and ensure some timely response to every request Triage PortCo needs and updates into the system as needed Help ping known resources within the DAO to facilitate PortCo requests Coordinate and iterate on help requests Iteration often looks like replying to the PortCo to request additional details such that the needs are clearly understood, so that assistance can be provided. Provide cleaned and updated request summaries to publish in Member email newsletter Regularly ping PortCos to update their needs Coordinate marketing amplification requests Triage Fund requests to coordinate w PortCos as needed Provide reports on Support utilization and assistance provided Benefits Build an MVP of a PortCo support mechanism Support PortCo onboarding to Orange DAO Improve ability of Orange Fund/Orange DAO to support portfolio companies Increase engagement and satisfaction of Orange DAO Members by providing opportunities to interact with and help other founders Success Metrics / KPIs Percentage of PortCos onboarded into database (minimum 60%, target 90%+) Percentage of PortCos in database that have submitted some sort of help request (minimum 50%, target 70%) Percentage of PortCos that have received some assistance (minimum 40%, target 60%) Monitor number of live Orange Hour sessions (no target) Monitor number of asynchronous help requests completed (no target) Monitor number of unique DAO members providing assistance (no target)

Duration Start: Upon approval End: End of Season 1

Tokens Requested - 206,000 $ORANGE in total Treasury control 86,000 $ORANGE total for creating and supporting the system through Season 1 15,000 for initial planning, user research, testing, and iteration (Byron#4552) 1,000 for proposal writing (Byron#4552) 10,000 for creating the PortCo Onboarding document + experience 7,500 for primary creation to JeremiahSmith#5560 2,500 for feedback and support to Byron#4552 40,000 for creating the v1 PortCo Support System 30,000 for primary development to Byron#4552 10,000 for development support to JeremiahSmith#5560 20,000 for creating the Assistance + Compensation Tracking System 15,000 for primary development to pineapple#5176 5,000 for development support to Byron#4552

Sponsors’ control 120,000 $ORANGE to fund additional compensation for DAO Members 30,000 $ORANGE total to fund Members (& maybe LPs) that provide assistance to PortCos through Season 1 $ORANGE payments for help will be paid at the discretion of the PortCo Support Committee Projecting 100 $ORANGE per hour live Orange Hours call Projecting 50 $ORANGE 30 minute live Orange Hours call Projecting 50 $ORANGE per asynchronous written help Projecting 1 $ORANGE per re-tweet (would need someone else to build the tracking system for this) Amounts may be adjusted as required to meet supply and demand by the Sponsors

Unused $ORANGE by the end of Season 1 will be refunded to the Treasury

40,000 for PortCo Support Committee to coordinate and support PortCo requests through Season 1

Currently volunteering to help pineapple#5176 tilde#2915 annapinol#3471 Byron#4552 JeremiahSmith#5560 peerrich.eth#3508 maqq#6908

Welcome additional Members as we get started, we hope others will show interest Final allocation of the 40,000 $ORANGE will be allocated fairly by group consensus of the Sponsors according to help given 50,000 $ORANGE for additional compensation for DAO Members that complete necessary but currently unforeseen work required to meet the goals.
Given the solution is still being developed, it is likely that the final strategy will continue to evolve as things are built and tested. These tokens will allow fair compensation and flexibility to adapt as the scope of work changes. Could comprise either additional building, or additional support activities Final allocation of the 50,000 $ORANGE will be allocated fairly by group consensus of the Sponsors

RISKS: (Open to All Members) Byron: If there is not enough volunteers, PortCos may stop using the system if they don’t find it valuable Byron: PortCo Support Committee would have ability to self-select or otherwise influence member volunteers Enx: tremendous scope could lead to not finishing, late delivery, difficult to track status, etc.

COUNTERPOINTS: (Open to All Members) Byron: If there are not enough volunteers, we would probably not mind if Committee members did self-select, as some volunteers are better than none. Byron: to Enx’s point: I added some additional detail up above to make the deliverables more clear and tangible. Hope that helps. The current plan is to use something simple like Airtable with some automations. I’m looking into alternatives to see if we can easily improve the UX without increasing the work too much. (ie discussing with Code2.io)

ADMIN: FOR TREASURY: Transactions Upon Passing: [Treasury to write]

Definitions

Additional thanks to Cryptpal Singh Orion Parrott Johnny Chin Chris Stanley

Off-Chain Vote

Yes: Allocate 206,000 $ORANGE
297.84K 100%
No
0 0%
Abstain (Counts towards quorum)
0 0%
Download mobile app to vote

Timeline

Feb 18, 2022Proposal created
Feb 18, 2022Proposal vote started
Mar 04, 2022Proposal vote ended
Oct 11, 2024Proposal updated