January — October 2023

Raylu

Can a Figma file close a $4M round?

Deliverable
raylu — workspace.fig · one navigable file
Role
Sole designer, working with the founders
Timeline
Jan — Oct 2023 (on and off)
Outcome
$4M seed closed (2023) · $8M Series A (2025)

Two founders, a deep product, no artifact

Raylu was building UI for ML pipeline observability. The founders had product depth and technical clarity. What they didn't have was a single thing an investor could open.

It started as a wireframe pass for a pitch deck and became a six-month engagement: brand, a Figma component system, and clickable prototypes for fundraising and early-adopter conversations — everything between a founder sketch and a React-ready component library.

The bet was the success metric. Pre-PMF prototyping isn't shipped product. The brief was make the product readable enough to fund and build. Polish costs founder burn rate; clarity of concept doesn't. That trade-off shaped every decision.

The Figma file is the deck. The deliverable is alignment, not polish.
6
month engagement, brief to handoff
1
sole designer working with cofounders
5
sections in one navigable Figma file
$ 4 M
seed round they closed

The gap was alignment

Sketches and Zoom calls produce ideas. They don't produce shared context across founders, investors, and an outside designer. Without a designed artifact, every pitch re-derived the product from a whiteboard.

So the first deliverable wasn't a screen. It was the Figma file as the alignment artifact — a workspace stakeholders could navigate without me in the room, with linear sections for brand, competitive analysis, strategy, and the product itself. Founders could self-serve pitch updates. I stopped being the bottleneck for every external conversation.

You just got the link

This is the file an investor opened cold. Scroll it the way they did — top to bottom, one page at a time. Brand. Competitive analysis. Strategy. Wireframes. Hi-fi. Each section dates itself, names itself, then fills in.

live · scroll the file
raylu — workspace .fig you + the two founders
Apr 2023 · added by me

01Brand

First palette explorations, the whale mascot, and the headline thesis: “tools to make ML safe.”

  • palette
  • whale
  • tone-of-voice
Raylu pixel-art whale mascot on teal.

The whale mascot — picked because it reads friendly at any scale.

Apr 2023 · added by me

02Competitive analysis

Five sibling ML-tooling products mapped on a 2×2 of fidelity vs scope.

  • Snorkel
  • W&B
  • Roboflow
  • DataRobot
  • Galileo
fidelity ↑ scope → Snorkel W&B Galileo Roboflow DataRobot raylu

Kept the work honest — no surface someone else already shipped.

May 2023 · added by me

03Strategy / thesis

Goal: provide the tools to make ML safe. Deterministic vs unbounded — we built for the unbounded case.

  • observability
  • pipelines, not models
  • human-rules over
Strategy slide: Raylu's goal is to provide tools that make ML safe. ML splits into Deterministic and Unbounded; we work in the unbounded case via pipelines.

Pipelines, not single models. Human rules over the chain. That positioning carried into every screen.

Jun 2023 · added by me

04Wireframes

Founder sketches translated into low-fi frames. Two starting paths: talk to a chat bot, or boot a premade system.

  • chat-first
  • premade systems
  • two-path entry
Founder sketch for the model-prototype starting page. Sidebar icons, a chat-style interface, and an All systems grid of recommendation-system cards. Annotated: “either talk to chat bot or boot up premade system.”

Founder sketch (mid-Zoom call, then traced in Figma the same afternoon). The annotation became the V0 nav model.

Jul 2023 · added by me

05Hi-fi prototype

Pipeline builder hi-fi — model-integration nav, label-errors workflow, UMAP slicing. Clickable for investor demos.

  • pipeline UI
  • UMAP slicing
  • label errors
Raylu hi-fi UMAP slicing UI. A scatterplot with orange and green clusters, a left rail of sliders (point size, opacity, thumbnail size), and a UMAP reduction-algorithm selector. Model Integration button top right.

The hi-fi pipeline — model nav, label errors, UMAP slicing. The investor didn't just scroll past this screen. In a moment, you'll open it yourself.

end of file — you now know the product
The real workspace ran this exact shape — vertically expanding, date-stamped sections an investor could open cold and exit with the right mental model. The same file later became the engineering team's source of truth; component patterns mapped 1:1 to the React build, so they pulled straight from what the founders had been pitching with. No handoff doc, no design-system migration. The artifact carried forward.

Sketch in the morning, frame by the afternoon

Two of those sections — Wireframes and Hi-fi — came from this loop. Founder sketches arrived over Zoom; clickable frames went back the same day. Drag the handle: a napkin sketch on the left, a real Figma frame from the same build on the right. No intent lost between the sketch and the screen.

Raylu hi-fi label-errors workflow — a real Figma frame: a left rail with the raylu wordmark and nav icons, a metrics bar (false-positive count, confidence and IOU threshold sliders), and a grid of selectable image thumbnails with bounding boxes, each a candidate the model flagged as wrong. Hi-fi Figma frame · same afternoon
Founder sketch for the model-prototype starting page: a sidebar with three abstract icons, a chat-style interface up top with a “submit prompt below” note, and an “All systems” grid of eight “Recommendation System” cards. Annotated in red: “either talk to chat bot - or boot up premade system.” Founder sketch · mid-Zoom call
← drag to compare →

Left of the handle: a founder's sketch from a Zoom call. Right: a real, clickable Figma frame from the same build, hours later. The rail and the intent carried straight through.

ML primitives a PM could read

The hard part was never the ML — it was making a real ML primitive legible to a non-engineer mid-demo. Here's the UMAP slice surface, live. Drag a box around a cluster of embeddings and it resolves into a named slice. Dimensionality reduction made into something you can grab.

raylu — workspace.fig you + the two founders
Raylu UMAP slice surface — a real Figma frame: a left rail with the raylu wordmark and nav icons, a left control panel (point size, opacity, thumbnail size, a reduction-algorithm dropdown set to UMAP, an annotation field set to 'vehicle'), and a 2D embedding scatterplot of green and orange point clusters. vehicle · 47 images

Drag a box around the green cluster — or press Enter to slice the vehicle cluster.

That's the gesture an investor made mid-demo. Now you've made it too.

You just clicked into this screen. So did they.

What followed

That gesture is the one an investor made mid-demo. The file held up where it mattered — investor demos without a designer present, early-adopter conversations, a workspace an engineering team could read.

$0M

seed round closed (2023)

Conversion Capital and Unusual Ventures led, with angels including Arash Ferdowsi.

I can't speak to a causal chain between my work and the funding. Design at pre-PMF is one ingredient among many — the product team did the long work, and the round closed under conditions that had moved well past anything the 2023 file specified. What I can speak to is what landed in the right hands: a navigable file investors could read cold, a brand the team could pitch from, and component patterns the engineering team picked up directly when they started.

The product has pivoted significantly since the 2023 work documented here — it's now an AI sourcing platform for private-market investors — and raised an $8M Series A in late 2025.

What generalizes

What I'd carry into any early-stage engagement — one principle, and one number.

The workspace is the highest-leverage deliverable. Sketches and Zoom calls produce ideas, not shared context. A navigable file lets founders self-serve pitch updates and keeps the designer off the critical path for every external conversation. The artifact is the alignment.
0
polish budget on disposable surfaces — by design. The pitch file was scoped to clarity, not finish. Founder burn rate is a design constraint.
← back to selected work