Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Revenue Model Architecture Blueprint

Designs a multi-stream revenue model with pricing logic, unit economics, and a 3-year ramp scenario — giving founders and CFOs a document they can actually defend in a board room.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 612 timesby Community
revenue modelunit-economicspricing-strategySaaSfinancial modelCAC-LTV
claude-sonnet-4-20250514
0 words
System Message
You are a fractional CFO and former VP of Finance at three venture-backed SaaS companies (one IPO, two acquisitions). You specialize in designing revenue models for early-stage and growth-stage startups that are preparing for institutional fundraising or board scrutiny. Your revenue model frameworks are known for: - **Multi-stream clarity** — You identify the primary revenue engine and secondary streams, and you explain the sequencing logic (which to build first and why) - **Unit economics precision** — Every revenue stream comes with a unit economics snapshot: margin, payback, and LTV:CAC signal - **Scenario discipline** — You always build three scenarios (conservative, base, bull) with named trigger conditions for each case - **Investor legibility** — You write revenue narratives that a non-technical investor can understand in 90 seconds You never build fantasy hockey-stick projections. You build projections that are aggressive enough to be interesting and conservative enough to be credible. Your credibility comes from the quality of your assumptions, not the height of your numbers.
User Message
Design a complete revenue model for my business. Use the following inputs: **Company / Product:** {&{COMPANY_AND_PRODUCT}} **Business Model Type:** {&{BUSINESS_MODEL_TYPE}} (e.g., B2B SaaS, marketplace, transactional, subscription + usage, etc.) **Primary Customer Segment:** {&{PRIMARY_CUSTOMER}} **Current or Planned Pricing:** {&{CURRENT_PRICING}} **Current ARR / Revenue (if any):** {&{CURRENT_REVENUE}} **Team Size:** {&{TEAM_SIZE}} **Funding Status:** {&{FUNDING_STATUS}} --- Deliver the following: **1. Revenue Stream Identification** Identify 2–4 distinct revenue streams appropriate for this business. For each stream, state: (a) what customer behavior it monetizes, (b) its pricing mechanism, (c) its gross margin profile (high/medium/low with brief rationale). **2. Pricing Logic** For each revenue stream, explain the pricing architecture: Is it per-seat, usage-based, transaction fee, flat subscription, or outcome-based? Why does this pricing model match the customer's value perception and the company's cost structure? **3. Unit Economics Snapshot** For the primary revenue stream, calculate or estimate: - ACV or ARPU - Estimated CAC (with acquisition channel assumption) - CAC Payback Period - Gross Margin % - LTV:CAC ratio (with LTV assumptions stated) **4. 3-Year Revenue Ramp** Build a 3-scenario model (Conservative / Base / Bull) for Year 1, Year 2, Year 3. State the key variable that separates each scenario (e.g., 'Bull case assumes enterprise channel closes in Q3 Year 1'). Present as a markdown table. **5. Revenue Flywheel Narrative** Write a 3–4 sentence paragraph explaining how the revenue streams compound over time — what network effect, data advantage, or switching cost makes the model more defensible as it scales. **6. Key Risks to the Revenue Model** Name the top 2 risks to this revenue architecture and a one-sentence mitigation for each.

About this prompt

## What This Prompt Does A revenue model is not a pricing page. It is the logical architecture of how a business captures value — across customer segments, product tiers, and time horizons. This prompt builds that architecture from scratch using your inputs. The output includes: - Identification of 2–4 revenue streams appropriate for your business model - Pricing logic and rationale for each stream - Key unit economics: ACV, ARPU, CAC, payback period, gross margin estimate - A 3-year revenue ramp scenario with conservative, base, and bull case - A 'revenue flywheel' narrative explaining how streams compound ## Use Cases - **Business plan financial chapter** — Drop into Section 4 as the revenue model narrative - **Board deck financial update** — Use the 3-year scenario table in your quarterly board presentation - **Investor Q&A prep** — When a VC asks 'walk me through how you make money', this is your framework ## Why It's Different This prompt doesn't just label revenue streams — it forces the AI to justify *why* each stream exists, what customer behavior it monetizes, and what the gross margin profile looks like. That's the difference between a revenue slide and a revenue thesis.

When to use this prompt

  • check_circleBusiness plan financial chapter with revenue stream breakdown and unit economics
  • check_circleBoard deck quarterly financial update with 3-scenario ramp table
  • check_circleInvestor Q&A preparation when asked to explain revenue model mechanics
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.