this is the first article in the series of multiple #BUILDL focused articles from ideation to web3 incubated startup , where i will work on describing the journey from the product conception (features , basic user story , tech stack , setup ) and then working out on the scaling the Dapp for real 🚀 by the community as the partners . taking inspiration from the likes of Ben-awad , Andre-Cronje getting some of the “non scalable , simplistic but promising Dapp services to mainstream . i tend to create it as the primer for the art of getting an hackathon project solving real life use cases and getting an successful in sustaining the project .

on an higher level , Following is the series of this edition of

1. Explanation of the domain of problem .

2. Planning and development

   1. creating mock the user Journey .

   2. system design of web3 dapps.

3. MVP creation and further strategies

Also called plug & play , business process automation ,connector ecosystem . it’s the most prominently rising ecosystem in the overall IT industry (gartner) , driven by the composable modular architecture with interoperable , native cloud applications providing simple visual interface to combine diffrent event driven services (being as simple as calender invite to more complex integrations for agile software teams , ERP systems etc) , these will eventually become the norm for scalable building data intensive / event driven applications that rely on the each other in scalable apps , which are becoming increasingly important as currently currently web3 has become much more vast ecosystem of services and frameworks , that cater to the needs of providing decentralised data storage , compute , and networking services with the aim of reducing the barriers of digital divide and creating community focused incentive driven applications .

Based on the analysis of the diffrent platforms , ranging from completely closed source(service-now , Integrately , zapier , IFTTT ) , to being open-sourced but fair use license (n8n) and completely open sourced (Node-Red).

workflows are divided into individual nodes , each of them are the wrapper on top of the API endpoints around the SaaS services , providing users simple form for defining the parameters (secret key , method calls , description ) that allows black box approach for n00bs having general domain knowledge to automate their idle tasks .

so for taking and simple example , here the workflow that is automated is the redeployment of site after creation of the new blog , and the nodes used ( netlify , custom webhooks) .

there there are basically 4 players in the lifestyle of these SaaS offerings

• Developer / integrators of the service :

• Third party service :

• Marketplace of automation workflows

• The users

After doing the review of the most of these applications , i find some of the key reasons they are facing issues due to innovation challanges in web2 , and thus provide more productivity to the

• most of them are created by the industry experts with wealth of info about the potential automations of manual work in IT sector , but they are not being rewarded significantly for their ingenuity to create these services .

• All of the closed source companies (serviceNow) have been making the integrations have potential vendor , their sheer market dominance has made them defacto leader and thus having monopoly in providing default integration services to the ERP /CRM platforms (ref).

• and most of the important is that they dont have an general adoption in the web3 ecosystem frameworks / projects

  • and the current tools still revolving around the arbitraging opportunities across defi Layer 2 based financial instruments (like furucombo) and we’re still long way to go have these services being used

thus for the future of these multi-chain ecosytem (both EVM and non EVM) will be significant mainstream adoption in traditional IT use cases , with the prominent components of the web3 ecosystem being divided into usecases like :

1. verticals ( DAO , DeFI , NFT’s , metaverse etc ),

2. tech-stack ( frontend app , data indexing , storage , identification services , compute , networking etc).

it becomes imperative to take benefit of of these services ( specially the fact that token driven services have inclusionary environment to incentivise each partner in the ecosystem to build the essential modules of the services and incentivising the main stakeholders : builders & users )

🌱 thus now presenting my project idea :

“marketplace for Workflow automation across diffrent Storage , compute and networking platform services ”

idea is to create SaaS platform cum protocol for incentivising an significant niche of web3 users (including me ) that are superbe in keeping tab of the latest Dapps / protocols being developed in the ecosystem and want to club these services for creating workflows that makes the web3 based workforce ( from developers , DeFI users , participants in DAO dev guilds , etc ) performant vis a vis their web2 counterparts .

taking an simple workflow as follows

potential use-case scenario

• consider you are an COO of an major DAO (and why not , many of them are now running as decentralised efficient coops) who has to swipe between the diffrent services (snapshot , tally , discourse , excel sheets , airtable …..) and hours of calls with the subject matter experts to determine the status of the grant , and then convey the status of the discussion board to start the voting for grant disbursement .

  • what if this is simplified by an developer , who programs the wrapper methods around those web3 services ( ie nodes ) and provides this as nodejs package as an NFT (will explain in upcoming sections about the architecture) .

  • then the COO (or might-be another generalist) buys these NFT (or reference open source nodes ) , combines their json config onto the workflow automation ecosystem , and take the benefit of the

the opportunities are immense for web3 ecosystem players to capitalise the benefits of combining the web3 services across diffrent verticals , driven by their OSS ethos (openAPI’s for using services , token incentives) to drive the real use cases across the diffrent lego bricks of the ecosystem , rather than going on the FOMO use cases only .

so thats it for this introductory session ,thanks a lot to make it till end , given that i am not an great in writing scientific ideas with great narration 😅 , but hopefully upcoming articles in the series will be mix of discussion in tech and narration , so will

feel free to share the article and i will be happy to get your feedbacks and suggestions regarding which real life usecases that you want to be implemented as the web3 dapp .

And till then , keep #BUIDLing 🏗👨‍💻.

About me:

I am in blockchain space since 2 years , My experience is in

• research of distributed consensus , cryptography

• architecting blockchain applications across EVM and non EVM chains .

• smart contract developement and auditing

feel free to follow on github for more updates on the project .

this is the first article in the series of multiple #BUILDL focused articles from ideation to web3 incubated startup , where i will work on describing the journey from the product conception (features , basic user story , tech stack , setup ) and then working out on the scaling the Dapp for real 🚀 by the community as the partners . taking inspiration from the likes of Ben-awad , Andre-Cronje getting some of the “non scalable , simplistic but promising Dapp services to mainstream . i tend to create it as the primer for the art of getting an hackathon project solving real life use cases and getting an successful in sustaining the project .

on an higher level , Following is the series of this edition of

1. Explanation of the domain of problem .

2. Planning and development

   1. creating mock the user Journey .

   2. system design of web3 dapps.

3. MVP creation and further strategies

Also called plug & play , business process automation ,connector ecosystem . it’s the most prominently rising ecosystem in the overall IT industry (gartner) , driven by the composable modular architecture with interoperable , native cloud applications providing simple visual interface to combine diffrent event driven services (being as simple as calender invite to more complex integrations for agile software teams , ERP systems etc) , these will eventually become the norm for scalable building data intensive / event driven applications that rely on the each other in scalable apps , which are becoming increasingly important as currently currently web3 has become much more vast ecosystem of services and frameworks , that cater to the needs of providing decentralised data storage , compute , and networking services with the aim of reducing the barriers of digital divide and creating community focused incentive driven applications .

Based on the analysis of the diffrent platforms , ranging from completely closed source(service-now , Integrately , zapier , IFTTT ) , to being open-sourced but fair use license (n8n) and completely open sourced (Node-Red).

workflows are divided into individual nodes , each of them are the wrapper on top of the API endpoints around the SaaS services , providing users simple form for defining the parameters (secret key , method calls , description ) that allows black box approach for n00bs having general domain knowledge to automate their idle tasks .

so for taking and simple example , here the workflow that is automated is the redeployment of site after creation of the new blog , and the nodes used ( netlify , custom webhooks) .

there there are basically 4 players in the lifestyle of these SaaS offerings

• Developer / integrators of the service :

• Third party service :

• Marketplace of automation workflows

• The users

After doing the review of the most of these applications , i find some of the key reasons they are facing issues due to innovation challanges in web2 , and thus provide more productivity to the

• most of them are created by the industry experts with wealth of info about the potential automations of manual work in IT sector , but they are not being rewarded significantly for their ingenuity to create these services .

• All of the closed source companies (serviceNow) have been making the integrations have potential vendor , their sheer market dominance has made them defacto leader and thus having monopoly in providing default integration services to the ERP /CRM platforms (ref).

• and most of the important is that they dont have an general adoption in the web3 ecosystem frameworks / projects

  • and the current tools still revolving around the arbitraging opportunities across defi Layer 2 based financial instruments (like furucombo) and we’re still long way to go have these services being used

thus for the future of these multi-chain ecosytem (both EVM and non EVM) will be significant mainstream adoption in traditional IT use cases , with the prominent components of the web3 ecosystem being divided into usecases like :

1. verticals ( DAO , DeFI , NFT’s , metaverse etc ),

2. tech-stack ( frontend app , data indexing , storage , identification services , compute , networking etc).

it becomes imperative to take benefit of of these services ( specially the fact that token driven services have inclusionary environment to incentivise each partner in the ecosystem to build the essential modules of the services and incentivising the main stakeholders : builders & users )

🌱 thus now presenting my project idea :

“marketplace for Workflow automation across diffrent Storage , compute and networking platform services ”

idea is to create SaaS platform cum protocol for incentivising an significant niche of web3 users (including me ) that are superbe in keeping tab of the latest Dapps / protocols being developed in the ecosystem and want to club these services for creating workflows that makes the web3 based workforce ( from developers , DeFI users , participants in DAO dev guilds , etc ) performant vis a vis their web2 counterparts .

taking an simple workflow as follows

potential use-case scenario

• consider you are an COO of an major DAO (and why not , many of them are now running as decentralised efficient coops) who has to swipe between the diffrent services (snapshot , tally , discourse , excel sheets , airtable …..) and hours of calls with the subject matter experts to determine the status of the grant , and then convey the status of the discussion board to start the voting for grant disbursement .

  • what if this is simplified by an developer , who programs the wrapper methods around those web3 services ( ie nodes ) and provides this as nodejs package as an NFT (will explain in upcoming sections about the architecture) .

  • then the COO (or might-be another generalist) buys these NFT (or reference open source nodes ) , combines their json config onto the workflow automation ecosystem , and take the benefit of the

the opportunities are immense for web3 ecosystem players to capitalise the benefits of combining the web3 services across diffrent verticals , driven by their OSS ethos (openAPI’s for using services , token incentives) to drive the real use cases across the diffrent lego bricks of the ecosystem , rather than going on the FOMO use cases only .

so thats it for this introductory session ,thanks a lot to make it till end , given that i am not an great in writing scientific ideas with great narration 😅 , but hopefully upcoming articles in the series will be mix of discussion in tech and narration , so will

feel free to share the article and i will be happy to get your feedbacks and suggestions regarding which real life usecases that you want to be implemented as the web3 dapp .

And till then , keep #BUIDLing 🏗👨‍💻.

About me:

I am in blockchain space since 2 years , My experience is in

• research of distributed consensus , cryptography

• architecting blockchain applications across EVM and non EVM chains .

• smart contract developement and auditing

feel free to follow on github for more updates on the project .