---
name: professional-thank-you
description: |
  Writes professional thank-you messages for interviews, meetings, referrals,
  and business interactions that strengthen relationships through specific
  acknowledgment and genuine appreciation. Use when the user needs to thank
  someone in a professional context. Do NOT use for general professional emails
  (use `professional-email`), business letters (use `business-letter`), or
  meeting follow-ups that are primarily about action items (use `meeting-notes`).
license: Apache-2.0
metadata:
  author: foundry-skills
  version: "1.0.0"
  tags: "writing email personal-communication"
  category: "writing"
  subcategory: "business-writing"
  depends: ""
  disclaimer: "none"
  difficulty: "beginner"
---
# Professional Thank You

## When to Use

Use this skill when the user's primary goal is expressing professional gratitude to strengthen a relationship, acknowledge a specific contribution, or close a meaningful professional loop.

**Use this skill when:**
- The user needs to write a post-interview thank-you to one or more interviewers within the critical 24-hour window
- The user wants to thank someone who made a referral, warm introduction, or wrote a recommendation letter on their behalf
- The user needs to thank a mentor, advisor, or senior colleague after receiving substantive career guidance
- The user wants to acknowledge a client, vendor, or partner after a significant milestone -- a deal close, a successful project delivery, a renewal, or a long-term relationship anniversary
- The user needs to thank a speaker, panelist, or event host for sharing their expertise or creating an opportunity
- The user wants to thank a colleague who went beyond their formal responsibilities to support a project, cover during a difficult period, or advocate for them internally
- The user needs to follow up on a referral outcome -- whether the referral led to an offer, an ongoing process, or a rejection -- to close the loop with the person who vouched for them

**Do NOT use this skill when:**
- The user's email has a primary purpose beyond gratitude -- requesting a meeting, sending a proposal, or sharing deliverables -- even if it opens with thanks (use `professional-email` instead)
- The user is writing a formal letter on company letterhead acknowledging a business partner or vendor for institutional purposes (use `business-letter` instead)
- The user's primary goal is capturing decisions, action items, and next steps from a meeting that happens to include a brief thanks (use `meeting-notes` instead)
- The user is writing a customer appreciation campaign, loyalty email, or bulk outreach designed to retain customers at scale (this is marketing copy, not personal communication -- use a copywriting skill)
- The user is writing a performance review or peer feedback that acknowledges contributions (that is a structured evaluation, not a thank-you)
- The user needs to write a resignation letter that expresses gratitude for the opportunity (the gratitude is embedded in a different primary document type)
- The user wants to thank a large group or company through a social post or public acknowledgment (this is a public communication, not a personal thank-you)

---

## Process

### Step 1: Gather the essential context

Before writing a single word, collect the four pillars of an effective professional thank-you. If the user has not provided them, ask directly and specifically.

- **Who:** The recipient's full name, title, and relationship to the user. A thank-you to a peer differs in tone and length from one to a C-suite executive or a hiring manager above the user's level.
- **What:** The specific action, event, or contribution being acknowledged. Vague inputs ("they were helpful in the meeting") produce vague thank-yous. Push for specifics: "What exactly did they do or say that you want to acknowledge?"
- **When:** The date of the interaction. If more than 48 hours have passed since an interview or meeting, acknowledge this lightly in the message. If more than a week has passed, the message must work harder to justify the timing.
- **Delivery method:** Email, handwritten card, LinkedIn message, or a brief spoken acknowledgment followed by a written one. The delivery channel determines length, formality, and tone.
- **Relationship stage:** First interaction, developing relationship, or established long-term relationship. First-interaction thank-yous should be shorter and more formal. Long-term relationship thank-yous can be warmer and more personal.

If the user cannot recall a single specific detail from the interaction, help them recover one with prompts: "What did they say that surprised you?" / "What would you have missed if they had not been in the room?" / "What is one thing they did that nobody else could have done?"

---

### Step 2: Diagnose the thank-you type and apply the correct framework

Each professional thank-you type has a distinct structural emphasis. Applying the wrong emphasis to the wrong type produces a message that feels off-key even when technically polished.

**Post-interview thank-you** -- Primary goal: advance the candidacy while building rapport.
- Structure: Gratitude (1 sentence) + Specific callback to a technical or substantive discussion point (2-3 sentences) + Reaffirmation of interest and fit without restating the resume (1-2 sentences) + Forward close (1 sentence)
- The specific callback is load-bearing. It proves the candidate was engaged, not just polite. It also gives the hiring manager a concrete memory anchor when comparing candidates.
- For technical roles, reference a technical insight or problem framing from the conversation. For business roles, reference a strategic challenge or market observation. Never reference small talk.

**Referral or introduction thank-you** -- Primary goal: honor the social capital the referrer spent and close the loop.
- Structure: Gratitude that names the specific referral (1 sentence) + Acknowledgment that they put their reputation on the line (1 sentence, implicit or explicit) + Status update so they are not left wondering (1-2 sentences) + Forward momentum (1 sentence)
- Critical nuance: When someone refers you, they are spending social capital they built over years. Acknowledging this -- even subtly -- shows emotional intelligence. "I know introductions carry weight, and I don't take it lightly" is more meaningful than "Thanks for connecting us."
- Always close the referral loop regardless of outcome. If the referral led to a rejection, send the thank-you anyway. Silence reads as ingratitude.

**Mentorship or advice thank-you** -- Primary goal: demonstrate that the advice landed, validate the mentor's investment of time, and keep the relationship active.
- Structure: Gratitude for the specific time and attention (1 sentence) + Reference the specific advice or insight they shared (1-2 sentences) + Explain concretely how you plan to use it or have already used it (1-2 sentences) + Invitation to continue the relationship (1 sentence)
- Mentors give advice to many people. The ones who report back on how the advice played out are rare. Closing this loop is one of the strongest relationship-building actions a professional can take.

**Client or partner acknowledgment** -- Primary goal: personalize the business relationship, acknowledge the human behind the contract.
- Structure: Reference the specific milestone or contribution (1 sentence) + Name what made the partnership work (1-2 sentences with a specific example) + Express genuine regard (1 sentence) + Forward-looking statement about the relationship (1 sentence)
- Avoid corporate language like "valued partnership" or "mutually beneficial relationship." These phrases are present in every vendor email and signal that this is a template, not a real message.

**Event or speaking opportunity thank-you** -- Primary goal: acknowledge the opportunity, demonstrate you took it seriously, offer reciprocity.
- Structure: Thank them for the specific opportunity (1 sentence) + Reference one specific insight from their remarks or one outcome from the event (1-2 sentences) + Offer a way to reciprocate or continue the conversation (1 sentence)

---

### Step 3: Identify the specific detail that will make the message irreplaceable

This is the most important editorial decision in the entire thank-you. A professional thank-you without a specific, recognizable detail is indistinguishable from a template. A single well-chosen specific detail transforms a polite formality into a genuine human moment.

What makes a detail work:
- It is something only someone who was in the conversation would know
- It is something the recipient said, decided, or did -- not a generic observation about their company or role
- It has a clear connection to why it mattered to the sender

Types of specifics that work well:
- A counter-intuitive opinion the person shared ("Your point about not optimizing the checkout flow until retention was above 40% changed how I'm thinking about our own prioritization")
- A decision or recommendation they made that had a direct consequence ("The introduction you made to Sarah led directly to the partnership conversation we had last week")
- A moment of candor or generosity ("When you told me the team rejected the same idea three years ago and why, it saved me from making the same pitch with the same gaps")
- A technical or strategic insight that was non-obvious ("The framing of customer churn as a product failure rather than a sales failure -- I had never heard it stated that clearly")

What to avoid:
- Generic positive adjectives: "insightful," "valuable," "inspiring" -- these appear in every thank-you and mean nothing
- Compliments about their title or reputation ("given your impressive background")
- References to things they did not actually say or do in this interaction ("your passion for innovation")

---

### Step 4: Calibrate length, tone, and formality

Professional thank-yous should be short. The most common mistake is writing too much, which dilutes impact and signals that the writer values their own words more than the recipient's time.

**Length guidelines:**
- Email thank-you in most professional contexts: 80-130 words. Never exceed 150 words unless the situation is genuinely exceptional (a major favor, a long mentorship engagement, a career-defining introduction).
- LinkedIn message thank-you: 40-70 words. LinkedIn is a higher-noise environment. Shorter messages command more attention.
- Handwritten note: 3-5 sentences, filling roughly half to two-thirds of one side of a note card. A note that fills the card completely reads as excessive. A single sentence reads as perfunctory.
- Thank-you text (for close professional relationships where texting is established): 1-3 sentences.

**Tone calibration:**
- First interaction with someone senior: Formal, precise, no contractions. "I appreciate" not "I really appreciated."
- Ongoing peer relationship: Conversational but professional. Contractions are fine.
- Mentor who knows the user well: Warm and direct. First name in the salutation.
- Client who maintains formal communication norms: Match their register exactly. If their emails are formal, the thank-you should be formal.

**Formality signals to watch:**
- Does the recipient sign their emails with their first name or full name? Match it.
- Have they used casual language or humor in prior communication? A slightly warmer tone is appropriate.
- Is this their first interaction? Default to formal regardless of the recipient's perceived approachability.

---

### Step 5: Write the subject line with precision

The subject line is read before the message and determines whether the message gets opened promptly or deferred. "Thank you" as a subject line is the weakest possible choice -- it is vague, offers no context, and competes with dozens of other emails for attention.

**Effective subject line structures:**
- "Thank you for the [specific topic] conversation, [First Name]" -- works for interviews and advice meetings
- "Thank you -- [brief context]" -- works when the conversation topic is not easily summarized
- "Following up -- and a thank you" -- works when the thank-you accompanies a brief status update
- "Grateful for the introduction to [Name]" -- works for referral thank-yous
- "[Recipient's company + specific milestone] -- thank you" -- works for client acknowledgments

**Subject line rules:**
- Always include enough context that the recipient knows what the email is about before opening it
- Avoid "Quick thank you" -- the word "quick" signals that the message is low-effort
- For post-interview thank-yous, including the recipient's first name in the subject line increases open rates in email environments where the sender name is not immediately visible
- Do not use all-caps or exclamation points in professional subject lines

---

### Step 6: Draft, then apply the four-point quality check

After drafting the message, run it through four specific quality checks before delivering it to the user.

**Check 1 -- The replacement test.** Could this exact message be sent to a different person about a different interaction without changing more than the name? If yes, it is not specific enough. Find and strengthen the specific detail.

**Check 2 -- The focus test.** Count the number of sentences focused on the recipient versus the number focused on the sender. The ratio should be at least 2:1 in favor of the recipient. If the message is primarily about the sender's experience or feelings, rebalance it.

**Check 3 -- The momentum test.** Does the message end with a clear forward-looking statement? A thank-you that ends only with gratitude leaves the relationship static. Every professional thank-you should include a gesture toward the future -- next steps, a reciprocity offer, or an expression of continued relationship.

**Check 4 -- The timing note.** If the message is being sent more than 48 hours after an interview or 72 hours after a professional meeting, the user should briefly acknowledge the delay without over-explaining it. One phrase is sufficient: "I've been reflecting on our conversation" signals intentionality rather than forgetfulness.

---

### Step 7: Select and recommend the optimal delivery method

The delivery method is a signal in itself. Choosing the right one amplifies the message; choosing the wrong one can undercut it.

**Email:**
- Standard for interviews, most business meetings, referral follow-ups, and client acknowledgments
- Advantage: Immediate, searchable, creates a written record
- Timing: Send within 24 hours for interviews; within 48 hours for other professional interactions

**Handwritten note (mailed or hand-delivered):**
- Appropriate for: major personal favors, career-defining introductions, significant mentorship over time, major client milestones, situations where the relationship is deeply personal
- Advantage: Physically differentiated from digital communication; perceived as requiring meaningful effort; more likely to be kept
- Timing: Must be mailed within 2 business days or the timing advantage is lost
- Format: Professional note card, legible handwriting, blue or black ink. No branded or overly personal stationery in business contexts unless the relationship is very close.
- When to add email + handwritten: For genuinely significant gestures (a referral that led to a job offer, a mentor who shaped a career trajectory), send the email immediately and follow with a handwritten note. The two-channel approach signals exceptional appreciation.

**LinkedIn message:**
- Appropriate when: The relationship was initiated through LinkedIn, the recipient is not a regular email user for personal correspondence, or the interaction was at a public event where email exchange did not occur
- Avoid for: Formal business relationships, post-interview thank-yous to hiring managers at large companies (email is more professional in this context), sensitive relationship contexts
- Keep LinkedIn messages shorter than email equivalents -- the platform's interface and norms favor brevity

**In-person verbal acknowledgment + written follow-up:**
- For close colleagues and mentors, a genuine in-person thank-you immediately after the interaction, followed by a brief written note within 24 hours, is the strongest possible combination

---

### Step 8: Flag timing and advise on timing recovery if needed

Timing is the second most important variable after specificity. A thank-you sent 10 days after an interview is not just late -- it communicates disorganization, low interest, or both.

**Standard timing windows:**
- Post-interview: 24 hours maximum. Under 12 hours is ideal if the interview was in the morning.
- After a meeting, mentorship session, or event: 24-48 hours.
- After a referral leads to a concrete outcome (offer, interview, introduction call): Within 24 hours of learning the outcome.
- After a project milestone or deal close: Within the same business week.
- After a speaking event: Within 48 hours while the event is still fresh for the speaker.

**Timing recovery language:**
If the window has passed, do not ignore the delay or over-apologize. One genuine phrase is enough:
- "I've been sitting with our conversation and wanted to make sure my thanks reflected how much it actually meant to me."
- "I wanted to write something that did justice to how useful our conversation was -- I hope this reaches you later than ideal but more genuinely for it."
- Avoid: "Sorry for the late response" as a standalone opener -- it shifts focus to the sender's failure rather than the recipient's contribution.

---

## Output Format

Deliver the thank-you in the following structure. Adapt the format to the delivery method (email, LinkedIn, handwritten note) and annotate any optional elements.

---

```
DELIVERY METHOD: [Email / LinkedIn message / Handwritten note / LinkedIn + Email]
SEND BY: [Date and time recommendation, e.g., "Today by 5 PM" or "Within 24 hours"]

---

Subject: [Specific subject line -- not just "Thank you"]
         Example: "Thank you for the architecture conversation, David"
         Example: "Grateful for the introduction to the Meridian team"

---

[Salutation: First name for established relationships; "Dear [First Name]" for most professional contexts]

[Sentence 1 -- Gratitude anchor: Name exactly what you are thanking them for and when it happened.
One sentence. Specific verb: "walked me through," "introduced me to," "took the time to share."
Never open with "I just wanted to" or "I am reaching out."]

[Sentences 2-3 -- Specific callback: Reference the one detail from the interaction that stood out.
Explain what it meant or what it changed. This is the load-bearing section.
For interviews: a technical insight, a strategic framing, or a problem they articulated.
For mentorship: the specific advice and what you plan to do with it.
For referrals: what the introduction led to or what you valued about the connection.
Do not reference anything generic. If it could appear in any thank-you, rewrite it.]

[Sentence 4 -- Impact or forward close: Explain what their action made possible, or look forward
to the next step. For interviews: reaffirm interest without restating qualifications.
For mentorship: commit to a specific next action from their advice.
For referrals: update on the outcome and express the relationship's value.
For clients or partners: name what you are looking forward to together.]

[Sign-off: "Best regards," for formal; "With appreciation," for significant favors;
"Best," for established peer relationships; "Sincerely," for very formal contexts.
First name only for established relationships; full name for first interactions.]

---

WORD COUNT: [Actual count] / TARGET: [80-130 for email; 40-70 for LinkedIn; 3-5 sentences for note]

TIMING NOTE: [Any flag if the timing window is at risk, e.g., "Send today -- 24-hour interview window closes at 6 PM"]

OPTIONAL ADDITIONS: [Handwritten follow-up recommended: Yes / No, with rationale]
```

---

## Rules

1. **Every thank-you must pass the replacement test.** If the message could be sent, unchanged, to a different person about a different interaction, it is not ready. The specific detail section is not optional -- it is the difference between a message that builds a relationship and one that satisfies a social obligation.

2. **Never open with "I just wanted to" or "I am writing to."** Both constructions minimize the message before it starts. "I just wanted to thank you" signals that the sender is uncertain the thanks is warranted. Open directly: "Thank you for walking me through..." or "Your introduction to [Name] led directly to..."

3. **Never exceed 150 words in a standard professional email thank-you.** Length is often confused with sincerity. In professional contexts, brevity is the more powerful signal -- it respects the recipient's time and forces the writer to be precise. The only exceptions are career-defining mentorship acknowledgments and situations involving a major personal favor.

4. **Never write the same thank-you to multiple people at the same organization.** If the user interviewed with three people on the same team, each thank-you must reference a different specific moment. If any two messages are compared -- and they will be, in competitive hiring processes -- identical messages create the impression of a form letter and damage the candidacy.

5. **Always close with forward momentum.** A thank-you that ends only on gratitude leaves the relationship static. Every professional thank-you should gesture toward the future: the next conversation, a reciprocity offer, a follow-up on advice taken, or the next phase of the project. Even "I hope our paths cross again" is more effective than a cold close.

6. **Never use generic professional flattery.** Phrases like "your impressive background," "your wealth of experience," "what an inspiration you are," and "your passion for [field]" appear in thousands of thank-you emails every day and register as noise. The recipient has heard them all. Replace every generic compliment with something specific that happened in the actual interaction.

7. **The referral thank-you must always close the loop.** Whether the referral led to a job offer, a first interview, a rejection, or simply a useful conversation, the person who made the referral deserves a direct status update. Silence after a referral is one of the most common professional relationship mistakes. It forces the referrer to wonder and prevents them from vouching again in the future.

8. **Match the register of the relationship precisely.** A thank-you that is warmer than the established relationship feels presumptuous; one that is more formal than the relationship feels cold. Read prior communications from the recipient for tone signals -- contraction use, opener style, sign-off choice -- and mirror them.

9. **For post-interview thank-yous, reinforce fit without restating credentials.** The hiring manager has the resume. The thank-you is not the place to re-list accomplishments. Instead, connect a specific discussion point from the interview to the user's perspective or experience -- showing applied thinking rather than raw qualifications.

10. **Recommend a handwritten note for any interaction involving a significant personal favor, a career-defining introduction, or a long-term mentorship relationship.** In a world of instant digital communication, a physical note is a meaningful differentiator. It does not replace the email -- it follows it within 2 business days as a second signal of genuine appreciation.

11. **Never let the user send a thank-you for an interview after 48 hours without timing acknowledgment language.** Late thank-yous that pretend to be timely are worse than late thank-yous that are honest about their deliberateness. If more than 48 hours have passed, include one sentence that reframes the delay as reflection rather than neglect.

12. **Specificity in the subject line is non-negotiable.** "Thank you" as a subject line in a professional email is the written equivalent of a limp handshake. It signals low effort in the first element the recipient reads. Every subject line must include enough context to be instantly recognizable and clearly distinguished from other emails in the inbox.

---

## Edge Cases

### 1. Multiple interviewers at the same company
The user must send a separate, individualized thank-you to each interviewer. The messages cannot share the same specific callback section -- hiring teams compare notes, and identical messages expose the strategy immediately. Help the user identify one distinct moment, question, or insight from each individual conversation. If the user spoke to someone briefly and cannot recall a specific detail, a 2-sentence LinkedIn message acknowledging the brief conversation and expressing interest in learning more about their work is acceptable. Never pad a vague thank-you with made-up specifics.

### 2. The referral led to a rejection
Send the thank-you anyway -- within 24 hours of learning the outcome. The referrer put professional capital on the line regardless of the result, and silence after a rejection is worse than awkward. The message should: thank them for the introduction, note that the conversation was valuable even if the timing or fit was not right, and express interest in staying in touch. Do not dwell on the rejection or ask for the referrer's assessment of what went wrong -- that is a separate conversation for a closer relationship.

### 3. The user cannot remember a specific detail
Do not fabricate specifics. Instead, help the user recover one with structured prompts:
- "What is one thing they said that you had not considered before?"
- "What would have been missing from the meeting if they had not been there?"
- "Was there a question they asked that made you think differently about something?"
- "What did they decide, recommend, or share that had a direct consequence for you?"

If after prompting the user still cannot recall a concrete detail, advise them to write a brief, honest message that acknowledges the value of the interaction in general terms -- and to use this experience as a reminder to take notes immediately after professional interactions. A 2-3 sentence general thank-you is better than a fabricated specific one.

### 4. The relationship is complicated -- the person was not fully helpful, or there is underlying tension
Do not write a thank-you that is entirely disconnected from reality -- the disconnect will read as hollow. Help the user identify the genuine positive within a mixed interaction. Even in a difficult meeting, something productive usually happened: a clarification, a shared problem, a step forward. Acknowledge that genuinely and briefly. Do not overcorrect into excessive warmth. For situations involving real professional conflict, advise the user that a thank-you may not be appropriate and that a neutral follow-up (using `professional-email`) may better serve the relationship.

### 5. Thank-you for a group event or team effort
Never write a single group thank-you as the sole acknowledgment. A group message ("Thanks to the whole team!") is perceived as low-effort by every individual and builds no specific relationship with anyone. The correct approach: send a brief group acknowledgment via the appropriate channel (a team Slack message, a group email), and then send individual messages to the 2-3 people who made the most meaningful contributions, referencing specifically what each person did. This two-tier approach honors the group without sacrificing the relationship-building function of individual acknowledgment.

### 6. The thank-you is long overdue -- weeks or months later
A thank-you sent weeks after an interaction faces a credibility challenge -- it can feel like it was triggered by a desire for something rather than genuine gratitude. To overcome this, the message must: be explicit (but not over-apologetic) about the delay, anchor the gratitude to a specific recent outcome or realization that made the thanks feel urgent now, and be shorter rather than longer. A brief, genuine late thank-you is far better than none, but the user should not pretend the timing is normal.

### 7. Thank-you via LinkedIn for someone the user has not met before
LinkedIn thank-yous to strangers require extra care. The message must immediately establish context (where the interaction occurred, what they shared), be very brief (under 60 words), and avoid any language that could read as a pitch or connection request wrapped in gratitude. The goal is to acknowledge a specific value received -- a public post, a presentation, a podcast appearance -- and express it genuinely without creating an obligation for the recipient to respond.

### 8. Thank-you after the user made a mistake in the interaction
If the interaction being thanked also involved an error by the user -- a fumbled interview question, a miscommunication in a meeting, a technical mistake during a presentation -- the thank-you is not the place to address or relitigate the error. Do not reference it, apologize for it, or explain it in the thank-you. The thank-you should focus entirely on what was positive. If an apology or correction is genuinely needed, handle it in a separate, prior communication, then send the thank-you once the issue is resolved.

---

## Example

**User input:** "I need a thank-you email to send to Marcus Webb, the Head of Product at a Series B fintech company. I had a final-round interview yesterday for a Senior Product Manager role focused on their lending product. We spent a lot of time talking about how they're handling credit risk scoring for thin-file borrowers and the tradeoffs between ML-based models and traditional FICO underwriting. I mentioned my experience building a cash-flow-based underwriting model at my last company. I'm really interested in this role."

---

**Assessment before writing:**
- Type: Post-interview thank-you, final round -- high stakes, 24-hour window in effect
- Recipient: Head of Product, senior but likely accessible; "Dear Marcus" is appropriate
- Specific detail: The thin-file borrower credit risk discussion -- specifically the ML vs. FICO tradeoff -- is the load-bearing callback. The user's cash-flow model experience is the connection point.
- Fit reinforcement opportunity: Connect the cash-flow underwriting experience directly to the thin-file problem without restating the resume bullet
- Length target: 110-130 words (final-round, senior stakeholder -- slightly more depth is appropriate)
- Timing: Yesterday's interview; send today

---

**Output:**

```
DELIVERY METHOD: Email
SEND BY: Today, within 24 hours of the interview

---

Subject: Thank you for the credit risk conversation, Marcus

Dear Marcus,

Thank you for the time you spent walking me through your approach to thin-file underwriting yesterday -- it was one of the more substantive product conversations I've had in this search.

Your framing of the FICO vs. ML tradeoff as a question of explainability risk, not just predictive accuracy, clarified something I'd been thinking about imprecisely. At my previous company, we ran into exactly that wall when regulators asked us to justify adverse action notices on cash-flow-based decisions -- we had the signal but not the documentation framework. That tension is exactly what I want to be working on.

I'm genuinely excited about the role and the problem. I hope to hear about next steps soon.

Best regards,
[Name]

---

WORD COUNT: 127 / TARGET: 80-130 for email ✓
TIMING NOTE: Send today -- final-round interview was yesterday; 24-hour window closes tonight
OPTIONAL ADDITIONS: Handwritten note not required for first-contact interview stage; reassess if offer is extended
```

---

**Why this works:**

- **Subject line** names the specific topic ("credit risk conversation") and the recipient's first name -- it is instantly identifiable in Marcus's inbox
- **Opening sentence** names the exact topic (thin-file underwriting) and the timeframe (yesterday) -- no ambiguity, no filler
- **Specific callback** goes beyond "I enjoyed our conversation." The candidate surfaces a specific framing Marcus used -- explainability risk vs. predictive accuracy -- and demonstrates that they understood the distinction, not just heard the words
- **Fit reinforcement** connects the candidate's cash-flow underwriting experience directly to the problem Marcus's team is solving, without restating a resume bullet. It shows applied thinking: "here is a specific scenario where my experience meets your exact problem"
- **Forward close** reaffirms interest without being sycophantic and ends with a clear request for next steps -- gives Marcus a natural action to take
- **Length** is 127 words -- within the target window for a final-round senior stakeholder message
- **No generic language** -- "insightful conversation," "your impressive background," "I really appreciate your time" are all absent
