Case Study NDA Restricted

FUNDIT Public Sector UI

How I designed FUNDiT Public Sector: a self-serve loan dashboard for civil servants, with one review queue that replaced Excel for the team behind it.

FUNDIT Public Sector UI
FUNDiT Public Sector
by FUNDiT Finance
Deliverables
Product design
Workflow mapping
Prototype
Project timeline
2026
What I did
Research
UX & UI design
Design system
Worked with
2 software engineers
4 operations team members

The Challenge

Public-sector employees couldn't apply for a loan or check what they owed without calling sales or support. Inside FUNDiT, staff tracked every loan in Excel and passed approvals by hand from office to office.

The Solution

With no MVP to start from, I designed two connected dashboards: a self-serve one where employees apply, check balances and see their eligibility, and a review queue that replaced Excel for FUNDiT's staff. Both reuse Digiit's design language, so they feel like one platform family.

The Result

Employees serve themselves, and approvals left Excel.

What changed

  • Employees apply for and manage loans without calling sales or support.
  • Staff work from one dashboard instead of Excel sheets.
  • Approvals no longer travel by hand from office to office.
  • Sales onboards new employees faster.
01

Who, why, and what

This was a new product, not a redesign. I started by learning how public-sector lending actually works.

Research

I ran discovery sessions with the public-sector sales team and the operations team. Eligibility rules, verification steps and the approval chain were nothing like Digiit's corporate lending, so I mapped the whole workflow before drawing a screen.

Report from discovery meeting

From discovery sessions with the sales and operations teams.

Employees, via sales
  1. “Can I get a loan?”
  2. “How much do I qualify for?”
  3. “How much do I still owe?”
  4. “Where is my application now?”
FUNDiT operations
  1. “Which office has this file?”
  2. “Who still needs to approve this?”
  3. “Is this the latest Excel sheet?”
  4. “How many loans are pending?”
Sales team
  1. “How do I onboard this employee faster?”
  2. “What documents do they need?”
  3. “Why is this application stuck?”

Who uses it, and what was missing.

Empathy map for public-sector employees and FUNDiT staff

Scope

The first release covered the full loan journey for employees and a single review queue for staff. It deliberately left out anything the contract with each government agency didn't yet allow.

02

Moodboard

I worked from the same moodboard as Digiit, so both products share one visual direction.

Figma board · MoodboardOpen in Figma
03

Structure and flows

Different lending rules meant a separate product, built on the same visual language as Digiit.

Two dashboards, one workflow.

Every screen on the employee side feeds a step in the staff review queue, so I designed both sides together and could see exactly where one handed off to the other.

[1] Employee dashboard.

Employees apply, check their balance and see how much more they qualify for, without calling sales or support.

Public-sector employee dashboard

[2] Account officer dashboard.

An internal admin view where account officers manage their clients' loans, from new applications to repayments.

Account officer loan management dashboard

[3] Management dashboard.

An insight view where management tracks loans, repayments and defaults, plus the top account officers and ministries each month.

Management loan oversight dashboard

[4] Staff review queue.

One queue replaced Excel sheets and office-to-office approvals. Each request shows which stage it's at and who acts next.

Other UIs are under NDAUnder NDA, so I can't share it.
04

Design decisions

Reuse what works, and design new only where the lending model differs.

Design system

  • Reused Digiit's component library (cards, status pills, data tables), so staff move between products without relearning anything.
  • Extended the status colours to cover every approval stage, so staff see where a request sits without opening a spreadsheet.
  • Added a guided onboarding step for the sales team to convert interested employees faster.
05

Outcome

Employees serve themselves, and approvals left Excel.

What changed

  • Employees apply for and manage loans without calling sales or support.
  • Staff work from one dashboard instead of Excel sheets.
  • Approvals no longer travel by hand from office to office.
  • Sales onboards new employees faster.

What I learned

A lending product can sometimes be mostly about permissions and approval logic, not just visual design.

Designing both sides of a workflow, starting with the customers' needs, helps keep the flow in sync, because you can see exactly where one screen feeds the other's queue.

Check out other works

Profile
I'm available for Work

Have a project to design?

Hit me up if you're looking for a fast, reliable UI/UX Designer, AI Design Dev., WordPress Web Designer, SEO Content Writer - who can bring your vision to life

Profile
Ifeoluwa Ajetomobi
Designed and developed by myself