The State of AI at COTU.
How we use AI across our investment processes today, what we've built, where the gaps are, and what our agent-powered future looks like.
Why this document exists
We are at an inflection point for how venture capital firms operate. AI is no longer a tool you bolt on to existing workflows — it is becoming the infrastructure around which the best investment teams are reorganizing themselves.
At COTU, we've been building in this direction for over a year. Some of what we've done is deliberate and structured. Some of it emerged organically from individual team members experimenting on their own. The result is a patchwork of genuinely impressive automation alongside significant gaps that cost us time and signal every week.
This document is an honest map of where we are. It covers each of our four core processes — deal sourcing, due diligence, portfolio monitoring, and LP relations — assessing what's working, what's missing, and what our next step should be. The goal is to give the whole team a shared view, and to lay the groundwork for building the AI-native version of COTU.
Our investment process & principles
Before mapping where AI fits, it helps to be explicit about what we're optimizing for. Our investment process is designed around seven principles that define how we want to operate as a partnership.
Better alignment
Get all partners on the same facts fast. Every call and internal discussion captured in a shared record.
Speed to decision
First call to term sheet in under 2 weeks via a light DDQ, multi-partner call, and immediate TS on conviction.
Discipline
Focus on high-signal opportunities. Keep outreach, questions, and meetings scoped to what can change the decision.
Depth
Structured DDQs and memo recipes to cover model, market, team, GTM, and competition systematically.
Diversity of thought
All three partners engage live before a term sheet. Each brings an independent perspective before alignment.
Clear decisions
Go/no-go on or the day after the multi-partner call. Pass reasons documented in Attio every time.
Less admin
Standardized documentation and handoffs. Auto-drafting memos and structured question frameworks.
These principles translate into a clear decision pipeline with target timing:
Deck review Day 1–2
Partners review deck against criteria (MENA-focused, Pre-Seed/Seed, cap <$30M, team, market). Pass or progress.
First partner call Day 2–4
Partner meets founder. Assesses depth, clarity, chemistry, and velocity. Notes captured in Granola. Light DDQ may follow.
All-partner call Day 5–7
All three partners join. Decision on the call or next day. Heavy DDQ issued post-alignment.
Term sheet Day 7–14
TS issued same or next day after partner alignment. 30–45 days secured for deeper diligence.
Continuous Q&A + close Day 14+
Fluid thread with founder during DD period. Investment-grade DDQ completed. Documentation finalized in Drive.
Our tech stack
We bias toward tools that integrate well over tools that do everything. Each tool in our stack does one thing exceptionally well — the goal is a setup where data flows automatically between them, not one where we manually move it between silos.
Deal sourcing & screening
This is our most automated process today. The inbound pipeline is built around a centralized email address — dealflow@cotu.vc — that triggers a Zapier workflow the moment a pitch arrives.
The pipeline handles edge cases intelligently: if the email contains a pass, the AI extracts the rejection reason and updates the Attio status automatically. If a Docsend link is present, it extracts the URL and passcode, then downloads the deck directly into the company's Google Drive folder. Confidence scoring flags low-certainty extractions for manual review. Any deal arriving at dealflow@cotu.vc is fully logged, filed, and visible to the team within minutes — with zero manual work.
For outbound, we use Harmonic for founder discovery, but this remains largely ad hoc — no structured workflow or tracking exists yet.
Inbound pipeline
Fully automated end-to-end via Zapier + AI. One of COTU's most mature workflows.
Partner personal emails & WhatsApp
Deals arriving outside dealflow@cotu.vc need to be manually logged into Attio, which doesn't always happen in the moment.
Deck review
Partners use Claude to review decks, but there is no standardized approach across the team. Each partner applies their own method, with no shared scoring or thesis-fit framework.
Outbound sourcing
No structured process. Harmonic used ad hoc by individual partners. No sequencing, no tracking, no outreach drafting.
Due diligence
Our DD process is designed for speed and rigor simultaneously — first call to term sheet in under two weeks, with all three partners engaged before any decision. Meeting notes are automatically captured via Granola, organized into folders by type, and founders are assessed on four dimensions.
The ambition is to auto-draft roughly 70% of the deal memo from notes, deck, and DDQ responses — with partners adding the remaining analytical layer and the system flagging missing questions. In practice, this vision is partially realized. Claude is used to fill the deal memo template, but each partner does this independently, without a shared, standardized workflow.
The goal is recipes that auto-draft ~70% of the memo from notes, deck, and DDQ. Partners add the remaining analysis; the system flags missing questions. Today, we have the ingredients but not yet the recipe running consistently across the team.
COTU investment process doc, 2026Meeting capture via Granola
All calls automatically captured and organized by stage. Notes linkable to Attio.
Attio as system of record
All deals tracked until investment. Pass reasons documented. LP reports sent in bulk. Fundraising pipeline managed.
Deal memo drafting
Claude is used to fill the template from deck + Granola notes, but each partner does this differently. The 70% auto-draft goal is not yet consistently achieved.
Granola → Attio sync
Requires a manual button press per note. Post-call observations depend on individual discipline.
Organizational memory
No system reads across calls, emails, and decks to build shared context. Each partner works from their own notes. No cross-deal pattern recognition.
Portfolio monitoring
We have built a portfolio monitoring platform — backed by Airtable and a Lovable front-end — that extracts KPIs from founder updates automatically and surfaces them in a structured dashboard. The core workflow is validated and functioning as a POC.
The vision for this platform has sharpened significantly. A web dashboard is a solid foundation — on top of that, the priority direction is a Slack-native interface where any partner can ask a question and get an instant, data-backed answer without opening any tool.
Priority direction — Slack-native portfolio intelligence
On top of the dashboard, partners simply type a question in Slack and get an answer drawn from all available data — updates, calls, data rooms, and emails.
Focus on the present, not the past. The priority is knowing how a company is performing now, and what we can do to help. Historical data remains useful as reference context — for example when onboarding a new team member — but the primary use case is current performance and actionability.
Where we capture data:
Performance metrics
- Month-on-month growth
- Monthly compounding growth since investment
- Revenue per employee
- ARR, burn rate
- Company-specific KPIs (users, beds, paid users, etc.)
- Fundraising round data & valuation multiples
- P&Ls from data rooms
Milestone & action tracking
- Critical milestones (major contracts, key customer wins)
- Pivots — capture the why at the moment it happens
- Action items from board calls & quarterly updates
- Proactive reminders on outstanding actions
- Data room intel during fundraising rounds
Portfolio monitoring platform
Core workflow validated and functioning as a POC. Not yet rolled out across the full portfolio.
Slack-native interface
Priority direction identified. Not yet built. Would sit on top of the dashboard and allow instant natural language queries.
Action item tracking
No system today captures and follows up on commitments made during board calls or quarterly reviews.
Slack channels
Real-time founder signal available but not yet integrated into any structured monitoring workflow.
LP relations & admin
Our LP reporting process is one of the most distinctive applications of AI at COTU. Quarterly, we produce Fund I and Fund II reports. Ismail builds the PowerPoint from our template, Amir reviews and adds per-slide commentary, then ElevenLabs generates Amir's voice over each slide. The result is a narrated video presentation sent to LPs alongside the PDF on Docsend — distributed via Attio's bulk send. This personal touch is a meaningful differentiator that very few funds are doing today.
LP report distribution
Attio bulk send, Docsend tracking, ElevenLabs voice narration per slide. Personal and differentiated.
Calendar & booking
Partners use Blockit for scheduling — reducing back-and-forth email overhead.
LP report preparation
Still largely manual. PowerPoint built slide by slide from template. No AI assistance in narrative drafting or data pulling.
Inbound email management
No centralized logic. Each partner manages their own inbox. Signals and updates sometimes stay in personal emails or WhatsApp rather than making it into shared tools.
What's next — our agent team
The next phase of COTU's AI journey is moving from automated workflows to autonomous agents — systems that don't just react to triggers, but actively monitor, reason, and act on behalf of the team.
The pattern that works: give each agent a name, a clear role, and access to the same tools a human teammate would use. Onboard them like employees. Let the team interact with them naturally.
We've already proven we can build tools that fit exactly how we work — the inbound deal pipeline and the portfolio monitoring POC are evidence of that. The agent layer is the natural next step: tools that don't wait to be triggered, but actively work alongside the team every day.
COTU — internal white paper, May 2026The highest-leverage starting point is Maya — the memory agent. Organizational memory benefits every other process simultaneously: better DD alignment, better meeting follow-through, better outbound context. Build one thing well, and the next problem reveals itself.
Build order — process coverage matrix. The table below shows which agents impact which processes. Maya is the clear first build: she is the only agent that touches all four processes simultaneously. Coverage score drives prioritization.
| Process |
MA
Maya
|
NO
Nora
|
KA
Karim
|
ZA
Zara
|
OA
Omar
|
LA
Layla
|
|---|---|---|---|---|---|---|
| Deal sourcing | ||||||
| Due diligence | ||||||
| Portfolio monitoring | ||||||
| LP relations | ||||||
| Coverage score | 4/4 | 1/4 | 1/4 | 1/4 | 1/4 | 1/4 |