# Hub Suggestions

I always start my search in the people directory due to many pipelines doing different things, but it doesn't have the quick links to the Linkedin profile etc, which are useful.

Hi Decile team,

We run Team Ignite's portfolio reporting on top of Decile and use the Decile MCP server with Claude every day. Marks are the one workflow we cannot complete through the API or MCP. Today we can read valuations but cannot create or update one, so every mark gets entered twice: once in our own portfolio tracker and once by hand in the Decile UI. This is the gap that keeps us from treating Decile as the system of record for NAV.

This feedback is based on the Decile MCP tool list as of Nov 5, 2026. If the REST API already covers any of the items below, please tell us and expose the same thing in the MCP.

WHAT WORKS TODAY

• list_portfolio_companies, get_portfolio_company
• list_portfolio_company_valuations, get_portfolio_company_valuation (with funding rounds embedded)
• list_portfolio_company_investments (tranche level FMV and mark provenance)
• Journal entries, organizations, people, files, capital accounts, schedule of investments

WHAT IS MISSING, IN PRIORITY ORDER

1. Create and update a valuation (the main ask) There is no write tool for portfolio company valuations. We need create, update, and delete (draft only) with these fields:

• portfolio_company_id (and optionally fund_id, since one company can be held by several funds)
• effective date
• event type or reason (SAFE cap, priced round, secondary sale, 409A, write-down, write-off, held at cost, public price)
• valuation basis (cap-adjusted, priced, cost) and the resulting mark: company valuation, price per share, or cap, whichever applies
• linked funding round
• free-text rationale
• supporting documents (existing file ids)
• source and confidence flag, so a mark based on a founder statement can be recorded as unverified until a document arrives

2. Draft and approval state controlled through the API Marks affect NAV and the administrator package, so we do not want an API call to publish a mark silently. Please let the API create marks in a pending or draft state, return the approval state in the response, and expose approve and reject actions so an authorized human or the administrator can do it in the UI or via the API. Record the API key or MCP user as the creator in the audit trail. A dry_run or preview mode, like the preview_email tool already offers, would be ideal.
3. Create and update funding rounds get_portfolio_company_valuation can embed funding rounds but we cannot create one. A SAFE or note round needs: security type, valuation cap, discount, amount raised, close date, lead investor, and whether the round is insider-led. Without this we cannot record a cap-based mark that is tied to its evidence.
4. Expose the cap-adjusted calculation list_portfolio_company_investments states that it uses the normal, non-cap-adjusted calculation. We report both cap-adjusted and priced-only values to LPs. Please add a valuation_basis parameter (or return both values side by side) for current FMV, mark price per share, and MOIC, so we can reconcile Decile to our own numbers.
5. Create portfolio companies and investments A newly closed SAFE is invisible to the API until someone enters it in the UI. We need create tools for a portfolio company (organization plus fund) and an investment tranche (date, amount, security, cap, series), plus a way to link source documents. Related: list_portfolio_companies has no name or legal name search and is ordered by id with keyset pagination only. Please add name search, fund filter, and an updated_since filter. The same company can appear more than once across funds, so a clear parent and fund relationship in the response would help.
6. One consistent portfolio across legacy and current list_portfolio_company_investments returns a 422 for entities moved to the current portfolio. Please make every portfolio, valuation, and investment tool work across both, and return a flag showing which portfolio an entity lives in.
7. Bulk upsert and idempotency Quarter-end marking touches 100+ positions. Please add a batch valuation upsert, an idempotency key on writes, and an external_id field so we can map our own record ids to Decile ids and avoid duplicates on retry.
8. Better read filters and events

• Filter list_portfolio_company_valuations by status (draft, approved, rejected), fund, and date range
• NAV as of a date by fund, on each basis
• Webhook or event when a valuation is approved, changed, or rejected

9. Permissions and MCP ergonomics

• Separate API scopes for valuation read, valuation write, and approval, so we can give an AI agent write-to-draft without approval rights
• Enumerate allowed values (event types, bases, security types) in each tool schema so the model does not guess them
• Stable machine-readable error codes with a clear message when a key lacks a scope

EXAMPLE REQUEST WE WOULD LIKE TO MAKE

POST /portfolio_company_valuations { "portfolio_company_id": 12345, "fund_id": 678, "effective_date": "2026-11-05", "event_type": "safe_cap", "valuation_basis": "cap_adjusted", "company_valuation_usd": 400000000, "funding_round_id": 9012, "rationale": "Latest bridge SAFE cap per founder. Document requested.", "source_confidence": "unverified", "document_ids": [], "status": "draft", "external_id": "our-tracker-rec-123" }

WHY IT MATTERS Decile feeds the administrator's NAV package, so it is the right system of record for marks. Right now the people who know about a new round (our team, using AI agents) cannot get that mark into Decile without a manual re-keying step, which causes delays and drift between our tracker and the NAV package. A write path with a draft and approval gate would let us keep the control we need and remove the double entry.

We are happy to beta test any of this, and to share a longer list of edge cases from our SAFE-heavy portfolio (extensions above the last priced round, acquihires with contingent consideration, secondary marks).

Thanks, Brian Bell

Hey everyone! We’re looking for people who want early access to new Hub features and are willing to give us feedback.

Drop a 🙋‍♂️ if you’d like to join the Hub Beta channel! We’ll post features we’d like user feedback on in there, and you can volunteer for whichever ones you’re interested in.

People with fundraising only access should not be allowed to export, this is related to my broader feedback about standard CRM controls when your team start growing

The people directory should store the last search like the pipelines do

In Dark Mode, Deal Memo text still shows up black, making it impossible to read.

Feature request: category-based email subscriptions for LP and contact lists

Hi Decile team,

We need email subscription categories. Right now, an unsubscribe is all-or-nothing. When a recipient clicks unsubscribe on one newsletter, they are removed from everything we send. That is a real problem for GPs who send different kinds of email to the same database.

What we are seeing: Several of our limited partners unsubscribed from our general newsletter because they wanted less volume. They then told us they were missing our deal and SPV emails, which they actually want. We cannot fix this on our end because the unsubscribe suppresses all future sends. The result is that LPs lose access to time-sensitive investment opportunities, and we lose the ability to reach people who would have invested.

What we are asking for: Let each account define its own email categories. Each email, newsletter, or campaign gets tagged with a category when it is created. The unsubscribe link in that email then lets the recipient opt out of that category only, or opt out of everything. Recipients should also get a preference page where they can toggle each category on or off.

Suggested default categories (based on what a typical VC or GP sends to a database):

1. New deals and SPVs: Syndicate opportunities, SPV invitations, co-investment offers, secondary deals. These are time-sensitive and often the main reason an LP stays on the list.
2. Fund and portfolio updates: Quarterly LP updates, portfolio company news, markups, exits, fund performance and milestones.
3. Newsletters and insights: Regular content, market commentary, research, podcast episodes, and thought leadership.
4. Events: Invitations, RSVPs, and reminders for LP meetings, annual meetings, demo days, dinners, and webinars.
5. Fundraising and new fund announcements: Communications about new funds, closes, and re-ups, which some LPs want and others do not.

Always-on category (not unsubscribable): Transactional and legal communications such as capital calls, distribution notices, K-1s and tax documents, LPA amendments, and compliance notices. This category should be clearly labeled so recipients understand why they cannot opt out of it. I think when we use our Gmail integration this is the case for newsletter sends?

Additional requests:

• Let admins rename, add, or remove categories, and set which are on by default for new contacts.
• Show each contact’s subscription status by category in their profile, and allow filtering and segmenting recipients by category.
• Make sure sends to a category automatically exclude contacts who opted out of that category only, rather than globally.
• Report unsubscribe rates by category so we can see which content drives opt-outs.

This would help us stay compliant, reduce list churn, and keep LPs informed about the things they care about. Happy to jump on a call to walk through our use case.

Thanks,
Brian

Need email newsletter send domain blocking, sometimes I'm emailing something about a company that I shouldn't send to certain companies if you catch my drift.

It would be great to have the ability to delete a pending application on this screen:

Bumped into a formatting issue on the investment committee tab

I'm trying to rename filenames in my data room, and there's a bug that's preventing me from doing so. When I click on the file name, it opens a new window with the document itself. It also is automatically adding a .pdf extension even if a .pdf extension is already on the filename.

Recently whatsapp is introducing usernames which means the phone field is not weird... how do you plan to work on that? Should it be a label change or more needs to happen?

We are arranging an event - a private dinner with limited seating.

We want the flow to be:

1. Invitee requests to attend
2. We either confirm or reject

However, as far as we can tell, on the event page as soon as the invitee requests to attend it will mark him as registered.

Is there any way to implement this flow?