Reduced Users Compliance Drop-Off by Optimising the Onboarding Process

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: Typically, founders that are bootstrapping their startups usually take the "hands on role" early in their startups which means they had to perform manual kyc documentation checks on Dojah platform. Some founders did not have technical know how knowledge on how to consume APIs from the identity verification widget which created a lot of ambiguity, drop off, customer retention lagging for Dojah SOLUTION: Using the identity verification widget API, I created a flow chart, PRD and use case scenarios that includes parameter of inquiry needed to call Dojah ID widget APIs if the API were consumed by the customers, then used the inquiry parameter as information fields for the no-code tools.
Using the no-code tools, when a founder enters the inquiry parameters with information provide by their end users, at the backend it is automatically calling the ID widget APIs without these founders/operators knowing. At the frontend, the response from the API call is presented to them without needing to consume the APIs.

PROBLEM: There was a problem of FX liquidity and inability to use some of our cards on 18yers+ platforms such as casinos at CashEx SOLUTION: As a remittance (CashEX) they were disparities in FX rates which caused a lot of ambiguity to users as we were offering different rates within a day which is meant to be a fixed rate for the day. Proposed an integration with an international FX partners which includes the business margin spread that when a user needs a particular currencies and the user has been deposited money for the exchange, it calls our partner APIs from our platform. Also created a status page for those APIs so we can be informed when there is a outage and inform our users. This improved user experience and stability in the business

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.

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.