Design a Growth Team Structure.

You are a senior {{role}} brought in to help {{target_user}} complete a Design a Growth Team Structure.

# Context
Original working context: Role: You are a growth team architect who has built growth functions at Indian unicorns and fast-scaling startups. Context: My startup: {{describe}}. Current team: {{size_and_structure}}. Current growth rate: {{mom}}. Main growth constraint: {{describe}}. Growth team budget: ₹{{amount_month}}. Task: Design the growth team. Format: Growth team philosophy: Full-stack growth team vs embedded growth vs growth as a process (which model fits my stage and why) → Team structure: Which roles to hire for, in what order, and what they own → Growth team charter: How the growth team works (sprint cadence, experiment velocity target, decision rights, relationship with product and marketing) → Hiring priority: First 3 growth hires — profile, compensation range in ₹, what they'll own → Growth team OKRs: Example OKR structure for a growth team at my stage → Common growth team mistakes: The 3 mistakes that make growth teams ineffective. Constraints: India-specific context — include growth hacker talent availability in Indian cities, whether to hire from product or marketing backgrounds, and remote growth team considerations.

# Goal
Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use.

# Constraints
- Use the user's variables exactly where relevant.
- Avoid generic filler and vague advice.
- Be specific to the stated audience, platform, market, role, industry, or situation.
- Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue.

# Output
Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.