Operating a six-month product cycle in financial technology demands rapid iteration. Visual consistency quickly becomes a major hurdle. You’ve got to deploy a cohesive user experience across web dashboards, iOS applications, and Android clients simultaneously. Lacking a dedicated in-house design team forces product managers into a tight corner. We must find ways to source, adapt, and implement assets that look professional enough to handle highly sensitive data workflows.
Deciding how to populate onboarding screens forces a hard choice. Do you commission custom artwork or tap into existing asset libraries?
The Six-Month Cycle Dilemma
Hiring a freelance illustrator presents distinct scheduling and budget challenges. Custom commissions require defining every single required screen upfront. You negotiate complex contracts and schedule endless revision rounds. Then product requirements inevitably pivot in month three to include a new biometric login flow. Suddenly you have to initiate a new commission, wait for sketches, and completely derail the sprint calendar. Bespoke work yields a unique brand identity, but you’ll sacrifice vital agility.
Relying on pre-made libraries offers the speed needed for fast-paced sprints. Quality varies heavily between platforms. Open-source libraries like unDraw pop up frequently for quick wireframing because they cost nothing. Unfortunately, they suffer from severe overexposure. Financial products using the exact same generic figures as a hundred other SaaS tools quickly lose authority. Trust is paramount in fintech. Users seeing stock characters asking for their social security number will immediately bounce.
Blush provides more customization through mixing and matching character components. Many of its available styles lean toward a playful, casual aesthetic. That clashes with the serious tone required for banking or investment apps.
Ouch, a library maintained by Icons8, attempts to bridge that gap. With over 101 illustration styles covering everything from minimalistic monochrome to detailed 3D scenes, it provides massive scale. Product managers get enough volume to support an entire application ecosystem. You don’t have to hunt across multiple disparate asset sites just to find matching icons.
Managing Cross-Platform Asset Demands
A late-stage sprint pivot illustrates exactly why rigid custom illustration pipelines break product timelines. Thursday morning standup arrived with bad news. Our mobile engineering lead flagged that the newly approved transaction history feature lacked empty state graphics. Tuesday was the hard iOS release date. Blank white screens with raw text in a banking app imply a critical loading error rather than a simple lack of recent purchases. Requesting a custom asset from an external contractor takes at least a week of back-and-forth communication.
We didn’t have a week.
Instead, I opened the Pichon desktop app. It syncs the entire Ouch library locally to your machine. We’d previously standardized our product using one of the clean, vector-based business styles. Filtering the 28,000 available business assets for empty state concepts took seconds. Next, I dragged a pre-designed illustration of an empty wallet directly onto the Figma canvas. Our paid plan meant the asset imported natively as an editable SVG. Clicking the accent layers, I swapped the default colors to our brand’s primary navy and secondary teal before exporting the final PNG.
The iOS team had it within twenty minutes.
Sprint continued without a single delay.
Sourcing the Right Assets for Financial Workflows
Building out a multi-step user onboarding flow requires far more than standalone decorative images. Assets must tell a coherent story across web and mobile platforms. Using Ouch for an end-to-end onboarding sequence involves a very specific workflow.
First, finding the right vector illustration style means looking beyond individual images. Search for expansive collections covering the entire user experience flow. I select a style containing distinct, matching scenes for account creation, identity verification, and initial bank deposits.
Next, I download SVG formats for the web team and PNGs for mobile developers. Ouch illustrations function as layered vector graphics broken down into tagged, searchable objects rather than flattened, rigid scenes. Download an identity verification scene, and you can crack it open in any vector editor. Swap out a generic document icon for a specific driver’s license element found elsewhere in the exact same style category.
Finally, web dashboard onboarding gets the Lottie JSON files associated with that exact style. Fintech onboarding is notoriously tedious. Adding a subtle animation to the final “Setup Complete” screen provides immediate, satisfying feedback for exhausted users. Front-end teams don’t even have to write custom animation code.
Handling failure states requires a similar start-to-finish approach. Static images on a 404 payment failure page often increase user frustration. Search the technology category for broken servers or disconnected cables. Using Mega Creator, Icons8’s browser-based editing tool, I combine a disconnected server object with a character from our chosen style looking confused. Adjust the layout, apply our specific hex codes, and export the composite image straight to the development pipeline.
Even our error states feel deliberate and strictly branded.
Breaking Points in Pre-Made Graphic Systems
Extensive libraries solve speed and volume issues, but they come with unavoidable structural limitations. Pre-made assets target broad utility. Highly specific financial concepts often require intensive manual composition. Need an illustration of a specific cryptographic ledger protocol? You won’t find it ready to download. Piecing together abstract network nodes and lock icons becomes your responsibility. That requires a baseline level of design competency.
Free tiers are also wildly impractical for a professional product. Basic accounts only provide standard-resolution PNG files. They also mandate a visible attribution link back to the creator. Embedding third-party attribution links on every mobile app screen or secure dashboard interface severely degrades the professional appearance of a fintech product. Standard PNGs also can’t be recolored to match strict corporate brand guidelines. Actually building a cohesive design system requires upgrading to a paid tier. Accessing editable SVGs and removing attribution is a hard requirement.
Here’s one final catch regarding complex formats. Ouch contains 44 distinct 3D styles available in FBX and MOV formats. Implementing 3D assets cohesively across native iOS, Android, and web environments introduces heavy performance overhead. Unless your engineering team prepares to optimize complex 3D models for low-end mobile devices, keep those specific assets far away from embedded application screens. They belong strictly on marketing landing pages.
Operating an Asset Library Like a Product Manager
Masking the fact that you rely on stock assets across a major application takes effort. Strict discipline is required during implementation.
- Select exactly one primary style from the library and completely ban the use of any others within the core application.
- Establish a centralized internal repository for recolored assets so developers don’t accidentally download default-colored illustrations directly from the site.
- Search specifically for layered objects to build custom composite scenes instead of relying entirely on pre-made narrative layouts.
- Download unused assets at the end of the month if your billing cycle rolls over unused credits.
Building a localized stockpile of matching elements pays off massively for future features.
Managing product visuals without a dedicated design team requires a complete mental shift. Treat an illustration library as a raw database of modular components rather than a gallery of finished art. Commit to a single style. Aggressively customize vector layers. Product managers can ship a fintech platform that looks entirely bespoke within a standard six-month development window.