ai-native-scale-stage

name	ai-native-scale-stage
description	Scale an AI-native startup after early traction. Use when a founder has users, revenue, pilots, retention signals, or market pull and needs repeatable GTM, metrics, hiring, fundraising narrative, operating cadence, AI-assisted workflows, infrastructure priorities, or bottleneck diagnosis.

AI-Native Scale Stage

Goal

Help founders convert early traction into repeatable growth, operating discipline, team leverage, and defensibility without losing customer learning.

Required Inputs

If the founder provides a structured brief, use these inputs:

Traction:
Retention/usage:
Revenue or pipeline:
Growth channel:
Team and hiring needs:
Operating bottlenecks:
Key metrics:
Funding context:
Desired output:

Guided Intake

Do not require the founder to provide a complete metrics package. If the request is broad, ask up to five questions first:

1. What traction do you have: users, revenue, pilots, retention, or pipeline?
2. Where does growth or delivery feel most constrained right now?
3. Which metric do you trust most, and which metric feels unclear or misleading?
4. What is the next major milestone: revenue, retention, hiring, fundraising, reliability, or GTM repeatability?
5. What output would help most: bottleneck diagnosis, metrics dashboard, hiring plan, operating cadence, or fundraising memo?

After the user answers, identify the likely bottleneck and produce the requested plan. Mark missing metrics as assumptions instead of stalling unless the user asks for a precise dashboard.

Workflow

1. Identify the real scale bottleneck: demand, activation, retention, delivery, data, reliability, hiring, or capital.
2. Use references/metrics.md to separate product-market fit signals from early hype.
3. Use references/operating-cadence.md to design weekly reviews, dashboards, decision rituals, and AI-assisted workflows.
4. Use references/hiring.md to decide what to hire, automate, outsource, or defer.
5. Use references/fundraising.md when the user needs a funding narrative, milestone plan, or investor memo.
6. Return a scale plan with priorities, owners, metrics, operating rhythm, and risk controls.

AI-Native Workflows

Use generic AI roles:

• Metrics analyst: monitor acquisition, activation, retention, revenue, and qualitative signals.
• GTM assistant: research accounts, draft campaigns, and maintain sales/customer-success artifacts.
• Ops agent: run recurring internal workflows with human approval points.
• Hiring assistant: draft scorecards, interview loops, and onboarding plans.
• Fundraising copilot: assemble narrative, milestones, and diligence materials.

Exit Criteria

The Scale stage is healthy when:

• growth is repeatable enough to forecast;
• retention and customer value are measurable;
• the team knows which work should be automated, hired, or personally owned;
• operating rituals catch problems early;
• fundraising or capital planning is tied to concrete milestones.

Common Failure Modes

• Scaling acquisition before retention is understood.
• Hiring for symptoms instead of bottlenecks.
• Automating broken workflows.
• Reporting vanity metrics instead of customer value.
• Raising on narrative without milestone discipline.

Recommended Outputs

Return the most useful artifact for the request:

• scale bottleneck diagnosis;
• metrics dashboard spec;
• hiring plan;
• fundraising memo outline;
• operating cadence.