Creating a banking app

Went through a full startup routine in creating the product, starting with generating ideas through ideations and co creations, making mind maps of them on Miro, leading it to a finished tech plan for developers and making it into life. Reviewed design via Figma and made testplans with researchers to verify ideas on target audience. Made integrations with bank front and back systems to aggregate data and made profit of it for our clients with complete analytics of their finances and budget that makes no one at the market right now together with banking functions.

A developer with over 10 years of experience in the field of Internet information resources. Implemented the product approach in the company and led product transition to a new technology stack.

– Hired and managed 4 teams of analysts (15+specialists) responsible for customer experience, monetization products, content and core data analysis; grew by experiments conversion to order by 15% – Developed and implemented data architecture for events transactions and storage for all the company products – Promoted the culture of experiments in the company: changed the processes of product discovery and delivery, hired A/B-platform Owner, who managed an internal product for A/B-test automation – Designed product key metrics, created datamarts and dashboards for their monitoring

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.