Pixipap

Product design for financial workflows where a wrong click costs real money.

I help fintech and SaaS teams design investing apps, wealth platforms, payments, and accounting flows that users trust, compliance signs off, and engineers can build without rework.

Polina Nikolova, founder of Pixipap

15+ years in product, design & UX · 5 years at DEGIRO, Europe's trading platform for millions of investors · Executive MBA

Client experience

Trusted by product and finance teams

Bossard logo
Accountia logo
KAM Project logo
DEVELOP BG logo
Telegrami Kaubamaja logo
Exigio logo

Most product problems in finance software are not design problems.

What teams usually do

  • • Redesign the UI
  • • Add another feature
  • • Patch it with spreadsheets and manual checks
  • • Rebuild screens engineers already built

What actually blocks them

  • • Unclear rules for money movement and edits
  • • Missing audit trails and approval logic
  • • Permissions that grew without structure
  • • Requirements engineers can't build from

When the workflow logic is clear, the interface becomes obvious.

Who this is for

Does this sound like your product?

Your team reconciles by hand

Overpayments, credits, and corrections live in spreadsheets and support tickets.

Edits feel risky

Users need flexibility, but every adjustment threatens ledger integrity or compliance.

Permissions grew without a plan

Roles, approvals, and access rules are tangled and slow everyone down.

Investors hesitate before they act

Onboarding, suitability checks, and order flows create doubt instead of confidence.

Portfolio data overwhelms clients and advisors

Performance, risk, fees, and holdings are all there, but hard to understand and act on.

Your AI feature isn't trusted

Users don't understand what it did, why, or how to correct it.

Engineers are blocked by unclear requirements

Features stall between business, product, and development.

How I work

Diagnose, structure, then design build-ready.

01

Diagnose

I map the workflow as it really runs today, including the edge cases, workarounds, and rules nobody wrote down.

02

Structure

I define the rules for money movement, edits, approvals, and permissions so every state has a clear owner and outcome.

03

Design build-ready

I deliver flows, screens, and specs your engineers can build from without guessing or rework.

Built for how teams ship in 2026

AI tools can now generate screens and code in minutes. What they can't do is decide the rules: who can approve a payment, when an entry can be reversed, what the user must see before confirming. That's where I work.

Specs your AI coding tools can use

Deliverables include structured flow specs, edge cases, validation rules, and design-system-aligned prototypes your engineers can feed straight into Cursor, Claude Code, or Figma Make.

AI features users trust

Designing AI assistants and agents inside financial products: explainable outputs, confidence and error states, human approval steps, and full audit trails.

From AI prototype to production

Already built a finance tool with Lovable, Bolt, or Cursor? I review the workflow logic, UX, and edge cases before real money and real users hit it (code review delivered with a development partner).

“Polina picked up our domain remarkably fast and communicated clearly at every step. We're very happy with the work she delivered.”
Conan Akrei, Managing Director, Accountia

Tell me which workflow worries you most.

Share what you're building or fixing. I'll reply within 2 working days with a recommended scope and next step.