Deal Flow to Pipeline
Deal Flow to Pipeline is a routine your Townie AI assistant runs on incoming email: it parses intros, pitch decks, and data room links into structured company and founder fields, logs each one to your deal sheet or CRM, and surfaces the high-priority deals. Term sheets always rise to the top; it never replies to a founder for you.
See it work: Monday's inbound, already a pipeline
Turn raw deal flow into a clean pipeline
How this routine works
Gmail
Google Drive
Google Sheets
HubSpot
Affinity
Outlook
Attio
SalesforceIt runs on incoming email
Every intro, pitch deck, and data room link gets checked against your filters — opportunity types you care about, senders you trust, domains you don't.
It reads and structures the pitch
Company, founder, stage, sector — parsed into clean fields and logged to your deal sheet or CRM, deduped at the thread level. No tracker yet? It creates one.
You see what matters first
High-priority deals surface for you: term sheets always on top, missed founder deadlines escalated, LP and fund-admin mail routed separately.
Deal Flow to Pipeline FAQ
It's a routine your Townie AI assistant runs on incoming email: it parses every intro, pitch deck, and data room link into structured company and founder fields, logs each one to your deal sheet or CRM, and surfaces the high-priority deals so they rise above the noise. You describe it once — the message on this page is that description.
Yes — its only automatic action is logging structured rows to your own tracker. It never replies to founders or sends anything external without you, and access is scoped to the accounts you connect. Read more in our security overview.
With investment-specific logic, not generic urgency: a term sheet attachment is always top focus, a founder who missed a committed deadline gets escalated, and LP or fund-admin mail is handled separately from deal flow entirely.
Your email for the inbound, and somewhere to log — a Google Sheet or your CRM. If the tracker doesn't exist yet, it creates one on first run, so there's no setup before the first deal lands.
Everything is classified against your opportunity-type whitelist, a sender allowlist, and a domain blocklist before it's logged, with a sensitivity threshold you control — and duplicates are caught at the thread level, so one deal never becomes three rows.
No. It parses, logs, and surfaces — that's it. Anything outbound, from a polite pass to a request for the data room, stays with you.
