U2V Automations

A small fleet of agentic automations that do real operating work for U2V — reading the shared inbox, scoring inbound startups, keeping Attio current, and preparing LP-facing material — with a human always able to step in.

This site explains the system two ways. Pick your entrance:

• U2V Team

  ---

  What these automations do for you today, the thinking behind them, and where they're going — in plain language, no code.

  Start here

• Technical

  ---

  A guided tour of the codebase: the design principles, the tools that run it, and a deep-dive on each automation — enough to find your way around the repo.

  Start here

The system in one picture

flowchart TD
    Inbox["📧 klaus@u2v.vc<br/>(one shared inbox)"] --> Dispatch
    Dispatch["<b>u2v-dispatch</b><br/>reads each email · an LLM classifies intent ·<br/>routes to a workflow · replies"]
    Dispatch -->|subprocess| Dealflow["u2v-dealflow"]
    Dispatch -->|subprocess| Share["u2v-lp-share"]
    Dispatch -->|subprocess| Match["u2v-lp-match"]
    Dispatch -->|subprocess| Intake["u2v-lp-intake"]
    Dispatch -->|subprocess| Tasks["u2v-lp-tasks"]
    Sample["u2v-dealflow-sample<br/><i>autonomous · scheduled</i>"] -.->|its own timer| Team["📎 emails the team"]
    Dealflow --> Attio[("Attio CRM")]
    Share --> Attio
    Match --> Attio
    Intake --> Attio
    Tasks --> Attio
    Sample --> Attio

There are two kinds of automation here: dispatcher-routed workflows that run in response to an email, and one autonomous, scheduled tool that runs on its own timer. Both are covered in the Technical section.

This documentation lives with the code

The site is built from the klaus-u2v/automations repo. Every automation also ships its own CLAUDE.md — so you can open the repo in Claude Code and ask it to explain any part in more depth than a page here goes.