Who are your clients/users? Our primary users will be the nongovernment organizations (Suppliers), government institutions (Consumers) and disaster victims who rate the government based on actual funds/relief efforts received.
What are their pain points? Governments always find themselves in need of outside support during disasters. It tends to be difficult for government units to coordinate with NGOs during critical situations.
NGOs rely heavily on government units for accurate data while responding to disasters. Disaster victims currently have no way to actually hold their gov't accountable for supposed relief funds/materials/efforts donated by outside sources
What is your product's value proposition? Our product is a platform for NGOs and Government to coordinate with transparency through the blockchain in order to address the lingering issues of proper communication and transparency during funding/relief efforts (see our previous update)
What is your distribution and go to market strategy? Who can you partner with? We have an existing non-government institution, Waves for Water, a global organization that provides access to clean water to communities. Currently, they are present in Marawi, Philippines, providing clean water to displaced communities due to the ongoing armed conflict. They are willing to prototype our solution with their existing partners and relief efforts.
After the initial prototype testing stage, we plan to go to reach out to other charitable/non government organizations, such as AISEC.
As we test our prototype, we will be collating all data needed during disaster response situations on behalf of governments who still do this manually. Once we bring in more and more NGOs, we can market it as the easiest place to look into the needs of a certain place.
What are the risks associated with your solution? Our team recognizes that the following factors could negatively influence the success of our solution;
- Governments might not see the point of asking for funds on our platform due to (1) a bad user experience or (2) simple lack of education/awareness of our solution
- NGOs would rather stick to their current routes than learn our platform altogether
- Not enough victims (are able to) make the effort to hold their government units accountable via LifeMesh’s 2 way reputation system
- LifeMesh having no existing reputation in the space
What is the impact of your solution? How will it be measured? Our primary key performance indicators will be the
- Number of successful and verified transactions based on our two way reputation score (equation to follow) a. Two way reputation score for entire situation from NGO donating funds to gov't unit, all the way to the overall/average rating scores from victims on the ground
- Cost saving analysis when LifeMesh is applied to a given disaster
Technical specifications and development roadmap Our team will be prototyping a fork of OpenBazaar (built with Electron) that runs on our own IPFS chain.
For the first prototype milestone, we will be ensuring that the base OpenBazaar local server and desktop client run on our own IPFS chain/fork.
Lastly, we will be replacing the OpenBazaar UI with our own implementation to suit LifeMesh’s use cases;
- 2 way reputation/rating system between a. governments and NGOs b. disaster victims and governments
- posting/listing of needs by a gov’t
- the funding/provisioning process by which an NGO can satisfy a government’s listing/post
If our group makes it past the qualifications, then we’ll be adding the following features next: 1. Different "layers" to LifeMesh as added features that can be accessed by NGOs and Governments (e.g heatmaps, reports, updated real time deployment reports etc.)
- Implementing Consensys Supply Chain (https://supplychain.consensys.net) to manage the asset tracking that takes place between NGO’s and governments
Log in or sign up for Devpost to join the conversation.