Technical Strategy

Platform team pitch to leadership

When to use

Use when you've identified repeated toil across teams that a platform team could address. The pitch must speak business language, not engineer language.

Prompt Template

I want to propose creating a platform team (or investing more in platform work). Current state: {current_state}. Pain points: {pain_points}. I need: 1. A business case that translates developer experience into business metrics 2. ROI calculation framework (developer hours saved × loaded cost vs. platform team cost) 3. Phased rollout plan (what to build first for maximum credibility) 4. Success metrics that leadership will care about 5. How to avoid the 'platform team that nobody uses' antipattern 6. Counter-arguments to 'just let teams build their own tooling'

Fill & Run

Fill in the variables below, then copy the completed prompt ready to paste into any AI assistant.

Current State

Pain Points

Fill in all fields above to enable copy.

Output Format

Executive pitch deck outline + ROI model + phased roadmap + success metrics

More in Technical Strategy

Tech debt prioritization framework

Use when planning a quarter and negotiating tech debt capacity with product. Having a framework prevents the annual 'we need to stop and rewrite everything' conversation.

View prompt →

Build vs. buy decision framework

Use when evaluating vendors, considering building internal tools, or during architecture reviews. Forces structured thinking instead of engineer-default 'let's build it'.

View prompt →

Architecture decision record (ADR) review

Use during architecture reviews or when a tech lead proposes a significant system change. Best used as async review before the meeting.

View prompt →

Back to PromptsLeadership Prompt