Revision #1

9 hours ago — system via atlasclaw-cli. Seed ingest

Cover-letter signoff

Last paragraph + signature block for institutional proposal cover letters. Multiple variants depending on the relationship history with the funder.

Signature defaults

Proposal type	Default signatory
Major institutional ask ($250K+)	CEO (Brad Lips)
Mid-range institutional ask	CAO (Michael Harden)
Renewal proposals to existing funders	The relationship owner (varies)
Smaller / project-specific	Director of Development (Kameron Griffin)

The skill should ask the user to confirm signatory rather than infer one.

Final paragraph — new funder

[FILL: 2–3 sentences. Should: invite a conversation, name the contact person (usually Kameron Griffin or the assigned officer with email + phone), and express appreciation for the funder's time. Avoid self-congratulatory language. No "we look forward to partnering with you" — that presumes the partnership.]

Final paragraph — existing funder (renewal or new ask)

[FILL: 2–3 sentences. Reference the existing relationship explicitly ("Our partnership with [Foundation] since [year] has supported X"). Acknowledge the impact their prior support has had — concretely. Invite the next conversation.]

Final paragraph — declining renewal / hard pivot

[FILL: 2–3 sentences for situations where the relationship has cooled or the funder declined recently. Acknowledge the gap, articulate what has changed in Atlas's work that warrants reconsideration, leave the door open without pressure.]

Signature block format

Sincerely,


[Signatory Name]
[Signatory Title]
Atlas Network
[Direct phone]
[Direct email]

Don'ts

Don't sign off with "Best" or "Warm regards" in institutional proposals — too casual.
Don't include cell numbers unless the signatory normally publishes one.
Don't repeat the ask amount in the signoff — it's redundant and reads as nervous.

Last reviewed

FILL: Michael Harden, date

Line diff vs current

Current	Revision #1
# Cover-letter signoff	# Cover-letter signoff

> Last paragraph + signature block for institutional proposal cover	> Last paragraph + signature block for institutional proposal cover
> letters. Multiple variants depending on the relationship history with	> letters. Multiple variants depending on the relationship history with
> the funder.	> the funder.

## Signature defaults	## Signature defaults

\| Proposal type \| Default signatory \|	\| Proposal type \| Default signatory \|
\|---\|---\|	\|---\|---\|
\| Major institutional ask ($250K+) \| CEO (Brad Lips) \|	\| Major institutional ask ($250K+) \| CEO (Brad Lips) \|
\| Mid-range institutional ask \| CAO (Michael Harden) \|	\| Mid-range institutional ask \| CAO (Michael Harden) \|
\| Renewal proposals to existing funders \| The relationship owner (varies) \|	\| Renewal proposals to existing funders \| The relationship owner (varies) \|
\| Smaller / project-specific \| Director of Development (Kameron Griffin) \|	\| Smaller / project-specific \| Director of Development (Kameron Griffin) \|

The skill should ask the user to confirm signatory rather than infer one.	The skill should ask the user to confirm signatory rather than infer one.

## Final paragraph — new funder	## Final paragraph — new funder

`[FILL: 2–3 sentences. Should: invite a conversation, name the contact	`[FILL: 2–3 sentences. Should: invite a conversation, name the contact
person (usually Kameron Griffin or the assigned officer with email +	person (usually Kameron Griffin or the assigned officer with email +
phone), and express appreciation for the funder's time. Avoid	phone), and express appreciation for the funder's time. Avoid
self-congratulatory language. No "we look forward to partnering with you"	self-congratulatory language. No "we look forward to partnering with you"
— that presumes the partnership.]`	— that presumes the partnership.]`

## Final paragraph — existing funder (renewal or new ask)	## Final paragraph — existing funder (renewal or new ask)

`[FILL: 2–3 sentences. Reference the existing relationship explicitly	`[FILL: 2–3 sentences. Reference the existing relationship explicitly
("Our partnership with [Foundation] since [year] has supported X").	("Our partnership with [Foundation] since [year] has supported X").
Acknowledge the impact their prior support has had — concretely. Invite	Acknowledge the impact their prior support has had — concretely. Invite
the next conversation.]`	the next conversation.]`

## Final paragraph — declining renewal / hard pivot	## Final paragraph — declining renewal / hard pivot

`[FILL: 2–3 sentences for situations where the relationship has cooled	`[FILL: 2–3 sentences for situations where the relationship has cooled
or the funder declined recently. Acknowledge the gap, articulate what	or the funder declined recently. Acknowledge the gap, articulate what
has changed in Atlas's work that warrants reconsideration, leave the	has changed in Atlas's work that warrants reconsideration, leave the
door open without pressure.]`	door open without pressure.]`

## Signature block format	## Signature block format

```	```
Sincerely,	Sincerely,


[Signatory Name]	[Signatory Name]
[Signatory Title]	[Signatory Title]
Atlas Network	Atlas Network
[Direct phone]	[Direct phone]
[Direct email]	[Direct email]
```	```

## Don'ts	## Don'ts

- Don't sign off with "Best" or "Warm regards" in institutional	- Don't sign off with "Best" or "Warm regards" in institutional
proposals — too casual.	proposals — too casual.
- Don't include cell numbers unless the signatory normally publishes one.	- Don't include cell numbers unless the signatory normally publishes one.
- Don't repeat the ask amount in the signoff — it's redundant and reads	- Don't repeat the ask amount in the signoff — it's redundant and reads
as nervous.	as nervous.

## Last reviewed	## Last reviewed

`[FILL: Michael Harden, date]`	`[FILL: Michael Harden, date]`