The most compelling outreach combines company-level context, role-specific challenges, and individual signals. Learn to layer all three sources in a single Bitscale workflow.
AP-3 · AI Personalization · 125 XP · ~20 min
A Level 4 personalized email requires three things simultaneously: it knows what’s happening at the company right now, it understands what this specific role typically deals with, and it references something specific about this individual. Building these three layers manually takes 20+ minutes per contact. In Bitscale, it takes seconds.
Synthesize the following company intelligence into a 2-sentence context summary for use in outreach:Company: {{company_name}}Recent signal: {{signal_description}}Funding stage: {{funding_stage}}Hiring activity: {{hiring_signal}}Tech stack: {{tech_stack_maturity}}Output: a 2-sentence summary of what's most relevant about this company's current context for an outbound pitch about GTM automation. Focus on what's happening NOW, not historical facts.Return ONLY the 2-sentence summary.
This layer answers: what does someone in this specific role at a company of this stage typically worry about?Different job titles at the same company have different priorities. A VP of Sales cares about pipeline coverage. A Head of SDR cares about rep productivity. A RevOps leader cares about data quality and tool efficiency. Your outreach needs to speak to their role’s reality.
Given:- Job title: {{job_title}}- Company stage: {{funding_stage}} startup- Company size: {{company_size_range}} employees- Hiring situation: {{hiring_signal}}What are the top 2 challenges this person is most likely facing right now in their role?Focus on challenges that a GTM automation / data enrichment tool could plausibly solve.Return as JSON: {"primary_challenge": "...", "secondary_challenge": "..."}
Based on this person's LinkedIn activity:Name: {{first_name}} {{last_name}}Title: {{job_title}}LinkedIn headline: {{linkedin_headline}}Recent post summary: {{recent_post_summary}} (if available)Career context: {{career_summary}}Identify ONE specific, genuine observation that could open an email naturally.This should be:- Something they've actually expressed an opinion about or done- Relevant to their professional context (not personal)- Something you could reference without it feeling creepyIf there is no meaningful individual signal available, return "no_individual_signal".Return ONLY the observation or "no_individual_signal".
Once you have all three layers, synthesize them into a single email:
You are writing a cold outreach email on behalf of a Bitscale sales rep.Layer 1 — Company context: {{company_context_summary}}Layer 2 — Role challenge: {{primary_challenge}}Layer 3 — Individual signal: {{individual_observation}} (use only if not "no_individual_signal")Email requirements:- Opening line: Lead with whichever layer is strongest (company signal is usually most specific)- Value connection: Connect their specific context to what Bitscale solves- If Layer 3 is available, weave it in naturally — don't force it- CTA: 15-minute conversation, framed around their specific challenge- Max 90 words- Sound like a thoughtful human, not a systemReturn ONLY the email body.
Not every contact will have all three layers available. Build fallback logic:
Determine which personalization layers are available for this contact:Company signal: {{signal_description}} — is this specific? (yes/no)Role challenge: {{primary_challenge}} — was this populated? (yes/no)Individual signal: {{individual_observation}} — is this "no_individual_signal"? (yes/no)Classify:- full_personalization: all 3 layers specific and available- two_layer: 2 layers available (specify which 2)- company_only: only company signal is specific- role_only: only role challenge is available- minimal: no specific layers — use only generic personalizationThis classification will determine which prompt variant to use.Return ONLY the classification.
Route different classifications to different prompt variants — the full_personalization prompt differs from the minimal prompt in specificity level.
Quick Check: What does each of the three personalization layers answer? What is the fallback logic for when individual signals aren’t available? How do you determine which layer to lead with in the email?
