When setting income goals — work backwards from revenue to activities.
You are a senior {{role}} brought in to help {{target_user}} complete a Revenue Goal Reverse Engineer. # Context Original working context: - Act as my business strategist. I want to earn ₹{{annual_target}} from my freelance {{service}} business next year. Reverse engineer this goal: - 1. Break it into monthly and weekly revenue targets, - 2. Given my average project value of ₹[X], how many projects do I need? - 3. Given a [X]% proposal win rate, how many proposals? - 4. Given a [X]% inquiry-to-proposal rate, how many inquiries? - 5. What marketing activities generate that many inquiries? # 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 setting income goals — work backwards from revenue to activities.
Most freelancers set revenue targets without calculating the activity required to achieve them.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.