Konnadex

Invoicing & Payment Platform

Built to help both personal and business users manage payments, invoices, salaries and wallets

https://www.konnadex.com/

Overview

Duration

12 months

My Role

Product & UX/UI Designer

Team

Product manager, backend & blockchain developer, security reviewer

Tools

Figma, Framer, Adobe Creative Suite, responsive testing, basic front-end prototyping

Problem Statement

No existing platform meeting both personal and business-level needs for payments, invoices, and salaries with Web3 / wallet features.

Users new to crypto or Web3 were confused by too many steps or unclear verification.

Business users needed multiple tools (invoicing, payroll, wallet) in one place with intuitive access.

Ensuring legal / KYC compliance without hurting usability.

Research

Goals

Understand what confuses new users during onboarding (esp. for crypto/Web3 novices)

Identify pain points for business vs personal users (which tasks or flows are hardest)

Discover what drives trust and clarity (verification, wallet funding, invoice/dashboard visibility)

Methods

Conducted 6 interviews with prospective users: 3 personal-account users, 3 small business owners

Reviewed analytics showing where drop-offs happen (on onboarding, verification, etc.)

Compared competitor apps and gateways to see how they design flows for invoices, payments, wallet verification

Top Insights

Many users didn’t understand what “business account” implied, what extra features or obligations it meant.

Crypto and wallet verification processes are confusing: unclear instructions or jargon, missing feedback about status.

Users value seeing payout / transaction history clearly; not knowing when an invoice is “sent”, “pending”, or “received” causes stress.

Multi-currency support is desired, but users want clear conversion info and fees up front.

Business users want a dashboard that surfaces invoice, salary, payments, wallet at first glance; too many menus slow them down.

Persona

Rita Nelson

29 Years old

Lagos, Nigeria

Role & Use Case

Freelancer who invoices clients internationally, sometimes in crypto

Tech Comfort

Moderate: uses mobile and desktop, some crypto tools, but not a power-user

Goals

Send invoices easily, get paid reliably, track payouts, avoid confusing fees

Pain Points

Long form fields, unclear status messages, confusing verification steps, waiting without feedback

Motivating Quote

“I just want to finish sending my invoice without worrying if I missed something.”

Ben Wilfred

38 Years old

Europe

Role & Use Case

Runs small business, uses business account to manage invoices, team, payment links

Tech Comfort

High: comfortable with tech, but wants reliability, clarity

Goals

Manage invoices, add team members, generate links, salaries; see transaction histories clearly

Pain Points

Overwhelming dashboard; hidden fees; unclear roles (what business vs personal can do), long wallet verification time

Motivating Quote

“I want a dashboard where I can see everything in one glance; invoices, salaries, wallet without toggling between screens.”

Decision Nodes

Ideation & Concept Development

I kicked off by sketching multiple versions of the onboarding flow: personal vs business account paths, country selection, details entry, email verification. Explored variations to reduce steps while preserving clarity.

Explored different dashboard layouts for business users: one version emphasized invoices first, another prioritized wallet balance and payout status, another mixed all core features in quick-access tiles.

Created feature cards for tasks business accounts must perform: Invoice, Payment Links, Wallet History, Salaries, etc., then ranked them based on importance to users (from research) and business value.

Sketch

Decision Points

Whether onboarding should separate personal vs business account first or show a toggle later. After prototype testing, separating them up-front reduced users choosing wrong account type.

How to verify users (email first, then KYC vs combined). Chose email verification first to reduce friction.

Layout of dashboard core features. Based on testing, users preferred tiles with icons and labels over menu-heavy layouts for quick recognition.

User Journey

Wireframes

Built low-fidelity wireframes in Figma to test how users understood selecting account type, entering verification, and moving from dashboard to core features. Used grayscale / minimal styling to focus users on flow and content.

Then moved to mid/high fidelity prototypes showing dashboard designs: tile vs list layout, how payment links and invoice creators are accessed. Tested user ability to find “Create Invoice” and “Fund Wallet” inside business dashboard.

Onboarding

Dashboard

Invoicing flow

Wallet - Mobile

Landing Page

Outcome

Hackathon Recognition

Konnadex was selected among the Mastery Track winners at the Polygon Bootcamp Africa Hackathon out of 412 teams, earning recognition for its innovation in Web3 invoicing and payment tools and being named a runner-up project.

https://polygon.technology…

Early Performance & User Feedback

Users report that tasks like invoice creation, payment link generation, and dashboard navigation feel far more intuitive compared to alternatives.

Early feedback suggests fewer support tickets related to wallet verification or “where is my invoice” confusion.

On the Konnadex website, features like real-time invoice status tracking are publicly advertised: users can monitor when payments are scheduled, processed, and completed, which speaks to transparency built into the product.

The platform allows businesses to spin up their own payment gateway via payment links shared with customers or clients.

Lessons Learned & What I’d Do Next

Verification steps need extremely clear feedback, when a user uploads documents, they need progress indicators, status messages. I learned that vague status or delays make users abandon.

Dashboard layout for Business users needs careful prioritization, too many options visible early can overwhelm. Next time I’d build a feature prioritization matrix based on actual user needs and usage data to order things.

Multi-currency support & fee/conversion info often cause trust issues when users can’t predict what they will be charged. I’d add currency and fee preview earlier in flows so users see what’s coming before finalizing invoice/payment.

Key Takeaways

Clear onboarding flows aren’t just about making things look smooth, they directly impact adoption, trust, and retention. In Web3, people often abandon platforms due to confusion around verification, wallets, or unclear steps. Strong design reduces these friction points.

Transparent account types and status feedback build user confidence. When users know if they’re on a personal or business journey, what each step means (KYC, payout, etc.), they feel more in control and less likely to drop off.

Feature overload is a risk, business users can get overwhelmed if too many options are visible too early. Prioritizing core tasks (invoice, payout, wallet) helps users orient quickly. Research shows that simplifying onboarding and showing only what’s necessary at each step improves completion rates.

Measuring how quickly users reach “first value” (e.g. send first invoice or make first payment) is key. Faster “aha” moments mean users understand the product’s value sooner and are more likely to stick around.

Building from scratch gave you full control over flow, UI consistency, and visual clarity. That matters in Web3 platforms especially, having clear visual hierarchy, recognizable icons, responsive design, and minimal jargon helps bridge the trust gap for users who are newer to crypto.

Award recognition (e.g. winning at Polygon Bootcamp Africa) shows the design not only solves problems but stands out among peers.

Related Work

Related Work

Related Work

Related Work

Related Work

Ready to build?

I’d love to collaborate if you’re building a product and want it to feel clear and usable…

Create a free website with Framer, the website builder loved by startups, designers and agencies.