Source: Group DM with VAs (C0AJ0541VRC) — Mar 2-9, 2026 Contributors: Laura Lake, Katherine Vittorio, Kerri Leathers Izunagbara, Frank Garcia Dashboards: Business Summary | Traditional Funds Context: Alexia set "business summary health dashboard data" as P1 for VAs (Mar 4). Daniel built both dashboards and asked VAs to review data accuracy + provide UX feedback.
- Who: Katherine Vittorio
- Dashboard: Business Summary
- Request: Fully hide columns that aren't needed, or let users customize which columns are visible.
- Why: Different roles need different views — fund ops doesn't need the same columns as accounting.
- Who: Laura Lake
- Dashboard: Business Summary
- Request: Filter within dashboard sections. Example: in Accounting, hide 1099 info (not relevant until next tax season) while keeping other accounting fields visible.
- Why: Sections currently show everything — too much noise for daily use.
- Who: Laura Lake
- Dashboard: Business Summary
- Request: Click a column header to sort/group by that field. Example: sort by YE Financials status to see all incomplete ones together.
- Why: Currently no way to reorder rows by a specific column — makes it hard to batch-process similar items.
- Who: Laura Lake
- Dashboard: Business Summary
- Request: The sticky left-side filter pins both Fund Name AND Health columns. Should only pin Fund Name.
- Why: Takes too much horizontal screen space, especially on smaller screens. Health doesn't need to be always-visible.
- Screenshots: Laura shared two screenshots showing the sidebar behavior (Mar 2).
- Who: Laura Lake
- Dashboard: Business Summary
- Request: Add a notes field per fund, similar to the notes in the Partners pipeline.
- Why: VAs use notes heavily as source of truth — context about the fund that doesn't fit into structured fields. Currently this context lives in scattered Slack messages and personal notes.
- Who: Katherine Vittorio (Mar 9 follow-up)
- Dashboard: Business Summary
- Request: A dedicated column (ideally 2nd column) for permanent short notes. Examples: "always check first before closing on LPs", "don't set meetings for Fridays", general top-level notes that VAs need to always see.
- Why: Important operational context gets lost. VAs need persistent, always-visible reminders per fund — not buried in activity logs or Slack threads.
- Who: Laura Lake
- Dashboard: Business Summary
- Request: Wherever numbers appear (e.g. LP Tax Info counts), make them clickable links to the original source. Example: clicking the number under LP Tax Info should go directly to that fund's Capital Account page.
- Why: Currently the dashboard shows data but VAs have to manually navigate to the source to take action. Adds friction to every task.
- Who: Katherine Vittorio
- Dashboard: Business Summary
- Request: Add a link to each fund manager's calendar from their fund row.
- Why: VAs frequently need to schedule or check availability — currently requires leaving the dashboard to look it up.
- Who: Katherine Vittorio
- Dashboard: Traditional Funds
- Request: Older funds (pre-2024) have engagement letters stored as PDFs in Google Drive, not in DocGen. The EL dropdown only shows DocGen-generated ELs. Need ability to link to an external PDF or manually attach an EL.
- Current behavior: EL dropdown pulls from
partners.decilehub.com/doc_gen/responses— only shows ELs created through the questionnaire flow. - Daniel's response: Can build manual PDF linking, but would require a manually-entered signed date. Deprioritized since these are pre-2026 funds — will address after current 2026 goals.
- Who: Katherine Vittorio (raised twice — Mar 3 and Mar 9)
- Dashboard: Business Summary
- Request: Easily see which fund ops person is assigned to each account without additional clicks.
- Why: VAs need to know who to escalate to. Currently requires navigating into the fund details.
- Who: Laura Lake
- Dashboard: Business Summary
- Request: Pull in open tasks from Base (Houston's task system) so VAs can see pending action items per fund directly in the dashboard.
- Why: Tasks and dashboard are disconnected — VAs check two separate systems to understand what needs doing on a fund.
- Who: Katherine Vittorio
- Dashboard: Business Summary
- Request: Show a list of all open GitHub issues/cards attached to a firm. Could be done by tying to the firm GitHub labels already in use.
- Why: Engineering work affecting a fund (bugs, feature requests) is invisible to fund ops. VAs would benefit from knowing if there's an active dev issue on a fund they're working.
- Who: Katherine Vittorio
- Dashboard: Business Summary
- Request: A quick visual (loading bar or pie chart) showing how close each fund is to reaching its fundraising target.
- Why: Currently just raw numbers — a visual would make it instantly scannable which funds are close vs far from target.
- Who: Katherine Vittorio
- Dashboard: Business Summary
- Request: An easy way to flag or highlight funds whose fundraising period is ending soon.
- Why: Time-sensitive — VAs need to prioritize outreach for funds about to close their fundraising window.
- Who: Katherine Vittorio
- Dashboard: Business Summary
- Request: Easily identify VIP clients and at-risk clients. Katherine noted she sees "top customers and problematic" section at the top — wants to understand how to set/configure this.
- Why: Not all funds need equal attention. VIPs and at-risk need proactive management.
- Who: Laura Lake
- Dashboard: Business Summary / General
- Request: Surface LPA signing events in the dashboard or as notifications. Currently VAs manually check this Blazer query every day to see which LPAs were signed.
- Additional context: This applies to Click-2-Close (C2C) funds too — VAs still manually move funds to "closed" status even in C2C, so they need to know when LPAs are signed regardless of the flow.
These are items where VAs found incorrect data but couldn't fix it themselves due to missing permissions or system limitations.
- Who: Kerri Leathers Izunagbara
- Dashboard: Traditional Funds
- Issue: Nearly none of the % commitment values are accurate for her funds. She cannot update them.
- Root cause (per Daniel): % Committed is calculated (total committed / target size). If wrong, either LP commitments or target size is incorrect. Updating commitments requires compliance role (fund ops only).
- Action needed: Either give VAs permission to update commitments, or have fund ops batch-fix the data.
- Who: Kerri Leathers Izunagbara
- Dashboard: Traditional Funds
- Example: Flair's target shows $5M (CAD) but they only raised $1,570,157 (CAD).
- Root cause: Target reflects original goal, not actual raise. Decision needed: update target to actual raise, or keep original target and show actual separately.
- Who: Kerri Leathers Izunagbara
- Dashboard: Traditional Funds
- Example: Grind Ventures shows as "Enrolled" — Kerri says it's not formed yet and she can't update it.
- Root cause (per Daniel): Status is auto-calculated from lifecycle milestones, not a manual dropdown. Current status shows "LPA Signed" which is based on system data.
- Who: Kerri Leathers Izunagbara
- Dashboard: Traditional Funds
- Example: Indelible Ventures Fund I and Fund II terminated on 9/30/25 but she can't set the termination date.
- Root cause (per Daniel): Only Decile admins can set termination dates. Daniel tested on Fund II — may be a role/permission issue for Kerri.
- Action needed: Check Kerri's role permissions or have admin batch-set termination dates.
- Who: Kerri Leathers Izunagbara
- Dashboard: Traditional Funds
- Questions:
- "What's the difference between Activated and Operating?" → Activated = first close done (commitments locked, no investments). Operating = first investment made. Applies to Decile-formed funds; migration logic differs.
- "What does LPA Signed mean?" → At least one LP signed the LPA. Doesn't mean formed. Mavka, NextGene, Nextverse show LPA Signed correctly even though not fully formed.
- Action needed: Add tooltips or a legend explaining status labels on the dashboard.
- Who: Kerri Leathers Izunagbara
- Dashboard: Traditional Funds
- Example: Suncoast Ventures - Suncoast Healthcare Equity Angels never formed, should be removed.
- Root cause (per Daniel): No delete function in dashboard. Options: set termination date (shows as "Terminated") or remove from database.
| Theme | Items | Impact | Effort (est) |
|---|---|---|---|
| Data/Permission Blockers | 7.1-7.6 | 🔴 High — VAs can't do their data cleanup work | Low-Med (permissions + batch fixes) |
| Notes & Context | 2.1, 2.2 | 🔴 High — most requested across multiple people | Medium |
| Column Customization | 1.1-1.4 | 🟡 Medium — usability for daily workflow | Medium |
| Links to Source | 3.1-3.3 | 🟡 Medium — reduces navigation friction | Low-Med |
| People/Assignment Visibility | 4.1-4.3 | 🟡 Medium — operational awareness | Medium |
| Visual Indicators | 5.1-5.3 | 🟢 Nice-to-have — scannability | Medium |
| Notifications | 6.1 | 🟡 Medium — eliminates daily manual Blazer check | Medium |
Compiled by Cortex from VA group DM (C0AJ0541VRC), Alexia DMs, and #group-venture-associates — March 11, 2026