When the team is growing and collaboration is breaking down — tool stack clarity prevents communication chaos.
You are a senior {{role}} brought in to help {{target_user}} complete a Build a Team Productivity & Tools Stack. # Context Original working context: - Act as an operations consultant helping an Indian startup design their productivity toolkit and workflows. - Step 1: My startup: {{describe}}. Team size: {{number}}. Functions in the business: {{list}}. Current tools we use: {{list}}. What's not working: {{describe}}. - Step 2: Design the tool stack by function: For each function, recommend the best tool for: project management, communication, documentation, and any function-specific tools. Prioritize tools with strong Indian support, UPI billing, and affordable startup pricing. - Step 3: Design the integration between tools: How do the tools connect? Where does the source of truth live for each type of information (e.g. customer data in CRM, project status in project management tool)? - Step 4: Build the 'how we work with our tools' guide: For the top 3 tools, write a 1-page usage guide — what to use it for, what NOT to use it for, and naming/filing conventions. - Step 5: Self-check: Is this stack too complex? The right tool stack for a 15-person startup should be learnable in 1 week. Flag any tool that's adding complexity without clear value. # 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.
{{double-curly}} with your real context.When the team is growing and collaboration is breaking down — tool stack clarity prevents communication chaos.
The best tool stack is the simplest one that does the job. Tool proliferation is a startup killer — every new tool requires onboarding, creates a data silo, and fragments attention. Add tools reluctantly. Remove tools aggressively.
Validate this business idea rigorously. Assess market size, competition, feasibility, and risk. Give an honest recommendation — do not flatter.
Conduct a structured competitor analysis. Map each competitor's strengths, weaknesses, positioning, pricing, and target customer. Identify the market gaps your business can own.
Write the complete narrative for a 10-slide pitch deck. For each slide, write the title, the key message (one sentence), and the talking points (3-5 bullets).
Recommend a pricing strategy with full rationale. Provide 3 pricing options (low/mid/premium tier) and explain what each achieves. Recommend one as optimal for the stated goal.