Fund13 Project Assistance :User Onboarding Manual

User-Onboarding Process Flow:

1. Form Completion

The form is designed to capture essential details about the project, its team, and its current status to ensure proper evaluation and support. Below is a table outlining the form fields, the reason behind each question, and any specific comments to assist in filling it out.

Imp: Please note that all these fields are not compulsory, but we highly appreciate if these are filled out. All of them transcribe onto the final Grant application directly or indirectly!
However the fields like Problem Statement or USP are the ones which will be further refined post-onboarding!
For all practical purposes, this form is the first in the direction of exploring mutual-synergies. Happy onboarding!!

Form Field	Purpose/Comments
Tentative Project Name	Identify the project uniquely within the system. Helps in branding and proposal tracking.
Proposer Name	Identifies the person submitting the project.
Email	Key contact point for follow-ups and updates.
Ideascale Profile Link	Verifies the proposer’s involvement in the Cardano ecosystem.
Referred By	Helps understand how the project or proposer was introduced to the platform (personal recommendation or external source).
How long have you been working on the project	Provides context on the project’s maturity and development status.
Project Category	Categorizes the project based on type (e.g., DeFi, Gaming, Ecosystem, NFT etc.) for internal sorting and prioritization.
Have you received a Grant from Cardano	Confirms if the project has prior funding or support from the Cardano community.
Problem Statement	Clear articulation of the problem the project aims to solve.
Short Summary of the Solution	Overview of how the project intends to address the identified problem.
Team Size (FTE & Contract)	Provides insight into the project’s human resources and scalability potential.
Team Members and their core contributions	Identifies the team structure and the key roles each member plays in achieving project goals.
Challenges for Execution	Highlights potential risks or blockers that may affect project success.
Biggest Edge Against Competition	Assesses the project’s competitive advantage.
What is your key contribution to the Cardano ecosystem	Determines how the project adds value to the Cardano ecosystem specifically.
Project Stage	Indicates how far along the project is (concept, MVP, etc.).
Current Runway and Sustainability Plan	Shows the financial health of the project and its sustainability strategies.
Community Involvement & Governance	Determines how the project is engaging with and managing its community.
Unique Selling Proposition	Establishes what makes the project different from others in the space.
Social Media Following (Twitter)	Measures the project’s online presence and potential for community engagement.
Funding Status	Helps in understanding the project’s current financial standing and needs.
Key Areas of Support Required	Specifies what types of support the project is seeking (e.g., legal, marketing).
KPIs of the Support Sought	Clarifies the metrics or goals the project wants to achieve with the requested support.
Rough Hourly Estimate	Necessary for budget planning, used in resource allocation.

2. User Journey Flow

Once the form is submitted, it goes through a structured evaluation and task management process. Below is an outline of each step:

2.1 Submit the Form

The user completes the form and submits it. Once submitted, it enters the evaluation process.

2.2 Form Evaluation Process

2.2.1 Collaborator Management:
- Storm Partners Exec adds the proposer on the specific entry
2.2.2 Form Integrity Check:
- The form is first verified for completeness and accuracy.
- Any missing information is flagged, and a follow-up is initiated through the ClickUp tool to ensure all required data is gathered. The proposer will have notified on the click-up dashboard
2.2.3 Priority and Assignment: After integrity checks, the form is assigned to the appropriate team or individual. A Point of Contact (PoC) is appointed for the proposer, ensuring streamlined communication and management of daily tasks.
- The Activity bar on the right will contain comments by collaborators, consider it TG for the specific project

2.3 Subtasks

Once assigned, the project is broken down into subtasks, which are milestone-based goals set by the Storm Executive after the first call with the Proposer. Subtasks are project checkpoints and do not contain further subtasks. Timelines and deadlines can be discussed and adjusted as needed.
The proposer then adds the required information/ add documents or links on the description section of the “Subtask page”, further closing the concerned Action item tab