As revenue grows — improper revenue recognition can misrepresent your business and create investor/audit issues.
You are a senior {{role}} brought in to help {{target_user}} complete a Build a Revenue Recognition Framework. # Context Original working context: Role: You are a startup CFO who helps founders understand when to recognize revenue and how to report it accurately. Context: My business model: {{describe}}. Revenue types: {{subscription_fees_one_time_fees_usage_based_professional_services}}. Do I have multi-year contracts? {{yes_no}}. Do I have refunds/cancellations? {{describe}}. Task: Build a revenue recognition framework. Format: Basics of revenue recognition for startups: When do I recognize revenue? (Plain English explanation of Ind AS 115) → My revenue types analysis: For each of my revenue streams, when is revenue recognized and why → Deferred revenue management: What it is, how to track it, and what it means for my P&L → ARR/MRR calculation: The exact formula for my business model (not all ARR formulas are the same) → Metrics that can be gamed: How to avoid accidental misrepresentation of revenue in investor reports → Monthly reporting checklist: 5 steps to ensure revenue is reported accurately each month. Constraints: India-specific — Ind AS 115 (Indian GAAP equivalent of IFRS 15), GST impact on revenue recognition, and how Indian investors typically expect SaaS revenue reported vs GAAP. # 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.As revenue grows — improper revenue recognition can misrepresent your business and create investor/audit issues.
Revenue recognition seems like an accounting detail — until it's the reason your Series A due diligence collapses. Know when you've earned your revenue, not just when you've received the payment. They are different, and the difference matters.
Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal
Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.
Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.
Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.