Poolman Ventures

Workflow map click once to trace a workflow, click again to open its card
Architecture how each ops-stack layer is actually built
Your firmrelationships, market intelligence, knowledge, content, internal ops
Your fundsfund and entity admin, valuations, LP reporting, wind-down
Your dealssource, evaluate, transact, own, exit: sixteen workflows
Your portfolio companiessales, operations, finance, product inside each holding
Surfaces dashboards, artifacts, agents and workspaces, built per workflow SignalTime
Dashboards & signal mailsweekly market signal, KPI and covenant views, pipeline analytics, readiness scoresmarket intelmonitoringpipeline
Artifact generatorsLP decks and letters, memo skeletons, screen memos, NDAs and NBOs, valuation bridges, board prep briefsLP reportingIC memolegalboard packs
Agents & chasersdealbot replies, stale-entry and action nudges, late-numbers chase, dunning, re-engage triggersdealbotnudgesportco ops
Workspaces & platformsDD workspace, closing workspace, value-creation platform, standing vendor data room, portco dev substrateDDVCPexit room
Records of truth structured reality, most of it already in your systems but siloed. We connect and complete it, we do not rebuild it; each record built once, then every surface trusts it. shared: the master chart Context
Fund ledgercalls, distributions, fees, capital accountsfund adminLP reporting
Ownership ledger & entity registrycap tables, deeds, KVK/UBO, STAK and MIP certificatesentity adminFMV cycle
Master chart of accountsevery portco's numbers, comparable; budgets as baselinemonitoringportco close
Deal-flow record & relationship graphevery inbound, every contact and advisor, on your CRMdeal capturerelationships
Market deal recordtransactions, buyers, advisors in your market, incl. KVK-only dealsmarket intelbuyer map
Terms, decisions & obligationsterms registry, IC decision log, post-signing deadline calendarstructuringIC logobligations
LP master recordLP entities, KYC files, side-letter terms, DDQ answersfundraising
Knowledge one classified corpus; specialised overlays, not separate builds shared: the corpus Context
The classified corpusevery document labeled and linked to its company and deal; AVG retention enforced; deal archives ingested at close or killknowledgescreeningDDIC memo
Precedent overlaypositions and mark-up history across every deallegal documents
Sector mapsliving theses per hunting groundtheses
Comp & assumption librarymultiples, past models, realized vs underwrittenvaluationFMV cycle
Engines & capture raw to structured; build once, point anywhere shared: the sourcing engine Scale
The sourcing engineone scored company universe, many profiles: deal sourcing, add-ons, buyer maps, portco lead gen, market scansoriginationadd-onsbuyer map
The capture agentemails, meetings, teasers and IMs parsed into the records; one agent, two cardsdeal capturerelationships
Ingestion pipelinesportco packs to the master chart (one pipeline, two ends); deeds and registry filings to the ledgers; documents to the corpusmonitoringentity adminknowledge
Your ops stack today structured truth, siloed, plus unstructured stores: nothing references anything else. The gap is the silo, not the mess.
Systems of record (structured, siloed)
Affinity (CRM)Affinity
Portco ledgersExactAFASTwinfield
Fund admin (Fundrbird)Fundrbird
Bank & fund recordsstatements, LPA, admin output
Cap table (Excel)Excel
Unstructured stores
DocumentsSharePointOneDrive
EmailOutlook
NotionNotion
Public: the market's
Entity & registry dataKVKUBO, deeds
Market dataDealsuitepress
Infra, security and people models, evals, training, security under every layer Control
Models & computecloud where fine, on-premise where confidentiality demands itAI capability
Evals & qualityevery shipped workflow measured for accuracy and drifteval harness
Human enablementtraining on real workflows, bundled into every engagementenablement