A payout prototype, rebuilt as a partner-ready B2B product
NVP is a fintech platform for companies with large freelance teams: it onboards, checks and pays self-employed, sole traders and civil-law workers. We designed the product UX/UI and its public site.
- Client
- NVP
- Industry
- Fintech platform
- Year
- 2026
- Services
- Product design, SaaS, Fintech
from brief to a first redesign on the product's code
prototype screens mapped before a pixel moved
dashboard blocks rebuilt around money and risk
contractor types, one payout flow
The challenge
Every freelancer a company pays needs a contract, an acceptance act and, if self-employed, a tax receipt. Mass payouts can also get a company account blocked. NVP had a working prototype for all of it, but it looked like an internal tool and had to face partners in May. It needed to read as a serious B2B product on a laptop and a phone.
Our approach
We designed on the product's own shadcn/ui components, so the first redesign ran in its code the next day. The key decision: put risk next to money. Every screen shows documents, checks and limits beside the amount, so a manager sees the problem before paying.
A payout is the end of a task. Check the person, the contract and the work first, and the money moves on its own.
What we did
01
Dashboard
The first screen after sign-in, built for the May partner demo. We rebuilt the prototype's seven blocks into one hierarchy: money and risk on top, then trends and compliance, then funnels.
- 4 KPIs, from turnover to open alerts
- Turnover chart with a period switch
- Compliance gauge and overdue documents
- Onboarding and task funnels
02
Single payout
Creating a task is creating a payout, and managers do it all day. We split the form into three steps: contractor, work, payment. The contract, the acceptance act and the contractor's checks sit inside the form.
- Three steps: contractor, work, payment
- Verified contractor card up front
- Acceptance act signed by OTP code
- Empty, filled, error and success states
03
Bulk payouts
Large payouts arrive as Excel registries. We designed the upload in four states, from file drop to result, and an error table that names the row, the field and the fix before anything goes to approval.
- Drop zone, processing, result, error table
- Duplicates, limits and gaps per row
- Patent and controlled persons checks
- Clean rows go to approval, the rest wait
How it works
- 1
Invite
Company invites contractors of any of the three types
- 2
Documents
Contractor uploads documents through a secure account
- 3
Checks
Patent and controlled persons register checks before work
- 4
Task
Manager assigns work and tracks it to acceptance
- 5
Signing
Contractor signs the contract and act with an OTP code
- 6
Approval
Managers prepare the registry, authorized staff approve it
- 7
Payout
Money leaves a nominal account for a bank or wallet
The live product
nvp-platform.ru
Results
- 01Final dashboard delivered in 15 days, on target for the May partner demo
- 02One form for a task and its payout, in empty, filled, error and success states
- 03A registry upload in four states, with errors named by row, field and fix
- 04A public site that walks visitors through six product modules
Built with
- Design
- Figma · components · auto layout
- UI kit
- shadcn/ui · Base UI · Recharts · Lucide
- Frontend
- Next.js · React · Tailwind CSS · TypeScript
- Platforms
- Desktop web · mobile web · PWA
Next case · Esturión de Sarrión
Online store for premium caviar, truffles and wagyu
Let's talk
Got a project? Let’s scope it in 30 minutes.
Tell us what you're building. You'll get a straight answer on timeline, team and approach on the first call.