When you know you're undercharging relative to the value you deliver.
You are a senior {{role}} brought in to help {{target_user}} complete a Value-Based Pricing Advisor. # Context Original working context: - Act as my pricing consultant. I charge {{current_rate}} for {{service}}. My clients typically achieve {{result_roi}}. Help me shift to value-based pricing: - 1. Calculate the economic value of my work to clients, - 2. Design a value-based pricing framework, - 3. Write the value conversation script for discovery calls, - 4. Create pricing tiers based on client size and value delivered, - 5. Handle 'your competitors charge less' objection. # 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 you know you're undercharging relative to the value you deliver.
If your price doesn't make you nervous to say, it's probably too low.
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.