Skip to content

What it does today

This is the core reference for the U2V team: what each automation does, how to use it, and what to know before you rely on it.

Everything starts with one email. Send a normal email to klaus@u2v.vc from your U2V address and Klaus works out which automation you need, runs it, and replies. There are no commands to learn — write in plain language. (One automation, the sample deck, runs entirely on its own; you never email it.)

Each automation below follows the same shape: what it does · how it works · how to use it · limitations · design decisions. The heading links to the technical deep-dive if you want to go under the hood.

Screening & filing startups — u2v-dealflow

What it does

Turns a startup into a scored, classified record in the U2V Dealflow list in Attio, with a briefing note attached. Every startup you send gets recorded. You can hand it a startup in almost any form:

  • a single pitch deck (PDF attached);
  • several decks in one email — each becomes its own deal;
  • a company website link;
  • just a company name;
  • several links or names in the body of one email;
  • a roster / list PDF of many startups (a cohort, a top-100 list) — it splits the list and processes each; long ones are worked through over time and you get a summary email with a CSV.

You can also just say extra context in the email — how you sourced it, what stage to file it at, which LPs to flag it for, the round and amount they're raising — and it's captured on the record.

How it works

It reads the deck (or researches the link/name), scores the startup on team, technology, business model and market, matches it to relevant LPs, and writes everything to Attio.

To start sharing dealflow with a specific LP

  1. In Attio, open the Soft LPs U2V list and find the LP.
  2. Set dealflow_sharing to “Yes” and fill in strategic_interests (their thesis — what they care about, what they don't).

From then on, dealflow automatically matches new startups against that thesis and flags the good matches on each deal's lp_relevance tag — which is exactly what u2v-lp-share later reads. (LPs added by u2v-lp-intake start at “No”, so you opt them in here.)

How to use it

"Please add this startup: https://acme.ai"

(deck attached) — "New deck for review; we met them at Slush, flag it for BASF."

"Add this one, put it straight into First Call — they're raising €3M Seed."

(top-100 list PDF attached) — "Here's the SET100 list, please run them all."

Limitations

It reads decks from attached PDFs. It cannot open a deck behind a Google Drive, Dropbox or DocuSign link — those can't be fetched, and it'll be left guessing from the name. If the deck lives in one of those, download it and attach the real PDF (or just give the website / company name).

Design decisions

  • Every deal is written. In scope → Sourced (fully scored); out of scope → Passed (recorded with a short reason, no score). Nothing that crosses the desk is lost.
  • It won't re-score a deal you've already moved forward. If a startup you re-send has already been advanced past Sourced — First/Second Call, Due Diligence, IC, Invested — or closed (Passed / Lost), it's left untouched. Only deals still sitting at Sourced get refreshed. Your funnel decisions are never overwritten by a re-submission.

The dealflow sample deck — u2v-dealflow-sample

What it does

Keeps the data-room sample deck fresh. Every two months it rebuilds a PowerPoint of representative startups — five per sector — and emails the finished .pptx to the team.

How it works

It runs on its own schedule — no email needed. Each edition it picks well-scored, recent, varied deals and fills a fixed PowerPoint template with their details (text only; the design never changes).

How to use it

Nothing to do — the deck lands in the team inbox roughly every two months. Tweak it and drop it in the data room. (An off-cycle edition can be triggered manually if you ever need one.)

Limitations

Only startups scored above the quality bar are eligible. A promising company that was never run through dealflow — or that scored below the bar — simply won't appear in the sample.

Design decisions

  • The PowerPoint template is never altered — only its text is filled in — so the deck always looks the way the team designed it.
  • It deliberately maximises variety across the five cards in each sector, so an edition shows range rather than five near-identical companies.

Building an LP's sharing pack — u2v-lp-share

What it does

For a named LP, produces two ready-to-use files: an Excel snapshot of every startup ever flagged for that LP, and an editable Word "what's new" briefing covering the deals added recently.

How it works

Inclusion is driven purely by the lp_relevance tag on each startup in Attio: a deal appears for an LP only if it's been flagged with that LP. (You set those flags through dealflow or directly in Attio.) Names resolve loosely — "Trumpf" finds "TRUMPF GmbH + Co. KG".

How to use it

"Can you send me the dealflow list for Precitec?"

"What's new for Trumpf since we last shared?"

Limitations

It is read-only — it never changes anything in Attio. And it only knows what's been flagged: if a startup isn't tagged for that LP in lp_relevance, it won't appear, however relevant it seems.

Design decisions

  • "New" is a rolling window (the last few weeks), with no memory of what was shared before. Run it twice, or have two people run it an hour apart, and everyone gets the identical document — never a confusing empty "second" one.

Finding deals for a prospective LP — u2v-lp-match

What it does

Given a prospective LP (a company name or link) or a sector, it returns a ranked shortlist of recent startups worth showing them, each with a one-line reason.

How it works

It researches the LP or sector, maps it to our deal areas, and proposes matches. It's the discovery counterpart to u2v-lp-share: lp-match suggests which deals to flag; a person then does the flagging.

How to use it

"We're speaking to Kion as a potential LP (kion.com) — what could we show them?"

"What deals do we have in warehouse logistics?"

Limitations

It only proposes — it writes nothing back and produces no files. For anything to actually reach the LP, someone still has to flag those deals (set lp_relevance, via dealflow or in Attio).

Design decisions

  • Recency is the filter, breadth is the safety net. It looks at deals from roughly the last two months (any stage), while casting a wide net across sectors so a relevant but oddly-tagged startup isn't missed.

Adding a new LP lead — u2v-lp-intake

What it does

Adds prospective LP leads to the Soft LPs U2V list in Attio — researched, de-duplicated, and written up with a note. It handles:

  • a single LP's website link;
  • a link plus named contacts to attach to that LP;
  • several LPs introduced in one email;
  • a PDF roster of many LPs at once;
  • "add this LP and then create a follow-up task on it" — it adds the LP first, then the task.

How it works

For each LP it de-duplicates on the company domain, researches it (category, sector, history), and writes or updates the Soft LPs entry plus a fresh note. New LPs are added with dealflow_sharing set to "No" — so they're on file, but you must deliberately opt them in before any dealflow is matched or shared with them (see dealflow).

How to use it

"New LP lead: https://kion.com — Jane Doe (jane@kion.com) is our contact."

"Please add these potential LPs — see the attached PDF list."

"Add this LP, then create a task for Sam to follow up next week."

Limitations

Send LP rosters as a PDF — an .xlsx attachment isn't picked up when it comes in by email.

Design decisions

  • It de-duplicates on the website domain only — never on a fuzzy name match — because wrongly merging two different LPs is worse than occasionally missing a duplicate.
  • On an existing LP it's conservative: it fills only empty fields, leaves your funnel stage alone, and never flips dealflow_sharing on its own.

Creating a follow-up task — u2v-lp-tasks

What it does

Creates a single follow-up task on an LP we already know, assigned to one or more team members, with a due date and a short description.

How it works

It finds the LP, resolves each assignee and the due date, and creates exactly one task (several assignees share the one task). If anything is missing or ambiguous, it asks a clarifying question rather than acting.

How to use it

"Create a task for Philipp to follow up with Precitec by Friday."

"Task for Acme Capital — Philipp and Johannes to follow up on their LOI, due next Friday."

Limitations

It never creates a new LP. If the company isn't already in Soft LPs U2V (or the name could match more than one), it asks instead of guessing — add the LP with u2v-lp-intake first.

Design decisions

  • It never guesses. A missing or ambiguous LP, an unrecognised name, or an unclear due date all get a clarifying reply before anything is written — you'll never get a task on the wrong LP or the wrong person.

The front door — u2v-dispatch

What it does

The shared inbox and router behind klaus@u2v.vc. It reads each email, works out which automation you need, runs it, and replies. It's the reason you only ever have to remember one address.

How it works

It checks you're on the team, classifies your request, runs the right automation, and replies with the result. If your email is missing something it needs — you asked to screen a deck but forgot to attach it — it writes back and asks, rather than guessing.

Limitations

  • Only U2V team senders are handled — a founder can't email Klaus directly; a teammate has to forward it.
  • It's not instant — it checks the inbox roughly every half hour.
  • It reads PDF attachments only.