VC & Investing: How Venture Capital Works
Startup Intelligence · The CODEW Intelligence
The practical operating layer for building companies that survive contact with reality — hiring, product, cash, KPIs, governance, and the decisions founders face when resources are limited and time is short.
Building a startup is not just about raising capital or finding product-market fit. It is about making thousands of operating decisions under uncertainty — and building a company that can survive contact with reality.
Fundraising decks get the attention. Operations determines whether you get to keep playing. Most startups don't die from one catastrophic mistake. They die from compounding operational drag: hiring too early, building too much, burning too fast, tracking the wrong metrics, and confusing motion with progress.
What Is Startup Operations?
Startup Operations is how you build a company that works in the real world. It is not generic startup advice. It is operator intelligence — the systems, decisions, and tradeoffs that determine whether a startup can execute consistently.
At its core, Startup Operations covers five realities every founder faces:
Turning strategy into execution — An idea is not a plan. A plan is not a product. Startup operations is the translation layer between what you want to build and what actually gets built.
Managing limited resources — You will never have enough people, money, or time. Operations is about allocation under constraint.
Making decisions with incomplete information — You will be wrong. Often. Good operations shortens the feedback loop between being wrong and knowing it.
Building systems before complexity overwhelms you — What works for 3 people breaks at 10. What works at 10 breaks at 30. Systems must be built slightly ahead of the chaos they are meant to contain.
Balancing growth with survival — Growth is optional in the short term. Survival is not. Operations maintains that balance.
If Startup Strategy is what to do and Startup Funding is how to finance it, Startup Operations is how to actually do it without breaking the company.
The Startup Operating System
Every startup runs on an operating system, whether intentional or accidental. The best founders make it intentional. The seven core areas:
People → Product → Cash → Customers → Capital → Systems → Governance
People — Who does the work and how they work together.
Product — What you build and why it matters.
Cash — How long you can keep building.
Customers — Who pays, why they pay, and whether they stay.
Capital — When and how you raise external funding.
Systems — How work gets done when founders aren't in the room.
Governance — How decisions are made, documented, and accounted for.
These areas are interdependent. A hiring decision is a cash decision. A product decision is a customer decision. A pricing decision is a capital decision.
A startup doesn't fail because one decision was wrong. It often fails because several small operational problems compound faster than the company can correct them.
The job of Startup Operations is to see compounding problems early — before they become existential.
Hiring & People
The first 10 hires define the next 100. Get this wrong, and everything else gets harder.
When should a startup hire? — Only when pain is validated and repeatable. If a founder is overwhelmed by sales calls for three months straight, that's a hiring signal. If you're hiring because you raised money and "need to grow the team," that's not.
Who should be the first employees? — Problem-solvers with range. Your first five people will do five jobs each. You need high-autonomy generalists who can own an outcome, not a job description. Specialists come later, when a function is validated and needs to be scaled.
What should founders continue doing themselves? — Longer than feels comfortable. Founders should own product direction, first 10 customer relationships, fundraising narrative, and hiring bar. Outsource execution only after you've done it yourself enough to know what good looks like.
Generalists vs. Specialists — Hire generalists to discover, specialists to scale. A generalist finds the channel; a specialist optimizes it. Most early-stage startups hire specialists too early and pay for expertise they can't yet leverage.
Hiring for the next stage, not the current crisis — Don't hire to fix last week's fire. Hire for the company you need to be in 12–18 months if your core assumptions are correct.
Compensation and equity — Early equity should be meaningful and tied to 4-year vesting with a 1-year cliff. Be transparent: base salary buys time, equity buys ownership. If someone only wants salary, they want a job, not a startup.
Building a small, high-leverage team — The best early teams are small and over-talented. 5 exceptional people will outperform 12 average ones every time — with lower burn, faster communication, and less management overhead.
CODEW Lens: Headcount should follow validated business needs — not fundraising milestones. If hiring doesn't reduce a validated bottleneck or unlock validated growth, it increases burn without increasing learning.
MVP & Product Execution
Most founders overbuild their first product and under-learn from it.
What an MVP actually means — An MVP is not a prototype. It is not a buggy v1. It is the smallest credible product that lets you test your riskiest assumption with real users. An MVP is not a cheap version of the final product. It is the fastest credible way to test whether a valuable problem exists.
Avoiding overbuilding — Founders overbuild for two reasons: fear of judgment and confusion about who the MVP is for. Your MVP is not for TechCrunch. It's for 10 design partners who have the problem badly enough to tolerate imperfection. Rule: If you aren't embarrassed by your MVP, you waited too long.
Build vs. Test — Before you build, test. Can you validate demand with interviews, a landing page, a concierge service, a clickable prototype, or a manual process behind the scenes? Code is the most expensive way to test an idea.
Customer feedback — Separate feedback into three buckets:
- Problem feedback — Do they have this problem, and how do they solve it today?
- Solution feedback — Does this approach actually help?
- Willingness to pay — Will they change behavior and pay for it?
Most founders only ask bucket 2. Buckets 1 and 3 are what matter.
Technical debt — Some technical debt is strategic. Shipping fast with messy code is rational when you're searching for product-market fit. It becomes fatal when you find fit and can't scale. Document your shortcuts. Plan to repay debt once retention proves you built something worth scaling.
When to add features — Only when existing users ask for the same thing repeatedly, and it aligns with your core wedge. Feature requests are not a roadmap. They are data points about jobs users are trying to do.
When to kill a product idea — When retention is flat despite iteration, when your best users don't care if you shut down, and when you've tested the core value proposition in three different forms. Persistence is admirable; delusion is expensive.
Burn Rate & Runway
Cash is the ultimate operating constraint. You can be wrong about many things if you manage cash well. You cannot be wrong about cash for long.
Connects to: Startup Runway Calculator In Development
Gross Burn — Total cash out each month. Everything.
Net Burn — Gross Burn minus Revenue. This is what actually depletes your bank account.
Fixed Expenses — Rent, salaries, software, insurance — costs that don't change with revenue.
Variable Expenses — Hosting that scales with usage, sales commissions, payment processing fees.
Runway = Cash Available ÷ Monthly Net Burn
If you have $600,000 in the bank and burn $40,000 net per month, you have 15 months of runway.
But runway is a strategic variable, not merely an accounting metric.
Hiring impact — A single $120k engineer at $10k/month fully-loaded doesn't just cost $10k. In a 15-month runway company, that hire cuts runway by 2–3 months. Always calculate: "What does this hire do to runway, and what must it unlock to justify it?"
Revenue assumptions — Never calculate runway on projected revenue. Calculate it on today's net burn, then model scenarios. Optimistic revenue forecasting is the fastest way to run out of money.
Fundraising timing — Start raising when you have 9–12 months of runway left, not 3. Fundraising takes 4–6 months when it goes well. If you start at 4 months, you are negotiating from weakness.
Scenario planning — Run three models every month:
- Base Case — Current burn, current growth.
- Survival Case — What if revenue goes to zero for 3 months and hiring freezes? How long do you live?
- Growth Case — What if you make 2 key hires? How much faster must you grow to maintain 12+ months runway?
Founders who only run one scenario are surprised by reality. Founders who run three are prepared for it.
Pivot or Persevere
Almost every successful startup considered quitting or pivoting. The skill is knowing which.
Is it a product failure? — Users try it once and leave. The problem is real, but your solution doesn't solve it 10x better than alternatives.
Is it weak customer demand? — You can't get meetings. Or you get meetings, but no one converts to paid. The problem may not be painful or frequent enough.
Is it poor retention? — You can acquire users but can't keep them. This is often the clearest sign of product-market misfit. Acquisition is marketing; retention is product.
Is it the wrong market? — You have passionate users who love the product, but there are only 200 of them in the world. A great product in a bad market is still a bad business.
Is it pricing? — Users love it but won't pay your price. Or they pay but churn when you raise the price. Test packaging and willingness-to-pay before rebuilding the product.
Is it distribution? — The product works, retention is strong for those who find it, but you can't find them efficiently. This is a go-to-market problem, not a product problem.
A problem worth solving differently — strong problem signal, weak solution signal, users are hacking together alternatives. Pivot the solution.
From a problem that isn't worth solving — weak problem signal no matter how you frame it. No urgency, no budget, no behavior change. Change the problem.
CODEW Lens: Persevere when retention and love from a small cohort is growing. Pivot when you've iterated on solution three times and retention hasn't moved.
Advisory Boards & Governance
You don't need an advisory board to start. You need one when you face problems you haven't solved before.
When an advisory board makes sense — When you enter enterprise sales for the first time, when you need FDA or regulatory guidance, when you are expanding to a new market, or when your cap table is getting complex. Advisors should fill specific experience gaps.
Advisors vs. employees — Employees execute. Advisors provide pattern recognition and introductions. If you need someone to do the work 20 hours a week, hire them. Don't advisory-wash a part-time employee role.
Advisors vs. investors — Investors are aligned with financial return. Good advisors are aligned with your learning. The best advisors will tell you not to raise when raising is premature.
Selecting useful advisors — Avoid prestige-only advisors. Look for:
- Someone who solved your next problem in the last 2–3 years
- Operator experience, not just commentary experience
- Willingness to make introductions and take your call
- No direct conflict with your business
The best advisor isn't the most famous person you can recruit. It's the person who has already solved the problem you're about to face.
Compensation and equity — Typical advisor grants: 0.1% to 0.5% for early-stage, vesting over 2 years with no cliff, no board seat. More if they are truly hands-on. Document expectations in a simple advisor agreement: time commitment, term, and what "helpful" means.
Board preparation and governance discipline — Even without a formal board, run yourself like you have one. Monthly investor updates, a clean cap table, documented decisions, and quarterly goals reviewed honestly. Governance discipline when no one requires it is what makes you fundable when it counts.
Startup Data Room
Your data room is your operational truth. Investors, partners, and acquirers will all ask for it eventually. Building it early forces you to be organized.
Connects to: Startup Data Room In Development
Corporate documents — Incorporation, bylaws, EIN, founder agreements, 83(b) filings.
Cap table — Fully diluted ownership, option pool, SAFEs/notes with terms, vesting schedules. Use a single source of truth.
Financials — P&L, balance sheet, cash flow, burn and runway models, last 12–18 months actuals, next 12 months forecast with assumptions.
Customer metrics — Revenue by customer, retention cohorts, pipeline, CAC, LTV, churn analysis.
Contracts — Customer contracts, vendor agreements, partnership agreements.
IP documentation — Invention assignments, IP licenses, open-source audits, trademarks, patents.
Employment agreements — Offer letters, IP assignment, non-competes, employee handbook, contractor agreements.
Investor documents — Prior financing docs, board consents, investor updates.
Product / technical information — Architecture overview, roadmap, security practices, key technical debt.
Legal / compliance materials — Litigation, regulatory filings, data privacy policies, insurance.
A messy data room signals messy operations. A clean data room signals a founder who can run a company. Build it before you need it — you will need it when you have the least time to build it.
Startup KPIs & Operating Metrics
Founders drown in dashboards. Good operators track decision-useful metrics. Your operating dashboard should answer: Are we building something people want, can we acquire them efficiently, and can we survive long enough to scale?
Revenue — MRR/ARR, new vs. expansion vs. churned. Not just top-line growth, but quality of growth.
Growth — Month-over-month and year-over-year, segmented by channel and cohort.
Gross Margin — Revenue minus cost of goods sold. Determines whether scale makes you more or less profitable.
Burn & Runway — Net burn and months remaining. Non-negotiable, updated weekly.
CAC — Fully-loaded cost to acquire a paying customer.
LTV — Gross profit you earn from a customer before they churn.
Retention & Churn — NRR (Net Revenue Retention) and logo retention. If NRR > 100%, your existing customers are growing.
Conversion — Lead to opportunity to closed-won. Where does your funnel break?
Cash efficiency — Burn multiple = Net Burn ÷ Net New ARR. <1.5 is excellent, >3 is warning.
Headcount productivity — Revenue per employee, or ARR per head. Measures whether hiring is creating leverage.
Don't track 30 KPIs. Track 8–10 that drive decisions. Every metric should have an owner, a target, and a defined action if it misses. If a metric doesn't change a decision, it's vanity. Remove it.
Building a Startup That Survives Contact With Reality
Ideas don't survive contact with reality because they are brilliant. Companies survive because they are disciplined and adaptable. A company that survives needs: cash discipline + product discipline + hiring discipline + customer discipline + strategic flexibility.
Surviving downturns — Cut burn early and deeply once. Rolling small cuts kills morale without extending runway meaningfully. Protect the core product and customer team.
Surviving missed targets — Targets will be missed. The operating failure is not missing; it's learning nothing from the miss. Do a post-mortem: What assumption broke? What changes now?
Surviving failed launches — Most launches underwhelm. Measure learning, not headlines. Did you get 10 deep customer conversations? Did you learn one thing that changes v2? That's success for an early launch.
Surviving fundraising delays — Assume your round takes twice as long as planned. Extend runway to 18 months before you start, build relationships 6 months before you need them, and have a survival plan that doesn't require new capital.
Surviving customer concentration — If one customer is >30% of revenue, you don't have product-market fit; you have consulting. Diversify before that customer has leverage over your roadmap.
Surviving key-person risk — Document critical processes. No single person should be the only one who knows how billing works, how deployment happens, or how your biggest customer is managed.
Surviving unexpected expenses — Keep a 10–15% cash buffer outside your runway calculation. Lawsuits, tax bills, and infrastructure overages don't ask permission.
Surviving market changes — Markets move. Regulations change. Competitors launch. Resilience is not predicting the future; it's maintaining enough cash, low enough fixed costs, and fast enough learning cycles to adapt when it changes.
The Startup Survival Stack
A proprietary framework for assessing operational readiness across Startup Intelligence. Use it as a monthly operating review. Score each layer Red / Yellow / Green.
1. People — Can we build the right team? Do we have high-leverage generalists with a low coordination cost?
2. Product — Are we solving a real problem? Have we validated with retention, not just interviews?
3. Customers — Will people consistently pay? Is retention growing in a defined cohort without heroic effort?
4. Cash — Can the company fund itself long enough to learn? Do we have 12+ months of runway on current burn and a survival plan?
5. Capital — When and how should we raise? Are we raising from strength with clean governance and metrics, or from desperation?
6. Systems — Can the company operate without everything depending on the founders? Are critical processes documented and delegated?
7. Resilience — Can the company survive when assumptions are wrong? Do we have scenario plans, margin for error, and the discipline to cut early?
If three or more layers are Red, stop trying to grow. Fix survival first.
Future Startup Operations Products
This hub will expand into an operator toolkit. Each product turns the operating principles on this page into a working tool.
Startup Runway Calculator (In development)
Model cash, burn, and survival scenarios against real operating conditions.
Startup Hiring Calculator (In development)
Understand the true runway cost of every hire before you make the offer.
Startup KPI Dashboard (In development)
Track the 8–10 metrics that actually drive operating decisions.
Startup Fundraising Readiness Score (In development)
Assess whether you're raising from strength or from desperation.
Startup Operating Scorecard (In development)
Score the seven layers of the Survival Stack on a monthly cadence.
Startup Data Room (In development)
Build the operational truth investors, partners, and acquirers will ask for.
Founder Operating Playbooks (In development)
Step-by-step guides for recurring operator decisions.
Startup Survival Mode (In development)
Runway extension plans and cut-early frameworks for downturns.
The strongest startups are not necessarily the ones with the most capital, the fastest hiring, or the biggest ambitions. They are the companies that learn quickly, control their burn, allocate people intelligently, adapt when assumptions break, and build enough operational discipline to survive long enough for the opportunity to compound.
Startup Operations is not about playing it safe. It is about building a company that earns the right to be ambitious — by surviving reality long enough to change it.
Methodology & Data Philosophy
Startup Operations is part of The CODEW Intelligence. It draws on operator experience, company disclosures, funding announcements, financial filings, and structured research on startup execution. Detailed methodology is published on individual methodology pages linked from each product and tracker.
Three principles govern the work.
Separate principles from opinion. Operating principles are stated as principles. Judgment is labeled as judgment.
Build tools, not just content. Every principle on this page is designed to become a working calculator, scorecard, or dashboard.
Update as the operating environment changes. Startup operations are not static. The page is a standing resource, not a one-time guide.
Explore Startup Intelligence
Explore the operating tools, funding intelligence, valuation research, and founder resources covering the decisions founders face from formation through growth and fundraising.
Startup Operations · Startup Funding 101 · Startup Valuation · Funding Stages · Dilution · SAFE vs Convertible Notes · Startup Data Room · Founder / Operator Playbooks
Methodology & Sources
Startup Operations draws on operator experience, company disclosures, SEC filings, funding announcements, public financial information, industry research, and other credible public sources. Detailed methodology for each product and tracker is published separately. Metrics and frameworks are labeled as reported, calculated, or CODEW-derived.
The CODEW Stat
7 survival layers · 8 operator tools Startup Operations organizes the founder operating problem into seven interconnected layers — People, Product, Customers, Cash, Capital, Systems, and Resilience — each connected through a common Survival Stack that scores operational readiness before growth decisions are made.
