Yeeter Fundraising Case Study
- Role
- Sole designer: UX, UI, branding and illustration, from requirements gathering through review of the shipped product.
- Timeline
- Mid-December 2021 to release in February 2022
- Funds raised through the platform
- 871.67 ETH / $73.3k DAI
The Project Brief
Yeeter lets people create a crowdfunding project with multiple core team members, and contributors can pull their funds back out at any time. We wanted a fundraiser built on top of our own system, and we ended up using it ourselves to raise about a million in funds to keep building our project. For the business, it would:
- Bring in funds (3% of each raise) for further platform work
- Funnel new people onto our platform
- Let us use it for our own fundraising
Step 1: Understand the Goals
- Worked closely with our lead backend dev to deeply understand the smart contracts: what they could do, and what limits we’d run into.
- Did competitive research on Kickstarter, Indiegogo and Juicebox for shared patterns and must-have features.
- Ran research interviews with interested community leaders and helped a few small projects launch as our first raises. They wanted something that fit into the platform they already used, and an easy way for supporters to send crypto straight to the DAO.
Step 2: Information Architecture & Flow
I made a user task flow diagram and iterated on it with the team to map where data is used, how things should function, and where you interact with the blockchain.

Step 3: Wireframing
Next came wireframes for early direction, with lots of back and forth with the team.

Step 4: Final Designs
Since we were a small, fast team with lots of communication, I kept the specs simple: screens for each state of the project page (contributed or not, funding met or not), the main project view, and the landing site, done with copy editors.
Step 5: Development & Release
I worked with 3 engineers to find solutions that balanced usability with technical limits, cut extras to meet the timeline, and made quick usability fixes during the first few raises.
Lessons Learned
- As an organization we should have put more energy behind the project after it launched. A few updates, key features and some marketing could have made it much more successful.
- We slimmed down the project description area, planning to come back to it. We should have built it in from the start, like a lot of competitors do. There is nothing more important than the description of the project; it’s the soul of the fundraiser. Unfortunately we never got to go back and update it.






