← Back PactFi Funds Flow case study
Close

PACTFI · PRODUCT IMPROVEMENT · 16-DAY DELIVERY

Reducing Funds Flow Setup
from eight steps to five.

I turned one prioritized usability issue into a focused research, redesign, and validation cycle for a live private-credit platform.

  • Lead product design
  • Complex workflows
  • Product improvement
  • Interview-gated
Reconstructed PactFi funds flow setup interface with a deal workspace, flow sequence, and setup details panel

Reconstructed interface shown for public-safe storytelling. Product names and visual details are adapted.

One focused redesign. Clear evidence of ownership.

I owned the Funds Flow Setup investigation and carried it from problem framing through redesign, validation, and delivery alignment.

01

8 → 5 steps

The shipped flow kept every required action inside one continuous setup sequence.

SHIPPED WORKFLOW
02

16 days

A focused cycle from issue framing and behavioral review through validation and delivery alignment.

END-TO-END OWNERSHIP
03

5 sessions

Individually moderated with partners from PM, Business Development, and Customer Support.

INTERNAL DOMAIN EXPERTS

Delivery built momentum. Research was needed to sustain growth.

As client adoption, workflows, and operational complexity grew, BD and Customer Support consolidated eight important issues using client feedback and information from the support tool. I helped the six-person design team turn that intake into a coordinated research cycle without stopping active delivery.

01
Platform intakeBD + Customer Support

Eight separate client-reported issues across the product, not eight reports of one problem.

INPUT
02
Design-team prioritizationSix-person design team

I helped prioritize six investigations, with one designer responsible for each selected issue.

SCOPE
03
My ownershipShared research framework

I created the common research framework and owned Funds Flow Setup through the shipped redesign.

DELIVERY

Behavioral evidence narrowed the problem. Human review established what mattered.

I used Ask Galileo’s natural-language chat to generate focused charts, funnels, path analyses, and session playlists. I reviewed the resulting sessions directly, mapped the complete task, and redesigned the flow around continuity rather than isolated screens.

Reconstructed review queue interface with operational cases, statuses, and a selected case inspector

I kept supporting work inside the primary task.

The shipped redesign reduced Funds Flow Setup from eight steps to five. Supporting entity work stayed inside the active Deal, existing entity information could be reused, and every required action remained in one continuous flow.

PactFiDeal / Funds flow
STEP 03 OF 05

Reuse entity information

Keep supporting work in the primary task.

EntityNorthwind Holdings
AccountOperating account
ReviewFunds flow setup
READY TO REVIEW

Everything required is in one flow.

Review the account details before submitting the Deal.

✓ Entity details reused
✓ Required actions complete

Validation summary reflects internal review signals. No externally verifiable baseline is claimed.

01

Five individual sessions

I moderated five separate sessions with partners from PM, Business Development, and Customer Support, each completing the full task individually.

INTERNAL DOMAIN EXPERTS
02

Task-level validation

I tested the complete sequence as one workflow, not a collection of screens, so continuity and return paths stayed visible.

END-TO-END TASK
03

Directional release signals

Post-release review indicated improved task completion, fewer support questions, and fewer errors and dead clicks.

NO EXTERNALLY VERIFIABLE BASELINE

Research capacity has to scale with product delivery.

Once client adoption and workflow complexity accelerated, relying primarily on reported issues made investigation too reactive. With more time and direct customer access, I would build a continuous practice around a standing participant panel, dedicated research capacity, and AI-assisted triage with human review.

A closing note

Complex products do not become simple. Their complexity becomes manageable.

Discuss the case