Pulse
My role
Product Designer
Year
2026
The team
Worked with Christian (cofounder) and Ipalibo (cofounder and engineer).
Live
Overview
Pulse is a startup building an AI powered data room for founders raising money. The product has two sides: a founder side for sharing documents and managing an investor pipeline, and an investor side where investors review shared materials and run diligence with Perry, Pulse's AI assistant.
The Problem
Pulse was live but had no design foundation: no system, no semantic tokens, no documentation. Components had been built in code as the product evolved, with no centralized way to align them.
The Goal
Build the design system from scratch, redesign both sides of the product, and rebuild the landing page, without slowing the team down.
Discovery
Before designing anything new, I needed to understand what already existed. Using Claude Code, I audited the codebase, mapping every component, every token (or lack of one), and every place the same UI pattern had been implemented differently. The audit gave us a shared picture of the work ahead: no design system, no tokens with roles, no documented components, no naming conventions.

Pulse didn't need rebuilding. It needed a foundation, and a structural, intuitive navigation and layout.
Process
This is how I worked, with structure over surface. 🏃
I joined Pulse's sprint cadence and ran the work in weekly design cycles, anchored in the audit. Each week I iterated rapidly with Claude Design, built proposals in Figma, and brought them to Christian and Ipalibo.
- Codebase audit via Claude Code MCP
- UX audit across the live product
- Information architecture mapping
- Tokens with semantic roles
- Components extracted via MCP
- Library documented and fixed
- Wireframed and iterated with the team
- IA restructured across both surfaces
- Designs refined to handoff ready
- Landing page rebuilt
- Designs synced to code via MCP
- Real use testing drove final refinements
- Codebase audit via Claude Code MCP
- UX audit across the live product
- Information architecture mapping
- Tokens with semantic roles
- Components extracted via MCP
- Library documented and fixed
- Wireframed and iterated with the team
- IA restructured across both surfaces
- Designs refined to handoff ready
- Landing page rebuilt
- Designs synced to code via MCP
- Real use testing drove final refinements
Foundation
I built it in Figma against the live codebase, with names matching at every layer: variables, components, React props. The MCP kept design and code in sync, so the system stayed live with the product, not parallel to it.
Step 01
Joined the repo branch and used the Claude Code MCP plugin to bring the current designs into my Figma file.
Step 02
Rebuilt the token layer with semantic roles for color, size, and typography, all meeting WCAG AA.

Step 03
Documented and fixed the core components, with naming consistent from Figma to code.

The design system became the source of truth for everything that followed.
Redesigns
Founder side.
The founder side is where founders share documents and manage their investor pipeline: Drive for files, Contacts for investors, Links for shared rooms. But it didn't feel like a fundraising tool. The interface wasn't intuitive enough, and that friction eroded the trust founders need in the tool running their raise.
Before the redesign
After the redesign
To rebuild that trust, I had to redesign around what founders actually do during a raise, not the features Pulse already shipped. I started with a Jobs to be Done audit, a framework that asks what a user is trying to accomplish in each session, then anchors every design decision in that intent.
It surfaced five founder jobs:
- 1.What's happening with my documents?
- 2.Who's most engaged right now?
- 3.What is each investor actually interested in?
- 4.Are my shared links still working?
- 5.What do I share next, and with whom?
These five jobs became the lens for every layout decision. The redesign worked at three levels.
Level 1: Navigation.
I built a side menu bar as the new navigation. Drive, Contacts, and Links are visible at all times, one click away from any screen.
Level 2: Workspace layout.
I built one shared layout across Drive, Contacts, and Links. It's structured by three panels: the collection holds the section's items, the content panel handles preview and actions, and the insights panel surfaces activity and controls.

Collection
Browse and filter items.
Content
Detail view and actions.
Insights
Activity, analytics, access.
Collection
Browse and filter items.
Content
Detail view and actions.
Insights
Activity, analytics, access.
Level 3: Pipeline.
I rebuilt Contacts as a ranked investor pipeline. Investors group by Hot, Warm, Cold, or Went Quiet, so founders can read the state of every relationship and work each investor through the raise.
Investor side.
The investor side had the same architecture problem as the founder side. When reviewing user feedback, we found that new investors felt uncertain when opening a data room. The app used to open with an empty screen, “Select a Data Room.” Perry, which was supposed to be the differentiator, was hidden in a right side panel, only noticeable when you clicked on a file. And the diligence checklist disappeared the moment you opened a document.
Before the redesign
After the redesign
I used the same framework and UX principles to approach this side, and the answer was simpler than the founder's. An investor opens a data room to do one thing: read the materials and make sense of them.
It surfaced what the investor actually needs to answer:
- 1.What's in this data room?
- 2.Does this company check out?
- 3.What does this document actually say?
- 4.What's still missing for my diligence?
Those questions reframed the entire layout around a single principle: Perry is the differentiator, and the interface should prioritize it as such. From there, the redesign came down to four moves.
Reused the architecture, flipped the hierarchy.
Same three panel layout as the founder side, with data rooms on the left and files in the middle, but Perry takes the main canvas instead of hiding in a side panel.

Data rooms & files
Navigation and shared materials.
Perry
Now part of the main canvas.
Data rooms & files
Navigation and shared materials.
Perry
Now part of the main canvas.
Killed the empty screen.
The “Select a Data Room” dead end became Perry's “What can I help with?”, so the investor never opens to a blank wall.
Kept diligence in view.
The checklist used to disappear the moment a document opened. Now it stays put, so investors always know what's still missing.

Shifted the palette to green.
Each side serves different users with different goals, so I moved the investor side to green, the color of investment and deals. The color shift makes it instantly clear which side you're on.
Landing page
The landing page needed to feel as solid and professional as the product itself, a clear showcase of Pulse's features and visual identity.
I started from the PRD and translated it into a low fidelity wireframe to align with stakeholders on structure, hierarchy, and copy before moving into the final, high fidelity design.

Low fidelity wireframe
Final result
Reflection
Pulse needed me to build the design system from scratch, on a sprint pace. I started by documenting every component carefully, then reevaluated my priorities: design first, documentation later. That experience taught me how valuable my own workflow systems are: when they're ready from day one, time goes into design instead of organization.
