National Business Capital · Product design · Web + mobile · Financial workflows

From referral to funding, every step made simpler.

Partner Portal dashboard and the mobile offer comparison

In brief

I redesigned three products for National Business Capital. One is the portal its partners use to track their deals. The other two are the steps a client takes to get funded: reviewing an offer and then submitting documents.

How a deal works

National Business Capital helps small and mid-sized businesses get funding. Some business owners come to it directly. Others are referred by partners, who earn a commission when a deal funds. An advisor presents the funding offers and guides the client through them. The client signs, sends the documents the deal needs, and the deal funds.

  • Partner PortalWhere partners submit new opportunities and track their deals and commissions.For partners
  • Presented OfferWhere a client compares funding offers with an advisor and signs one.For clients
  • Document CollectionWhere a client uploads the documents a deal needs and sees where each one stands.For clients
Role
Senior Experience Designer. UX and UI for all three products; lead designer on the Partner Portal, with research run alongside a research partner.
Timeline
2025 – 2026
Status
All three products launched

01 · 2025

Partner Portal

Enough visibility to trust the process.

Partners are the people and firms who bring deals to National. They use the portal mostly to submit new opportunities, then to track those deals and the commission they earn. Brokers, consultants and affiliates are the most active on the portal: they send the most deals and come back to track their pipeline and their commission. Investment bankers, private equity and M&A firms send fewer, larger deals, usually using National for junior or bridge capital.

“My name is on this deal — I need to know what’s going on every step of the way.”

Partner · from interviews

“I just want to see where my lead is and when I’m getting paid.”

Affiliate · from interviews

Before and after

From an outdated portal to a pipeline partners can follow.

Before: the old partner portal on a phone
After: the new pipeline, each deal with its stage, scrolling under a fixed header

Study

We started with the portal partners already had.

I audited every screen of the existing portal. With a research partner, I interviewed partners and internal stakeholders, and we ran a usage survey.

The old partner portal, and the redesigned dashboard on desktop
The redesigned partner dashboard, scrolling under its fixed header
The partner home screen on a phone: pipeline, commissions, referral links, announcements

Study

What partners told us.

We grouped what we heard into themes: notifications, transparency, support, mobile, resources and security. Most were requests we could build: real-time status alerts, a legend for the pipeline stages, chat tied to each deal.

One was a conflict. Partners wanted to see the dollar amounts behind their deals. National does not share a deal’s terms or its rates with partners. The portal had to give partners enough to trust the process without showing those numbers.

  • Pain pointNo split between partner types
  • Pain pointStatus only visible after logging in
  • Pain pointLogin expires too often
  • Pain pointDollar amounts and terms hidden
  • RequestReal-time status alerts
  • Pain pointPartners didn’t know they could send clients the uploader
  • Pain pointSupport is hard to find
  • ThemeTransparency
  • Pain pointRelationship managers slow to reply
  • RequestA legend for every pipeline stage
  • RequestSave and complete later
  • RequestChat tied to each deal
From partner interviews

Partners want to see the dollar amount on a deal and cannot get it from the portal. They read that as a lack of transparency.

From stakeholder interviews

The business is hesitant to give partners too much detail, and wants to be able to keep it concealed.

What it came down to

A tension between transparency and control.

The portal had to earn trust without showing the terms.

Make

Deciding what to build first.

The survey showed that submitting new opportunities was the most-used feature, real-time status was the most requested, and email was the preferred way to be alerted. I ranked each problem by how often it came up, then agreed with leadership what would go into the first release and what would wait for a second phase.

HighLimited mobileMissing metricsNo segmentation
MediumMessaging not real-timeNo deal status updatesLimited view of terms
LowGeneric co-branded linksFew trust signalsLimited onboarding

Make

Structure first, mobile first.

I organised the portal around what partners come to do and wireframed it for mobile first, setting each existing screen beside its replacement to compare them.

Wireframes of the partner dashboard on desktop and mobile

Decide

Where every deal stands, without its terms.

Each deal moves through six stages, named in plain language. A partner can see which stage a deal is in, whether it funded, and the commission they earned. The deal’s terms and National’s rates stay out of view. The old portal gave no reason when a deal was closed-lost. Now it always does, so a partner is never left wondering why a deal fell through, and they can chat with someone to find out more.

The partner pipeline screen
Every deal in the pipeline with its stage
One deal opened: contact, stage and actions
In ReviewClient possibly working with NBC

Decide

The same data, made comparable.

The old dashboard listed totals. A partner could see how many opportunities they had sent, but not how many became applications or what their funded deals were worth. The redesign pairs the same data to answer that, and a prompt showing the days since their last submission nudges them to send the next one.

Three dashboard cards: opportunities against completed applications, funded units against funded volume, and commission by source

Decide

A chat that feels like a conversation.

Chat was one of partners’ top requests. In the old portal, a message felt like a note left on a file, and the reply came back as an email. I proposed a chat feature inside the portal, tied to each deal, with an automatic reply when the advisor is unavailable. The chat launched with the new portal. Confirmations and compliance details across the portal made it easier to trust.

Submitting a support request, and the partner support team’s contacts
Wireframes of the partner dashboard on desktop and mobile
The partner pipeline screen
Every deal in the pipeline with its stage
One deal opened: contact, stage and actions
In ReviewClient possibly working with NBC
Three dashboard cards: opportunities against completed applications, funded units against funded volume, and commission by source
Submitting a support request, and the partner support team’s contacts

Outcome

The new portal replaced the old one, and partners valued the whole redesign.

Partners and leadership responded well to the layout and the experience as a whole, and partners singled out the chat they had asked for. In finance, that matters: a partner sending a client to National has to trust where the deal is going, and a clearer, more transparent portal builds that trust. The first release launched with onboarding and a guide that explains each stage. Notifications, the most complex request, were designed and built in a second phase, with email or text alerts for each stage.

The onboarding tour and pages from the partner user guide
  • Six plain-language stages, and a reason on every closed-lost deal.
  • Chat that feels like a conversation, with confirmations across the portal.
  • Designed mobile first, so partners can use it from a phone.

Carried forward →

That was the partner’s side of a deal. On the client’s side, offers still arrived as a PDF and documents went back by email.

02 · 2025 – 2026

Client Journey

From an emailed PDF to funding.

Funding offers used to be emailed as a PDF that ran to several pages. Every offer was in it, but the information was cramped and hard to read, and the client worked through it alone, with no easy way to compare one offer with another.

Before and after

From a PDF and an email thread to offers compared on screen and a checklist for documents.

Before: a PDF financing proposal. After: offers compared side by side, and the document upload centre.

Make

From a PDF to steps on screen.

I audited the PDF process and looked at how consumer brands let people compare plans. The first release turned the PDF into three steps: choose an offer, sign, upload documents. It showed one offer at a time.

Each offer is pulled from the deal record in Salesforce, so I worked closely with the Salesforce and front-end developers on which fields appear, how the screens behave and how they perform.

The first web flow: approved funding options, then the selected offer

Decide

Why a table: compare it on the call.

One offer at a time made each offer easy to read, but hard to weigh against the others.

After conversations with the business about how offers are actually discussed, we chose a comparative layout: every offer side by side, visible to the advisor and the client on a call, from a link the advisor sends.

The client selects one, reviews its term sheet on the next screen, where DocuSign is embedded in the product, and signs there.

Three directions for comparing offers, and the side-by-side table that was built

Make

On a phone, offers become cards.

The client swipes between offers and signs from the same screen.

The offer comparison and the next-steps upload screen on a phone
First offer cardSecond offer card, swiped into view
The first web flow: approved funding options, then the selected offer
Three directions for comparing offers, and the side-by-side table that was built
The offer comparison and the next-steps upload screen on a phone
First offer cardSecond offer card, swiped into view

Outcome

A client can go from comparing offers to a signed term sheet in one flow, with an advisor on the call and no email back-and-forth.

  • Every offer on the deal, side by side.
  • Disclosures such as APR sit inside the comparison.
  • Selecting an offer leads straight to its term sheet and signature.

Carried forward →

Once an offer is signed, the client still has documents to send. That step became a product of its own.

Study

Documents went back and forth by email.

National emailed the client a list of required documents, and the client sent them back as attachments, a few at a time. Advisors followed up by email, and clients had to guess what was still missing. Before designing, I studied how other products show progress through a long set-up, from payroll onboarding to commerce platforms.

Reference screens from other upload and onboarding flows

Make

The brief, and what we proposed instead.

The brief was to take the document screen the team used in Salesforce as the wireframe and restyle it in the new brand. That screen worked well for staff. For a client handing over bank statements and tax returns, it did not: nothing explained what was needed, what had been received, or what would happen next. The Creative Director and I went back to that research and proposed a guided checklist that takes one document at a time. We presented it with our reasoning, and leadership approved it.

Early drafts: documents as a table, then as a checklist

Decide

A status on every document.

The checklist sits beside the upload area, on desktop and on mobile. Each document shows its status: pending, under review, approved or rejected, and then in underwriting. If a document is rejected, the advisor’s reason comes with it, and the client can reply with a note. Nothing has to be finished in one sitting. The client uploads what they have, the link stays active, and they can come back for the rest. If a document needs another look, an email tells them.

The document checklist: seven documents, each selectable

Decide

Undoing a wrong upload.

In the first build, a file could not be removed once it was uploaded. I asked what a client would do after uploading the wrong one, and proposed a fix to the Salesforce developer and the product manager. After a few rounds of discussion, clients can now delete a file until they press Complete.

The upload card with three uploaded files, each with a delete icon
Reference screens from other upload and onboarding flows
Early drafts: documents as a table, then as a checklist
The document checklist: seven documents, each selectable
The upload card with three uploaded files, each with a delete icon
The document upload centre: checklist on the left, upload and advisor note on the rightThe same upload centre on a phone

Outcome

Collecting documents by email was replaced by a guided checklist.

  • A status on every document.
  • Files can be deleted until the client presses Complete.
  • The link stays active until the documents are done.

Summary

Where it stands

All three products launched. I was responsible for UX and UI on each, and for the portal research alongside a research partner. I designed every state and handed over developer-ready specifications, then checked the build through release, working with the Creative Director, product and engineering.

Accessibility

Designed to WCAG AA.

Every colour pair checked for contrast, every field labelled, touch targets sized for a phone and a set focus order, all written into the specifications engineering built from.