Write a feature rejection response

Description

You're saying no to a feature request from a major customer or a senior stakeholder. The default email sounds dismissive. This writes a rejection that acknowledges the need, explains the decision, offers alternatives, and preserves the relationship.

You are writing a feature rejection response to {{requester_role}} who asked for {{feature_request}}. My context: {{context}}.

## Structure

### 1. Acknowledgment (1-2 sentences)
Show you understood the underlying need — not just the feature asked for.

### 2. Our current thinking (1 paragraph)
Why we're not building this right now. Be specific: strategy fit, capacity, evidence, timing.

### 3. What we are building instead (1 paragraph)
Name the adjacent work that addresses the same need, if any. If none, say so honestly.

### 4. Alternatives (2-3 bullets)
Workarounds or third-party options that address their immediate pain.

### 5. Revisit trigger (1 sentence)
What would have to be true for us to reconsider.

### 6. Thank you (1 sentence)
Specific appreciation, not generic.

## Tone rules
- Don't over-apologize
- Don't blame "priority"
- Don't promise vague future consideration without a trigger

## Output
1. Full rejection response
2. The alternative phrasing if the requester is a top-10 customer
3. The one sentence most likely to feel dismissive — and the rewrite
4. The follow-up we should schedule in 90 days

Customize This Prompt