# Outreach examples

Reference for the `vamo-outreach` skill. The people, projects, companies and roles are invented.

## The role, written once

From a job description the sender pasted, confirmed with the sender:

- **One-line pitch:** "We're building a voice assistant that answers the phone for clinics."
- **The work:** the real-time audio pipeline. The hard part is replying within 300 ms while
  people talk over each other.
- **Three reasons to care:** seed stage with a small team, the pipeline is this hire's to own,
  the founders built voice systems before.
- **Facts:** senior engineer, remote in the US, Rust and Python.
- **The ask:** a 20 minute call with the founder.
- **The sender:** `<sender>`, founder, `<company>`, with a LinkedIn link.

## 1. They built something close to the role

**Read.** `<login>` owns `<project>`, a streaming speech pipeline. The README describes dropping
stale audio when the speaker changes. Active last month.

> Subject: interruptions in `<project>`
>
> Hi `<first name>`, `<project>` (`<link>`) drops stale audio as soon as the speaker changes,
> which is the problem we spend most of our time on. I'm `<sender>`, founder of `<company>`.
> We're building a voice assistant that answers the phone for clinics, and keeping replies under
> 300 ms through interruptions is the job. Open to a 20 minute call next week?

60 words. Opens on the repository.

## 2. They contribute, but do not own

**Read.** `<login>` has many merged changes to `<project>`, a widely used audio library, mostly
in the buffering code. They own no related repository.

> Subject: buffering in `<project>`
>
> Hi `<first name>`, I've been reading your changes to the buffering code in `<project>`
> (`<link>`). I'm `<sender>`, founder of `<company>`. We're building a voice assistant for
> clinics, and our hardest problem is the same one: audio arriving late and out of order while
> people interrupt. Would a 20 minute call next week work?

53 words. Opens on how they worked on it, and says "your changes to" instead of "you built".

## 3. Nothing they built relates to the role

**Read.** Strong standing, but every owned repository is a web app or a course exercise.

**Output.** No row. Note for the sender: "No work related to the role to open with. Leave out, or
write from the role side without a line about their work."

## Follow-ups for example 1

Follow-up 1, four days later:

> `<first name>`, one more detail: you would own the audio pipeline end to end, and work with a
> founder who built the voice system at their last company. Still open to a short call?

Follow-up 2, a week after that:

> I'll leave it here and won't write again. If real-time voice is ever something you want to
> work on full time, my inbox is open.

## A reply

Candidate: "Thanks, but I'm not looking to leave right now. What's the comp range?"

> Thanks for answering. The range is `<range from the sender>` plus equity. No pressure on timing.
> If it ever makes sense to talk, the offer stands.

The question is answered first, in two sentences, and the reply respects the "not now".