Budget:

KPIs:

KPI Dashboard:

https://docs.google.com/spreadsheets/d/1zH3QPuqTv4yL17VcdNQrCgpQHRqkl5YJqambb5JAcqQ/edit?usp=sharing

Monthly Comparison:

Bugs:

• No change from last month

Deadline:

• Improvement from last month due to the completion of new dashboard integration partners.

• Dashboard integrations move quicker than native integrations.

FIO Crypto Handles:

• Increase of 29.9% of FCH registrations from the previous month.

  • Opera registrations: 39,169

  • Partner with the 2nd highest registrations is still Guarda.

Domains:

• Increase of 563.6% of Domain registrations from previous month.

  • 87.7% of domain registrations/renewals came from Edge

  • Have been communicating with partners to renew their domains.

  • Many pre-mainnet domains have been set to renew and renewed during this month.

Revenue:

• Increase of 57.6% of partner revenue from the previous month.

  • Due to increase of FCH registrations and domain renewals.

Completed Integrations:

• Media Partners: NFT.Blog. Cryptocurrent - Dashboard Integration

• Pillar - Wrapped FIO

Future Integrations (March):

• Bifrost - FIO Send

• XRP Toolkit - FIO Send

Domain Marketing Campaign:

• To participate in winning @excalibur domain, you had to be a previous domain owner.

• Open

  

  Campaign was not successful and did not contribute to additional registrations. Only contributed to Handle registrations.

• Possible issue was messaging, or cost of participation.

  • Possible messaging issue: What is a domain vs a handle? What does it mean to own a domain? (Some users were claiming ownership of the @hodl domain for example). Would messaging be resolved if instead of saying participants must own a domain, we instead say participants must purchase a domain.

  • Possible cost issue: Users do not want to purchase a domain ($40) to win the chance of another domain. Would this be improved with a domain of less characters? What is an attractive domain to users?

• Can re-run campaign with adjusted messaging to rule out messaging issue. Help to see if the issue is cost of participation.

Onboarding and Expansion of Features Conversations:

• Edge

  • Discussed onboarding experience

    • Very interested in implementing an onboarding like experience.

    • Will likely not manifest into an onboarding experience due to Edge’s account registration but have discussed exploring some kind of pop-up or banner for the FCH registrations.

  • Improve UX

    • Will implement in next sprint. Will move away from webview (reg site) to their own UX (similar to Opera).

• Guarda

  • Discussed onboarding experience

    • Seemed interested but not as interested as Edge

  • Discussed adding Domain functionality and additional FCH registrations (currently can only register 1 Handle)

    • Very interested in implementing this but dev workload is a concern due to their current roadmap

• Opera

  • Parity for Domains and additional Handle registrations has not been reached across all platforms.

    • So far Domains and additional Handle registrations are only available for Opera for Android and IOS.

  • All other Opera browsers have the free Handle registrations w/ onboarding experience.

    • Opera Broswer, Opera Crypto Broswer, Opera GX, and mobile versions of each (both IOS and Android)

    • All above browsers have launched FIO Handles with onboarding experience. The moment you create a wallet for the first time, you are guided to make FIO registrations

      • Previously Opera got rid of this and replaced it with a pop up. We spoke with them to add the onboarding experience back in.

    • Likely reason for increase in registrations.

Post Call Thoughts and Comments:

• Opera - signing capabilities - dev site to play around. + Set up call