> ## Documentation Index
> Fetch the complete documentation index at: https://guide.kello.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Kello brief templates: copy-paste emails by role

> Copy-paste Kello brief emails: a general template for any role, plus seven role templates from Founding Engineer to Plant Head.

These Kello brief templates are ready-to-send emails: a general template for any role, plus seven role-specific ones. Copy one, replace everything in square brackets, attach or link your JD (Job description: the document that describes the role.), and send it to [source@kello.ai](mailto:source@kello.ai). Kello confirms how it read the role within minutes.

> [!NOTE]
>
> These are illustrative templates, not real briefs. Replace everything in \[square brackets]. Delete any line that doesn't apply. Each role goes in its own email.

> [card] [General template](#general-template-for-any-role)

> [card] [Founding Engineer](#founding-engineer)

> [card] [Forward Deployed Engineer](#forward-deployed-engineer)

> [card] [ML Engineer](#ml-engineer)

> [card] [Head of SDR](#head-of-sdr)

> [card] [Product Marketing Manager](#product-marketing-manager)

> [card] [Finance Manager](#finance-manager)

> [card] [Plant Head](#plant-head)

## How do I use a template?

**1. Copy**

Copy the block for your role.

**2. Replace the placeholders**

Replace each `[placeholder]` with your details. Keep must-haves to the two or three that are truly firm.

**3. Paste or attach the JD**

Paste the JD text, or attach it. If you send a link, paste the key details too. No JD? The template on its own is enough to start, as long as it says what the person will do.

## General template for any role

Use this when your role isn't one of the seven below. It covers everything Kello asks about most, so the search can start without a question back.

```text General template wrap highlight={7-9,24-25} theme={null}
To: source@kello.ai
Cc: [hiring manager's email]
Subject: [Role title] – [Your company]

Role: [Title]
Company: [Your company], [your website]
Location: [City], [on-site / hybrid N days / remote + time zone]
Relocation: [open to people willing to relocate? yes / no]
Budget: [range, or "No fixed budget, use market rates"]
Experience: [N–M years]
Joining: [e.g. within 30 days]

Must-haves:
- [the two or three that are truly firm]
Nice-to-haves:
- [what helps but can bend]
Hire from: [companies or kinds of companies]
Avoid: [companies, segments or profile types]
People I'd hire in a heartbeat:
- [LinkedIn profile URL] – why: [one line on what makes them the template]
Already in our pipeline (don't contact): [names, or "none"]

JD (pasted below, PDF attached as backup):
Responsibilities:
- [what the person will do]
Requirements:
- [what they need to have]
```

* **Role and company in the subject** tell Kello which role the thread is about from the first line.
* **CC the hiring manager** so they're on the thread from the start.
* **Budget:** a range or "use market rates". Check the number with the hiring manager first.
* **Location, work setup and relocation** are, with budget, the details Kello asks about most.
* **Responsibilities** are required. A JD with only requirements can't start.
* **Pasted JD text** is the most reliable format. See [which JD formats work best](https://guide.kello.ai/kello/write-a-great-brief.md#which-jd-formats-work-best).

> [!WARNING]
>
> "Flexible" isn't a budget. Kello treats it as unanswered and asks again. Give a range, or say "no fixed budget, use market rates".

## Founding Engineer

```text Founding Engineer brief wrap theme={null}
To: source@kello.ai
Subject: Founding Engineer – [Your company]

JD: [attach, or link to the job post]
Company: [Your company], [your website]

Location: [City], [office days per week, or remote]
Budget: [salary range] plus [equity range]
Must-haves:
- Has built and shipped a product end to end at an early-stage startup
- Strong in [your core stack]
Nice-to-haves:
- Has been one of the first engineers at a company before
- Open-source code or side projects we can look at
Hire from: [companies or kinds of companies you admire]
Avoid: [companies you don't want to hire from]
People I'd hire in a heartbeat:
- [LinkedIn profile URL]
- [LinkedIn profile URL]
```

* **"Has built and shipped… end to end"** tells Kello to look at what people actually worked on, not just titles.
* **Open-source code** lets Kello look at public work, since this role calls for it. Missing accounts are never held against anyone.
* **Your website** helps Kello read the right company if your name is shared with others.

## Forward Deployed Engineer

```text Forward Deployed Engineer brief wrap theme={null}
To: source@kello.ai
Subject: Forward Deployed Engineer – [Your company]

JD: [attach, or link to the job post]
Company: [Your company], [your website]

Location: [City], [days on-site with customers per week]
Budget: [salary range]
Must-haves:
- Writes production code and has deployed software inside customer environments
- Comfortable working directly with [customer type, e.g. enterprise IT teams]
Nice-to-haves:
- Has built on LLMs or AI products
- Startup experience
Avoid: [companies you don't want to hire from]
People I'd hire in a heartbeat:
- [LinkedIn profile URL]
- [LinkedIn profile URL]
```

* Kello has function-specific reading for forward-deployed engineers, so naming both halves of the job (code and customers) matters.
* **On-site days** can narrow the search. Say whether they're firm, so Kello knows if they can bend when few people fit.

## ML Engineer

```text ML Engineer brief wrap theme={null}
To: source@kello.ai
Subject: ML Engineer – [Your company]

JD: [attach, or link to the job post]
Company: [Your company], [your website]

Location: [City, or remote within your region]
Budget: [salary range]
Must-haves:
- Has trained and deployed models in production
- Experience with [your model type or domain, e.g. ranking, speech, LLM fine-tuning]
Nice-to-haves:
- Published research
- Models or code we can look at publicly
Hire from: [companies or labs you admire]
People I'd hire in a heartbeat:
- [LinkedIn profile URL]
- [LinkedIn profile URL]
```

* **"In production"** separates people who shipped models from people who studied them.
* **Published research and public models** are nice-to-haves here, so Kello weighs them without leaving out people who don't have them.

## Head of SDR

```text Head of SDR brief wrap theme={null}
To: source@kello.ai
Subject: Head of SDR – [Your company]

JD: [attach, or link to the job post]
Company: [Your company], [your website]

Location: [City], [office days per week]
Budget: [base range] plus [variable range]
Must-haves:
- Has led a team of [N]+ SDRs
- Has sold into [segment, e.g. mid-market B2B SaaS] in [region]
Nice-to-haves:
- Has built an SDR team from scratch
Avoid: [companies you don't want to hire from]
People I'd hire in a heartbeat:
- [LinkedIn profile URL]
```

* For managers, Kello reads how the teams they led performed. **Team size** tells it what scale to look for.
* **Segment and region** keep the list to people who've sold to buyers like yours.

## Product Marketing Manager

```text Product Marketing Manager brief wrap theme={null}
To: source@kello.ai
Subject: Product Marketing Manager – [Your company]

JD: [attach, or link to the job post]
Company: [Your company], [your website]

Location: [City, or remote]
Budget: [salary range]
Must-haves:
- Has launched products to [B2B or B2C] buyers in [your category]
- Has worked closely with sales on positioning and messaging
Nice-to-haves:
- Experience at a company at our stage ([your stage, e.g. Series A])
Hire from: [companies whose marketing you admire]
People I'd hire in a heartbeat:
- [LinkedIn profile URL]
- [LinkedIn profile URL]
```

* **Company stage** matters. Kello reads the size and stage of each employer when the person joined and when they left.
* **Companies whose marketing you admire** gives Kello a concrete starting point beyond the JD.

## Finance Manager

```text Finance Manager brief wrap theme={null}
To: source@kello.ai
Subject: Finance Manager – [Your company]

JD: [attach, or link to the job post]
Company: [Your company], [your website]

Location: [City], [office days per week]
Budget: [salary range, or "No fixed budget, use market rates"]
Must-haves:
- [CA, CPA or equivalent]
- Has owned month-end close and audits at a company of [size]
Nice-to-haves:
- Experience in [your industry]
- Has supported a fundraise
Avoid: [companies you don't want to hire from]
```

* **"Owned"** tells Kello you want the person who ran the close, not someone who contributed to it.
* If you don't set a budget, Kello asks before searching. **"No fixed budget, use market rates"** answers that up front.

## Plant Head

```text Plant Head brief wrap theme={null}
To: source@kello.ai
Subject: Plant Head – [Your company]

JD: [attach, or link to the job post]
Company: [Your company], [your website]

Location: [Plant location]. Relocation: [yes/no]
Budget: [CTC range]
Must-haves:
- Has run a plant of [size, e.g. 500+ people] in [industry]
- Owned plant P&L
Nice-to-haves:
- Has set up a new plant from the ground up
Hire from: [companies or kinds of plants you admire]
Avoid: [companies you don't want to hire from]
```

CTC: cost to company, the total yearly pay package.

* For senior roles, Kello reads how each person's org performed. **Plant size and P\&L** tell it what scope to look for.
* Kello leaves out people for whom your role would be a step down, so a clear **scope and budget** keeps the list to people likely to say yes.

## Related

> [card] [Write a great brief](https://guide.kello.ai/kello/write-a-great-brief.md)
>
> What to add, with strong and weak examples.

> [card] [Quickstart](https://guide.kello.ai/kello/quickstart.md)
>
> What happens after you send.

Send your next role to [source@kello.ai](mailto:source@kello.ai).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.