---
# System prepended metadata

title: W4P Updates

---

# W4P Updates


## TRIF plans
Conversations with [Maitree](https://w4p-papad.test.openrun.net/item/6283a04b2b9b8d6404b1e90a) and Neeraj([1](https://w4p-papad.test.openrun.net/item/6279453c2b9b8d6404b1e8ed),[2](https://w4p-papad.test.openrun.net/item/627944a12b9b8d6404b1e8ec),[3](https://w4p-papad.test.openrun.net/item/627943847548f0121ab1e8d1)) are on course. There has been initial Alignment conversations to understand how both partners are working and plan to work. We will be following up on upcoming coalition and block-level meetings. We have also received survey samples from TRIF as well as the context to why and what the surveys were for. 

## Janastu Discoveries 

 1. There are atleast 3-4 different user personas in the W4P scenario which increase if you take geographies
     1. People conducting/participating on-ground activities like the SHG meetings  
     2. Intermediate facilitators (eg. preraks, Block level executives, Coalitions)  
     3. Entrepreneurs - new - old, Small - Mid - Big
     4. Institutions - N/SRLM, MDSS/SVSS, DA, Banks

2. Each of these user groups have different needs. But if we consider 1 and 3 as the primary focus groups, we may have identified some places where technology might be able to help. We also narrowed down, for now, the prototype to the CSC-Kiosk network

## ASPi-Cloud (Hypothesised)
Imagine a scenario where there is a whatsapp or telegram bot that is able to do a few things for different user groups. Different applications for various puposes may be surveys, helpline, support group, meetings, online interactive prototype activities and other enterprise applications, ordering, delivery, customer service, Social media marketing etc. Which should be evaluated by co-creating with the user groups in 1 and 3. However, the core server and services required for such applications are already explored and some shortlisted for testing.

## ASPi-ESS Plans: Enterprise Support System
- Daily logging of expenses
- Profit loss calculations
- Invoice formatting
- (+ a few other templatised, deliverable modules for WA/Telegram)



## ASPi-Discover

The second is a discovery system in the same bot format. It would serve as a location-based discovery system for CSCs in the area. But this work can be expanded into other institutions and enterprises as well. 
What ASPi-Discover will focus on is initial contact and discovery. This can be modularised in many small little chunks.
 - Nextcloud/Syncthing used as a file-storage/sharing system between CSCs (ASPi Share)
 - Papad integration with kiosk model (Discussion pending with team) (ASPi Listen)
 - Tutorials (ASPi Learn)
        - What would a new CSC need
        - How to produce this
 - Proximity Map 


## ASPi-Bell

The third component would be an end-to-end notification system which extends ASPi-Discover by adding a notification system for availability. If a CSC is found in ASPi-Discover then the seeker is directly connected to them. What ASPi-Bell will do is send notifications to either side when a request is made and when they are available to service that request

## Important Caveats

- This stack will be based on ERPNext, Chatwoot, Papad, Nextcloud, Syncthing and a localised frontend
- This includes building several integrations between already built software, our development team thinks the integration is at least worth 8-9 months of work including a design phase to reach upto a beta release.
- This has to be informed in design from grounded insights
- This system would have to be supported by human processes that have to be co-designed(DA, Janastu, Users, any other stakeholder) as well

## Way Forward
- Conversations on Nextcloud/Syncthing as a usecase for the CSC entrepreneur
- Currently running ground activities in this regard
- How to plan for the future

## Activities

#### Immediate Needs --
1. Kiosk (Entrepreneurs - what are the types of kiosk )
   
   It is to set up p2p - everyday practice
    Journey Map 
    -   Daily
    -   Yearly
    
    Pain and Future
    -   Pain Points
    -   Aspirations
    
1. People conducting/participating on-ground activities like the SHG meetings
   
   - What are the storytelling needs at this level, how can narratives shape reponsibility and action at this level for entrepreneurship and knowledge archives, how to make community radio. radio team, recording interviews, different kinds of stories, whatsapp and dissemination
   
#### Emergent --
2. Intermediate facilitators (eg. preraks, Block level executives, Coalitions)
   - Who should we focus on, who would gain the most from a technological intervention, what are some mvp(minimum viable problems)
   
   
3. Institutional 
   - Communications - jotform - how to articulate needs as a organisation - 
   
   
## DA catch up
   -  Sheet Updated
   -  List of Entrepreneurs, TRIF+DA overlaps
   -  Personas for Technological intervention
   -  Brainstorming session with Maitree and possibly Debasis
   -  Finding Needs + places of intervention
   -  on ground facilitation, Planning to go on ground, What is the DA+TRIF session?
   -  What is happening next?


## 26th May Meeting
   
- TRIF already is planning to deploy kiosks
- Can align with them 
- 