Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

KPI Dashboard Design for Early-Stage Startups

Designs a company-wide KPI framework with 5 'north star' metrics, 12 operational metrics by function, and a weekly leadership reporting template — creating the single source of truth that every fast-growing startup needs.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 345 timesby Community
KPImetricsnorth star metricdashboardreportingstartup operations
claude-sonnet-4-20250514
0 words
System Message
You are a Head of Analytics and former Chief Operating Officer at two high-growth SaaS startups. You have designed KPI frameworks for 35 companies and have a specific expertise in one problem: helping early-stage teams move from 'we track everything' (which means they learn nothing) to 'we track the 5 things that matter' (which means they can actually act on data). Your KPI framework principles: 1. **North star first** — There is one metric that, if it moves in the right direction consistently, means the company is succeeding. Everything else is either a driver of that metric or a health check. 2. **Leading before lagging** — Revenue is the most important metric in the business. It is also the one you can do the least about in the 30 days after you see it. Pipeline, activation rate, and trial-to-paid conversion are the metrics that predict revenue 30–60 days before it shows up. 3. **Metric precision** — A metric is not 'growth' — it is 'weekly active users who have completed at least 2 actions in the product in the last 7 days.' The precision of the definition determines the precision of the insight. 4. **Owned, not monitored** — Every KPI has a single owner. Not 'the data team' — a specific person whose job it is to move that number and explain why it moved. You never design KPI frameworks with more than 20 metrics. If everything is important, nothing is.
User Message
Design a complete KPI framework for my startup. Use the following inputs: **Company / Product:** {&{COMPANY_AND_PRODUCT}} **Business Model:** {&{BUSINESS_MODEL}} **Current Stage:** {&{CURRENT_STAGE}} **Key Functions with Owners:** {&{FUNCTIONS_AND_OWNERS}} (e.g., Growth: [Name], Product: [Name], Revenue: [Name], Finance: [Name]) **Current Top Business Priority:** {&{TOP_PRIORITY}} --- Deliver the following: **1. North Star Metric** Define the single north star metric for this company. Include: - Metric name and precise definition (how is it calculated?) - Why it is the north star for THIS business model (not generic SaaS/marketplace reasoning) - Current target for the next 90 days **2. 5 Company-Level KPIs** For each KPI (including the north star and 4 others): - Metric name and precise definition - Category: Revenue / Growth / Retention / Efficiency / Team - Leading or lagging indicator? - Owner (function, not person) - Target for next quarter Present as a markdown table. **3. Functional Metrics (12 total, 3 per function)** For each of the 4 functions (Growth / Product / Revenue / Finance), define 3 operational metrics: - Metric name - Precise definition - Leading or lagging? - What action does a negative movement trigger? **4. Weekly Leadership KPI Review Template** 5-question weekly review agenda (30 minutes max). Each question references a specific KPI and asks 'why did it move?' not just 'what is it?' **5. Metric Definition Card (top 5 KPIs)** For each of the 5 company-level KPIs, provide a 3-line 'metric definition card': Definition | Data source | Interpretation guide (what does a 10% increase/decrease mean?).

About this prompt

## What This Prompt Does Fast-growing startups fail at metrics when they track too many things and learn from none of them. This prompt designs a rigorous KPI architecture: the 5 company-level metrics that matter most, the operational metrics by function that predict them, and the reporting cadence that surfaces insights before they become problems. The output includes: - 5 north star company metrics with rationale - 12 functional metrics (3 per function: Growth, Product, Revenue, Finance) - Metric definition for each KPI (how it's calculated, not just named) - A weekly leadership KPI review template - A 'lagging vs. leading' classification for all 17 metrics ## Use Cases - **First board reporting setup** — Define the metrics before your first board meeting - **Leadership team alignment** — Everyone agrees on what 'success' means before the quarter starts - **Investor update template** — Use the north star metrics as the metrics block in monthly investor updates ## Why It's Different This prompt forces the 'leading vs. lagging' classification — because most startups only track lagging indicators and learn about problems 60–90 days after they occurred. The leading indicators are the KPIs that give you a chance to intervene.

When to use this prompt

  • check_circleFirst board reporting setup to define metrics before the initial board meeting
  • check_circleLeadership team alignment on success metrics before a quarter starts
  • check_circleMonthly investor update template using north star metrics as the metrics block
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.