VC Technical Infrastructure

Venture ops infrastructure for funds, accelerators, and operator-led programs: clean data models, right-sized automations, dashboards, Slack ops, and production workflows that replace manual coordination.

Worked with
Iterative

Context

Funds, accelerators, and venture studios often run on a fragile mix of Airtable bases, Notion docs, Slack threads, email templates, spreadsheet trackers, and half-connected automations. That works until volume increases, ownership blurs, or the team starts layering AI on top of messy process data.

I help teams turn that sprawl into a usable operating system. The work starts with auditing how the team actually operates, then designing the right boundary between database, automation, dashboard, and custom software. Airtable or Notion can remain the source of truth. Pipedream or n8n can handle cross-system orchestration. Custom apps are reserved for workflows that need richer UI, stronger configuration, or better control.

This pattern was proven inside Iterative, where I owned the operating stack behind a 70+ company VC portfolio: application intake, founder communication, partner assignment, interview scheduling, IC preparation, term sheet generation, SLA reporting, and portfolio dashboards.

What I Build

  • Ops Audit & System Map: Translate messy team workflows into a clear operating model: who owns each step, what data matters, where state should live, and which handoffs are currently fragile.
  • Data Model Design: Normalise Airtable, Notion, spreadsheet, and CRM structures so automations and AI systems have clean records to work with instead of ambiguous process state.
  • Right-Sized Automation: Use Airtable automations for table-native state changes, Pipedream or n8n for cross-system workflows, and custom apps only when configuration, reporting, or control justify the build.
  • Document & Asset Pipelines: Build flows for pitch decks, attachments, memos, reports, and founder materials so files are stored, named, linked, and retrievable without manual cleanup.
  • Slack-Native Operations: Route reminders, SLA alerts, approvals, handoffs, infrastructure health checks, and exceptions into the channels where teams already operate.
  • Dashboards & Reporting: Build fund, program, and portfolio dashboards for funnel health, SLA tracking, conversion, partner workload, and portfolio performance.
  • Production Guardrails: Add filtered triggers, runtime checks before transactions, idempotency, rate limits, cost limits, and clear ownership between no-code automations and custom code.

Stack & Use Cases

AirtablePipedreamn8nNotionSlackMetabasePostgreSQLAirbyteVenture operationsDeal flow CRMApplication intakeFounder communicationsIC preparationSLA dashboardsPortfolio reportingAsset backup pipelines

Outcome

  • Manual coordination replaced by visible, reliable operating workflows
  • Cleaner data models that support automation, reporting, and AI layers
  • Fewer missed handoffs across applications, interviews, approvals, follow-ups, and reporting cycles
  • Clearer SLA visibility, workload tracking, and operational accountability
  • A reusable venture-ops playbook for turning messy internal process into production-grade infrastructure