Sudo.doc - WordPadケーススタディ
← Back to projects もどる
Sudo

Sudo

1st place · UBC Product Heist

Helping VC associates turn inbox chaos into a ranked pipeline. 1st place at UBC Product Heist.

Team

Darius Alexander

Pauline Ongchan

Philippe Grosjean

My role

User Research

Wireframing

Prototyping

Tools

Figma

FigJam

Duration

2-day hackathon

Overview

Sudo pulls a VC associate's whole pipeline into one workspace.

Our team of four built it in two days for a challenge set by Overdrive, an AI-for-VC studio. It placed 1st at UBC Product Heist.

Problem

VC analysts spend their day organizing, not evaluating.

Much of their day goes to repetitive manual work across tools that don't talk to each other.

Emails, decks, notes and reports scattered across separate tools

Too much mundane work

Emails, pitch decks, meeting notes and market reports live in different tools. Nothing is automated.

Separate tools floating apart with broken links between them

No single source of truth

Each tool holds part of the picture, so analysts stitch it together by hand.

Complex relationships

Who knows who and who has backed which founder lives in people's heads and scattered CRM notes.

Hard to rank startups

Signals sit across spreadsheets and are rarely evaluated the same way twice.

Discovery

What does an associate's day actually look like?

We built a persona and mapped their day in FigJam. Three things kept coming up:

  1. 1

    Deal updates are buried in the inbox

    Emails, pitch decks, meeting notes and market reports live in different tools. Nothing is automated.

  2. 2

    Warm intros live in people's heads

    Who knows who, and who has backed which founder, sits in memory and scattered CRM notes.

  3. 3

    Every startup gets scored a different way

    Signals sit across spreadsheets and are rarely evaluated the same way twice.

Design decisions

Inbox that updates the dealSolves 1

New emails move the deal stage and fill in the metrics on their own.

Relationship graphSolves 2

Shows which partner already knows the founder, so the warm intro is obvious.

One rubric for the whole teamSolves 3

Team, traction and market, weighted the same way every time.

Today at a glanceSolves 1

What's due today, without opening a single email.

Challenges

Too many good ideas for 48 hours.

Email intelligence, a relationship graph, scoring and a dashboard could each be a product. As a team we scoped every screen to one associate's day and cut anything that didn't fit it.

Eight ideas pass through a 48-hour funnel; four features come out

Result

1st place at UBC Product Heist.

Judges responded to the story as much as the screens: an associate's day first, the product second.

A podium with Sudo on the top step: 1st place at UBC Product Heist

Reflections

  • Structure is storytelling. Walking judges through an associate's day before showing the product landed better than a feature list.
  • Know what to cut. Guide the audience; don't dump information on them.

Next steps

Put it in front of real associates.

The demo ran on sample deals. Next, I'd test the email-to-deal flow with VC associates and learn which automatic updates they trust without double-checking.

Sample deals with an arrow to three people: next, test with real associates

Thank you

To Darius, Pauline and Philippe.

Ready 準備完了9 sections