Prospecting
AuraScore 81/100

Technical Debt Modernization Intro for Scaleup CTOs

Write an executive-level outbound email addressing monolith refactoring risks and engineering velocity drag.

Apply this prompt when prospecting scaleup CTOs who need to modernize legacy codebases without halting roadmap delivery. It frames code modernization as an executive growth enabler.

Template

Role: Principal Solutions Sales Director specializing in automated code refactoring and technical debt remediation.

Context

  • Prospect name: {{cto_name}}
  • Company name: {{scaleup_name}}
  • Legacy architecture stack: {{monolith_stack}}
  • Milestone trigger: {{recent_scaling_milestone}}
  • Quantified drag: {{quantified_engineering_cost}}
  • Introductory asset: {{free_audit_offer}}

Task

Generate a compelling, executive-level outbound prospecting email to {{cto_name}} establishing the commercial impact of technical debt in {{monolith_stack}} and proposing an automated diagnostic assessment.

Method

  1. Acknowledge {{scaleup_name}}'s growth context following {{recent_scaling_milestone}}.
  2. Translate codebase technical debt into business risk: feature velocity slowdown and onboarding friction.
  3. Frame {{monolith_stack}} maintenance overhead against the estimated {{quantified_engineering_cost}}.
  4. Introduce our automated code analysis platform that safely maps dependency graphs and accelerates modularization.
  5. Present {{free_audit_offer}} as a zero-risk, high-insight first step for their engineering leadership team.
  6. Formulate a frictionless closing call to action seeking permission to share a 3-minute sample report.

Constraints

  • Message body MUST NOT exceed 140 words.
  • You MUST anchor the pitch in business velocity, not just code hygiene.
  • Avoid disparaging the engineering team's previous architecture decisions.
  • Ensure the tone balances executive business acumen with architectural literacy.

Output format

  • Subject Line: [Executive-level, max 5 words]
  • Contextual Hook: [1 sentence linking milestone to engineering scale]
  • Business Impact: [2 sentences quantifying technical debt cost]
  • Proposed Next Step: [Offer {{free_audit_offer}} with clear permission check]

Self-review

  • Does the email clearly tie {{monolith_stack}} debt to executive revenue priorities?
  • Is the mention of {{recent_scaling_milestone}} natural and well-integrated?
  • Is the call to action low friction and completely free of aggressive meeting demands?
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering8/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency9/10 · Strong

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-prospecting
software-engineering-debugging
cto-outreach
refactoring
email