---
# System prepended metadata

title: TurboTools!
tags: [Project Proposal Engine]

---

---
###### tags: `Project Proposal Engine`
---

# TurboTools!

![](https://i.imgur.com/Yd8kSDp.jpg)


### 1. Name or working title of the project
TurboTools!

### 2. A logline (one sentence description of the product)

Turbo Tools is a suite of tools designed for rapid, decentralized application development on DAOhaus. 

### 3. Details

This product is a supercharged version of the current DAOhaus toolkit. Similar to Wordpress in the early Web2 era, TurboTools aims to productize a suite of development tools for building DAOs and DAO interfaces, driving developer adoption by greatly simplifying the DAO building process.

Beyond the software products, TurboTools also fosters developer community through its own TurboTool DAO (The TurboShed), regular live coding sessions, bounties, cohorts, consultation sessions, and more.

In short, Turbo Tools allows developers to build faster, better, and more decentralized applications. 

#### who will use this 

- Developers who are in interested in building a DAO platform application or an application for a single DAO.
- These developers do not need to have a lot of experience building DAOs 
- Community managers who use the low/no code tooling (form & TX builder) 

#### why would it be useful

- Writing the TX for a single proposal on a Moloch DAO is labor intensive. DH tooling has greatly simplified that process. 
- We are only scratching the surface. With a tighter focus, revenue streams, and a strong developer community, we can simplify this process far beyond where it is now
- **Censorship Resistance:** The tooling, as it stands, is fostering an emerging pattern of Distributed Application Development. This allows portions of the app to be stored in IPFS as legos or building blocks. Saving modular components of applications on the perma-web is potentially a more flexible and useful form of application resilience than the monolithic IPFS hosting pattern used today. 

#### what problem is it solving

- *The DAO complexity and accessibility problem.* DAO Interfaces are really hard for any user who isn't a DAO nerd. Having better, faster, cheaper tools will allow the ecosystem to: 
    - Experiement and find UX patterns that drive engagement and user empowerment
    - A better tool suite that lowers the bar of entry for DAO builders. Instead of learning all the data-manipulation logic of the contract, subgraph, and application architecture, developers can focus more on the application's business logic. 
- *The Imperative interface problem*. DAO apps currently allow users to interact with the contract imperatively, meaning that the application forces users to use the contract in the way that it was written. However, this is only useful to users who understand the inner workings of the contracts. Users should be focused instead on the game of governance and the community logic of their DAO. 
- *Frontend Centralization*. App building blocks stored on IPFS could allow users, DAOs, community engineers to configure their DAO's shape by selecting decentralized building blocks of an application. Front ends are the current weak link in decentralizing applications. Hosting front ends on IPFS only get us part way there. Hosting parts of apps on the permaweb adds an additional level of security and flexibility to Dapps.   

#### how can it be built with our tooling

It is our tooling. 

#### why the timing is good

- Currently, there is interest in building with our tooling
- Development of the tools is the main bottleneck
- We have no funding set aside for maintaining these tools (beyond a few months)
- Developing product strategy around the tooling could accelerate the utility and power of these tools, both in terms of community engagement and sustainable funding for the project as a whole. 
- Lifting the financial burden of DH tooling (and some aspects of devrel) from the core protocol will allow DH to further decentralize and focus more on community and protocol goverance

#### how it might generate revenue

Before talking about revenue, it is important to stress that the tools -- in order to be effective and popular -- are and must always remain open source. Putting the tools behind some sort of paywall (good luck trying anyways) would ruin their credibility, reliability, and overall use. For this reason, development of the tools will always be a loss-leader for other revenue models. 

But that doesn't mean in anyway that these tools couldn't generate revenue through a DAO. Here are some of the ways a DAO of core contributors could turn a set of open source tools into a profitable enterprise. 

**Non-Scalable Means**
- Consulting
- Services (building, troubleshooting, debugging, maintaining)


**Scalable Means** 
- Educational Content and Courses (paid courses)
- Technical Consortium Governance. Using a token or Baal shares/loot to offer governance of the tools. 
- No/low coding applications for dapp development. While the tools themselves will need to remain open source, we could use the tools to build GUI applications that are closed-source. These could be gated by a membership in a DAO or through a token. It's worth noting that these are still tools and could provide even more utility to the core offering. 

#### anything else you feel is important.

(notes for later; Write your ask. What do I want from this? Why invest? How would investors see their return?)