Quartz 5

TalentQuote-Outreach-Sequence-Library-v0.3

26 min read

TalentQuote Outreach Sequence Library v0.3

Version: 0.3
Status: Working Draft
Audience: Victoria, Douglas, Founder, TalentQuote Specialists, Growth, Sales
Primary Use: Copy-ready outbound messaging for LinkedIn, email, follow-up, reply handling, discovery call conversion, registration push, role availability replies, and field testing.

Purpose

This document helps TalentQuote move qualified buyers into the product experience through practical outbound copy.

This is not a strategy document.

This is not a sales playbook.

This is not a GTM plan.

The Revenue Engine defines the commercial model. This library provides outreach messages.

Governing Documents

This document should remain aligned with:

  • AI Documentation Workflow Standard v1.0.1
  • TQ_CONTEXT_PACK_v1.1
  • TalentQuote Revenue Engine Playbook v1.0
  • TalentQuote Canon v1.1.1
  • TalentQuote Website Copy Guide v1.0
  • TalentQuote Sales Brochure v2.4

Core Outreach Principle

The objective of outbound is not simply to generate meetings.

The objective of outbound is to move qualified accounts into the TalentQuote product experience.

Primary conversion goal:

Registered Account

Secondary conversion goal:

Discovery Call

Revenue conversion goal:

Talent Activation

Scale conversion goal:

Active Talent Assignment

CTA Hierarchy

Primary CTA:

Start Exploring Talent

Use when the buyer can enter the product directly.

Secondary CTA:

Book a Discovery Call

Use when the buyer needs explanation, trust, qualification, or help mapping a role.

Information CTA:

Send Sales Brochure

Use when the buyer asks for more information before registering or booking.

Positioning Rules

Always reinforce:

  • Engineering Capacity
  • Talent Activation
  • Instant Match
  • Verified Engineering Talent
  • Hiring Latency
  • Product Entry
  • Speed
  • Execution

Avoid:

  • Recruiting agency
  • Staffing
  • Outsourcing
  • Freelancers
  • Candidate database
  • Resume marketplace
  • Custom search
  • Body shop

Target Buyers

Primary outbound targets:

  • Founder / CEO
  • Technical Founder
  • CTO
  • VP Engineering
  • Head of Engineering
  • Engineering Manager
  • Product Leader

Primary ICP:

  • U.S.-based software startups
  • Series A as core
  • Seed with operational maturity
  • Technology SMBs and scaleups when aligned
  • Recently funded
  • Active roadmap pressure
  • Need engineering capacity quickly
  • Can accept a standardized process

Avoid:

  • Price-only buyers
  • Custom recruiting searches
  • Very long hiring loops
  • One-week project requests
  • Buyers requiring 4+ interview rounds
  • Companies refusing standardized process

Campaign Cadence Guidance

Keep cadence simple. Do not turn this into a full SDR playbook.

LinkedIn

  • Day 1: Connection request
  • Day 2-3 after accept: Follow-up 1
  • Day 5-7: Follow-up 2
  • Day 10-14: Discovery / product push
  • Day 21+: Breakup

Email

  • Day 1: Email 1
  • Day 3-4: Email 2
  • Day 7-10: Email 3
  • Day 14+: Breakup

Job-Post-Based Outreach Sequence - Actively Hiring Engineers

Best For

Companies with open engineering roles on LinkedIn, Wellfound, company careers pages, or public job boards.

Goal

Start Exploring Talent while internal hiring continues. Book a Discovery Call only if the buyer needs role mapping first.

Channel

LinkedIn and email.

Message 1

LinkedIn connection request:

Hi {{first_name}}, saw {{company}} is hiring for {{role}}.
 
TalentQuote may be useful if you want to explore available engineering talent while the internal process continues.
 
Thought it was worth connecting.

Email 1:

Subject: While {{company}} hires for {{role}}
 
Hi {{first_name}},
 
I noticed {{company}} has an open {{role}} role.
 
Internal hiring can keep moving. TalentQuote can act as a faster capacity layer when the role maps to available profiles and the roadmap needs help sooner.
 
Start Exploring Talent:
{{landing_url}}
 
Best,
{{sender_name}}

Message 2

LinkedIn follow-up 1:

Thanks for connecting, {{first_name}}.
 
Quick context: TalentQuote helps teams review available engineering profiles and request interviews through a standardized process.
 
It can be useful when a role is open but the team needs capacity before the hiring process finishes:
{{landing_url}}

Email 2:

Subject: Open roles and faster capacity
 
Hi {{first_name}},
 
Quick follow-up.
 
TalentQuote does not replace your hiring process. It gives your team another path to evaluate available engineering talent while open roles are still being filled.
 
If the {{role}} need is active, the fastest next step is to explore profiles:
{{landing_url}}
 
Best,
{{sender_name}}

Message 3

LinkedIn follow-up 2:

If the {{role}} role is still open, this may be worth a look.
 
TalentQuote works best when the need maps to an available category and your team wants to move from profile review to interview without a long search cycle.

Email 3:

Subject: Still hiring for {{role}}?
 
Hi {{first_name}},
 
If the {{role}} role is already covered, no problem.
 
If it is still open, TalentQuote may help your team review available profiles and request interviews while internal hiring continues.
 
Start Exploring Talent:
{{landing_url}}
 
Best,
{{sender_name}}

Optional Discovery Call Push

If you want to map the open role first, we can do a quick 15-minute fit check.
 
Goal is simple: confirm the role, category fit, and whether TalentQuote is useful right now.
 
Book a Discovery Call:
{{calendar_url}}

Breakup

LinkedIn breakup:

I will pause here.
 
If the role stays open longer than expected, TalentQuote may be useful as an additional path to interview-ready engineering capacity.

Email breakup:

Subject: Closing the loop on {{role}}
 
Hi {{first_name}},
 
I will close the loop here.
 
If the {{role}} role remains open and your team needs capacity sooner, TalentQuote may be useful as an additional path while internal hiring continues.
 
Start Exploring Talent:
{{landing_url}}
 
Best,
{{sender_name}}

LinkedIn Sequence - Recently Funded Startup

Best For

Recently funded Series A or mature Seed startups likely adding engineering capacity.

Goal

Registered Account first. Discovery Call only if the buyer needs help.

Channel

LinkedIn.

Message 1

Soft version:

Hi {{first_name}}, saw {{company}} recently raised. Congrats.
 
I work on TalentQuote - helping teams review available engineers faster when roadmap pressure picks up.
 
Thought it could be relevant to connect.

Direct version:

Hi {{first_name}}, congrats on the raise.
 
If {{company}} is adding engineers, TalentQuote lets teams review profiles and request interviews without starting a long recruiting cycle.
 
Worth connecting?

Founder-style version:

Hi {{first_name}}, congrats on the raise.
 
After funding, the hard part is usually turning roadmap plans into real delivery capacity fast enough.
 
Building something for that. Thought it was worth connecting.

Message 2

Thanks for connecting, {{first_name}}.
 
Quick context: TalentQuote helps teams browse available profiles, review fit, and request interviews through a clear process.
 
The fastest next step is usually to start exploring talent:
{{landing_url}}

Message 3

If engineering roles are already open, TalentQuote can be a faster capacity layer while internal hiring continues.
 
It is not a custom search.
 
It works best when the role maps to available verified talent.

Optional Discovery Call Push

If useful, we can do a quick 15-minute call.
 
Goal is simple: clarify the model, check fit, and map your role to available categories.
 
{{calendar_url}}

Breakup

I will pause here.
 
If capacity becomes a bottleneck later, TalentQuote may be useful.
 
Best first step is still to start exploring talent:
{{landing_url}}

LinkedIn Sequence - CTO / VP Engineering

Best For

Technical leaders hiring multiple engineers or feeling roadmap pressure.

Goal

Registered Account or Interview Request path.

Channel

LinkedIn.

Message 1

Soft version:

Hi {{first_name}}, noticed you lead engineering at {{company}}.
 
I work on TalentQuote - available engineering profiles teams can explore when they need capacity faster.
 
Thought it could be useful to connect.

Direct version:

Hi {{first_name}}, if {{company}} is adding engineers, TalentQuote may be relevant.
 
Teams can explore verified profiles and request interviews without opening a long sourcing cycle.
 
Worth connecting?

Founder-style version:

Hi {{first_name}}, engineering leaders keep telling us the issue is not talent scarcity. It is latency.
 
TalentQuote is built to reduce the time from need to interview.
 
Thought it was worth connecting.

Message 2

Thanks for connecting.
 
TalentQuote is built for teams that need engineers but do not want another long hiring loop.
 
Browse profiles, check fit, request interviews.
 
{{landing_url}}

Message 3

One important note: TalentQuote is not a resume marketplace.
 
Profiles are organized by role/category so teams can decide who is worth interviewing faster.
 
Useful if you are adding capacity this quarter.

Optional Discovery Call Push

If you want to map current roles first, we can do 15 minutes.
 
No long demo - just fit, categories, and next step.
 
{{calendar_url}}

Breakup

I will step back.
 
If hiring latency starts slowing delivery, TalentQuote may be useful as a faster way to review available engineers.

LinkedIn Sequence - Founder / CEO

Best For

Founders who care about runway, roadmap velocity, and execution speed.

Goal

Registered Account first. Discovery Call if the founder wants context.

Channel

LinkedIn.

Message 1

Soft version:

Hi {{first_name}}, saw what you are building at {{company}}.
 
I am working on TalentQuote - helping founders move from role need to interview faster.
 
Thought it could be relevant to connect.

Direct version:

Hi {{first_name}}, if roadmap velocity is tied to adding engineers, TalentQuote may help.
 
Teams can explore verified talent and request interviews faster than a traditional hiring cycle.
 
Worth connecting?

Founder-style version:

Hi {{first_name}}, founder to founder - hiring latency quietly burns roadmap time.
 
I am building TalentQuote to make engineering help easier to access and evaluate.
 
Thought it was worth connecting.

Message 2

Thanks for connecting.
 
The short version: TalentQuote helps teams explore profiles and move toward interviews without starting from a blank search.
 
Best first step:
{{landing_url}}

Message 3

If {{company}} is planning new product work, this may be useful before hiring becomes a bottleneck.
 
You can explore talent first.
 
No call needed unless you want help mapping roles.

Optional Discovery Call Push

Happy to do a quick intro if that is easier.
 
15 minutes, focused on fit and available categories.
 
{{calendar_url}}

Breakup

I will pause here.
 
If capacity becomes a constraint later, TalentQuote is built for faster movement from need to interview to activation.

Email Sequence - Recently Funded Startup

Best For

Recently funded companies with likely roadmap or hiring pressure.

Goal

Registered Account.

Channel

Email.

Message 1

Short version:

Subject: Engineering capacity after {{company}}'s raise
 
Hi {{first_name}},
 
Congrats on the recent raise.
 
If {{company}} is adding engineers, TalentQuote may be useful. Teams can review profiles and request interviews through a clear process.
 
Start Exploring Talent:
{{landing_url}}
 
Best,
{{sender_name}}

Standard version:

Subject: Faster engineering capacity for {{company}}
 
Hi {{first_name}},
 
Saw {{company}} recently raised / is scaling.
 
After funding, the challenge is often turning roadmap plans into delivery capacity fast enough.
 
TalentQuote helps software teams review available profiles, request interviews, and move toward activation without starting a long recruiting cycle.
 
You can start here:
{{landing_url}}
 
Best,
{{sender_name}}

Stronger pain version:

Subject: Roadmap pressure after the raise
 
Hi {{first_name}},
 
Funding creates momentum, but open engineering roles can slow the roadmap quickly.
 
TalentQuote is built for teams that need qualified engineering help faster than traditional hiring usually allows.
 
If useful, start by exploring available talent:
{{landing_url}}
 
Best,
{{sender_name}}

Message 2

Subject: Quick follow-up
 
Hi {{first_name}},
 
Quick follow-up.
 
TalentQuote is not a recruiting agency or resume marketplace. It is a way to review available engineering profiles and request interviews through a clear process.
 
If adding engineers is on the roadmap, this may be worth a look:
{{landing_url}}
 
Best,
{{sender_name}}

Message 3

Subject: Worth exploring?
 
Hi {{first_name}},
 
Last note from me.
 
If adding engineers is not a priority, no problem.
 
If open roles or slow interviews are delaying execution, TalentQuote may help you move from need to interview faster.
 
Start Exploring Talent:
{{landing_url}}
 
Best,
{{sender_name}}

Optional Discovery Call Push

Subject: Quick role mapping?
 
Hi {{first_name}},
 
If you would rather map the role first, we can do a short 15-minute discovery call.
 
The goal is to confirm fit and point you to the right talent categories.
 
{{calendar_url}}
 
Best,
{{sender_name}}

Breakup

Subject: Closing the loop
 
Hi {{first_name}},
 
I will close the loop here.
 
If engineering capacity becomes a priority later, the fastest first step is to explore available TalentQuote profiles:
{{landing_url}}
 
Best,
{{sender_name}}

Email Sequence - CTO / VP Engineering

Best For

Technical buyers evaluating quality, fit, and speed.

Goal

Registered Account or Discovery Call.

Channel

Email.

Message 1

Short version:

Subject: Engineering capacity for {{company}}
 
Hi {{first_name}},
 
I am reaching out because TalentQuote helps software teams review available profiles and request interviews faster.
 
If {{company}} is adding capacity, you can start here:
{{landing_url}}
 
Best,
{{sender_name}}

Standard version:

Subject: Reducing hiring latency for {{company}}
 
Hi {{first_name}},
 
For engineering teams, the painful part is often not just hiring. It is losing roadmap velocity while roles stay open.
 
TalentQuote helps teams browse engineers by category, review profiles, and request interviews through a clear process.
 
Start Exploring Talent:
{{landing_url}}
 
Best,
{{sender_name}}

Stronger pain version:

Subject: When hiring latency becomes roadmap latency
 
Hi {{first_name}},
 
Every week spent sourcing, screening, and coordinating interviews is a week the roadmap is under capacity.
 
TalentQuote helps teams explore relevant profiles and move to interviews faster when the role fits available categories.
 
Worth a look?
{{landing_url}}
 
Best,
{{sender_name}}

Message 2

Subject: Not a resume database
 
Hi {{first_name}},
 
One quick clarification: TalentQuote is not a resume database.
 
The goal is to make available engineers easier to evaluate, compare, and interview without creating a long hiring loop.
 
You can explore here:
{{landing_url}}
 
Best,
{{sender_name}}

Message 3

Subject: Should I send details?
 
Hi {{first_name}},
 
If {{company}} is actively hiring engineers, I can send a short overview or you can start exploring directly.
 
Best next step:
{{landing_url}}
 
Best,
{{sender_name}}

Optional Discovery Call Push

Subject: Quick fit check?
 
Hi {{first_name}},
 
If you want to map roles before exploring, we can do a short 15-minute call.
 
No long demo - just role fit, available categories, and next step.
 
{{calendar_url}}
 
Best,
{{sender_name}}

Breakup

Subject: Closing this out
 
Hi {{first_name}},
 
I will pause here.
 
If hiring latency starts slowing delivery, TalentQuote may be useful as a faster way to review available engineers.
 
Best,
{{sender_name}}

Email Sequence - Founder / CEO

Best For

Founders focused on runway, roadmap velocity, and speed of execution.

Goal

Registered Account first. Discovery Call if the founder wants context.

Channel

Email.

Message 1

Short version:

Subject: Engineering capacity without the hiring delay
 
Hi {{first_name}},
 
If {{company}} is adding engineers, TalentQuote may help you explore profiles and request interviews faster than a traditional hiring cycle.
 
Start Exploring Talent:
{{landing_url}}
 
Best,
{{sender_name}}

Standard version:

Subject: Your roadmap should not wait for hiring
 
Hi {{first_name}},
 
Most founders do not lose momentum because talent does not exist.
 
They lose momentum because talent takes too long to find, evaluate, interview, and activate.
 
TalentQuote helps teams explore profiles and move toward interviews through a clear process.
 
Start here:
{{landing_url}}
 
Best,
{{sender_name}}

Stronger pain version:

Subject: When hiring latency burns roadmap time
 
Hi {{first_name}},
 
Hiring latency quietly burns roadmap time, runway, and founder attention.
 
TalentQuote is built to help teams move from engineering need to profile review to interview faster.
 
If useful, start exploring here:
{{landing_url}}
 
Best,
{{sender_name}}

Message 2

Subject: Quick follow-up
 
Hi {{first_name}},
 
TalentQuote is not a recruiting agency.
 
It is a product-led way to explore available profiles and request interviews when the role maps to current categories.
 
Best next step:
{{landing_url}}
 
Best,
{{sender_name}}

Message 3

Subject: Worth a look?
 
Hi {{first_name}},
 
If adding engineers is not a bottleneck, timing may be wrong.
 
If roadmap commitments are ahead of current team capacity, TalentQuote may be worth a look.
 
{{landing_url}}
 
Best,
{{sender_name}}

Optional Discovery Call Push

Subject: 15-minute fit check?
 
Hi {{first_name}},
 
If easier, we can do 15 minutes to map your current roles to available TalentQuote categories.
 
{{calendar_url}}
 
Best,
{{sender_name}}

Breakup

Subject: Closing the loop
 
Hi {{first_name}},
 
I will pause here.
 
If capacity becomes a constraint later, TalentQuote may be useful as a faster path from need to interview.
 
Best,
{{sender_name}}

Trigger-Based Openers

Recently Funded Startup

LinkedIn opener:

Congrats on the raise. If {{company}} is turning that into product velocity, TalentQuote may be useful for reviewing available engineers faster.

Email opener:

Saw {{company}} recently raised. A common challenge after funding is adding delivery capacity fast enough to keep up with the roadmap.

Follow-up angle:

Funding creates momentum, but open engineering roles can slow execution quickly.

Currently Hiring Engineers

LinkedIn opener:

Saw {{company}} is hiring engineers. TalentQuote may be useful if you want to explore verified profiles while the hiring process runs.

Email opener:

I noticed {{company}} has open engineering roles. TalentQuote can work as a faster capacity layer when the role maps to available verified talent.

Follow-up angle:

Internal hiring can continue. TalentQuote is useful when the roadmap needs capacity sooner.

Founder Posting About Product Velocity / Roadmap Pressure

LinkedIn opener:

Saw your post about product velocity. TalentQuote is built for the moment when roadmap ambition needs engineering help faster.

Email opener:

Your recent post about product velocity stood out. TalentQuote helps teams review available profiles when execution speed depends on adding capacity.

Follow-up angle:

The issue is often not talent scarcity. It is how long activation takes.

CTO / VP Engineering Hiring Multiple Roles

LinkedIn opener:

Saw you are hiring across multiple engineering roles. TalentQuote may help you explore verified talent by category and move faster on interviews.

Email opener:

Noticed {{company}} is hiring multiple engineering roles. When several roles are open at once, hiring latency can quickly become roadmap latency.

Follow-up angle:

TalentQuote works best when the need maps to defined categories where verified talent is already available.

Warm Intro / Referral

LinkedIn opener:

{{referrer_name}} suggested I reach out. TalentQuote helps teams review available profiles and request interviews faster when capacity becomes urgent.

Email opener:

{{referrer_name}} suggested I reach out because {{company}} may be adding engineering capacity.

Follow-up angle:

Happy to keep this simple: explore available profiles first, or do 15 minutes if you want to map roles.

Qualification Reply Snippets

How does this work?

TalentQuote lets teams explore verified engineering profiles, request interviews, and activate talent through a clear process.
 
Best next step: Start Exploring Talent here:
{{landing_url}}

Do you have [role]?

Potentially. It depends on the exact role, seniority, and stack.
 
Best next step is to explore available profiles or share the role so we can map it to the closest category.

Role Availability Reply Snippets

Use these when a buyer asks, “Do you have X?”

Keep the answer short. Do not promise availability, pricing, or guaranteed fit.

Full-Stack TypeScript Engineer

Potentially. Full-stack TypeScript is one of the stronger fits for TalentQuote when the role maps to product engineering work.
 
Best next step is to Start Exploring Talent or share the stack so we can map it correctly.

Frontend Engineer

Potentially. Frontend can be a good fit when the need is clear on framework, seniority, and product scope.
 
Start Exploring Talent, or send the role details and we can map it to the closest category.

Backend Node.js Engineer

Potentially. Backend Node.js is often a clean category fit when the role is tied to product or platform work.
 
Best next step is to review available profiles or share the role requirements.

Backend Python Engineer

Potentially. Backend Python can fit depending on the product area, seniority, and data or API requirements.
 
Start Exploring Talent, or send the role so we can check the closest category.

Platform / DevOps Engineer

Potentially. Platform and DevOps fit best when the scope is defined around infrastructure, reliability, CI/CD, or cloud operations.
 
Share the role details or Start Exploring Talent to see whether the current profiles map well.

AI Engineer

Potentially. AI roles vary a lot, so we would want to understand whether the need is product AI, applied ML, LLM integration, or data infrastructure.
 
Best next step is to map the role before promising fit.

Data / Analytics Engineer

Potentially. Data and analytics roles can fit when the scope is clear around pipelines, analytics engineering, dashboards, or warehouse work.
 
Start Exploring Talent, or share the role so we can map it.

QA Automation Engineer

Potentially. QA automation can be a good fit when the team needs test automation, release confidence, or coverage around a product roadmap.
 
Best next step is to review available profiles or share the role details.

React Native Engineer

Potentially. React Native fit depends on mobile product scope, seniority, and whether the need is build, maintenance, or acceleration.
 
Start Exploring Talent, or send the role so we can map it.

Product Engineer

Potentially. Product engineers are often a strong fit when the team needs someone who can move across frontend, backend, and product execution.
 
Best next step is to explore profiles or share the product scope.

Backend Go Engineer

Potentially. Backend Go can fit when the need is clear around systems, APIs, infrastructure, or performance-sensitive backend work.
 
Share the role details or Start Exploring Talent to see whether available profiles map well.

What does it cost?

Pricing depends on role, seniority, and engagement structure.
 
Most engagements are monthly and full-time during Phase 1.
 
The best next step is to explore available profiles or map the role first.

Can I see profiles?

Yes. That is the best first step.
 
You can start exploring here:
{{landing_url}}

Is this full-time?

Phase 1 is mainly focused on full-time monthly engineering capacity.
 
If you have a specific role in mind, we can confirm whether it fits the current model.

Can we do part-time?

Phase 1 is mostly built around full-time monthly engagements.
 
Part-time may not be the best fit unless the role maps cleanly to an available profile and engagement structure.

Are they employees or contractors?

TalentQuote provides engineering capacity through a standardized engagement model.
 
The exact structure depends on the role and commercial setup, but the goal is fast, reliable access to verified talent.

How fast can someone start?

It depends on role fit, interview timing, commercial agreement, and availability.
 
The fastest path is to explore profiles, request interviews, and confirm fit quickly.

Is this like staffing?

No. TalentQuote is not a staffing agency.
 
It is built around verified engineering talent, product entry, profile exploration, and a standardized activation process.

Can you send info?

Yes. Here is the short overview:
{{sales_brochure_url}}
 
The fastest next step is still to start exploring available talent:
{{landing_url}}

Reply Handling

Interested

Great. Best next step is to start exploring available talent here:
{{landing_url}}
 
If you want help mapping the role first, you can book 15 minutes here:
{{calendar_url}}

Next step: Start Exploring Talent.

Send More Information

Absolutely. Here is the short overview:
{{sales_brochure_url}}
 
TalentQuote helps teams explore verified engineering talent, request interviews, and move toward activation through a standardized process.
 
Best next step after that:
{{landing_url}}

Next step: Send Sales Brochure.

Not Now

Totally understood.
 
I will pause here. If engineering capacity becomes a priority later, TalentQuote may be useful when you need to move from open roles to available engineers faster.

Next step: Pause / reconnect later.

Already Hiring Internally

Makes sense.
 
TalentQuote does not need to replace internal hiring. It can work as an additional capacity layer when the roadmap needs engineers sooner than the hiring process can deliver.
 
Worth exploring as a backup path?
{{landing_url}}

Next step: Start Exploring Talent.

Budget Concern

Understood.
 
TalentQuote is usually not the right fit for teams looking for the cheapest freelancer option.
 
It is built for teams that value speed, verified talent, and a standardized process.

Next step: Pause or map role if still qualified.

TalentQuote is intentionally not built around custom recruiting searches in Phase 1.
 
The model works best when your need maps to available verified talent categories.

Next step: Pause unless the role fits an existing category.

Wants Many Interviews

Totally understand wanting confidence.
 
TalentQuote works best with a focused process: usually 1 technical interview and 1 culture/team fit interview.
 
That keeps the path to activation fast.

Next step: Qualify process fit.

Asks For Pricing

Pricing depends on role, seniority, and engagement structure.
 
Most engagements are monthly and full-time during Phase 1.
 
Best next step is to map the role or explore available profiles first.

Next step: Start Exploring Talent or Book a Discovery Call.

Optional Follow-Up Channels

These are for warm opportunities only. Do not use SMS, WhatsApp, or phone as primary outbound channels.

SMS

Example 1:

Hi {{first_name}}, quick note from {{sender_name}} at TalentQuote. Sharing the direct link in case it is easier from here: {{landing_url}}

Example 2:

Hi {{first_name}}, thanks again for the interest. If the {{role}} need is still active, Start Exploring Talent here: {{landing_url}}

WhatsApp

Example 1:

Hi {{first_name}}, sending the TalentQuote link here as well so it is easy to find: {{landing_url}}

Example 2:

Hi {{first_name}}, if helpful, we can either map the role in 15 minutes or you can Start Exploring Talent directly: {{landing_url}}

Phone Introduction

Hi {{first_name}}, this is {{sender_name}} from TalentQuote. I will keep it brief. I am calling because you showed interest in exploring engineering talent, and I wanted to point you to the fastest next step or help map the role if needed.

Discovery Call Booking Messages

LinkedIn Booking Message

Happy to walk you through it.
 
It should only take 15 minutes.
 
Goal is fit, role mapping, and the right next step:
{{calendar_url}}

Email Booking Message

Hi {{first_name}},
 
Happy to set up a short intro.
 
The call is 15 minutes and focused on fit, available categories, and the best next step.
 
You can book here:
{{calendar_url}}
 
Best,
{{sender_name}}

Discovery Call Confirmation

Hi {{first_name}},
 
Thanks for booking.
 
We will keep it focused:
 
1. Current engineering capacity need
2. How TalentQuote works
3. Relevant talent categories
4. Best next step
 
Best,
{{sender_name}}

Post-Call Follow-Up

Hi {{first_name}},
 
Thanks for the conversation.
 
Based on what you shared, best next step is to explore available talent and decide whether there are profiles worth interviewing:
{{landing_url}}
 
Best,
{{sender_name}}

Registration Push Messages

After Interest But No Registration

Quick nudge with the direct link:
{{landing_url}}
 
Best next step is to create an account and start exploring available talent.

After Registration But No Action

Saw you created an account - great.
 
Next useful step is to explore available talent and favorite any profiles that look relevant.

After Profile Views But No Interview Request

Noticed you were exploring profiles.
 
If any profile looks close but you are unsure whether to interview, we can help you evaluate fit quickly.

After Interview Request

Thanks for requesting an interview.
 
The TalentQuote team will help coordinate the next step and confirm availability.
 
Recommended process: 1 technical interview and 1 culture/team fit interview.

Qualification Questions

Use these to qualify manually when needed.

Company Fit

  • What stage is the company currently in?
  • How large is the team today?
  • Is there an active product roadmap requiring engineering capacity?

Role Fit

  • What roles or stacks are you trying to add?
  • How many engineers do you need in the next 30-60 days?
  • Is this full-time capacity or a short-term project?

Process Fit

  • Are you comfortable with a standardized interview process?
  • Can you move forward with 1 technical interview and 1 culture/team fit interview?

Commercial Fit

  • Are you looking for monthly engineering capacity or a one-off freelance task?
  • Would a 3-month minimum engagement be workable if the profile fits?

Decision Fit

  • Who needs to be involved before requesting interviews or activating talent?
  • If you find the right profile, how quickly could you move forward?

Auto-Disqualifying Signals

Pause or decline if the prospect says:

  • We only need someone for one week.
  • We want the cheapest freelancer possible.
  • We need a custom search.
  • We need five interview rounds.
  • We require a long take-home assignment.
  • We do not want a standardized process.
  • We are not ready to define the role.
  • We do not have an active product or roadmap.
  • We do not have budget.

Recommended response:

Based on what you shared, TalentQuote may not be the right fit right now.
 
The model works best for teams that need verified engineering capacity, can move through a standardized process, and are ready to evaluate available talent quickly.

Do Not Say

Do not say:

  • We can find anyone.
  • We can hire in 24 hours.
  • We are a recruiting agency.
  • We are staffing.
  • We have unlimited candidates.
  • We can do any custom search.
  • We guarantee replacement immediately.
  • We are the cheapest option.
  • We can do 5 interview rounds.

Personalization Examples

Recent funding:

Congrats on the raise. Usually the next pressure point is turning that capital into product velocity.

Open engineering roles:

Saw {{company}} has a few engineering roles open. TalentQuote may help you explore verified profiles while hiring continues.

Product launch:

Saw the new launch. If the roadmap is expanding after this, TalentQuote may help with engineering capacity.

Hiring post:

Saw your post about hiring engineers. TalentQuote may be useful if you want a faster path to verified profiles.

VC portfolio:

Noticed {{company}} is in {{vc_name}}'s portfolio. We work best with teams that need to turn roadmap pressure into engineering capacity quickly.

Founder content:

Your post about execution speed stood out. TalentQuote is built around reducing talent activation latency.

CTO post:

Your post about engineering priorities stood out. If capacity becomes a constraint, TalentQuote may be relevant.

Tech stack match:

Saw {{company}} works with {{stack}}. TalentQuote has categories that may map to that kind of engineering need.

Sender Notes

Victoria

Use operational, clear, helpful language.

Best for:

  • LinkedIn outreach
  • Email outreach
  • Follow-ups
  • Discovery coordination
  • Qualification

Example:

Hi {{first_name}}, saw {{company}} is hiring engineers.
 
TalentQuote may help you explore verified profiles faster if the role maps to available categories.
 
Best first step:
{{landing_url}}

Douglas

Use commercial and strategic framing.

Best for:

  • Strategic opportunities
  • Commercial support
  • Escalations
  • Higher-value opportunities
  • Warm intros

Example:

Hi {{first_name}},
 
The commercial issue we usually see is not talent scarcity. It is the delay between need, evaluation, and activation.
 
TalentQuote is built to reduce that delay when the role fits available engineering capacity.

Founder

Use thesis-driven, founder-to-founder language.

Best for:

  • Strategic intros
  • Partnerships
  • Founder-to-founder messages
  • Thought leadership follow-up
  • VC / accelerator relationships

Example:

Hi {{first_name}}, founder to founder - engineering capacity is still too slow to activate.
 
TalentQuote is our attempt to make verified talent feel closer to software: easier to access, evaluate, and activate.

Personalization Tokens

Recommended variables:

{{first_name}}
{{company}}
{{role}}
{{recent_raise}}
{{trigger_event}}
{{stack}}
{{vc_name}}
{{referrer_name}}
{{landing_url}}
{{calendar_url}}
{{sales_brochure_url}}
{{sender_name}}

Outreach QA Checklist

Before sending, check:

  • Does this sound like TalentQuote, not a recruiting agency?
  • Is the CTA clear?
  • Is the message short enough?
  • Does it connect to engineering capacity?
  • Does it avoid overpromising?
  • Does it avoid “hire in 24 hours” language?
  • Does it avoid hourly pricing unless approved elsewhere?
  • Does it move the prospect toward registration, discovery, or interview?
  • Is the personalization real enough to justify the outreach?

Field Testing Suggestions

Keep testing lightweight. This is for message learning, not dashboard design.

Suggested tests:

  • Pain-led opener vs trigger-led opener
  • Product CTA vs Discovery CTA
  • Founder voice vs SDR voice

Suggested metrics:

  • Connection Acceptance Rate
  • Reply Rate
  • Registration Rate
  • Discovery Call Rate
  • Interview Request Rate

Testing principle:

Remove low-performing messages quickly and keep the versions that create qualified movement toward Start Exploring Talent, Book a Discovery Call, or interview requests.

Requirements Before v1.0

Do not approve this library as v1.0 until field evidence exists.

Minimum validation:

  • Victoria has tested the sequences in live outbound.
  • Douglas has reviewed tone and strategic fit.
  • Multiple LinkedIn and email variants have been tested.
  • Low-performing messages have been removed or rewritten.
  • Real reply data has been incorporated.
  • CTA performance has been compared across Start Exploring Talent, Book a Discovery Call, and Send Sales Brochure.
  • Role availability snippets have been used in real buyer replies.
  • Job-post-based outreach has been tested against active open engineering roles.

v1.0 should represent tested outbound execution, not more documentation.

What This Library Does Not Include

This document does not define:

  • ICP strategy
  • Revenue strategy
  • Content calendar
  • Website structure
  • Pricing policy
  • Replacement policy
  • CRM process

Those belong elsewhere.

This library is only for outbound execution.

Final Operating Principle

Do not sell recruiting.

Do not sell staffing.

Do not sell a candidate database.

Sell faster access to verified Engineering Capacity.

Outbound should create qualified movement toward:

Registered Account -> Talent Exploration -> Interview Request -> Talent Activation -> Active Talent Assignment

Graph View