When Investors Ask for More

Investor expectations have evolved. Standard quarterly reports are no longer enough—investors want deeper insights, faster responses, and increasingly tailored views of their data. For fund managers, this creates a familiar tension: how do you meet custom reporting needs without breaking your operations?

At Pinnacle Fund Services, we see this challenge firsthand. Custom reporting can strengthen investor relationships, but without the right structure, it can quickly erode operational control. The key is not to avoid customization—it’s to govern it.

Where the Risk Comes From: Ad Hoc Reporting

Custom requests often start small. An investor asks for a slightly different breakdown of performance, a new capital activity view, or a specific format aligned to their internal systems. These requests are reasonable—and often valuable.

However, when handled informally, they introduce risk.

Ad hoc reporting typically relies on manual processes: offline spreadsheets, one-off data pulls, or adjustments outside core systems. This creates multiple versions of the truth, increases the likelihood of errors, and reduces auditability. Over time, what began as a single request becomes a parallel reporting process—untracked, uncontrolled, and difficult to scale.

Risk Mitigation:

Custom outputs should always originate from a controlled data environment. By anchoring all reporting—standard or customized—to a single source of truth, managers can ensure consistency, accuracy, and traceability across every investor deliverable.

Reframing the Request: Solve for the Need, Not the Format

When an investor asks for a custom report, the instinct is often to respond with “we can build that.” Over time, this leads to fragmented outputs and operational strain.

A more effective approach is to pause and understand the underlying objective.

• Is the investor looking for a different performance lens?
• A reconciliation to their internal systems?
• A more frequent update?

In many cases, the answer already exists within your reporting suite—it’s just not presented in the way they expect.

By reframing the conversation, managers can often meet the requirement without changing the reporting standard itself.

Risk Mitigation:

Introduce a structured intake process for custom requests. Before building anything new, assess whether the requirement can be addressed through existing reports, alternative views, or minor configuration changes. This reduces one-off builds and preserves consistency.

One-Off Requests vs. Standardized Outputs

Not all custom reporting is created equal. Some requests are truly unique, while others are variations of common investor needs. The problem arises when every request is treated as a one-off.

This approach leads to duplication of effort, inconsistent formatting, and growing operational burden. Teams spend more time recreating similar reports than delivering value. As the investor base grows, this model becomes unsustainable.

In our experience, many “custom” requests follow predictable patterns—alternative performance views, investor-specific capital summaries, or tailored fee disclosures. These can and should be standardized.

Risk Mitigation:

The objective is to convert repeat custom requests into configurable outputs. By building a reporting framework that allows for parameterization—such as fund selection, date ranges, or investor-specific filters—managers can deliver tailored insights without reinventing the process each time. This shifts reporting from reactive to scalable.

Offering Alternatives Without Breaking Your Model

There is a right and wrong way to respond to custom requests.

A rigid “we don’t support that” creates friction and weakens the investor relationship. On the other hand, immediately agreeing to every request introduces long-term operational risk.

The more effective approach is to guide the outcome.

In many cases, asking the investor “is there another way we can provide this information?” leads to a better solution. The investor’s goal is rarely tied to a specific format—they are trying to access a specific insight. That insight can often be delivered through existing reports, different cuts of data, or self-service tools.

For example:

• Providing an alternative view of an existing report rather than building a new one
• Offering dashboard access where investors can apply their own filters
• Delivering structured data extracts aligned to their internal models

This positions managers as responsive and solutions-oriented, without compromising operational integrity.

Risk Mitigation:

Define a catalogue of approved alternatives that teams can consistently offer. This ensures a controlled, repeatable response to custom requests and avoids ad hoc decision-making.

When Customization Crosses Into Risk: A Capital Call Example

A common example we see in practice is around capital call notices.

An investor may request that a capital call notice reflect cash they have already paid—effectively asking for a “net amount due” presentation within the notice itself. On the surface, this seems reasonable. It aligns with how the investor is tracking their position internally.

However, capital call notices are standardized for a reason. They are formal documents, often reviewed by auditors and relied upon by multiple stakeholders. Modifying the template to reflect investor-specific adjustments introduces several risks.

First, it breaks consistency. Two investors in the same fund could receive different versions of what is intended to be a uniform notice. Second, it creates reconciliation challenges—particularly if the “netted” amount does not clearly tie back to the official call amount. Third, it increases the likelihood of error, especially if these adjustments are handled manually or outside the core system.

Over time, accommodating these types of requests can lead to multiple variations of the same document—each slightly different, and none fully aligned to the original standard.

Risk Mitigation:
Rather than modifying the capital call notice itself, a more controlled approach is to maintain the standardized notice and provide the requested information separately. This could include a supplementary statement showing payments received, an investor capital account summary, or access to a portal view where the investor can see real-time balances and activity.

This approach achieves the same outcome—the investor gets the information they need—without compromising the integrity of the official document.

Governance Around Customization

Customization without governance introduces control gaps. Who approved the report? Was the data validated? Does it align with official financials? These questions become difficult to answer when processes are informal.

This is particularly important in environments subject to audit scrutiny or regulatory oversight. Even minor inconsistencies between reports can create confusion—or worse, undermine investor confidence.

At the same time, overly rigid controls can slow responsiveness.

Risk Mitigation:

Custom reporting should follow defined workflows, including approval processes, version control, and audit trails. A maker-checker framework ensures that all outputs—whether standard or customized—meet the same quality and control standards.

It is equally important to distinguish between official reporting and supplementary outputs. Official reports should remain standardized and tightly controlled, while supplementary information can be more flexible—but still governed. This protects the integrity of your reporting framework.

Turning Requests Into Scalable Improvements

Not every custom request should be redirected. Some are signals.

If multiple investors are asking for similar information, that is not a one-off request—it is a gap in the current reporting framework.

Ignoring these signals leads to repeated work. Addressing them strategically strengthens your operating model.

Risk Mitigation:

Track custom reporting requests over time. Identify recurring themes and incorporate them into your standardized reporting suite where appropriate. This allows your reporting to evolve in a controlled, scalable way.

Delivering More Without Compromise

Investor demand for custom reporting will continue to increase as transparency expectations rise and investors seek more granular insights.

The question is not whether to offer customization—but how to do it without breaking your operations.

Please contact David Smith at [email protected] for more information about addressing investor needs.