02 / 2025
Crashybara
A SaaS reporting platform
Product
My role
About
Crashybara is a platform for searching a large database of traffic accidents and turning selected records into structured reports.
crashybara.com ↗The live site may differ due to post-launch product updates.
Challenge
The challenge was to make a large, complex dataset searchable across multiple criteria, while enabling users to turn selected records into structured reports. The product also needed to support both individual and team accounts, with different levels of access depending on subscription status. Administrators needed tools to manage team members and monitor credit usage.
Approach
I worked across the product from information architecture to final UI, defining its structure, user flows, and interactions. The process combined client interviews, database analysis, requirements review, and usability evaluation. I worked closely with the client, CTO, project manager, frontend and backend developers, and QA to align design decisions with product requirements and technical constraints.
Key design decisions
01
Advanced search
The search needed to handle a large number of criteria without making the interface difficult to navigate. Users could search by accident and vehicle attributes, with the option to add criteria for a second vehicle when needed.
02
Result count before search: preventing unnecessary data loads
The result count was surfaced while users built their search criteria. If the result count exceeded 300, users had to refine their criteria before loading the results.
03
From search to report
Once users found relevant records, they could unlock the results, review the available data, select the accidents they needed, and export the corresponding reports as PDF.
Search → Unlock with credits → Review results → Select → Export
04
Designing for edge cases
Subscription and account changes introduced a wide range of states across access, members, and settings.
One challenge was handling plan changes without leaving the rest of the product in an inconsistent state — for example, ensuring that changes to account configuration were reflected across member access and related settings.
UI & design system
I built the product's UI system, using the existing engineering framework as a foundation for development consistency.
- Variables & styles: Colors, typography, spacing, and layout properties.
- Custom components & states: Base UI controls, including inputs, buttons, and selectors; forms with validation; step indicators; section modules; complex functional cards; and modals.
- Desktop & mobile: Reusable components and layouts adapted for desktop and mobile experiences.
- Light & dark themes: Consistent interface styling across both themes, with colors adapted for each mode.
Visual direction
The visual direction was built around the existing Crashybara logo, extending its colors into the interface. I proposed two visual directions, and the client chose the more expressive option.
A subtle line motif, inspired by a crack, was introduced across the interface as a visual reference to crashes and accidents.
Style options
Final design
Search
Advanced criteria and result count.
Results locked
Search results with the information needed to review and select records.
Report export
Selected records prepared for PDF export.
Account / Team members
Subscription, members, and account settings.
Outcome
The platform was successfully launched as a subscription-based SaaS product, providing a structured way to search a large database and generate reports.