OrangeDAO

Full proposal doc: https://docs.google.com/document/d/1-jPu2BBXT_Ub8NmIVLA5f6yXDJrr8WHj6elIkblqJuI/edit#heading=h.3bs9563px4gi

Single Point of Contact: David Head (davidh.eth) Goal: To compensate myself for work done since Nov ‘21, and will maintain for the rest of Season 0. Work Summary When I joined the DAO in October ‘21, new members were “signing up” by posting their wallet IDs in a Discord channel. None of it was structured, and we had no emails to re-engage people with.

Then separately, all of our major announcements were being posted in Discord. A vast majority of our DAO members (especially the most successful ones) are not active in Discord. It’s too noisy. So we had little way of engaging them more.

As a solution to this, I designed, built, implemented, and have maintained a new member onboarding workflow to capture structured data on new members including emails, wallet IDs, and Discord IDs. So far 419+ DAO members (~33%) have gone through it to date.

Then I took those profiles and used them to launch a new email communication channel. Currently it has a ~75% open rate and a ~30% click rate, which is ~3.5x and ~10x higher than the industry average, respectively. I’ve been maintaining and distributing communications through this channel to date.

Details on Contributions & Tokens Requested New Member Onboarding Flow - 25,000 $ORANGE Work Duration: (Nov ‘21 - April ‘22)

Problem: When I joined the DAO in October ‘21, new members were “signing up” by posting their wallet IDs in a Discord channel.

We had about 200 IDs in a channel. None of it was being captured as structured data. And we weren’t capturing any emails to be able to re-engage members with. Solution I designed and built a new onboarding workflow, then worked with stakeholders to integrate it into the existing onboarding flow channels (i.e. Bookface). Resulted in capturing structured profiles for 419+ members, or ~33% of the DAO. Still is in use today. Line Items Cleaned Discord data of ~200 members from thread of individual messages listing Discord IDs and Wallets to airdrop $ORANGE tokens into Seeded database with Discord IDs, timestamps of submissions, and $ORANGE token wallets. Setup dev@ account for tooling to be owned by Researched database options Setup database Researched form options to reliably associate seed data with future emails, preferences, and other data capture Setup forms Audited current onboarding channels Developed plan for updating channels to include the new onboarding flow with UX in mind Worked with owners of current onboarding flows to execute plan Continuous monitoring of onboarding forms for reliability Iterated on forms to make onboarding more simple as we gained more knowledge on current and future use cases General maintenance Value: Build an email list of 419+ members (as of 3/10/22) Likely captured close to 100-150+ more member profiles due to urgently acting, as the rate of onboarding new members was much higher for a few weeks initially. High quality seed data for future web applications Since the data is structured and email and other metadata is associated with other IDs like Discord ID and Wallet ID, it is able to be higher quality seed data for future Orange DAO applications. This will enable a smoother onboarding experience for “Connect with Wallet” applications.

Launching Email Communication Channel - 20,000 $ORANGE Work Duration: (Nov ‘21 - April ‘22)

Problem: In Nov ‘21, most of the DAO didn’t know what we were doing or how or when to engage.

For example, we were posting newsletter digests in the #announcements channels in Discord. But most of our DAO does not actively use Discord. Especially our most successful members. There are simply too many channels and messages. So any fund activity, new app development, proposal activity, etc wasn’t being seen by most members. Solution I used the structured member profiles from the New Member Onboarding Workflow to launch an email channel with a ~75% open rate and a ~30% click rate. I’ve been distributing our email communications through this channel since Nov ‘21. Line Items: Newsletter distribution software setup Seeding and syncing new member data Newsletter template creation, routine enhancements, and maintenance Routine conversion of Notion/PDF into email-acceptable format Deliverability audits and troubleshooting Ongoing communications distribution Value: Increased visibility for new applications being developed Easier growth channel for new apps to get new members Increased exposure for Orange Fund activities Increased proposal engagement Increased visibility of Orange DAO events Increased visibility for miscellaneous other use cases

Building Proposal Workflow v1 - 5,000 $ORANGE Work Duration: (Nov ‘21)

Problem We didn’t have a way to track proposals being created, or the status of them.

Solution Setup a no-code workflow for members to clone a template and progress through a series of steps, which would track the statuses of which in a database. Work Done Drafted spec with governance leaders to go from template > comments > dissents > final, as well as auto-increment numbers and track stages Circulated spec for feedback Finalized spec Evaluated database solutions Setup forms to track status changes at each stage change Setup notifications and messages from dev@ accounts with instructions Setup workflow automation software Refined flows for UX (comprehensibility) Launched to community for use on OIP-10 and forward Maintained software Value Helped initiate a pre-proposal system and workflow for DAO improvements. Helped track proposal statuses across DAO.

How was the $ORANGE comp determined?

Value driven to the DAO. We could assume that just one hyper-successful member in our DAO could drive millions or more in value. Before my work here, it was unlikely that many, if any, of those hyper-successful members knew about any of the projects we were working on. Now it’s likely that many of them are regularly seeing ways to engage.

The stage of the DAO. The bulk of my time on these projects was spent working in Q4 ‘21. $ORANGE tokens didn’t exist then even, so there was little idea of what their value should be for project work. It seems like there should be a premium placed on work done at this point relative to now when it is more clear.

Using other project comp as a benchmark. Other projects in Q4 ‘21 had up to 1,000,000 tokens allocated to them at this point. Granted, those were much more technically complex and had multiple members getting token distribution. So I’ve adjusted for that accordingly.

Token Distribution: 50,000 $ORANGE to be paid out immediately to davidh.eth.

(Sponsors’ control) $ORANGE

Risks: (Open to All Members)

Counterpoints: (Open to All Members)

ADMIN: FOR TREASURY: Transactions Upon Passing: Send 50,000 $ORANGE From: 0xXXXXXXXXXXXXXXXX (Treasury Gnosis Multisig) To: 0x16D56FA9b31479315a05b0b31F83D88f5F8Ca6e4 (davidh.eth’s wallet)

Special thanks to the following 🍊’s for helping me revise: Maqq Enx Huh.eth Don Ho Oparrott.eth Cryptpalsingh Johnny Chin Byron