// types/fundraising.ts

export type InvestorStage = 'angel' | 'seed' | 'series_a' | 'growth';
export type Sector = 'saas' | 'fintech' | 'ai_infra' | 'marketplace';
export type PipelineStatus = 'sourced' | 'contacted' | 'meeting' | 'dd' | 'ts' | 'closed' | 'rejected';

export interface InvestorProfile {
  id: string;
  firm: string;
  partner: string;
  stages: InvestorStage[];
  sectors: Sector[];
  checkSize: { min: number; max: number }; // in USD
  thesis: string;
  fitScore?: number;
}

export interface StartupMetrics {
  mrr: number;
  growthRate: number; // Monthly %
  burnRate: number;
  runwayWeeks: number;
  cac: number;
  ltv: number;
  sector: Sector;
  currentStage: InvestorStage;
}

export interface PipelineLead {
  investorId: string;
  status: PipelineStatus;
  lastInteraction: Date;
  nextAction: string;
  feedback: string[];
  probability: number; // 0.0 to 1.0
}

// engine/fitScorer.ts

import { InvestorProfile, StartupMetrics } from '../types/fundraising';

export interface FitResult {
  score: number;
  reasons: string[];
  isMatch: boolean;
}

export function calculateInvestorFit(
  investor: InvestorProfile,
  startup: StartupMetrics
): FitResult {
  let score = 0;
  const reasons: string[] = [];

  // 1. Stage Alignment (Weight: 30%)
  const stageMatch = investor.stages.includes(startup.currentStage);
  if (stageMatch) {
    score += 30;
    reasons.push('Stage alignment confirmed');
  } else {
    reasons.push('Stage mismatch');
    return { score: 0, reasons, isMatch: false };
  }

  // 2. Sector Fit (Weight: 30%)
  const sectorMatch = investor.sectors.includes(startup.sector);
  if (sectorMatch) {
    score += 30;
    reasons.push('Sector fit verified');
  } else {
    reasons.push('Sec

tor outside thesis'); // Allow slight score for adjacent sectors if data supports, // but generally low probability. }

// 3. Check Size Compatibility (Weight: 20%) const targetRaise = startup.burnRate * startup.runwayWeeks / 4.3; // Approx monthly burn * weeks / 4.3 const withinCheckSize = targetRaise >= investor.checkSize.min && targetRaise <= investor.checkSize.max;

if (withinCheckSize) { score += 20; reasons.push('Check size compatible'); } else { reasons.push('Check size mismatch'); }

// 4. Metric Thresholds (Weight: 20%) // Example: Seed stage requires >$10k MRR or >20% MoM growth if (startup.currentStage === 'seed') { if (startup.mrr >= 10000 || startup.growthRate >= 20) { score += 20; reasons.push('Key metrics meet threshold'); } else { reasons.push('Metrics below threshold'); } }

return { score, reasons, isMatch: score >= 60 // Threshold for engagement }; }

#### 3. Pipeline Management Class

This class manages the state transitions and provides analytics hooks.

```typescript
// pipeline/fundraisingPipeline.ts

import { PipelineLead, PipelineStatus } from '../types/fundraising';

export class FundraisingPipeline {
  private leads: Map<string, PipelineLead> = new Map();

  addLead(investorId: string, lead: PipelineLead): void {
    this.leads.set(investorId, {
      ...lead,
      probability: this.calculateBaseProbability(lead.status)
    });
  }

  updateStatus(investorId: string, newStatus: PipelineStatus): void {
    const lead = this.leads.get(investorId);
    if (!lead) throw new Error(`Lead ${investorId} not found`);

    lead.status = newStatus;
    lead.lastInteraction = new Date();
    lead.probability = this.calculateBaseProbability(newStatus);
    
    // Trigger analytics event
    this.emitEvent('status_change', { investorId, from: lead.status, to: newStatus });
  }

  getPipelineMetrics() {
    const allLeads = Array.from(this.leads.values());
    const weightedValue = allLeads.reduce((sum, lead) => sum + (lead.probability * 1000), 0); // Placeholder $1k unit
    
    return {
      totalLeads: allLeads.length,
      weightedValue,
      conversionRate: this.calculateConversionRate(allLeads),
      avgVelocity: this.calculateVelocity(allLeads)
    };
  }

  private calculateBaseProbability(status: PipelineStatus): number {
    const probs: Record<PipelineStatus, number> = {
      sourced: 0.05,
      contacted: 0.10,
      meeting: 0.25,
      dd: 0.50,
      ts: 0.85,
      closed: 1.0,
      rejected: 0.0
    };
    return probs[status];
  }

  private emitEvent(event: string, payload: any): void {
    // Integration point for analytics dashboard
    console.log(`[FOS Event] ${event}:`, payload);
  }

  // ... helper methods for conversion and velocity calculations
}

Rationale for TypeScript

TypeScript is mandated for the FOS implementation to enforce data integrity. Fundraising involves high-stakes numerical data; a typo in MRR or a misclassified sector can derail a round. Strong typing catches these errors at compile time. Additionally, the interfaces serve as living documentation for the data room structure, ensuring that the technical representation of the startup matches the legal and financial documentation.

Pitfall Guide

Technical founders often apply engineering rigor to product but neglect it in fundraising, leading to predictable failure modes.

1. Ignoring the Feedback Loop:

   • Mistake: Treating a rejection as a binary outcome without capturing the reason.
   • Correction: Implement a mandatory feedback field in the pipeline. Aggregate rejection reasons weekly. If "Valuation" appears in >30% of rejections, adjust the ask. If "Traction" dominates, delay fundraising.

2. Metric Inconsistency:

   • Mistake: Presenting MRR in the deck but showing ARR in the data room, or using different definitions of "Active User."
   • Correction: Define a "Single Source of Truth" for all metrics. The FOS schema must dictate the metric definitions. Any deviation must be explicitly documented and justified.

3. Spray-and-Pray Outreach:

   • Mistake: Contacting 200 investors with a generic email. This burns reputation and yields low conversion.
   • Correction: Use the Fit Score to prioritize the top 20 investors. Personalize outreach based on the investor's thesis and portfolio. Quality of engagement outweighs quantity of touches.

4. Running Out of Runway During the Process:

   • Mistake: Starting fundraising when runway is <6 months. Investors smell desperation and adjust terms accordingly.
   • Correction: Initiate fundraising when runway is >9 months. The FOS velocity metrics should predict close dates. If velocity drops, trigger contingency plans (bridge, cost reduction) immediately.

5. Valuation Obsession:

   • Mistake: Maximizing valuation at the expense of terms, lead investor quality, or speed.
   • Correction: Model the "Total Cost of Capital." A lower valuation with a strong lead investor who accelerates product growth may yield higher founder equity value at exit than a high valuation with passive capital. Use the Decision Matrix to evaluate trade-offs.

6. Technical Debt in the Pitch:

   • Mistake: The pitch deck claims technical moats that cannot be verified or are easily replicable.
   • Correction: Prepare a technical deep-dive appendix. Include architecture diagrams, IP status, and security audits. Be prepared to discuss technical risks openly; investors respect transparency over hype.

7. Neglecting the Data Room:

   • Mistake: Uploading a disorganized folder structure during due diligence.
   • Correction: Structure the data room to match the FOS pipeline stages. Have a "DD Ready" state that can be activated instantly. Use tools that track which documents investors are viewing to gauge interest.

Production Bundle

Action Checklist

• Define ICP for Investors: Create the InvestorProfile schema and populate with target firms based on sector and stage.
• Instrument Metrics: Audit all startup metrics. Ensure MRR, CAC, LTV, and Burn Rate are calculated consistently and stored in the FOS.
• Build Fit Model: Implement calculateInvestorFit and run scoring on the target list. Filter out investors with isMatch: false.
• Initialize Pipeline: Import scored leads into the FundraisingPipeline. Set initial status to sourced.
• Configure Analytics Dashboard: Connect the FOS event stream to a visualization tool (e.g., Metabase, Looker) to monitor pipeline health.
• Prepare Data Room: Structure documents according to the schema. Verify consistency with FOS metrics.
• Launch Sequenced Outreach: Begin contact with top-tier leads. Log all interactions in the pipeline.
• Review Weekly: Analyze rejection reasons and velocity. Adjust targeting or metrics as needed.

Decision Matrix

Use this matrix to determine the fundraising strategy based on startup context.

Scenario	Recommended Approach	Why	Cost Impact
High Growth, <6 Months Runway	Bridge Round + Aggressive FOS	Need immediate capital; FOS maximizes speed.	Lower valuation on bridge; higher dilution.
Strong Product, Low Traction	Pre-Seed / Angel Focused	VCs require traction; angels buy vision/team.	Lower capital raise; faster close.
Technical Moat, Complex Sales	Strategic Investor / Corporate VC	Alignment on tech roadmap; longer sales cycles.	Potential loss of control; strategic constraints.
Bootstrapped, Profitable	Non-Dilutive / Revenue-Based Financing	Avoid dilution; capital matches cash flow.	Higher cost of capital; repayment obligations.
Series A Ready, Market Downturn	Defensive Fundraising + FOS Optimization	Extend runway; focus on efficiency metrics.	Dilution protection via strict fit scoring.

Configuration Template

Copy this template to initialize the FOS configuration. Adjust weights and thresholds based on your specific market conditions.

// config/fos.config.ts

import { FundraisingConfig } from '../types/config';

export const defaultConfig: FundraisingConfig = {
  pipeline: {
    stages: ['sourced', 'contacted', 'meeting', 'dd', 'ts', 'closed', 'rejected'],
    stallThresholdDays: 7, // Alert if lead stays in stage > 7 days
  },
  scoring: {
    weights: {
      stage: 0.3,
      sector: 0.3,
      checkSize: 0.2,
      metrics: 0.2,
    },
    thresholds: {
      minFitScore: 60,
      metricThresholds: {
        seed: { mrr: 10000, growth: 20 },
        seriesA: { mrr: 100000, growth: 15 },
      },
    },
  },
  outreach: {
    maxDailyContacts: 5, // Prevent spam flags
    followUpIntervalDays: 3,
    personalizationFields: ['portfolio_company', 'recent_tweet', 'thesis_match'],
  },
  metrics: {
    definitions: {
      mrr: 'recurring_revenue_monthly',
      churn: 'logo_churn_percentage',
      runway: 'cash_balance / monthly_burn',
    },
    refreshInterval: 'daily',
  },
};

Quick Start Guide

Get your Fundraising Operating System running in under 5 minutes.

1. Initialize Project:

   mkdir fundraising-os && cd fundraising-os
   npm init -y
   npm install typescript zod
   npx tsc --init
   

2. Add Schema and Config: Create types/fundraising.ts and config/fos.config.ts using the code blocks from this article. Run npx tsc to verify type safety.

3. Seed Data: Create a seed.ts script to import a CSV of investors. Map columns to InvestorProfile and run calculateInvestorFit. Save results to a JSON file or local database.

   node seed.ts
   

4. Launch Pipeline: Instantiate FundraisingPipeline, load seeded leads, and generate the initial metrics report.

   node pipeline-runner.ts
   

   Output should display: Total Leads: 50 | Weighted Value: $X | Conversion Rate: Y%.

5. Integrate Dashboard: Point your analytics tool to the pipeline event log. Configure a dashboard with widgets for "Pipeline Funnel," "Top Investors by Fit," and "Runway Projection."

You now have a production-grade system to manage capital acquisition. Iterate based on data, not intuition.