Deployed with the world's largest private company.
Founder cold emails, warm intros, conference leads, portfolio referrals, Greymatter operator intros. Thousands per year. Today the procedure for triage — sector fit, stage fit, which partner takes it, fast-yes vs. polite no — lives in the analyst’s head. Phyvant watches the analyst run it, then runs it against Gmail, calendar, and Affinity directly.
Every portco financing ripples through Carta, fund accounting, Affinity, and the LP reporting line. Which board observer signs. Which info-rights propagate. Which fund vehicle takes the allocation. The procedure lives in the COO’s head. Phyvant encodes the closeout step nobody wrote in the checklist.
Fee waivers, MFN provisions, ESG addenda, info-rights variants. Each quarter, every packet checks against every LP’s specific letter. The exception map lives in the controller’s head and three Excel sheets. Phyvant infers the map by watching a few cycles, then runs the cycle itself.
Q1 close. Capital call. LP letter. Distribution. Q2 the same. Audit prep in Q3. K-1s by March. Form ADV by April. The cycle is identical every quarter; the exceptions per fund and per LP are not. Today the controller runs each cycle from a checklist that lives mostly in their head. Phyvant watches a couple of cycles, encodes the exceptions, then runs the cycle on cadence.
Founder cold emails, warm intros from operators in the network, conference leads, portfolio referrals. Today an analyst triages every one — classifies by sector and stage, routes to the right partner based on coverage and active sourcing focus, schedules the meeting if accepted, logs to Affinity with linked priors. The routing logic — which AI infra leads go to Saam, which enterprise SaaS goes to Corinne, which warm intros warrant a fast yes — lives in the analyst's head. Phyvant watches a few weeks of triage, infers the procedure, then runs it: reads Gmail, classifies, drafts the response, holds the calendar, logs to Affinity with the right tags and linked priors. Exceptions route back to the analyst. Every correction is a labeled training example.
Every inbound classified, routed, and logged against the analyst’s actual procedure — including the warm-intro fast-yes pattern that was never written down.
When a portfolio company prices a financing, the firm runs a closeout: the new cap table to Carta, the allocation to the right fund vehicle in fund accounting, the round update to Affinity with linked board materials, the info-rights propagation to the board observer, the LP reporting line item. The procedure lives in the COO’s and controller’s heads — including the per-vehicle allocation logic for cross-fund deals and the info-rights variants per LP side letter. Phyvant watches a handful of closeouts, then runs the procedure end-to-end against Carta, fund accounting, and Affinity. Operators review the exceptions; the next closeout takes less of the hour.
Every closeout step driven by the procedure your team already runs — including the cross-fund allocation logic and per-LP info-rights propagation that lives in the COO’s head.
Assembled per fund, FX-applied, routed through banking and the LP portal — on cadence, with every per-LP exception baked in.
Every per-LP carve-out — fee waiver, MFN, info rights, ESG addendum — tracked automatically across every fund cycle.
Inbound meeting requests routed to partner availability, calendar held, prep doc drafted from priors, Affinity logged on completion.
Pulled from fund admin, per-LP exceptions applied, assembled in the partnership’s voice, routed through the LP portal.