Decentralized app implementation

I was part of the team that implemented from ideation to deployment.:

• the Decentralized exchange (DEx)- smartswap.rigelprotocol.com
• the Launchpad Decentralized Application (DApp)- launchpad.rigelprotocol.com from idealization to deployment.
• the GiftDApp: A Decentralized Application (DApp)- giftdapp.rigelprotocol.com for gifting users and community members making airdrops more organized.

Implemented features Drive Safe: Monitoring and Recording Driving Behaviour and Drive Insights: Business Intelligence tool kit for visualisation from ideation to successful release

Goal: Increase revenue by 2x in 12 months. Initiatives: Identified key metrics that are important for revenue. Clustered and segmented users. Established conversions that need to be monitored daily. Worked with data team to build monetization dashboards. Defined and owned the strategy and execution of changes to be made in monetization. Results: Revenue increased by 2.5x in 12 months. Conclusion: The key to success was identifying the right metrics to track, clustering and segmenting users, and establishing daily monitoring of conversions.

PROBLEM: Using Amplitude and moseif tools, noticed that there was a lot of drop off early on at Dojah especially during compliance stage. Compliance requested for documentation via mail which created room for a lot of forth and backs with the customers. SOLUTION: Reworked the onboarding at Dojah, once users does the first set of information signups which includes email, company name and product you want to use, they are directed to calendly to book a demo of our product. The personal touch from sales during demo, they will more likely want to use the product. After demo, they are sent automated link to complete their sign up which includes uploading compliance document on their dashboard. At the admin dashboard, the compliance analyst views the documents. If the documents are good to go, the approval is toggled. Then user is verified to use our services.

PROBLEM: There was a problem that web2 users could not onboard easily on web3 platform because of the complexity with the process at Fly wallet SOLUTION: Not a lot of travelers are web3 enthusiasts which kind of created a segmented market for FlyWallet. So I created documents and flowchart that will enable users that have Google account, Facebook account and Apple ID to onboard easily and save for travels ahead. Created multiple integration partners and monitored the API wrappings by the engineers. This created a diverse customer base for the web3 travel tech company.