Back to Projects
DesignFrontendReact/TSAISEO

PulzAid v2

Redesigned and rebuilt both the official website and the web application — two products, one shared design system, owned end-to-end as the founding Design Engineer.

Role
Design + Frontend Lead
Company
Carelyze / PulzAid
Stack
React, TypeScript
Impact
+65% time-on-site

The Problem

PulzAid had two products that both needed a ground-up overhaul:

  • The official website (pulzaid.com) was built from a Tailwind UI template — a generic landing page that didn't reflect PulzAid's evolving business model or product capabilities.
  • The web app (pulzaid.app) had an injury request flow that confused customers — they couldn't understand what was happening with their case or what to do next.

As the founding Design Engineer, I owned the redesign and rebuild of both — connected by a shared design system.

Part A

Official Website

From a Tailwind UI template landing page to a custom-designed multi-page site reflecting PulzAid's new business model and product positioning.

What Changed

New Visual Language

Replaced the generic Tailwind template aesthetic with a custom design system — calm, clinical, and trustworthy. Healthcare demands credibility at first glance.

Multi-Page Architecture

Expanded from a single landing page to a complete site with dedicated pages for services, about, and the new business paradigm — giving each audience a clear path.

Design Decisions

1

Brand refresh for the paradigm shift

The business model changed — the website had to communicate a fundamentally different value proposition. I redesigned the visual hierarchy and content structure to tell the new story, not just reskin the old one.

2

SEO-first architecture

Built with semantic HTML, proper heading hierarchy, structured data, and performance optimization from day one — not as an afterthought. This directly contributed to the 65% time-on-site increase.

How I Built It

Designed in Figma, built in React/TypeScript, deployed to production. I owned both design and implementation — every animation, spacing value, and responsive breakpoint was intentional, not interpreted by someone else.

Part B

Web Application

A major overhaul of the injury request and case management experience — driven by customer feedback and enhanced with AI-guided next steps.

What Changed

Redesigned Request Flow

Rebuilt the injury request experience based on customer feedback. The old flow left users confused about their case status and next steps. The new flow is clear, guided, and transparent at every stage.

AI-Guided Next Steps

Embedded AI assistance into the management experience — the system now suggests what to do next based on case context, reducing decision fatigue for both workers and case managers.

Design Decisions

1

Customer-feedback-driven redesign

Instead of guessing, I used real customer feedback to identify the pain points. The biggest complaint: "I don't know what's happening with my case." Every design decision was measured against this core problem.

2

AI as a guide, not a replacement

The AI suggestions appear as contextual recommendations — not automated actions. Users always have the final say. This "human-in-the-loop" pattern was critical for healthcare, where trust and control matter.

How I Built It

Translated customer complaints into strict technical specs, then designed and built the new flows in React/TypeScript. The AI suggestion layer integrates with the LLM classification backend — I designed how AI recommendations surface in the UI while keeping the experience simple and non-intrusive.

The Thread: Shared Design System

Both products share a unified design system I created in Figma and implemented in React.

Color tokens, typography scale, component library, spacing rhythm — all consistent between the marketing site and the web app. When a design decision was made for one, it informed the other. This is what happens when one person owns both: coherence without meetings.

Outcome & Impact

+65% average time-on-site on the redesigned website — validating the new IA, visual language, and SEO strategy.

Clearer case management — customers could finally understand their case status and what to do next, reducing confusion-driven support requests.

Zero handoff design — owning both Figma and React meant every pixel shipped as designed. The shared design system ensures consistency across both products without coordination overhead.