Introduction
You’re in a meeting. Your PM says: “We need to improve our CAC to LTV ratio and focus on retention metrics to achieve PMF before we can scale.”
You nod, but internally you’re confused. Is this English?
This is the problem: Developers and business people speak different languages. When you don’t understand business terminology, you can’t contribute meaningfully to product decisions. You can’t advocate for technical solutions. You can’t understand why certain features matter.
This guide translates business jargon into plain English. No fluff. Just the terms you actually need to know to communicate with PMs, marketers, and sales teams.
Core Business Metrics
Revenue & Growth
MRR (Monthly Recurring Revenue)
- The predictable revenue you make each month from subscriptions
- Example: 100 customers × $50/month = $5,000 MRR
- Why it matters: Shows business health and growth trajectory
- Developer context: This is what keeps the company alive
ARR (Annual Recurring Revenue)
- MRR × 12 (or total annual subscription revenue)
- Example: $5,000 MRR = $60,000 ARR
- Why it matters: Used for valuation and investor pitches
- Developer context: Bigger number, same concept
Churn Rate
- Percentage of customers who cancel each month
- Example: 100 customers, 5 cancel = 5% churn
- Why it matters: High churn means the product isn’t sticky
- Developer context: If churn is high, your features aren’t solving the problem
Burn Rate
- How fast you’re spending money (usually monthly)
- Example: Spending $50,000/month with $100,000 in the bank = 2 months runway
- Why it matters: Determines how long the company can survive
- Developer context: Affects hiring, feature priorities, and urgency
Runway
- How many months until you run out of money
- Calculated as: Cash in bank ÷ Monthly burn rate
- Example: $200,000 ÷ $50,000/month = 4 months runway
- Why it matters: Determines urgency and decision-making
- Developer context: Short runway = move fast, cut scope
Customer Metrics
CAC (Customer Acquisition Cost)
- How much you spend to acquire one customer
- Calculated as: Total marketing spend ÷ New customers acquired
- Example: Spent $10,000 on ads, got 100 customers = $100 CAC
- Why it matters: Determines if your business model is sustainable
- Developer context: If CAC is high, you need to build features that reduce it
LTV (Lifetime Value)
- Total profit you make from a customer over their lifetime
- Rough calculation: Average monthly profit × Average customer lifetime (months)
- Example: $40 profit/month × 12 months = $480 LTV
- Why it matters: If LTV > CAC, your business works
- Developer context: Features that increase retention directly increase LTV
CAC Payback Period
- How many months until a customer pays back their acquisition cost
- Example: $100 CAC, $40 profit/month = 2.5 months payback
- Why it matters: Determines cash flow and sustainability
- Developer context: Shorter payback = healthier business
NRR (Net Revenue Retention)
- Revenue from existing customers this month vs. last month (including upgrades and churn)
- Example: 100 customers at $50 = $5,000. Next month: 95 customers (5 churned) + 10 upgrades = $5,250 = 105% NRR
- Why it matters: Shows if the product is getting stickier
- Developer context: Improving NRR means building features customers love
Cohort Analysis
- Grouping customers by when they signed up and tracking their behavior
- Example: “Customers from January have 8% churn, customers from February have 12% churn”
- Why it matters: Shows if product improvements are working
- Developer context: Helps identify which features reduce churn
Product & Market Fit
PMF (Product-Market Fit)
Definition: Your product solves a real problem for a specific market, and customers actively want it.
Product-market fit (PMF) is when a product satisfies a strong market demand, meaning it solves a real problem for a specific group of people who enthusiastically buy, use, and recommend it, leading to natural growth and profitability without constant heavy marketing push. It’s the crucial alignment where your solution truly resonates with customers, making them pull the product from you rather than you pushing it on them, making it essential for startup success and easier fundraising.
Signs you have PMF:
- Customers are asking for your product
- Churn is low (< 5% monthly)
- NRR is positive (> 100%)
- Word-of-mouth is strong
- You can’t keep up with demand
Why it matters: PMF is the inflection point. Before PMF, you’re experimenting. After PMF, you’re scaling.
Developer context: Before PMF, focus on building the right thing. After PMF, focus on scaling what works.
TAM (Total Addressable Market)
- The total revenue opportunity if you captured 100% of your market
- Example: 1 million potential customers × $100 average price = $100M TAM
- Why it matters: Determines if the business can be big enough
- Developer context: Affects long-term strategy and feature priorities
SAM (Serviceable Addressable Market)
- The portion of TAM you can realistically reach
- Example: TAM is $100M, but you can only reach $10M = $10M SAM
- Why it matters: More realistic than TAM
- Developer context: Helps set realistic growth targets
SOM (Serviceable Obtainable Market)
- The portion of SAM you can realistically capture in the next 3-5 years
- Example: SAM is $10M, realistic capture is $2M = $2M SOM
- Why it matters: Used for business planning and forecasting
- Developer context: Affects hiring and infrastructure planning
ICP (Ideal Customer Profile)
- The specific type of customer that’s most valuable to your business
- Example: “Mid-market SaaS companies with 50-500 employees, $5M+ ARR, in the US”
- Why it matters: Focuses marketing and sales efforts
- Developer context: Helps you understand who you’re building for
Beachhead Market
- The first, smallest market segment you target to gain traction
- Example: Start with freelance designers, then expand to agencies
- Why it matters: Easier to dominate a small market than compete in a large one
- Developer context: Affects feature priorities and messaging
Marketing & Acquisition
CAC Payback & Unit Economics
Unit Economics: The profit/loss on a single customer transaction
Example:
- Customer pays $100/month
- Cost to serve (hosting, support): $20/month
- Gross margin: $80/month
- CAC: $500
- Payback period: 500 ÷ 80 = 6.25 months
Why it matters: Determines if the business is sustainable
Acquisition Channels
Organic/Viral
- Users find you through word-of-mouth, referrals, or search
- Cost: Low (mostly content creation)
- Why it matters: Most sustainable long-term
- Developer context: Build features that encourage sharing
Paid Ads
- Google Ads, Facebook Ads, LinkedIn Ads, etc.
- Cost: High (per click or per impression)
- Why it matters: Fast but expensive
- Developer context: Affects feature priorities (need to convert quickly)
Content Marketing
- Blog posts, videos, guides that attract organic traffic
- Cost: Medium (time to create)
- Why it matters: Builds authority and trust
- Developer context: Technical content can drive developer adoption
Sales (Outbound)
- Direct outreach to potential customers
- Cost: High (sales team salaries)
- Why it matters: Works for high-ticket products
- Developer context: Sales team needs good product documentation
Partnerships
- Integrations, referrals, co-marketing with other companies
- Cost: Low to medium
- Why it matters: Leverages other companies’ audiences
- Developer context: Requires good API documentation
Conversion Funnel
Awareness → Interest → Consideration → Decision → Retention
- Awareness: People know you exist
- Interest: People are interested in learning more
- Consideration: People are evaluating your product
- Decision: People buy
- Retention: People stay and expand
Why it matters: Each stage has different metrics and optimization strategies
Developer context: Different features optimize different stages (landing page for awareness, onboarding for decision, features for retention)
Conversion Rate
- Percentage of people who take a desired action
- Example: 1,000 visitors, 50 sign up = 5% conversion rate
- Why it matters: Small improvements compound
- Developer context: Improving onboarding by 1% = 1% more customers
Funnel Leakage
- Where people drop off in the conversion funnel
- Example: 1,000 visitors → 500 sign up (50% drop) → 100 activate (80% drop)
- Why it matters: Identifies where to focus optimization
- Developer context: If onboarding has high drop-off, fix that first
Product Strategy
Feature Prioritization
RICE Scoring (Reach, Impact, Confidence, Effort)
- Reach: How many users will this affect?
- Impact: How much will it improve their experience?
- Confidence: How confident are you in these estimates?
- Effort: How much work is required?
- Score: (Reach × Impact × Confidence) ÷ Effort
- Why it matters: Objective way to prioritize features
- Developer context: Helps you understand why certain features are prioritized
MoSCoW Method (Must have, Should have, Could have, Won’t have)
- Must: Critical for launch
- Should: Important but not critical
- Could: Nice to have
- Won’t: Explicitly deprioritized
- Why it matters: Clear scope management
- Developer context: Helps manage expectations
MVP (Minimum Viable Product)
- The smallest version of your product that solves the core problem
- Example: Dropbox MVP was just file syncing, not all the features it has now
- Why it matters: Get to market fast, learn from users
- Developer context: Build the MVP, not the dream product
Feature Creep
- Adding features beyond the original scope
- Why it’s bad: Delays launch, increases complexity, dilutes value
- Developer context: Say “no” to features that aren’t core
Pivot
- Changing your product, market, or business model based on feedback
- Example: Slack started as an internal tool for a gaming company
- Why it matters: Sometimes your original idea isn’t right
- Developer context: Be prepared to change direction quickly
Moat
- Competitive advantage that’s hard to replicate
- Examples: Network effects (more users = more valuable), brand, data, switching costs
- Why it matters: Determines long-term viability
- Developer context: Affects feature priorities (build network effects early)
Sales & Revenue Models
Pricing Models
Freemium
- Free tier with limited features, paid tier with full features
- Example: Slack (free with message history limit), Figma (free with project limit)
- Pros: Low barrier to entry, easy to convert
- Cons: Most free users never convert
- Developer context: Requires clear upgrade path
Subscription (SaaS)
- Monthly or annual recurring payment
- Example: $29/month for all features
- Pros: Predictable revenue, customer loyalty
- Cons: Requires continuous value delivery
- Developer context: Focus on retention and feature updates
Tiered Pricing
- Multiple price points for different customer segments
- Example: Starter ($29), Professional ($99), Enterprise ($299+)
- Pros: Captures different customer segments
- Cons: Complexity, cannibalization
- Developer context: Each tier needs different features
Usage-Based (Pay-as-you-go)
- Pay based on consumption
- Example: AWS (pay per compute hour), Twilio (pay per SMS)
- Pros: Fair pricing, scales with customer
- Cons: Unpredictable revenue, customer anxiety
- Developer context: Requires good metering and billing
One-Time Purchase
- Single payment for perpetual license
- Example: Photoshop (before Creative Cloud)
- Pros: Simple, high upfront revenue
- Cons: No recurring revenue, hard to scale
- Developer context: Rare in modern SaaS
Sales Metrics
Sales Cycle
- Time from first contact to closed deal
- Example: Enterprise sales might be 6 months, SMB might be 2 weeks
- Why it matters: Affects cash flow and forecasting
- Developer context: Longer sales cycles = need more runway
Win Rate
- Percentage of deals that close
- Example: 100 prospects, 20 close = 20% win rate
- Why it matters: Shows sales effectiveness
- Developer context: If win rate is low, product might not be compelling
Deal Size
- Average revenue per customer
- Example: Average customer pays $500/month = $500 deal size
- Why it matters: Affects sales strategy (high-touch vs. self-serve)
- Developer context: Affects feature priorities (enterprise features vs. SMB features)
Pipeline
- Total value of deals in progress
- Example: 10 deals × $50,000 average = $500,000 pipeline
- Why it matters: Predicts future revenue
- Developer context: Affects hiring and planning
Customer Success & Retention
Onboarding
- The process of getting new customers to their “aha moment”
- Why it matters: Determines if customers stick around
- Developer context: Invest in onboarding, it directly affects churn
Aha Moment
- The moment a customer realizes the value of your product
- Example: Dropbox aha moment is when files sync across devices
- Why it matters: Customers who reach aha moment are more likely to stay
- Developer context: Design features to reach aha moment quickly
Activation Rate**
- Percentage of new users who reach their aha moment
- Example: 100 new users, 40 reach aha moment = 40% activation
- Why it matters: Predicts long-term retention
- Developer context: Improving activation by 10% = 10% more retained customers
Engagement**
- How actively customers use your product
- Measured by: DAU (Daily Active Users), WAU (Weekly Active Users), feature usage
- Why it matters: Engaged customers are less likely to churn
- Developer context: Build features that increase engagement
NPS (Net Promoter Score)**
- How likely customers are to recommend you (0-10 scale)
- Calculation: % Promoters (9-10) - % Detractors (0-6)
- Example: 60% promoters - 20% detractors = 40 NPS
- Why it matters: Predicts growth and churn
- Developer context: NPS feedback guides feature development
CSAT (Customer Satisfaction Score)**
- How satisfied customers are with your product (usually 1-5 scale)
- Why it matters: Identifies unhappy customers
- Developer context: Low CSAT = product issues
Customer Health Score**
- Overall assessment of customer satisfaction and engagement
- Factors: Usage, support tickets, NPS, feature adoption
- Why it matters: Predicts churn risk
- Developer context: Helps prioritize support and feature work
Expansion Revenue**
- Additional revenue from existing customers (upgrades, add-ons)
- Example: Customer upgrades from $50/month to $100/month
- Why it matters: Cheaper than acquiring new customers
- Developer context: Build features that encourage upgrades
Growth & Scaling
Growth Rate**
- Month-over-month or year-over-year growth percentage
- Example: 100 customers last month, 120 this month = 20% MoM growth
- Why it matters: Shows business momentum
- Developer context: Affects infrastructure planning
Viral Coefficient**
- How many new users each existing user brings
- Example: Each user invites 0.5 new users = 0.5 viral coefficient
- Why it matters: Determines if growth is sustainable
- Developer context: Build features that encourage sharing
Viral Loop**
- The mechanism by which users bring other users
- Example: Dropbox referral program (get free storage for each referral)
- Why it matters: Sustainable growth without marketing spend
- Developer context: Design viral loops into the product
Scaling**
- Growing the business while maintaining quality and profitability
- Challenges: Infrastructure, team, processes
- Why it matters: Determines long-term success
- Developer context: Affects technical architecture decisions
Blitzscaling**
- Rapid growth prioritizing speed over efficiency
- Example: Uber’s aggressive expansion into new cities
- Pros: Market dominance, network effects
- Cons: Burn rate, quality issues
- Developer context: Requires robust infrastructure
Funding & Business Models
Bootstrapping**
- Building a company with your own money, no external funding
- Pros: Keep control, no dilution
- Cons: Slower growth, limited resources
- Developer context: Affects hiring and feature priorities
Seed Funding**
- Early-stage funding to build MVP and validate idea
- Typical amount: $100K - $1M
- Why it matters: Gives runway to find PMF
- Developer context: Affects hiring and scope
Series A/B/C**
- Later-stage funding rounds as company grows
- Series A: $2M - $15M (scale after PMF)
- Series B: $15M - $50M (expand market)
- Series C: $50M+ (scale globally)
- Developer context: Each round brings new priorities and pressure
Valuation**
- Estimated worth of the company
- Calculated as: Revenue × Multiple (varies by industry)
- Example: $1M ARR × 10x multiple = $10M valuation
- Why it matters: Determines dilution in funding rounds
- Developer context: Affects equity compensation
Burn Rate vs. Revenue**
- If burn rate > revenue, company is losing money
- If revenue > burn rate, company is profitable
- Why it matters: Determines runway and urgency
- Developer context: Affects decision-making speed
Market & Competition
Market Size**
- Total addressable market (TAM), serviceable addressable market (SAM), serviceable obtainable market (SOM)
- Why it matters: Determines business potential
- Developer context: Affects long-term strategy
Competitive Advantage**
- What makes your product better than competitors
- Examples: Better UX, lower price, faster, more features
- Why it matters: Determines if you can win
- Developer context: Affects feature priorities
Positioning**
- How you want customers to perceive your product
- Example: “Slack is email for teams” (positioning against email)
- Why it matters: Guides marketing and product decisions
- Developer context: Affects feature design and messaging
Differentiation**
- What makes you different from competitors
- Example: Notion is “all-in-one workspace” vs. Asana (project management only)
- Why it matters: Determines if customers will choose you
- Developer context: Build features that differentiate
First-Mover Advantage**
- Benefits of being first to market
- Pros: Brand recognition, user base, network effects
- Cons: Educate market, absorb mistakes
- Developer context: Affects urgency and scope
Network Effects**
- Product becomes more valuable as more people use it
- Example: Slack is more valuable with more team members
- Why it matters: Creates defensible moat
- Developer context: Design features that encourage network effects
Analytics & Metrics
Cohort Retention**
- Percentage of customers from a cohort who stay over time
- Example: 100 customers from January, 80 still active in February = 80% retention
- Why it matters: Shows if product is sticky
- Developer context: Improving retention by 5% = 5% more revenue
Churn Cohort**
- Percentage of customers who leave each month
- Example: 100 customers, 5 leave = 5% churn
- Why it matters: Predicts revenue decline
- Developer context: Focus on reducing churn
Payback Period**
- How long until a customer pays back their acquisition cost
- Example: $100 CAC, $40 profit/month = 2.5 months payback
- Why it matters: Determines cash flow
- Developer context: Shorter payback = healthier business
Burn Multiple**
- How much you spend to generate $1 of revenue
- Example: Spend $3 to generate $1 = 3x burn multiple
- Why it matters: Shows efficiency
- Developer context: Affects hiring and spending decisions
Rule of 40**
- Growth rate + Profit margin should equal 40%
- Example: 30% growth + 10% profit margin = 40 (healthy)
- Why it matters: Balances growth and profitability
- Developer context: Affects feature priorities
Conclusion: Speak the Language
Understanding business terminology isn’t about becoming a business person. It’s about communicating effectively with the people who make product decisions.
When you understand:
- CAC and LTV, you understand why certain features matter for acquisition and retention
- Churn and NRR, you understand why product quality is critical
- PMF and TAM, you understand the long-term vision
- Pricing models, you understand why certain features are in certain tiers
- Sales cycles, you understand why enterprise features take priority
You become a better engineer. You can advocate for technical solutions that solve business problems. You can understand trade-offs. You can contribute meaningfully to strategy.
The next time someone says “We need to improve our CAC to LTV ratio,” you’ll know exactly what they mean—and you’ll know how to help.
Quick Reference Glossary
| Term | Definition | Why It Matters |
|---|---|---|
| MRR | Monthly recurring revenue | Shows business health |
| ARR | Annual recurring revenue | Used for valuation |
| Churn | % of customers who leave | Shows product stickiness |
| CAC | Cost to acquire one customer | Determines profitability |
| LTV | Lifetime value of a customer | If LTV > CAC, business works |
| PMF | Product-market fit | Inflection point for scaling |
| TAM | Total addressable market | Determines business potential |
| NRR | Net revenue retention | Shows if product is getting stickier |
| Cohort | Group of customers by signup date | Tracks product improvements |
| Activation | % reaching aha moment | Predicts retention |
| Engagement | How actively customers use product | Predicts churn |
| NPS | Net promoter score | Predicts growth |
| Viral Coefficient | New users per existing user | Determines sustainable growth |
| Burn Rate | Monthly spending | Determines runway |
| Runway | Months until out of money | Determines urgency |
| ICP | Ideal customer profile | Focuses marketing efforts |
| Beachhead | First market segment | Easier to dominate |
| Moat | Competitive advantage | Determines long-term viability |
| Positioning | How customers perceive you | Guides marketing |
| Unit Economics | Profit/loss per customer | Determines sustainability |
Master these terms. Speak the language. Build better products.
Comments