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

# Drafts and your writing voice

> How Deal Brain writes in your voice, and how to steer it when a draft doesn't sound like you.

Deal Brain drafts messages that sound like you, not like a template. Two things make that work: your **tone profile** and your **templates**.

## Your tone profile

Deal Brain builds a tone profile from your own sent email. It's a description of how you write — sentence length, directness, greeting and sign-off habits, how you handle asks — not a set of canned phrases.

```text wrap theme={null}
Show me my writing tone profile. I want to check it still sounds like me.
```

It covers a prose style guide, structured breakdowns of your habits, and archetypes for different kinds of message.

<Note>
  The tone profile is empty until Deal Brain has analyzed enough of your sent mail. If it comes back blank, [connect Gmail](/integrations/google) and give it a little time.
</Note>

The tone profile captures **voice only** — how you say things. It deliberately doesn't capture what you say for a given situation. That's what templates are for.

## Templates

A template is a reusable structure for a recurring kind of message.

```text wrap theme={null}
Show me my available templates.
```

Every seller starts with five presets:

| Template            | Produces                                                |
| ------------------- | ------------------------------------------------------- |
| **Daily Brief**     | Your morning triage across active deals                 |
| **Daily Debrief**   | End-of-day retrospective and tomorrow's starting points |
| **Meeting Brief**   | Pre-meeting prep for a specific meeting                 |
| **Meeting Debrief** | Post-meeting takeaways, action items, and deal impact   |
| **Draft Message**   | A message on a deal, ghostwritten in your voice         |

### Scope

Templates resolve in priority order:

```
your own  →  your organization's  →  Deal Brain preset
```

If you've authored a personal version of a template, yours wins. Otherwise your org's version applies, and the preset is the fallback. This means an admin can standardize a team-wide format without stopping individuals customizing their own.

## Drafting a message

```text wrap theme={null}
Draft a follow-up to my most recent meeting with Acme in my voice. Use my tone profile and any relevant template.
```

Deal Brain pulls the deal state, stakeholders, relevant observations, your tone profile, and the matching template, then writes the draft for you to review.

Nothing sends automatically. Every draft is yours to edit first.

## Correcting a draft

Push back directly and ask for a rewrite. The more specific you are about what's off, the closer the next version lands:

```text wrap theme={null}
That draft is too formal. I don't open with "I hope this finds you well" and I keep paragraphs to two sentences. Rewrite it.
```

```text wrap theme={null}
Before drafting, show me my tone profile. I want to see whether it's picked up my internal writing style rather than how I write to customers.
```

<Note>
  Corrections apply to the conversation you're in. The tone profile is read-only — you can't edit it or save feedback to it, so repeat any standing preferences the next time you draft.
</Note>

## Working with drafts

```text wrap theme={null}
Show me my pending draft messages.
```

```text wrap theme={null}
Draft three versions of a re-engagement email to [Name]: one short, one medium, one with a specific ask.
```

```text wrap theme={null}
Rewrite that draft to reference the ROI numbers from last week's call, and keep it under 120 words.
```

## Tips

* **Name the template when you know it.** "Use my recap template" beats leaving it to inference.
* **Be specific when you push back.** "Too formal" gets you less than "drop the opener and keep paragraphs to two sentences." Corrections shape the rewrite in front of you, so state them each time you draft.
* **Org templates are the place for team standards.** If everyone's recap emails should include next steps and owner, put it in the org template rather than asking each rep to remember.