TalentQuote Content Library v0.2
Status: Working Draft
Version: 0.2
Owner: Marketing / Growth
Governing Document: TalentQuote Content Engine and Editorial Playbook v0.3
Primary Narrative Source: SCRIPTS FOR TALENTQUOTE VIDEOS v1.1
Purpose:
Store reusable content assets that can be transformed into posts, videos, carousels, emails, website snippets, and outbound support materials.
This is not:
- A content calendar
- A post repository
- A copy repository
- A campaign repository
- A marketing strategy document
- An outreach workflow document
SECCIÓN ESPAÑOL
Propósito
La Content Library existe para capturar ideas, temas, narrativas y activos reutilizables.
Cada activo debe permitir múltiples ejecuciones creativas por parte de José Luis, Steven, Victoria, Douglas, Hugo y TalentQuote.
El objetivo no es producir contenido terminado.
El objetivo es crear una biblioteca reutilizable que alimente:
- Founder Posts
- Videos
- Carousels
- Product Education Content
- Website Snippets
- Email Assets
- Outbound Support Assets
- Future Content Calendar entries
Los activos de contenido se mantienen en inglés porque TalentQuote se dirige a un mercado de habla inglesa.
Gobernanza
Esta biblioteca está gobernada por:
- TalentQuote Content Engine and Editorial Playbook v0.3
- SCRIPTS FOR TALENTQUOTE VIDEOS v1.1
- TalentQuote Canon v1.1.1
- TalentQuote Revenue Engine Playbook v1.0
La Content Library almacena activos reutilizables.
La Content Library no almacena:
- Campañas terminadas
- Content calendars terminados
- Content calendar entries
- Post libraries
- LinkedIn posts finales
- Emails finales
- Finished email sequences
- Outreach workflows
- Apollo workflows
- Sales Navigator workflows
- Marketing automation
Los activos pueden evolucionar, pero no deben introducir nuevo posicionamiento, nuevos pilares estratégicos ni mensajes que contradigan los documentos aprobados.
Instrucciones de Uso
José Luis y Steven deben usar la biblioteca como punto de partida para crear ejecuciones.
Flujo recomendado:
Asset ↓ Execution Concept ↓ Draft ↓ Review ↓ Publication
Roles Operativos
- José Luis: planificación de contenido, coordinación editorial, gestión de creación, mantenimiento de la biblioteca y coordinación con el calendario.
- Steven: edición de video, producción creativa, visual assets, carousels, short-form adaptations y soporte multimedia.
- Victoria: apoyo de distribución, organización de activos y uso de assets para oportunidades comerciales.
- Douglas: amplificación comercial y feedback de oportunidades estratégicas.
- Hugo: founder perspective, narrativa fundacional y revisión cuando exista riesgo de drift narrativo.
Estructura de Activos
Cada activo debe incluir:
- Asset ID
- Pillar
- Theme
- Narrative Source
- Core Idea
- Possible Formats
- Example Hooks
- Suggested CTA
Los hooks, CTAs, video titles, narrative assets y conceptos de contenido se mantienen en inglés.
Foundational Narrative Assets
Asset ID
FA-01
Video Title
Hiring Takes Months. Execution Can’t Wait.
Primary Pillar
Engineering Capacity
Primary Theme
Activation Speed
Core Narrative
Modern markets move faster than traditional hiring, and the real bottleneck is activation speed.
Supports Content Assets
- EC-01
- EC-03
- SE-01
Asset ID
FA-02
Video Title
You Don’t Need a 60-Day Hiring Cycle
Primary Pillar
Startup Execution
Primary Theme
Execution Before Hiring
Core Narrative
Startups do not need to wait for a complete hiring cycle before execution begins.
Supports Content Assets
- HL-02
- SE-02
- SE-04
Asset ID
FA-03
Video Title
The Opportunity Cost of Waiting
Primary Pillar
Hiring Latency
Primary Theme
Cost of Waiting
Core Narrative
The real cost of hiring delay is delayed execution, delayed momentum, and delayed revenue.
Supports Content Assets
- HL-01
- HL-04
Asset ID
FA-04
Video Title
They Didn’t Lose The Candidate. They Lost The Window.
Primary Pillar
Startup Execution
Primary Theme
Speed Compounds
Core Narrative
In startups, speed compounds and delays compound.
Supports Content Assets
- HL-03
- SE-01
- SE-03
Content Asset Inventory
Hiring Latency
Asset ID: HL-01
Pillar: Hiring Latency
Theme: Cost of Waiting
Narrative Source: FA-03
Core Idea:
The largest hiring cost is not salary. It is the work that never ships while the position remains open.
Possible Formats:
- Founder Post
- Carousel
- Video Clip
- Industry Commentary
Example Hooks:
- The most expensive engineer is the one you never hired.
- Hiring delays create execution delays.
- Every unfilled role creates hidden opportunity costs.
Suggested CTA:
Start Exploring Talent
Asset ID: HL-02
Pillar: Hiring Latency
Theme: Slow Hiring Cycles
Narrative Source: FA-02
Core Idea:
Markets move faster than traditional hiring processes.
Possible Formats:
- Founder Post
- Video
- Carousel
Example Hooks:
- Startups move in days. Hiring moves in months.
- The market won’t wait for your hiring process.
- You don’t need a 60-day hiring cycle to begin execution.
Suggested CTA:
Start Exploring Talent
Asset ID: HL-03
Pillar: Hiring Latency
Theme: Missed Opportunities
Narrative Source: FA-04
Core Idea:
Slow hiring can cost a company the market window it needed to capture.
Possible Formats:
- Founder Story
- Carousel
- Video Clip
- Industry Commentary
Example Hooks:
- They didn’t lose the candidate. They lost the window.
- Another company moved faster.
- Missed timing can cost more than missed talent.
Suggested CTA:
Start Exploring Talent
Asset ID: HL-04
Pillar: Hiring Latency
Theme: Lost Execution Time
Narrative Source: FA-03
Core Idea:
Every week without product movement creates distance between the company and the market.
Possible Formats:
- Founder Post
- Carousel
- Outbound Support Asset
Example Hooks:
- Every week without product movement creates distance from the market.
- Waiting looks quiet until momentum disappears.
- Delayed execution becomes delayed revenue.
Suggested CTA:
Start Exploring Talent
Asset ID: HL-05
Pillar: Hiring Latency
Theme: Hiring Latency Becomes Execution Latency
Narrative Source: FA-01, FA-02
Core Idea:
Hiring delay is not only an HR delay. It becomes a product, roadmap, and revenue delay.
Possible Formats:
- Founder Post
- Carousel
- Video Clip
- Product Education
Example Hooks:
- Hiring latency becomes execution latency.
- When hiring slows, the roadmap feels it first.
- Recruiting delay is product delay in disguise.
Suggested CTA:
Start Exploring Talent
Engineering Capacity
Asset ID: EC-01
Pillar: Engineering Capacity
Theme: Capacity vs Hiring
Narrative Source: FA-01
Core Idea:
Companies do not always need another hiring process. They need execution capacity.
Possible Formats:
- Founder Post
- Product Post
- Carousel
- Video
Example Hooks:
- Stop hiring. Start activating talent.
- Capacity solves problems faster than recruiting.
- The issue was never talent.
Suggested CTA:
Start Exploring Talent
Asset ID: EC-02
Pillar: Engineering Capacity
Theme: Availability Advantage
Narrative Source: FA-01
Core Idea:
Availability is a strategic asset. The best available engineer today may create more value than the perfect engineer available in three months.
Possible Formats:
- Founder Post
- Carousel
- Product Education
Example Hooks:
- Availability beats perfection.
- Speed creates advantage.
- The best talent is only useful when it can be activated.
Suggested CTA:
Start Exploring Talent
Asset ID: EC-03
Pillar: Engineering Capacity
Theme: Activation vs Recruiting
Narrative Source: FA-01
Core Idea:
TalentQuote shifts the conversation from recruiting activity to capacity activation.
Possible Formats:
- Founder Post
- Product Education
- Carousel
- Website Snippet
Example Hooks:
- This isn’t a hiring problem anymore.
- It is not about finding more resumes. It is about activating capacity.
- Activation beats recruiting when execution is urgent.
Suggested CTA:
Start Exploring Talent
Asset ID: EC-04
Pillar: Engineering Capacity
Theme: Engineering Capacity On Demand
Narrative Source: TBD
Core Idea:
Engineering capacity should be accessible when the roadmap needs it, not only when the hiring process catches up.
Possible Formats:
- Product Education
- Carousel
- Founder Post
- Website Snippet
Example Hooks:
- Engineering capacity should be available when the roadmap needs it.
- Your roadmap should not wait for recruiting to catch up.
- Capacity should be easier to activate.
Suggested CTA:
Start Exploring Talent
Asset ID: EC-05
Pillar: Engineering Capacity
Theme: Engineering Capacity as Infrastructure
Narrative Source: TBD
Core Idea:
Modern software teams should treat engineering capacity as operational infrastructure, not as a slow one-off hiring event.
Possible Formats:
- Founder Post
- Carousel
- Product Education
- Industry Commentary
Example Hooks:
- Engineering capacity is becoming infrastructure.
- Talent should be easier to activate than it is today.
- Modern teams need capacity systems, not only hiring processes.
Suggested CTA:
Start Exploring Talent
Asset ID: EC-06
Pillar: Engineering Capacity
Theme: Capacity Gaps During Scale
Narrative Source: FA-01
Core Idea:
Scaling companies often hit execution gaps before the hiring process can fill them.
Possible Formats:
- Founder Post
- Carousel
- Outbound Support Asset
Example Hooks:
- Scale breaks when capacity arrives too late.
- Growth creates capacity gaps before hiring closes them.
- Your team can be right and still be under capacity.
Suggested CTA:
Start Exploring Talent
Startup Execution
Asset ID: SE-01
Pillar: Startup Execution
Theme: Roadmap Velocity
Narrative Source: FA-01, FA-04
Core Idea:
Execution speed is a competitive advantage.
Possible Formats:
- Founder Post
- Video
- Carousel
Example Hooks:
- Roadmaps fail when capacity disappears.
- Execution compounds.
- The fastest companies win because they start building faster.
Suggested CTA:
Start Exploring Talent
Asset ID: SE-02
Pillar: Startup Execution
Theme: Execution Before Hiring
Narrative Source: FA-02
Core Idea:
Execution can begin before a complete hiring cycle is finished.
Possible Formats:
- Founder Post
- Video Clip
- Carousel
Example Hooks:
- You don’t need a 60-day hiring cycle to begin execution.
- Execution starts earlier than most teams think.
- While one company is interviewing, another one is already shipping.
Suggested CTA:
Start Exploring Talent
Asset ID: SE-03
Pillar: Startup Execution
Theme: Speed Compounds
Narrative Source: FA-04
Core Idea:
Small speed advantages compound into market advantages.
Possible Formats:
- Founder Story
- Video Clip
- Carousel
- Industry Commentary
Example Hooks:
- Speed compounds. So do delays.
- The company that moves first gets more learning cycles.
- In startups, timing compounds.
Suggested CTA:
Start Exploring Talent
Asset ID: SE-04
Pillar: Startup Execution
Theme: Shipping With Limited Teams
Narrative Source: FA-02
Core Idea:
Startups need ways to keep shipping while internal hiring continues.
Possible Formats:
- Founder Post
- Carousel
- Outbound Support Asset
Example Hooks:
- Shipping should not stop while hiring catches up.
- The roadmap still needs movement while roles are open.
- Keep building while the hiring process runs.
Suggested CTA:
Start Exploring Talent
Asset ID: SE-05
Pillar: Startup Execution
Theme: Execution Bottlenecks During Growth
Narrative Source: FA-01, FA-03
Core Idea:
Growth creates bottlenecks when roadmap ambition exceeds available engineering capacity.
Possible Formats:
- Founder Post
- Carousel
- Product Education
Example Hooks:
- Growth creates bottlenecks before it creates clarity.
- Roadmap ambition needs capacity behind it.
- The bottleneck is often activation speed.
Suggested CTA:
Start Exploring Talent
Asset ID: SE-06
Pillar: Startup Execution
Theme: Product Momentum
Narrative Source: FA-02, FA-03
Core Idea:
Product momentum depends on reducing the time between need and execution.
Possible Formats:
- Founder Post
- Video Clip
- Carousel
- Industry Commentary
Example Hooks:
- Product momentum is fragile.
- Momentum disappears while teams are still interviewing.
- The market rewards teams that keep learning.
Suggested CTA:
Start Exploring Talent
Founder Perspective
Asset ID: FP-01
Pillar: Founder Perspective
Theme: Founder Lessons
Narrative Source: TBD
Core Idea:
Lessons learned building engineering teams for more than 20 years.
Possible Formats:
- Founder Story
- Founder Post
- Video
Example Hooks:
- One hiring mistake cost us months.
- What I learned building engineering teams.
- The expensive lessons are usually about timing.
Suggested CTA:
Book a Discovery Call
Asset ID: FP-02
Pillar: Founder Perspective
Theme: Hiring Mistakes
Narrative Source: FA-03, FA-04
Core Idea:
Founders often underestimate the hidden cost of waiting too long to add execution capacity.
Possible Formats:
- Founder Story
- Founder Post
- Video Clip
- Carousel
Example Hooks:
- The mistake was not hiring slowly. It was waiting to execute.
- I used to think the safest path was to wait for the perfect hire.
- Hiring mistakes often show up as missed execution windows.
Suggested CTA:
Book a Discovery Call
Asset ID: FP-03
Pillar: Founder Perspective
Theme: Runway and Execution
Narrative Source: FA-03
Core Idea:
Runway is consumed while teams wait for execution capacity to arrive.
Possible Formats:
- Founder Post
- Carousel
- Founder Story
- Industry Commentary
Example Hooks:
- Runway is not only spent in dollars. It is spent in waiting.
- Every week without product movement burns more than budget.
- Waiting quietly consumes founder attention.
Suggested CTA:
Book a Discovery Call
Asset ID: FP-04
Pillar: Founder Perspective
Theme: Building With Constraints
Narrative Source: TBD
Core Idea:
Founders need practical ways to keep building when team size, budget, and timing are constrained.
Possible Formats:
- Founder Story
- Founder Post
- Video
- Carousel
Example Hooks:
- Constraints make execution speed matter more.
- You do not always need a bigger team. You need the right capacity at the right moment.
- Building under constraints forces better capacity decisions.
Suggested CTA:
Book a Discovery Call
Product Education
Asset ID: PE-01
Pillar: Product Education
Theme: What Is Instant Match
Narrative Source: TBD
Core Idea:
Instant Match reduces friction between need and capacity.
Possible Formats:
- Product Post
- Carousel
- Product Walkthrough
Example Hooks:
- What if hiring started with available talent?
- Instant Match explained in 60 seconds.
- Start with available engineering capacity.
Suggested CTA:
Start Exploring Talent
Asset ID: PE-02
Pillar: Product Education
Theme: Candidate Introductions
Narrative Source: TBD
Core Idea:
Candidate Introductions help teams move from interest to evaluation without restarting a slow sourcing process.
Possible Formats:
- Product Education
- Carousel
- Website Snippet
- Email Asset
Example Hooks:
- Candidate Introductions should reduce friction, not add steps.
- Meet available talent without starting from zero.
- The first conversation should happen sooner.
Suggested CTA:
Start Exploring Talent
Asset ID: PE-03
Pillar: Product Education
Theme: Talent Activation
Narrative Source: FA-01
Core Idea:
Talent Activation is the movement from need to evaluation to working capacity.
Possible Formats:
- Product Post
- Carousel
- Product Walkthrough
- Website Snippet
Example Hooks:
- Talent activation is the point where capacity becomes real.
- The goal is not more profiles. The goal is activated capacity.
- Activation is where hiring latency turns into execution speed.
Suggested CTA:
Start Exploring Talent
Asset ID: PE-04
Pillar: Product Education
Theme: Browse → Interview → Activate
Narrative Source: TBD
Core Idea:
TalentQuote should make the buyer path feel simple: browse available talent, request interviews, and activate capacity.
Possible Formats:
- Product Education
- Carousel
- Website Snippet
- Email Asset
Example Hooks:
- Browse. Interview. Activate.
- Talent exploration should feel simple.
- Start with profiles that are already available.
Suggested CTA:
Start Exploring Talent
Asset ID: PE-05
Pillar: Product Education
Theme: Why TalentQuote Is Not Recruiting
Narrative Source: FA-01, FA-03
Core Idea:
TalentQuote is not a recruiting agency. It is a way to activate engineering capacity faster.
Possible Formats:
- Product Education
- Carousel
- Founder Post
- Website Snippet
Example Hooks:
- This is not another recruiting platform.
- TalentQuote is built for activation, not recruiting activity.
- The goal is not to collect candidates. The goal is to activate capacity.
Suggested CTA:
Start Exploring Talent
Future Asset Backlog
Founder Stories
- Founder lessons from missed timing
- Founder lessons from scaling too slowly
- Hiring lessons from building engineering teams
- Runway pressure and execution choices
Product Education
- How TalentQuote works
- How Talent Activation works
- How Candidate Introductions work
- What buyers should do after registration
Startup Execution
- Execution bottlenecks during growth
- Product momentum after funding
- Roadmap pressure with open roles
- Shipping while hiring continues
Industry Commentary
- Why hiring cycles are misaligned with startup speed
- Why availability matters more in fast markets
- Why engineering capacity is becoming infrastructure
- Why activation speed creates advantage
ENGLISH SECTION
Purpose
The Content Library exists to capture reusable ideas, narratives, themes, and content assets.
Each asset should support multiple creative executions by José Luis, Steven, Victoria, Douglas, Hugo, and TalentQuote.
The goal is not to store finished content.
The goal is to store reusable content assets that can support:
- Founder Posts
- Videos
- Carousels
- Product Education Content
- Website Snippets
- Email Assets
- Outbound Support Assets
- Future Content Calendar entries
Content assets remain in English because TalentQuote serves an English-speaking target market.
Governance
This library is governed by:
- TalentQuote Content Engine and Editorial Playbook v0.3
- SCRIPTS FOR TALENTQUOTE VIDEOS v1.1
- TalentQuote Canon v1.1.1
- TalentQuote Revenue Engine Playbook v1.0
The Content Library stores reusable assets.
The Content Library does not store:
- Finished campaigns
- Finished content calendars
- Content calendar entries
- Post libraries
- Final LinkedIn posts
- Final emails
- Finished email sequences
- Outreach workflows
- Apollo workflows
- Sales Navigator workflows
- Marketing automation
Assets may evolve, but they should not introduce new positioning, new strategic pillars, or messages that contradict approved documents.
Instructions
José Luis and Steven should use the library as the starting point for execution.
Recommended flow:
Asset ↓ Execution Concept ↓ Draft ↓ Review ↓ Publication
Operating Roles
- José Luis: content planning, editorial coordination, content creation management, library maintenance, and calendar coordination.
- Steven: video editing, creative production, visual assets, carousels, short-form adaptations, and multimedia support.
- Victoria: distribution support, asset organization, and use of assets for commercial opportunities.
- Douglas: commercial amplification and strategic opportunity feedback.
- Hugo: founder perspective, foundational narrative, and review when narrative drift is possible.
Asset Structure
Every asset should include:
- Asset ID
- Pillar
- Theme
- Narrative Source
- Core Idea
- Possible Formats
- Example Hooks
- Suggested CTA
Hooks, CTAs, video titles, narrative assets, and content concepts remain in English.
Foundational Narrative Assets
Asset ID
FA-01
Video Title
Hiring Takes Months. Execution Can’t Wait.
Primary Pillar
Engineering Capacity
Primary Theme
Activation Speed
Core Narrative
Modern markets move faster than traditional hiring, and the real bottleneck is activation speed.
Supports Content Assets
- EC-01
- EC-03
- SE-01
Asset ID
FA-02
Video Title
You Don’t Need a 60-Day Hiring Cycle
Primary Pillar
Startup Execution
Primary Theme
Execution Before Hiring
Core Narrative
Startups do not need to wait for a complete hiring cycle before execution begins.
Supports Content Assets
- HL-02
- SE-02
- SE-04
Asset ID
FA-03
Video Title
The Opportunity Cost of Waiting
Primary Pillar
Hiring Latency
Primary Theme
Cost of Waiting
Core Narrative
The real cost of hiring delay is delayed execution, delayed momentum, and delayed revenue.
Supports Content Assets
- HL-01
- HL-04
Asset ID
FA-04
Video Title
They Didn’t Lose The Candidate. They Lost The Window.
Primary Pillar
Startup Execution
Primary Theme
Speed Compounds
Core Narrative
In startups, speed compounds and delays compound.
Supports Content Assets
- HL-03
- SE-01
- SE-03
Content Asset Inventory
This inventory contains 26 reusable content assets. It is not a repository of finished copy.
Assets are grouped by pillar:
- Hiring Latency: HL-01 through HL-05
- Engineering Capacity: EC-01 through EC-06
- Startup Execution: SE-01 through SE-06
- Founder Perspective: FP-01 through FP-04
- Product Education: PE-01 through PE-05
Use the Spanish section inventory as the operational asset list. Asset fields and creative concepts are intentionally kept in English for market-facing reuse.
Future Asset Backlog
Founder Stories
- Founder lessons from missed timing
- Founder lessons from scaling too slowly
- Hiring lessons from building engineering teams
- Runway pressure and execution choices
Product Education
- How TalentQuote works
- How Talent Activation works
- How Candidate Introductions work
- What buyers should do after registration
Startup Execution
- Execution bottlenecks during growth
- Product momentum after funding
- Roadmap pressure with open roles
- Shipping while hiring continues
Industry Commentary
- Why hiring cycles are misaligned with startup speed
- Why availability matters more in fast markets
- Why engineering capacity is becoming infrastructure
- Why activation speed creates advantage