Stackles: “Bookmarking and File storage” tool for DAOs and Web3 Ecosystems

[GENERAL] Name and surname of main applicant

Osinachi Patrick

[GENERAL] Email address of main applicant

sinachpat@gmail.com

Additional applicants

• Obongono Udosen (Research & Marketing) - (https://www.linkedin.com/in/obongono-udosen/)
• Soumyadeep Roy (Software Engineer) - (dev-soumyadeep (Soumyadeep Roy) · GitHub)
• Tiffany Yang (Software Engineer) - (https://enterthevault.app/, tiff0000 (tiffany6.eth) · GitHub)
• Ekta Singh (Project and Business Development) - (https://www.web3lex.io/, LinkedIn)

[GENERAL] Please specify how many months you expect your project to last (from 2-12 months)

6

[GENERAL] Please indicate if your proposal has been auto-translated into English from another language.

No

[GENERAL] Does your project have any dependencies on other organizations, technical or otherwise?

No

[GENERAL] If YES, please describe what the dependency is and why you believe it is essential for your project’s delivery. If NO, please write “No dependencies.” .

We don't have any dependence on any organisation.

[GENERAL] Will your project’s output/s be fully open source?

No

[GENERAL] If NO, please describe which outputs are not going to be open source. If YES, please write “Project will be fully open source.”

Our first set of outputs will be the Web platform and the Plugin which would both not be open source.

After this first release, then we'll build our public APIs that enables builders extend our functionalities and features to their platform.

[METADATA] Category of proposal

DAO

[METADATA] SDG rating

SDG goals:

• Ensure inclusive and equitable quality education and promote lifelong learning opportunities for all.
• Promote sustained, inclusive and sustainable economic growth, full and productive employment and decent work for all.
• Build resilient infrastructure, promote inclusive and sustainable industrialization and foster innovation.

SDG subgoals:

• Achieve higher levels of economic productivity through diversification, technological upgrading and innovation, including through a focus on high-value added and labour-intensive sectors.
• Promote development-oriented policies that support productive activities, decent job creation, entrepreneurship, creativity and innovation, and encourage the formalization and growth of micro-, small- and medium-sized enterprises, including through access to financial services.
• By 2030, substantially reduce the proportion of youth not in employment, education or training.

Key Performance Indicator (KPI):

• Annual growth rate of real GDP per employed person.

[IMPACT] Please describe your proposed solution.

Stackles is a powerful software tool that can help organisations manage their files and links in a simplified interface and a plugin with token-gating feature afforded for DAOs that want to gate their links, files and tools with a particular token access requirements. In today's fast-paced and digital world, businesses, organisations (Decentralised and Traditional) generate vast amounts of data and information that can be challenging to manage. With Stackles, DAOs in Cardano will really work in a decentralised way by easily uploading and organising files and links, making them readily available to employees and DAO members. DAOs within Cardano use multiple platforms for information sharing and collaboration like Discourse, and other tools for voting that are all fragmented so that a new member of an already existing member may always find it difficult to locate all the important tools, with Stackles DAOs can link all the tools and information they produce is an accessible interface where it's members can easily find it.

The tool is designed to simplify the process of managing files and links within DAOs. Employees or team members can access and share files and links with ease, reducing the amount of time spent searching for information and increasing productivity. It is also designed to improve the onboarding process of new recruits into any DAO. Stackles is easy to use and provides features that make it simple to find and share information and tools used in an organisation.

Stackles is built to boost your teams productivity and make it simple and fast for you to easily manage access to your files, links, and tools.

Any individual and organisation can use Stackles to improve onboarding, collaboration and navigation within teams, communities and groups. The tool at it’s core enables team to achieve these three things:

The Stack

An organisation/admin can stack tools, files and links in one place, making it easy for quick access to this assets when they are needed. This is seen in our MVP features of Collections, Boxes and Teams.

Collections:

These are different stacks of all the links within an organisation. Here the admin can easily create a new collection within an organisation and keep adding important links to the collection. The user can be able to share a particular collection to individual team members or invite a whole team ( — These teams have special permission requirements or not — ).

In later features, there will be added features that enables the user to import links from their bookmarks and also export links to their bookmark.

Boxes:

These are different stacks of all the files uploaded within an organisation. Here the admin can easily create a new box within an organisation and manually upload files within a box and add recordings of video/audio files of sessions from events done in Discord. The user can be able to share a particular box to individual team members or invite a whole team ( — These teams have special permission requirements or not — ).

In later features, there will be added features that enables the user to import files from third-party file storage integrations and also export files to their third-party file storage tools.

Teams:

The purpose of teams in the organisation is the different workstreams within an organisation for categorising — Workstreams refer to distinct components or streams of work within a larger project or initiative. They represent specific areas or tasks that need to be addressed and accomplished to achieve the overall project objectives. Workstreams are often used to break down complex projects into manageable and focused sections, allowing teams to organise their efforts and track progress more effectively.

Each workstream typically focuses on a particular aspect of the project and may involve different teams or individuals with specialised skills and responsibilities. Workstreams can run concurrently or sequentially, depending on the project's requirements and dependencies. They help provide structure and clarity to the project, ensuring that different activities and deliverables are properly coordinated and aligned towards the common goal.

Workstreams often have their own goals, timelines, milestones, and resources assigned to them. They enable efficient collaboration, as teams can work independently on their respective workstreams while maintaining overall project visibility and integration. By dividing the project into workstreams, it becomes easier to manage complexity, allocate resources, identify dependencies, and monitor progress.

Examples of workstreams in various projects could include design and development, marketing and communication, research and analysis, procurement and supply chain, testing and quality assurance, implementation and deployment, training and support, and so on. The specific workstreams depend on the nature of the project and the goals it aims to achieve.

This is where the members of an organisation who are not admins lives. This can be created and managed from the teams page or the settings page for organisations. There can be custom access requirements settings set by the admin for teams and there can also be free access teams — these are teams created without any access requirements.

Cardano DAOs and communities can be able to token-gate their organisation and teams within the community/ecosystem.

For teams with custom access requirements, the access requirements for teams collections, boxes and tools who are web3 based organisations and communities would be based on participation and engagements elements like Token, NFTs etc. Some of the options we can provide for admins to set to manage access are covered more extensively below. This design is with respect to the fact that these members would be signing up with their wallet address and under the hood we also provide a single sign-on system for organisations for all their tools.

[IMPACT] How does your proposed solution address the challenge and what benefits will this bring to the Cardano ecosystem?

1. File and Link Management: The software tool provides a single reliable and easy to access (URL and chrome plugin) user interface (UI) for managing files and links within DAOs and other organizations. By organising these resources in a verified environment, it eliminates the clutter and confusion that can occur when files and links sharing is scattered across different platforms, channels, or individuals. A dedicated UI that users can familiarise themselves with and trust improves accessibility to important governance-related documents and information. New files or links can simply be distributed to community members by uploading and saying “it’s in Stackles”.
2. Eliminating Scams in DAOs and Communities: Scams and fraudulent activities can pose a significant risk to DAOs and Communities. The tool helps address this by providing a secure and trusted platform for managing files and links. We will implement security measures such as authentication, access control, and encryption to ensure that only authorized individuals can add, modify, or access the resources (links and files) uploaded. Equally, new files or links can be added to this UI that users already know, hence reducing the risk of phishing. By reducing the risk of scams, the tool improves governance accessibility by fostering trust and confidence within the community.
3. Streamlined Organization: DAOs and collectives often involve multiple stakeholders, each with their own roles and responsibilities. Stackles makes it easier to organize and structure the files and links according to different categories, permissions, or access levels. This streamlines the management process, making it more efficient and allowing participants to quickly find the information they need. Improved organization and streamlined workflows contribute to better governance accessibility as participants can easily navigate and contribute to the collective decision-making process.
4. Collaboration and Transparency: Effective governance relies on collaboration and transparency. The tool can facilitate collaboration by enabling participants to upload, share, and discuss files and links within the collective. It can support version control, annotations, and commenting features to encourage constructive discussions and feedback. Furthermore, the tool can provide transparency by maintaining an audit trail of changes. By promoting transparency, the tool enhances governance accessibility.

[IMPACT] How do you intend to measure the success of your project?

1. Minimum Viable Product Delivery: Make sure a stable first version and maybe improvements of the product is released within the stipulated period.
2. Adoption Rate: Measure the number of DAOs and collectives and members that have adopted the software tool for file and link management. This KPI indicates the level of acceptance and usage of the tool within the Cardano ecosystem and web3 communities.
3. User Engagement: Track user engagement metrics such as the number of files and links uploaded, comments and discussions generated, and overall activity within the software tool. Higher user engagement signifies the effectiveness of the tool in facilitating collaboration and information sharing within the Cardano ecosystem and other web3 communities.
4. Reduction in Scams: Monitor the number of reported scams or fraudulent activities within the DAOs and collectives from the period of deploying the tool and a quarter after using the tool. A decrease in such incidents indicates the tool’s effectiveness in enhancing security and reducing risks.
5. Time Saved in File and Link Management: Calculate the time saved by participants, moderators and core team members of Cardano Community and DAOs in managing files and links compared to the previous methods or alternative tools. This KPI reflects the efficiency and productivity gains achieved through the streamlined management provided by the software tool.
6. Accessibility and Ease of Use: Gather feedback on the accessibility and ease of use of the tool through user surveys or usability testing. This KPI measures user satisfaction and indicates the tool’s ability to improve accessibility for participants with varying levels of technical expertise.
7. Governance Efficiency: Assess the impact of the tool on the overall governance efficiency as it provides a source of truth within the DAOs and collectives. This can be measured by tracking the speed of decision-making processes, the accuracy of information dissemination, and the level of safety within the DAOs and collectives.
8. Feedback and Recommendations: Collect feedback and recommendations from DAO members, collectives, and stakeholders after a quarter of using the tool. This qualitative data can provide insights into areas of improvement and inform future iterations of the tool.

[IMPACT] Please describe your plans to share the outputs and results of your project?

We intend to share the progress of this project any other way the funding team seems right but apart from that, we have multiple channels in which we share updates and we won't also mind if we are given a channel in the Project Catalyst server where we will share product updates, changelogs and update the community and receive feedbacks too.

Also, we already have a culture of keeping a strict journal/record of meetings, activities and plans in our Notion space. So we keep all the Stakeholders updated on all fronts.

[CAPABILITY/ FEASIBILITY] What is your capability to deliver your project with high levels of trust and accountability?

I, Osinachi Patrick will be leading the team with an experience and a background as a product lead and co-founder of previous startup Stanrute Technologies, FastHousing and other community projects, over the course of this project we have been able to sweat fund with so little resources and our personal savings and this can only lead us so far. Thus the need for this raise.

For my previous accomplishments:

Over the past 4+ years I have worked with product teams across Nigeria, United States and Kenya to deliver products in the Software, Fintech, Real estate, Blockchain and Supply chain management industries.

• I worked with Sonr Inc in the United States as a Product and Design Lead in their Sonr Learn product to discover, plan, design and design their blockchain network educational arm and ecosystem product idea factory which led to the preaching of the Sonr gospel within the African ecosystem and the online community reaching about 1,500 members within the community in my time of staying there.
• I co-founded and worked with Stanrute Technologies, a blockchain fintech startup in Nigeria to design and manage the building of a crypto trading OTC system that serves local and global traders leading to growth in MRR of $12,000 and delivered a crypto exchange product MVP that is in beta testing phase right now.

This is not me working on this alone, I also have a team of dedicated superstars behind me executing this which are:

1. Ekta Singh (Project and Business Development): Ekta Singh’s Master's background in IP Law, project and business development will be valuable in overseeing the execution of the mission. She can contribute to strategic planning, stakeholder management, partnership development, and ensuring the compliance of the project with web3 (or blockchain) regulatory requirements.
2. Obongono Udosen (Research & Community Relations): With a focus on research and community, Obongono Udosen can bring valuable insights into understanding user needs, and effective strategies for promoting and fostering the adoption of the tool. Her expertise in the community can help drive user acquisition and awareness.
3. Tiffany Yang (Software Engineer): Tiffany is a software engineering ninja with 5 years of experience working with companies like Pixel Vault, Beagle.ai, Brandlume Inc., and Orbiseed. She also has experience as Head of Engineering at Brandlume where she led other engineers building within the firm.
4. Soumyadeep Roy (Software Engineer): Roy’s background as a software engineer indicates his technical proficiency and ability to contribute to the system design and development of the tool for 1 - million of users. He has 2 years of experience in software development and showcased his skills in previous projects.
5. Daniel Ospina (RnDAO Mentor): As a mentor from RnDAO, Daniel Ospina can provide guidance, support, and expertise in navigating the decentralized ecosystem. His experience in decentralized governance and organization design can be beneficial in shaping the project’s governance model and ensuring its alignment with best practices.
6. Gospel Chinyereugo (Frontend Engineering Lead)
7. Chukwunonso Ikeji (Frontend/Blockchain Engineer)
8. Olawande Armstrong (Frontend Engineer)

[CAPABILITY/ FEASIBILITY] What are the main goals for the project and how will you validate if your approach is feasible?

• Simplify the management of files and links within organisations.
• Enable the smooth onboarding of new employees and members to organisations and communities.
• Promote easy access and distribution of important files and links within an organization.
• Increase productivity within an organisation by cutting down on the time spent in searching for files and links.
• Overtime, we'll also build out tools integration solutions for these organisations and communities -- Integrating tools they already use like Notion, Asana, Snapshot, Figma, GitHub with a layer for access control and token-gating.

[CAPABILITY/ FEASIBILITY] Please provide a detailed breakdown of your project’s milestones and each of the main tasks or activities to reach the milestone plus the expected timeline for the delivery.

Phase 1: Minimum Viable Product (MVP) - Timeline: 2 months

• Develop the core features of Stackles, including file and link upload, search function, easy share, security measures, and basic analytics.
• Create the user interface (UI) for the web application, ensuring it is intuitive and user-friendly.
• Work on a Chrome Plugin that allows for easy navigation — something like Metamask widget.
• Implement the Stack feature, starting with Collections, Boxes, and Teams.
• Set up basic access control for teams, allowing admins to manage permissions for collections, boxes, and tools.
• Establish integrations with popular tools such as Notion, GitHub, Figma, and Snapshot to automate access granting.

Phase 2: Enhanced Features and Customisation - Timeline: 2 months

• Refine and optimise existing features based on user feedback and usability testing.
• Expand the analytics function to provide more detailed insights on user engagement and platform interactions.
• Improve accessibility by developing a mobile application for Stackles, allowing users to manage data and access files from anywhere.
• Introduce advanced customisation options, such as the ability to import links from bookmarks and export links to bookmarking tools.
• Add a Single Sign-On feature with Sismo.
• Enhance file management capabilities by adding the ability to import files from third-party file storage integrations and export files to external storage tools.

Phase 3: Advanced Access Control and Collaboration - Timeline: 2 months

• Implement advanced access control settings for teams, including web3-based organisations and communities. This will involve integrating token based participation and engagement elements.
• Expand the collaboration features by enabling collaborative editing of files and real-time communication within the platform.
• Integrate additional productivity tools and services, allowing users to seamlessly work with their preferred tools within the Stackles environment.
• Enhance security measures by implementing additional encryption methods, multi-factor authentication, and continuous monitoring for potential vulnerabilities.

After the first 6 months

Phase 4: Deeper Integration with Blockchain and Smart Contracts and Public API release

• Explore integration with blockchain technology to leverage its benefits for access management and security.
• Develop smart contract-based permissions and access control mechanisms, allowing users to store and manage their access credentials securely.
• Enable integration with blockchain wallets to support the storage and management of cryptocurrencies, governance tokens, NFTs, reputation tokens, locked/staked tokens, identity credentials, and smart contract permissions.
• Ensure compatibility with different blockchain networks and wallet providers to cater to a wide range of users.
• Bundle these solutions as SDKs to provide some of the features to other developers to build.

[CAPABILITY/ FEASIBILITY] Please describe the deliverables, outputs and intended outcomes of each milestone.

1. Phase 1: Minimum Viable Product (MVP)

• Develop the core features of Stackles, including file and link upload, search function, easy share, security measures, and basic analytics.
• Create the user interface (UI) for the web application, ensuring it is intuitive and user-friendly.
• Work on a Chrome Plugin that allows for easy navigation — something like Metamask widget.
• Implement the Stack feature, starting with Collections, Boxes, and Teams.
• Set up basic access control for teams, allowing admins to manage permissions for collections, boxes, and tools.
• Establish integrations with popular tools such as Notion, GitHub, Figma, and Snapshot to automate access granting.

2. Phase 2: Enhanced Features and Customisation

• Refine and optimise existing features based on user feedback and usability testing.
• Expand the analytics function to provide more detailed insights on user engagement and platform interactions.
• Improve accessibility by developing a mobile application for Stackles, allowing users to manage data and access files from anywhere.
• Introduce advanced customisation options, such as the ability to import links from bookmarks and export links to bookmarking tools.
• Add a Single Sign-On feature with Sismo.
• Enhance file management capabilities by adding the ability to import files from third-party file storage integrations and export files to external storage tools.

3. Phase 3: Advanced Access Control and Collaboration

• Implement advanced access control settings for teams, including web3-based organisations and communities. This will involve integrating token based participation and engagement elements.
• Expand the collaboration features by enabling collaborative editing of files and real-time communication within the platform.
• Integrate additional productivity tools and services, allowing users to seamlessly work with their preferred tools within the Stackles environment.
• Enhance security measures by implementing additional encryption methods, multi-factor authentication, and continuous monitoring for potential vulnerabilities.

After the first 6 months

4. Phase 4: Deeper Integration with Blockchain and Smart Contracts and Public API release

• Explore integration with blockchain technology to leverage its benefits for access management and security.
• Develop smart contract-based permissions and access control mechanisms, allowing users to store and manage their access credentials securely.
• Enable integration with blockchain wallets to support the storage and management of cryptocurrencies, governance tokens, NFTs, reputation tokens, locked/staked tokens, identity credentials, and smart contract permissions.
• Ensure compatibility with different blockchain networks and wallet providers to cater to a wide range of users.
• Bundle these solutions as SDKs to provide some of the features to other developers to build.

[RESOURCES & VALUE FOR MONEY] Please provide a detailed budget breakdown of the proposed work and resources.

Brand/Marketing Design, UI/UX Design & Product Mgt/Operations work: 31,250 (12.5%)

Web App and Plugins (Remunerations, & Tools): 62,500 (25%)

Backend services, APIs, Infrastructure(Remunerations, & Tools): 62,500 (25%)

Community management/engagement (Remuneration/Logistics): 15,625 (6.25%)

Project Management/Operations: 46,875 (18.75%)

Contents Marketing, Communications and Publicity: 31,250 (12.5%)

Total: $71,750 ~ 250,000

[RESOURCES & VALUE FOR MONEY] How does the cost of the project represent value for money for the Cardano ecosystem?

Brand/Marketing Design, UI/UX Design & Product Mgt/Operations work: 41,380

This is very important inorder to tell the story of the product in the Cardano ecosystem and beyond, it's utility and impacts in a visually appealling way and this will be achieved by having a world class designer work on great creative assets let graphics, product design, video and motion illustrations etc inorder to boost the perception of the product and brand.

Web App and Plugins: 62,500

The cost attached here will be used to pay and to retain our superstar frontend engineers so they are not forced to leave the project to go and look for a job or get discouraged, this covers a pay for them for 6 months.

Backend services, APIs, Infrastructure: 62,500

This covers the cost for our backend and devops engineering team work. This goes into salary and any other infrastructure payments.

Community management/engagement: 15,625

This covers costs for a community platform, salary for mods and facilitators in the Stackles community. We wish to fly the story of Stackles on the wings of community engagements and feedbacks.

Project Management/Operations: 46,875

This would cover costs legal services, business setup and incorporation and project/operations management salary.

Contents Marketing, Communications and Publicity: 31,250

This would cover the cost for our content machine for telling custom stories for Stackles, Developing, Advertising and pushing creative contents for Marketing the product across all channels that we will be strategically exploring.

[IMPORTANT NOTE] The Applicant agreed to Fund10 rules and also that data in the Submission Form and other data provided by the project team during the course of the project will be publicly available.

I Accept