Decile Base
Ctrl + K
Log In Sign Up

Loading...

# Hub Feedback

1
Community Member

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?
0 replies
Today
Community Member
Hi, given the new feature of whatsapp usernames can we have a field for that. In our country it's already out and some people we are adding we do not have their phones just usernames
1 reply
Friday, September 4
Community Member
Hi, I started using the Newsletters and Files to run SPV deals. However, there's no "Sign an NDA" feature available before they see the full IM that I saved in Files. This is critical as some of the info can be confidential. Could this be added?
1 reply
Thursday, September 3
Community Member
For venture studio adjacency can we get the DEX recommendation

Recommendation

If the locking and audit trail are material to your LP or auditor commitments, I'd suggest raising this as a feature request with the Decile team directly, since audit trail functionality is something the community has been asking for. In the meantime, the data room + manual amendment log approach is the most defensible workaround available today.

Origin: 

We add to every portfolio company an assigned one of three deal source designations at the time of initial investment:
STUDIO_ORIGINATED, the company was built inside or directly by the Grow Cycle Solutions studio before the fund invested.
STUDIO_REFERRED, the company was introduced to the fund by the studio or a studio partner but was not built by the studio.
MARKET_SOURCED, the company was sourced through the fund's independent deal flow, with no studio involvement in the introduction.
This designation is set at closing, timestamped, and locked against editing. Any subsequent change requires a dated Amendment Log entry stating the prior value, the new value, the reason for the change, and the name of the person who made it. The Amendment Log is available to LPs and auditors on request.
in decilehub?

DEX RESPONSE - This is a great question about whether Decile Hub's data model can accommodate a custom deal-source designation field with the locking and audit-trail behavior you've described. Let me search the knowledge base for what's actually supported.
Here's an honest breakdown of what Decile Hub can and cannot do for your deal-source designation policy:

What Hub supports today

Hub does have custom fields on deal pipeline records (including a custom dropdown field with limited options, per community replies). You could create a dropdown called something like "Deal Source Designation" with the three values: STUDIOORIGINATED, STUDIOREFERRED, and MARKET_SOURCED. That covers the core tagging requirement.

What Hub does NOT natively support

The specific controls your policy requires go beyond what Hub currently offers out of the box:

  • Field locking at closing. Hub does not have a native "lock this field after a certain event" mechanism. Nothing prevents a team member from editing the designation after it is set.
  • Timestamped designation at closing. Hub tracks when records are created and modified generally, but there is no native "set this field at closing and timestamp it" workflow.
  • Amendment Log with prior value, new value, reason, and author. Hub does not have a structured amendment log for custom field changes. The community has explicitly requested audit trail functionality for field edits and commitment changes, and as of the knowledge base results, it is not yet available as a built-in feature.
  • LP/auditor-accessible Amendment Log. There is no native mechanism to expose a field-change history to LP data room viewers.
Practical workaround

You can approximate this policy inside Hub using a combination of:

  1. A custom dropdown field on the deal/organization record for the designation itself.
  2. A notes or text field (or a pinned note on the deal) where you manually log any amendment: prior value, new value, reason, date, and name of the person who made the change.
  3. A document in the LP data room (a simple Amendment Log file) that you update and version whenever a change is made, giving LPs and auditors access to it there.
The enforcement and locking, though, would be procedural (team discipline and process) rather than technical. Hub cannot currently prevent an edit or auto-enforce the amendment requirement.
0 replies
Tuesday, September 1
Community Member
Would be great if PACT and LPA landing pages had open/view analytics similar to what hubspot or other crm systems show with email tracking. At minimum knowing if a prospect opened the links or not would be helpful before reaching out to them again.
👍 1
0 replies
Tuesday, August 25
Community Member
When publishing newsletters, it is not clear if I have to publish before I schedule an email.  I'm expecting that after setting the scheduled date/time to send, it will send without me having to click "publish".
0 replies
Sunday, August 23
Community Member
With Newsletters, it would be great if under the recipients list, there could be a checkbox to exclude a recipient.  For instance, I'm sending newsletters to my SPV investors, which also includes LPs, but the LPs have already received an LP specific newsletter. 

Thank you,
Eric
0 replies
Friday, August 21
Community Member
I'm confused as to how the tasks system works... I see that in the deal I can assign a stage to a person and i can also assign the deal in general... but how do I automatically assign individual tasks ? 
2 replies
Wednesday, August 19
Community Member
Is there a way to manage folder permissions for a small data room in Hub?  

For example, I have one folder "Fund Overview" with the LP presentation, ExecSum and FAQs. Then I could have a separate folder(s) for a more detailed data room supplement. But I only grant access to that second folder for serious investors who ask for it. 

I could create two separate data rooms that both contain "Fund Overview" (either with or without the supplemental folders), but then I have to update versions across 2 separate "Fund Overview" folders manually to keep them in sync. This could be managed by instead creating a hyperlink in the detailed data room that goes back to the "Fund Overview" folder.

I'm not sure what the best way to do this is inside the Hub data room. Any guidance is appreciated. Thanks 
2 replies
Tuesday, August 18
Community Member
Bug in MCP documentation . instructions for claude code mcp should not contain ${} as the token should be after the :
1 reply
Community Member
One last bit of feedback on Inbound Emails.  I've noticed a lot of them are not actionable.  It would help if AI could filter out and focus on those emails with action items or requests I need to reply to.  This is where I could really use the help, especially to make sure an important email doesn't fall through the cracks.
👍 1
1 reply
Monday, August 17
Community Member
I love the Inbound Email tool to help put focus on relevant emails in my pipelines.  Would it be possible to update this to capture inbound emails only from those who are in the given pipeline?  Right now, it appears that the list of the same Inbound Emails is showing across all pipelines.  Thank you!
3 replies
Saturday, August 15
Community Member
Thank you for adding the dismiss button to Inbound Emails!  As a next addition, I'd like to be able to quickly add a note to that contact in order to capture my response to the communication in their profile.  Can you add an "Add Note" button?
1 reply
Community Member
Newsletters are great, but I'd like the ability to craft a personalized email to each LP as a header to the template newsletter.  I appreciate visibility to open/click rate of the newsletters, and don't have that when I send individual emails. 
2 replies
Thursday, August 13
Community Member

Feature Request: Cross-Fund Price-Per-Share & SAFE Benchmarking



Summary
Decile should build a shared, company-level object for pricing data — priced-round price per share (PPS) and SAFE terms — aggregated across the GPs on your platform who hold a position in that company. Today each fund's Decile instance is an island. If ten different GPs hold Company X, Decile has ten independent, unreconciled data points sitting in ten separate accounts, and none of us can see the other nine. Surface that as a shared object and you turn Decile from a bookkeeping system into the pricing utility of record for the venture asset class.

The Problem
Early-stage investors write small checks at pre-seed and seed and routinely lose contractual information rights by the Series A or B. By the time a company reaches Series C or D, we often have no reliable way to know the current price per share short of emailing the founder directly and hoping they respond. That means our marks on older, smaller positions are frequently stale, guessed, or simply carried at last-round cost long after the company has repriced multiple times in either direction.

This isn't a hypothetical. I'm currently running a reconciliation across our own fund between Decile, our internal Airtable, and our management schedule, and the discrepancies are exactly the kind of thing this feature would catch automatically instead of manually. Every GP on your platform has some version of this problem. You're sitting on the data to fix it and you're not using it.

Proposed Feature

1. Priced-round price per share, aggregated by company

For any portfolio company held by two or more funds on Decile, surface:
  • Latest price per share on file across all contributing funds, with the date and round name attached to each data point
  • Highest price per share in the system for that company, and which fund/round it corresponds to
  • Lowest price per share in the system for that company, and which fund/round it corresponds to
  • Median and count of contributing marks, so a GP can tell whether they're an outlier of one against a group of nine, or whether the "market" itself is only two data points deep and shouldn't be trusted
  • Your own fund's current mark shown side by side against that range, with a flag if you're above the highest peer mark or below the lowest

2. Do the same for SAFEs

SAFEs need their own version of this because they don't have a clean single "price" the way a priced round does. At minimum:
  • Valuation cap (and whether it's pre-money or post-money) — highest, lowest, latest, median across contributing funds
  • Discount rate, if any
  • MFN status and whether an MFN clause has since been triggered by a later, more favorable SAFE
  • Conversion status (converted / outstanding), and if converted, into what round and at what terms

3. A reconciliation and audit view for fund accounting

This is the actual deliverable GPs will pay for. Not just the numbers, but the workflow:
  • A per-portfolio-company report showing "here's what you're marked at, here's what the system-wide range is, here's the delta"
  • A portfolio-wide audit report that surfaces every position where a fund's mark falls outside the peer range (either direction), sorted by dollar impact so the biggest valuation errors surface first
  • A prompt, at the point a GP is about to lock a quarterly mark, showing the current cross-fund range for that company so the mark isn't made blind

4. Guidance, not just data, on aggressive vs. conservative marking

GPs are going to ask "should I mark at the high end or the low end of the range," and Decile is well positioned to give a defensible, documented answer rather than making every GP invent their own policy. At minimum, show standard conservative approaches (e.g., last-round price, or the lower of last-round price and the most recent contributing mark) next to the aggressive alternative (e.g., latest priced round regardless of recency, or highest observed mark), so a GP can pick a stated policy and apply it consistently, and so LPs and auditors can see the policy was applied consistently rather than cherry-picked deal by deal.

What Carta Already Does, and Where This Should Go Further
Carta has adjacent functionality worth being aware of. Their Data Desk / Round Benchmarking Tool surfaces aggregate round-size, valuation, and dilution benchmarks across their network, filterable by stage, sector, and region, and their platform description references "last preferred valuation" as a data point available to investors. That's market-level benchmarking (what are Series B valuations doing broadly), not the same thing as this request. It doesn't appear to give a GP a company-specific, cross-fund reconciliation view showing exactly who else holds Company X, what they're marked at, and where a specific fund's number is out of line with peers holding the identical security. That's the gap. Decile's fund administration relationship with GPs (as opposed to Carta's broader company-cap-table-plus-investor footprint) may actually put you in a better position to build the reconciliation and audit workflow specifically, rather than just the market-benchmarking layer Carta already has.

Implementation Considerations
  • Consent and disclosure. Funds will need to opt in (or out) to contributing their data to the shared pool, and probably opt in per-company or per-fund rather than as a blanket platform setting. Anonymize the contributing fund identity by default (show "Fund A held at $X, Fund B held at $Y" rather than naming funds), with an option for GPs to identify themselves to each other if they want to.
  • Data provenance. Every data point needs a timestamp, a source (priced round vs. secondary vs. GP-entered estimate), and ideally a confidence flag, since a number pulled from a signed round document is not the same quality as a number a GP typed in from memory.
  • Stale data handling. A "latest" price per share from fourteen months ago should be visually distinguished from one dated last week. Don't let an old number silently anchor a current mark.

The Ask
I'd like to talk through scoping this, including whether it's a near-term roadmap item or something that needs a design partner group of GPs to pilot. Happy to be a design partner given we're actively living this problem on our own portfolio reconciliation right now.
1 reply

Loading more posts...

Log In or Sign Up

Please Log In, or Sign Up to participate in the discussion.

Log In
or
Sign Up

Apply to VC Lab Cohort 22

Get full access to Decile Base and the Decile Hub venture platform for free by joining the VC Lab program.

Apply to VC Lab Cohort 22

Decile Group Inc. uses cookies for our website to function properly; some are optional and help deliver a personalized and enhanced experience. By clicking "Allow all", you consent to store cookies on your device in accordance with our cookie policy. You can reject all non-essential processing by choosing to accept only necessary cookies. To learn more check Cookie Policy