In this latest release, we are introducing greater automation and workflow flexibility to reduce manual effort across key workflows. Our team has also made platform improvements that make Taghash faster, more stable and more reliable in day-to-day use.

Meeting Insights Updated Automatically

If you use Granola to capture meeting notes, you know how valuable that context can be. Manually moving it into Taghash, however, adds unnecessary effort. Through our Claude MCP integration, Taghash can now connect directly with Granola.

Your meeting notes can now sync into Taghash automatically. This reduces manual copying, limits context switching and helps ensure that discussions with founders or LPs remain connected to the right records once the meeting is complete.

Read more: Granola to Taghash Through MCP: A Smarter Meeting Notes Workflow for Private Capital

Manage Secondaries with More Flexibility

Secondary transactions do not always follow a single workflow path, yet many systems require one fixed process. We have enhanced secondary transaction processing to give your team greater flexibility in how secondary activity is recorded.

Whether you are handling bulk uploads, processing transactions alongside valuation events or recording individual entries, you can now manage secondaries through a workflow that fits the activity in progress. This helps maintain cleaner records while reducing manual handling.

Faster Performance and More Reliable Platform Operations

Alongside these workflow updates, we have also improved the underlying platform to support faster performance, greater stability and more consistent performance.

A database infrastructure upgrade: We have migrated to a modern infrastructure that supports faster response times and more consistent platform performance, including during high-volume reporting periods.

Proactive platform monitoring: Our enhanced real-time monitoring and alerting help identify issues earlier and support more reliable platform performance over time.

Team Note

Every update we ship is designed to reduce manual effort, improve continuity across workflows and support more dependable execution across the platform.

We are pleased to bring these improvements to your team and will continue to strengthen the workflows you rely on every day.

As always, your feedback continues to shape our roadmap. Log in, explore the latest updates and let us know where we can continue improving Taghash for your team.

— The Taghash Team

Private capital firms work across many systems every day. Depending on the firm’s current workflows and operating setup, deal capture, meeting notes, research inputs, investor communication, task coordination and internal updates might happen in different places. The operational challenge is keeping that information connected and ensuring the right next step happens on time.

That is where Taghash’s integration with Zapier becomes useful.

Taghash centralizes core private capital workflows across dealflow, CRM, LP coordination, portfolio monitoring, fund operations and related records. Zapier connects the external systems around those workflows, helping firms capture information into Taghash automatically and trigger follow-on actions across other systems when needed.

The practical benefit is straightforward: less manual work, better continuity and stronger workflow discipline.

The problem it addresses

As firms grow, information linked to deals and ongoing workflows starts coming in from many directions. Meeting summaries, external inputs, internal updates and process signals all need to be captured, routed and acted on accurately.

Without automation, teams spend time copying information across systems, updating records manually, assigning next steps and checking whether follow-ups have happened. This slows execution and increases the likelihood of gaps in records, delayed actions and inconsistent coordination across the team.

Zapier helps reduce that burden by automating how information is routed and how workflows are triggered.

How it works

The integration runs through three components: triggers, workflows and actions.

A trigger starts the process when something happens in a connected system. That trigger activates a predefined workflow, which determines the logic of what should happen next. The workflow then executes the required actions, whether inside Taghash, in another system or across both.

This structure allows repeatable processes to run with consistency. Instead of depending on someone to manually capture an update, assign the next step and send the required communication, the workflow can carry that sequence forward automatically.

Why this matters in private capital

In private capital, execution quality often depends on small operational details being handled well. A missed update, an incomplete record or a delayed follow-up can weaken visibility across the pipeline and slow decision-making.

The value of this integration lies in preserving continuity across workflows. Taghash maintains the structured operating context. Zapier helps ensure surrounding systems feed into that context properly and respond to it when something changes.

This is especially useful where teams need stronger discipline across deal intake, internal coordination, investor-related workflows, portfolio tracking and supporting operational processes.

What Zapier does in the Taghash ecosystem

Zapier plays two clear roles around Taghash.

First, it helps bring external information into Taghash from systems such as Fireflies and other connected platforms. This helps ensure important updates are captured in the right place without manual re-entry.

Second, it helps trigger next steps outside Taghash when activity inside the platform requires action elsewhere. That could include email workflows, task assignment, tracking updates or other predefined actions across connected systems.

This makes Taghash more effective as an operating layer because the workflows around it stay connected instead of depending on manual handoffs.

Example use cases

Based on the information shared, the integration can support use cases such as:

• Bringing external data into Taghash automatically from connected systems
• Sending emails automatically when a defined condition is met
• Maintaining a rejected sheet without manual updates
• Assigning tasks to team members based on role or position
• Triggering changes in other connected systems based on activity inside Taghash

Each of these use cases helps reduce repetitive coordination work and improves how consistently workflows are executed.

Where the value compounds

The impact becomes more visible when firms are handling a high volume of deal-related information from multiple sources. In those environments, the issue is rarely one isolated update. The issue is the cumulative weight of repeated manual work across dozens of small actions every day.

By defining how information should enter Taghash and what should happen next, firms can reduce coordination overhead while keeping workflows cleaner and easier to manage. That supports better pipeline coverage, clearer ownership and more dependable execution across the team.

Final perspective

Taghash remains the central operating layer for core private capital workflows. Zapier strengthens that layer by connecting the systems that surround it and automating the flow of information and actions between them.

The result is lower manual effort, fewer coordination gaps and stronger continuity across the workflows private capital teams run every day.

About Taghash

Taghash provides an end-to-end platform for venture funds, private equity, fund of funds and other alternative investment funds. Over the last seven years, we have served as the tech arm for top VCs, helping them manage operations across deal flow, portfolio, fund and LP management. 

We also offer a services layer to support execution across data management, legal and compliance, fund administration coordination, trustee and custodian interfacing and valuations and advisory.

Trusted by leading fund managers like Blume Ventures, Kalaari Capital and A91 Partners, we enable our clients to achieve greater success. Click here to book a demo.

Private capital workflows often break at the point where tools stop connecting.

A founder update comes through email. A new relationship starts on LinkedIn. An inbound opportunity enters through a form. Research happens in the browser. A team member uses AI to analyse or summarise the information. Each step adds value, but when these systems operate in isolation, continuity drops and execution becomes harder to maintain.

Taghash integrations are built for that reality.

They connect the tools closest to day-to-day private capital work, helping teams keep deal, relationship and operating context structured in one system across sourcing, evaluation, follow-up and execution.

The tools around the workflow

Taghash connects with the channels where communication, intake, research and coordination already happen.

Communication and relationship channels

• Gmail
• Outlook
• WhatsApp
• LinkedIn

These are the channels where conversations, introductions, outreach and follow-ups already happen. When that activity remains spread across separate tools, relationship history becomes harder to track and team visibility starts to weaken. Taghash helps bring that context into one operating layer.

Intake and capture workflows

• Google Forms
• Taghash Chrome Extension

These integrations support how opportunities and information enter the workflow. Forms help structure inbound opportunities and requests. The Chrome Extension helps teams capture relevant company context directly from the browser during sourcing and research. This reduces manual entry and keeps source activity closer to the system of record.

AI and automation

• ChatGPT
• Claude
• Zapier

This layer helps teams extend structured context into analysis, synthesis and workflow automation. AI becomes more useful when it works with live deal and relationship context. Automation becomes more valuable when routine steps run with more structure, visibility and control.

Why this matters

Integrations matter when they create continuity across the tools already in use.

For private capital teams, that means being able to:

• capture deal and relationship context closer to the source
• reduce manual data entry and repeated handoffs
• connect sourcing, communication, intake and research with internal workflows
• support AI-driven analysis with a structured operating context
• automate repeatable operational steps with more control

This is where execution becomes more reliable.

Instead of rebuilding context across inboxes, chats, forms, browser tabs and AI tools, teams can work from a connected system that keeps information usable across the deal lifecycle.

Where Taghash fits

Taghash operates at the centre of this workflow.

Email, messaging, forms, browser research, AI and automation all feed into one structured environment for execution. That gives teams better visibility across active work, stronger continuity across interactions and more control over how information moves.

For private capital teams, that matters because execution depends on context. The more fragmented the workflow, the harder it becomes to maintain momentum across sourcing, evaluation, relationship management and follow-up.

Final thought

Taghash integrations are built around how private capital already works.

By connecting Gmail, Outlook, WhatsApp, LinkedIn, Google Forms, the Taghash Chrome Extension, ChatGPT, Claude and Zapier, Taghash helps teams keep activity connected, context structured and execution on track across the workflow.

About Taghash

Taghash provides an end-to-end platform for venture funds, private equity, fund of funds and other alternative investment funds. Over the last seven years, we have served as the tech arm for top VCs, helping them manage operations across deal flow, portfolio, fund and LP management. 

We also offer a services layer to support execution across data management, legal and compliance, fund administration coordination, trustee and custodian interfacing and valuations and advisory.

Trusted by leading fund managers like Blume Ventures, Kalaari Capital and A91 Partners, we enable our clients to achieve greater success. Click here to book a demo.

In private capital, important signals often appear first in conversation.

A founder call can surface changes in customer traction, hiring plans or fundraising timing. An LP meeting can reveal interest level, objections, internal decision process or likely next steps. A portfolio review can bring up emerging risks before they appear in a formal update.

The challenge starts after the meeting ends.

In many firms, notes remain inside the meeting tool, in personal notes or in a summary that never reaches the system where the team manages deals, relationships, portfolio records and follow-ups. Over time, that weakens continuity. Follow-ups become inconsistent. Deal history loses depth. Relationship context stays with individuals instead of the firm. Future AI workflows also have weaker records to work from.

This is where the workflow of Granola → AI → Taghash through MCP becomes useful.

It creates a path from meeting capture to reasoning to workflow execution.

Granola captures the meeting context

Granola sits at the start of that workflow as the meeting capture layer.

It captures meeting notes, transcript context and conversation history. This is where the first usable record of the discussion exists. Before anything is written into a workflow system, Granola becomes the source of what was said, what was asked and what may matter later.

That matters because only some parts of a meeting belong in a deal record, relationship note or portfolio update. Raw notes are often too long. Transcripts include repetition, side comments and loose phrasing. Even summaries can combine core takeaways with secondary detail.

When all of that moves directly into the next system, the result is usually more clutter and less clarity.

The AI layer adds reasoning before the record is written

The middle step is what gives this workflow its value.

The AI layer sits between Granola and Taghash as the reasoning bridge. It accesses meeting context from Granola through MCP, interprets what matters and then uses Taghash’s MCP connection to write the relevant summary into the right workflow record.

That distinction matters.

Granola is the meeting source. Taghash is the workflow system. The AI layer handles interpretation in between. It reads the captured context, identifies the key takeaways and decides what should become part of the firm’s working record.

That can include:

• a concise meeting summary
• next steps
• open diligence questions
• key risks
• requested materials
• changes in conviction
• updates relevant to an LP or portfolio company

The aim is simple. Preserve what the team will need later in a form they can actually use.

Taghash turns meeting context into workflow context

Taghash is where the information becomes operationally useful.

Once the relevant meeting context has been interpreted, it can be written into the right record inside Taghash. That may be a deal entry, a company note, a relationship history, a portfolio update or a follow-up trail.

This makes the information more useful across the firm.

The next person opening a deal record does not just see that a meeting took place. They can see what changed, what matters now and what should happen next. The same applies to LP conversations and portfolio reviews. Context becomes easier to retain, search and use across future workflows.

Why this is stronger than a basic note sync

A basic sync can move content from one tool to another.

This workflow adds reasoning before the context is written into Taghash. That makes the record cleaner, more usable and easier to act on.

That difference matters in private capital because decisions usually build across repeated conversations over time. A founder may sound more credible in the third meeting than in the first. An LP may move from curiosity to intent over several months. A portfolio issue may first surface as a passing comment before it becomes a material concern.

Firms need records that carry context forward across those touchpoints.

What this looks like in practice

Founder meetings
A founder call captured in Granola can be interpreted into a structured summary and written into the relevant deal record in Taghash. That record can then reflect what changed, what needs follow-up and what should shape the next conversation.

LP conversations
An LP meeting can be translated into a clearer view of interest level, timing, objections and next steps, then written into the right relationship context in Taghash. That helps preserve continuity across long fundraising cycles.

Portfolio reviews
A portfolio review can be distilled into operating updates, blockers, support requests and partner actions, then attached to the relevant portfolio record. That creates a more useful operating history than a scattered trail of meeting notes and inbox follow-ups.

Why MCP matters in this workflow

MCP makes this model workable.

It gives the AI layer a structured way to operate across both systems. On one side, it can access meeting context from Granola. On the other, it can interact with Taghash as the workflow system where that context needs to live.

Without that bridge, teams still spend time reading notes manually, interpreting them by hand and entering updates one record at a time.

With MCP, the workflow moves much closer to what firms actually want in practice: access the meeting context, interpret it, structure it and write it into the right workflow record.

Final takeaway

Private capital is cumulative. The advantage comes from retaining what was learned across conversations and making it usable across the firm.

Granola captures the meeting.The AI layer interprets the discussion. Taghash becomes the workflow system where the relevant output is written into the right record.

Granola to Taghash through MCP helps private capital teams turn captured conversations into structured, reusable context across deals, relationships and portfolio workflows.

About Taghash

Taghash provides an end-to-end platform for venture funds, private equity, fund of funds and other alternative investment funds. Over the last seven years, we have served as the tech arm for top VCs, helping them manage operations across deal flow, portfolio, fund and LP management. 

We also offer a services layer to support execution across data management, legal and compliance, fund administration coordination, trustee and custodian interfacing and valuations and advisory.

Trusted by leading fund managers like Blume Ventures, Kalaari Capital and A91 Partners, we enable our clients to achieve greater success. Click here to book a demo.

If you are planning to launch an Alternative Investment Fund in India, the setup phase now carries more operational importance than before. The choices made here can influence how investors are onboarded, how service providers are coordinated and how prepared the fund is for ongoing reporting and compliance once it goes live. 

SEBI’s AIF Regulations were last amended on 19 November 2025 and the framework around AIFs has continued to evolve through the AIF Master Circular and newer reporting-related circulars issued in 2026.

For fund managers, this makes launch planning more than a registration exercise. It is also the stage where the fund’s operating setup starts taking shape.

Why setup quality matters more now

AIF launch tends to work better when the early groundwork is thought through carefully. That includes the structure, the core documents, the people responsible for key roles, the onboarding workflow, the service provider setup and the reporting processes the fund may need to support after registration.

The regulatory environment also reflects this broader level of preparation. Registration and PPM review now sit alongside expectations around team readiness, disclosure completeness, grievance handling, service provider coordination and downstream reporting obligations.

For fund managers, the practical takeaway is straightforward: setup quality has a direct bearing on how smoothly the fund can move into execution.

What fund managers should think through at launch

If you are setting up a fund, a few areas deserve close attention from the beginning.

1. Start with a structure that can support execution

The structure chosen at the outset affects several things that follow, including scheme documentation, investor onboarding flows, trustee coordination, service provider setup and ongoing compliance handling.

A strong structure usually reflects how the vehicle is expected to function over time, across fundraising, drawdowns, investment holding, investor servicing and reporting. This becomes easier when legal form and execution requirements are aligned early in the process.

2. Build a PPM that works in practice

The PPM is central to the fund launch. It supports registration, investor communication, contribution documentation and internal alignment across teams.

In practical terms, a well-prepared PPM should give fund managers and their teams enough clarity on the strategy, category, tenure, drawdown process, fee framework, investor rights, governance arrangements and key compliance responsibilities across the scheme lifecycle.

That is why it helps to review the PPM not only as a legal document, but also as an operating document.

3. Treat team readiness as part of launch readiness

Launch planning also benefits from clarity on who will own the key investment, compliance and operating responsibilities once the fund is live.

Certification requirements for the key investment team and compliance officers have made this even more important. For fund managers, this means team mapping, role ownership and certification readiness are worth addressing early rather than later.

4. Set up investor grievance handling early

Investor grievance handling is easier to manage when it is designed into the launch process. That usually means having clarity on who will receive complaints, how issues will be tracked internally and how escalation and response workflows will be handled.

That makes grievance readiness a practical part of launch planning.

5. Map onboarding and KYC workflows before first close

Investor onboarding can become time-consuming when multiple checks, documents, intermediaries and handoffs need to move together without a clearly mapped process.

For fund managers, it helps to define early how document collection, KYC checks, exception handling, intermediary coordination and status tracking will be managed. Early process design here can make the first close execution easier to manage.

6. Plan custodian, depository and issuer setup early

Custodian, depository and issuer-related setup now have greater operational relevance at launch than many teams assume.

More recent reporting and depository-related requirements have also increased the need for cleaner records, timely coordination with service providers and stronger reporting preparedness from the outset.

For fund managers, that makes early planning around custodians, RTAs, issuer setup and related workflows increasingly useful.

7. Prepare early if foreign investors are expected

If the fund expects foreign investors, RBI-related reporting readiness should also be planned in advance.

This is easier to handle when the relevant filing readiness is built into the launch workflow rather than addressed only at the transaction stage.

Where launch usually gets difficult

In many cases, launch becomes harder when important setup workstreams move forward in isolation.

One common challenge during fund launch is that important processes do not always come together at the same time. Documentation, onboarding, service provider setup, and reporting planning may all be progressing on different tracks.

AIF launch is usually more manageable when these threads are connected early enough to support one another. That includes structure, documentation, registrations, service provider coordination, onboarding preparation and compliance readiness.

Where Taghash fits

Taghash Services helps fund managers bring these setup workstreams together in a coordinated way.

Our support across the setup and launch lifecycle includes:

• Structuring and investment manager entity setup
• PPM drafting and finalisation
• Trustee coordination
• Trust deed and investment management agreement support
• SEBI registration support
• Operational review of PPM and contribution documents
• KRA, CKYC, LEI and GIIN related registrations
• PAN and TAN-related setup
• RTA and custodian coordination
• FIU and GST registration, where required
• RBI-related readiness for Form InVI support
• SCORES registration
• NSDL and CDSL issuer setup

For a new manager, this can help create a more structured launch process from the beginning.

For an experienced manager launching another vehicle, it can help improve coordination and reduce rework across parallel tasks.

That is the kind of preparation that can help fund managers move into operations with more confidence.

To take this forward, feel free to email us at atul@taghash.io.

CSCRF is a baseline operating requirement for SEBI-regulated entities, including AIFs, to strengthen cybersecurity and cyber resilience in a graded manner.

CSCRF stands for Cybersecurity and Cyber Resilience Framework issued by SEBI for SEBI-regulated entities. It sets expectations for governance, access controls, security monitoring, incident response readiness, assurance activities, including VAPT and regulatory reporting and disclosures.

Why it matters for AIFs in 2026

For AIF managers, cyber risk is now inseparable from investor data protection, fund operations continuity, third-party risk and governance quality. A breach can affect LP confidence, deal confidentiality and regulatory exposure. CSCRF is designed to address evolving threats and push consistent control maturity across regulated entities.

What AIF teams should actually execute in 2026

In 2026, CSCRF compliance comes down to five execution moves that are simple to state and hard to skip.

1. Governance you can evidence
   Approved policies, defined roles, periodic risk reviews and records that show what controls exist, who owns them and how they are monitored.
   
2. Identity and access discipline
   MFA on critical systems, least privilege, admin controls and clean onboarding and offboarding across all tools that touch fund and investor data.
   
3. Third-party and cloud risk management
   An AIF stack is third-party intensive. 2026 readiness needs a clear third-party inventory, access boundaries, security checks and documented oversight.
   
4. Assurance on schedule
   Plan VAPT early, submit on time, close findings on time and keep closure evidence organised.
   
5. Incident readiness that works under pressure
   Clear incident playbooks, escalation paths, logging and audit trails and a reporting workflow that can meet short timelines.

How Taghash Services can help

For AIFs, we run CSCRF as a structured execution program:

• CSCRF scope definition, gap assessment, control mapping and evidence checklist
• Policy and SOP stack aligned to CSCRF expectations
• VAPT coordination, report packaging, closure tracking and revalidation support aligned to the one-month and three-month clocks
• Incident response readiness aligned to CERT in timelines

If you share your AUM band and your core systems list, we will convert it into an actionable plan with sequencing, ownership and a complete audit-ready trail.

For more information email us at atul@taghash.io.

Social media is now a common place where securities market-related content is shared. SEBI has issued a circular to improve transparency so investors can identify when such content is uploaded by a SEBI-regulated entity or its agent.

AIFs are within scope because the circular is addressed to multiple categories, including Alternative Investment Funds and it also applies broadly to all persons regulated by the Board and their agents.

SEBI states that the provisions come into effect from 1 May 2026 for all content uploaded on or after that date.

Who this applies to in the AIF ecosystem

This guidance is relevant for:

• AIFs that are SEBI-regulated entities
• Agents of SEBI-regulated entities, which the circular also covers

The circular uses the umbrella concept of persons regulated by the Board by reference to SEBI’s intermediaries framework, which is why the approach is not limited to a single category.

What counts as social media content for this rule

SEBI defines content uploaded on Social Media Platforms broadly. It includes content or videos published, broadcasted, uploaded, or posted on any SMP. It also explicitly includes content shared in closed groups and publicly available groups and lists examples such as YouTube, Instagram, Facebook, WhatsApp, X, LinkedIn, Threads, Telegram, Reddit and others.

For AIF teams, this matters because communication can extend beyond public posts into private groups and communities. Under this circular, closed group sharing is still within the scope of SMP content.

The core requirement in plain language

If you are a SEBI-regulated entity, such as an AIF or you are an agent and you upload securities market-related content on SMPs, SEBI requires you to prominently disclose your registered name and registration number in two places.

1. On the home page of your social media handle
2. At the beginning of each securities market-related post or video

How to comply depends on your setup

SEBI sets out different instructions depending on whether you have one registration or multiple registrations and whether you are a regulated entity or an agent.

1) AIF or other regulated entity with a single SEBI registration

You must disclose your registered name and registration number on the home page near the handle name and at the beginning of each securities market-related post or video.

2) AIF or other regulated entity with multiple SEBI registrations

SEBI requires two actions:

1. On your handle home page, provide a weblink directing to your website listing all registered names and registration numbers.
2. At the beginning of each securities market-related post or video, disclose the registered name and registration number relevant to the capacity in which you are posting.

SEBI provides an example showing that when an entity has multiple registrations, the disclosure used for a post should match the specific capacity relevant to that content.

3) Agent with a single registration as agent

If you are an agent, SEBI requires a two-part disclosure. You must disclose the principal’s registered name and registration number, followed by the agent’s registered name and registration number. This must appear on the home page and at the beginning of each securities market-related content.

4) Agent with multiple registrations as an agent

SEBI requires:

On the handle home page, a weblink directing to the agent’s website listing the registered names and registration numbers of the principal entities the agent works for, followed by the agent’s own registered names, registration numbers and capacities.

At the beginning of each content, disclosure of the principal entity relevant to that content, followed by the agent’s registered name and registered number.

SEBI also provides an example illustrating how an agent should disclose principal details relevant to the specific content, along with the agent's details.

A simple action checklist for AIF teams

1. Confirm whether you use a single SEBI registration context for social content or whether you operate under multiple SEBI registrations across the group.
2. Update the home page of each social media handle with the required disclosure or with the required weblink where multiple registrations apply.
3. Ensure every securities market-related post or video uploaded on or after 1 May 2026 includes the required disclosure at the beginning.
4. If you have multiple registrations, ensure the disclosure used in each post matches the capacity relevant to that content.
5. If you use agents, ensure principal details are disclosed first, followed by agent details, on the home page and at the beginning of each content.
6. Apply the same approach even when content is shared in closed groups on SMPs.

Closing note

SEBI’s direction is focused on transparent identification. When AIFs and their agents upload securities market-related content on SMPs, the registered name and registration number should be visible on the handle home page and at the beginning of each relevant content for uploads from 1 May 2026.

About Taghash

Taghash provides an end-to-end platform for venture funds, private equity, fund of funds and other alternative investment funds. Over the last seven years, we have served as the tech arm for top VCs, helping them manage operations across deal flow, portfolio, fund and LP management. 

We also offer a services layer to support execution across data management, legal and compliance, fund administration coordination, trustee and custodian interfacing and valuations and advisory.

Trusted by leading fund managers like Blume Ventures, Kalaari Capital and A91 Partners, we enable our clients to achieve greater success. Click here to book a demo.

DPDP and AIF rules meet in fund operations because AIF managers handle investor personal data while running SEBI-regulated workflows. In practice, teams operate a dual compliance stack: SEBI for fund mechanics and DPDP for privacy and security.

SEBI governs fund formation, fundraising, investments, reporting and governance. DPDP governs how digital personal data is collected and used, stored and shared, protected through reasonable security safeguards, notified in case of a breach and deleted once the purpose is met, subject to legally required retention. DPDP applies to private organisations and, in specified contexts, government processing of digital personal data.

DPDP is operational through the DPDP Rules, 2025, with an 18-month phased compliance period. In parallel, SEBI’s cybersecurity and cyber resilience framework raises expectations for security controls and governance.

DPDP scope and principles

Who it applies to:

• Any organisation processing digital personal data of individuals in India
• Indian and foreign entities offering goods or services in India, even if processing happens outside India
• Fund and fund vendor ecosystems, including managers, administrators, RTAs, KYC providers, CRMs and data rooms and other vendors that touch investor data

It is not intended for purely personal or domestic use. For AIFs, scope matters because processing is vendor-mediated and vendor location does not remove DPDP exposure if the data principal is in India or the service is offered into India.

The principles that shape fund workflows:

• Consent and transparency
• Purpose limitation
• Data minimisation
• Accuracy
• Storage limitation
• Security safeguards
• Accountability

In a fund context, this becomes a practical design. What you collect, where you store it, who can access it, how long you keep it and how you respond when something goes wrong.

DPDP requirements for investor onboarding

Onboarding is the highest concentration of personal data in an AIF. A typical KYC pack includes identity and address documents, PAN, banking coordinates, UBO details for institutions and tax declarations. The key point is that the data is high-impact and widely shared during onboarding across internal teams and vendors.

Personal data in onboarding is broader than KYC PDFs. It also includes identifiers like name, phone and email, banking details, tax and account data and in many contexts online identifiers and system logs linked to a person.

DPDP pushes onboarding away from buried, catch-all clauses and toward clear, purpose-specific communication. The Rules emphasise a separate consent notice that is clear and states the specific purpose.

A DPDP-aligned consent notice should be separate and in plain language, covering:

• What data is collected and the specific purpose for collection and use
• Who it is shared with, such as KYC providers, fund administrators, RTAs, auditors and advisors, where applicable
• Retention approach, framed as purpose-based retention plus legally required retention
• Rights, grievance handling and consent withdrawal, with a visible contact point for queries

Consent should be free, specific, informed and revocable and should not rely on dark patterns or pre-ticked boxes. Consent withdrawal must be workable, with a clear channel and SOP. Where retention is required for legal or regulatory reasons, the notice should clarify what stops and what must continue.

Children’s data is uncommon in AIF onboarding, but if any child’s personal data is processed, DPDP requires verifiable parental consent and additional safeguards.

DPDP controls after onboarding

After onboarding, personal data continues to flow through capital calls, distributions, investor statements, tax documentation, audits and routine communications.

Purpose limitation and role-based access

Use data only for the purpose stated in the consent notice and restrict access by role. This reduces casual reuse and limits internal exposure.

Data minimisation and accuracy

Minimise collection and reuse so you are not moving data you do not need. Maintain accuracy of core investor master data, including contact details, authorised signatories and bank updates, so statements and notices do not go to the wrong place.

Retention and deletion with an evidence trail

Delete personal data once the purpose for which it was collected is served, unless retention is required by law or regulation. Implement a retention schedule based on applicable legal and SEBI requirements, internal policy and an evidence trail showing what was retained, what was deleted and why.

Rights requests and timelines

DPDP gives data principals rights such as access, correction and updating and erasure or removal in certain situations, along with grievance redressal and consent withdrawal.

Two operational requirements matter:

• Data fiduciaries must respond to rights requests within a maximum of 90 days
• Individuals can nominate someone else to exercise their rights

Fund operations should run a simple intake, verification and response workflow that meets the 90-day outer limit, including requests that come through authorised signatories or nominated persons.

Where DPDP meets SEBI in daily workflows

SEBI’s February 2026 circular on reporting the value of AIF units to depositories requires NAV reporting per ISIN through RTAs with a defined timeline. The operational deadline is to upload the latest available NAV for each ISIN in the depository system before 1 May 2026 or within 30 days from the valuation date, whichever is later.

This creates a repeatable data flow across the manager, RTA, depository systems and internal teams. When a workflow becomes repeatable, privacy and security controls cannot be informal. Role-based access, audit trails and controlled sharing become part of the operating system.

Breach response under DPDP

Incidents in funds are often ordinary but serious, for example, a statement sent to the wrong investor, a compromised mailbox, an exposed shared folder or a vendor incident.

A DPDP-ready response should:

• Inform affected individuals without delay in plain language
• Include what happened, possible impact, steps taken and contact details for help
• Notify the Data Protection Board of India without delay and furnish detailed information within 72 hours or within a longer period if permitted
• Preserve evidence, contain exposure and document actions end-to-end

SEBI’s cyber resilience framework sets expectations for security controls and governance. DPDP adds privacy, breach notification and accountability on top, so the incident playbook should cover both.

Penalties and why this matters

Non-compliance can lead to significant monetary penalties. The government explainer highlights penalties up to ₹250 crore for failures relating to reasonable security safeguards, with other penalty categories such as up to ₹200 crore for breach notification failures and child-related violations and up to ₹50 crore for other violations. Penalty quantum depends on the nature of the violation, scale of impact and facts around negligence and repetition.

Third-party ecosystem: vendors and consent managers

AIF operations are third-party dependent. Investor data touches KYC providers, fund administrators and RTAs, auditors and advisors and common tools such as CRMs, data rooms, cloud storage and email systems. DPDP pushes vendor management from trust-based to contract and control-based.

Vendor contracts and SOPs should define:

• Data scope and purpose
• Expected reasonable security safeguards
• Incident escalation and cooperation, including timelines and evidence sharing
• Retention and disposal at termination
• Logs and audit evidence that the vendor must provide

Legacy vendor arrangements often fail here because they were designed for convenience, not accountability.

DPDP also introduces Consent Managers and the government explainer notes that they must be companies based in India. Even if most AIF managers do not use a Consent Manager immediately, this signals the direction of travel toward more standardised consent management and clearer consent records over time.

Significant Data Fiduciary readiness and AI workflows

DPDP introduces Significant Data Fiduciaries with higher obligations, such as independent audits and impact assessments, with designation criteria expected to be clarified. Larger managers should prepare early because the compliance load can change once classified.

The government explainer also links SDF expectations to stricter checks when using new or sensitive technologies. For funds, that matters as teams adopt AI-assisted workflows for onboarding automation, screening, analytics, profiling or investor servicing.

Practical next steps for AIF teams

Keep it recurring:

• Map data flows from onboarding to exit, including every vendor touchpoint
• Standardise separate consent notices, grievance handling and the visible contact point process
• Design consent capture and withdrawal workflows across systems, not only in documents
• Implement role-based access and controlled sharing for investor reporting and sensitive documents
• Define retention schedules with evidence trails for retention and deletion
• Refresh vendor contracts with DPDP-aligned processor clauses and incident cooperation
• Run one breach drill so the 72-hour Board reporting expectation is realistic
• Map overlaps between DPDP, KYC and AML obligations, SEBI recordkeeping and SEBI cyber resilience controls

Closing

As AIF operations become more institutional, managers who treat investor personal data as a core asset, not as paperwork, will build stronger LP confidence. In 2026, good operations combine SEBI-compliant fund mechanics with DPDP disciplined data handling, running together as one seamless system.

About Taghash

Taghash provides an end-to-end platform for venture funds, private equity, fund of funds and other alternative investment funds. Over the last seven years, we have served as the tech arm for top VCs, helping them manage operations across deal flow, portfolio, fund and LP management. 

We also offer a services layer to support execution across data management, legal and compliance, fund administration coordination, trustee and custodian interfacing and valuations and advisory.

Trusted by leading fund managers like Blume Ventures, Kalaari Capital and A91 Partners, we enable our clients to achieve greater success. Click here to book a demo.

On 12 February 2026, the IRDAI issued a clarification circular on how insurers can invest in AIFs when the fund may undertake overseas investments, utilising Exclusion Rights while still complying with Section 27E of the Insurance Act, 1938.

If insurer money is in your fund, the message is crystal clear:

Your process must demonstrate that insurer capital and proceeds are not invested outside India, supported by documentation, reporting and audit evidence.

The core problem IRDAI is solving

IRDAI’s existing framework already allowed insurers to invest in AIFs, but it required insurers to ensure their AIF investments do not result in overseas exposure under Section 27E.

In practice, many AIF strategies may include overseas opportunities, but the question is:

How do insurers participate in the fund without violating Section 27E when a fund does overseas deals?

IRDAI’s answer is a structured approach using Excusal Rights, paired with a strict operating framework that prevents any insurer capital from being drawn down, used, pledged or charged toward overseas assets.

What IRDAI clarified 

IRDAI’s clarification boils down to a few practical rules that make excusal rights enforceable in day-to-day fund operations and auditable under Section 27E.

1) Insurers can invest even if the AIF does overseas deals, but only if the excusal is airtight

IRDAI allows insurer investments in such AIFs if the insurer has “Excusal Rights” and the insurer’s proceeds are not invested outside India.

But IRDAI does not stop at intent. It demands an evidence trail.

2) The fund documents must hard-code the restriction

IRDAI requires a clause in the PPM stating that insurer capital and proceeds will not be drawn down, used or pledged for any investment outside India. In the annexure framework, this is described as hard-coding Section 27E into fund documents, including a “Statutory Exclusion” clause and a “Deemed Excusal” covenant in the contribution agreement.

3) There must be third-party verification

IRDAI requires confirmations and certifications, such as:

• Statutory auditors of the AIF confirming insurer capital is not invested outside India
• AIF compliance certificate confirming that excusal rights were validly invoked and no overseas costs were charged to the insurer
• Insurer's concurrent auditor certification of excusal rights compliance

4) Exposure limits must consider direct plus indirect exposure

IRDAI replaces a clause to clarify that the single AIF exposure limit must be complied with considering both direct exposure and indirect exposure through FoFs.

The operating framework IRDAI expects

The annexure is the real playbook. It lays out a “comprehensive operating framework” built around “zero contamination” of insurer capital.

A) Documentation level controls

You need the fund documents to explicitly define insurer capital as restricted and automatically excused from overseas opportunities.

B) Process flow controls

IRDAI expects the manager to run pre-drawdown checks and reporting that makes the excusal operational, not informal. Examples in the annexure include:

• The insurer provides a Section 27E declaration
• The manager flags the insurer as restricted domestic only in the investor register
• Before overseas drawdowns, the manager generates a drawdown eligibility schedule showing insurer allocation as zero
• Quarterly reporting includes a Section 27E compliance annexure showing insurer allocation as ₹0 and beneficial interest as 0% in overseas assets

C) Certification “three lines of defence”

IRDAI’s framework describes a three-tier certification model:

• Level 1: AIF compliance officer and manager quarterly certification
• Level 2: AIF statutory auditor annual certification, including economic segregation and no P and L attribution
• Level 3: Insurer concurrent or internal auditor quarterly verification using cash flow checks

Practical checklist for AIF managers and fund ops teams

Use this as a readiness scan aligned to what the circular actually expects.

Fund documentation readiness

• PPM includes a clear Section 27E exclusion clause for insurer capital and proceeds
• The contribution agreement includes a standing deemed excusal instruction for overseas opportunities
• Side letters, if used, do not conflict with the above

Deal and accounting readiness

• Every deal is tagged clearly as domestic or overseas
• Deal-specific overseas expenses are not pooled into general fund expenses and are excused from insurer allocation
• Accounting can support segregation so the insurer has zero attribution for overseas assets and related P and L

Capital call readiness

• You can generate a drawdown eligibility schedule that explicitly shows insurer allocation as zero for overseas calls
• You issue a negative confirmation-style notice to the insurer for overseas calls, stating their share is zero

Reporting and audit readiness

• Quarterly report includes a Section 27E compliance annexure with overseas totals and insurer allocation as ₹0
• AIF compliance certificate workflow exists for quarterly reporting
• Annual statutory auditor certification language and scope are agreed upfront
• Insurer concurrent auditor verification can be supported with clean evidence trails

Where Taghash fits

This circular effectively asks for a repeatable operating system:

• Investor level restriction flags
• Deal tagging and expense tagging
• Capital call calculations that handle exclusions cleanly
• Reporting packs that include the required annexures
• Audit trails that are easy to evidence

Taghash can support by turning this into a tracked workflow from document clauses and onboarding declarations to deal tagging and drawdown controls to quarterly reporting and certification packs, so teams can show compliance without spreadsheet firefighting.

About Taghash

Taghash provides an end-to-end platform for venture funds, private equity, fund of funds and other alternative investment funds. Over the last seven years, we have served as the tech arm for top VCs, helping them manage operations across deal flow, portfolio, fund and LP management. 

We also offer a services layer to support execution across data management, legal and compliance, fund administration coordination, trustee and custodian interfacing and valuations and advisory.

Trusted by leading fund managers like Blume Ventures, Kalaari Capital and A91 Partners, we enable our clients to achieve greater success. Click here to book a demo.

Private market valuations are often discussed using shorthand such as comparable company multiples (CCM), comparable transaction multiples (CTM) or the entry price from the most recent financing. Under current industry guidance for private equity and venture capital, these are only part of the toolkit. The objective is to estimate fair value, meaning the price that would be received to sell an asset in an orderly transaction between market participants at the measurement date.

Valuation is a recurring fund workflow that feeds reporting, reviews and LP communication. Taghash Services runs this end-to-end with an IPEV-aligned process, audit-ready documentation and a repeatable evidence trail, so quarter closes stay predictable and valuations stay defensible.

What valuations are

A valuation is an estimate of the value of an investment at a specific measurement date, prepared using a valuation technique and inputs that reflect market participant assumptions.

In private markets, there is usually no continuous public price discovery for each holding. That is why valuation is a disciplined process of converting evidence into a fair value measurement by selecting:

• an appropriate valuation approach and technique
• inputs that are supportable
• documentation that explains the selection and what changed since the prior measurement date

Practically, valuation is not just a number; it is the technique, inputs and evidence trail that make the number credible.

Why valuations matter

Valuations matter because they are at the centre of fund credibility and decision-making.

LP reporting and transparency
Fair value measurements support investor reporting and help users of financial statements make informed economic decisions.

Fund performance measurement
Return metrics and portfolio concentration views depend on valuation consistency. Inconsistent technique selection or unsupported inputs can distort what the portfolio is actually doing.

Governance and review readiness
Best practice guidance emphasises consistency, calibration discipline and documentation of assumptions and changes, especially when inputs are not directly observable.

Portfolio decisions
Follow-ons, exits and write-downs improve when valuation reflects current fundamentals and market evidence rather than stale entry prices.

Fair value frameworks require entities to maximise the use of relevant observable inputs and minimise the use of unobservable inputs. This is why two teams can apply the same technique, such as comparable company multiples, but reach different valuation conclusions depending on the quality of inputs, the appropriateness of adjustments and the completeness of documentation.

Start with the three core valuation approaches

IFRS 13 and private markets guidance organise valuation techniques into three broad approaches: market, income and cost.

Market approach

Uses prices and market data from comparable assets or companies.

Common techniques and indicators include:

• Comparable Company Multiples
• Comparable Transaction Multiples
• Industry or sector valuation benchmarks, where they reflect how market participants price
• Available market prices and other observable price inputs where available

This approach is widely used, but it depends on selecting defensible comparables and making appropriate adjustments for differences in growth, margins, scale, liquidity and risk.

Income approach

Values an asset based on expected future cash flows discounted to present value.

Common techniques include:

• Discounted Cash Flow at the company level
• Discounted cash flows from the instrument, often used for debt-like or structured instruments, where investor cash flows can be modelled

This approach typically becomes more decision useful as cash flows become more supportable, either through business maturity or contractual terms.

Cost approach

Reflects the amount required to replace the service capacity of an asset.

In private market portfolios, this commonly appears as:

• Net Assets method, particularly for asset-heavy businesses or investment holding structures, where the balance sheet is the most relevant anchor

Why recent transaction price is not a default technique over time

In private markets, the most recent financing price can be important evidence, especially close to the transaction date. Current guidance emphasises calibration to the entry transaction, meaning you align valuation model inputs so that, at initial recognition, the technique reconciles to the transaction price when that transaction price represents fair value.

At subsequent measurement dates, the question is what has changed since entry and how that change should be reflected in the valuation technique and inputs. In practice, this means:

• Treat the recent transaction price as an evidence anchor
• Document calibration to the entry transaction as a step within the chosen technique
• Update fair value based on company progress, market movements and any new financing or secondary evidence

Techniques needed for complex capital structures

Private market cap tables often include liquidation preferences, participation features, convertibles and multiple share classes. In these situations, you still estimate overall value, but you also need equity allocation across classes based on rights and terms. Guidance explicitly supports techniques built for these structures.

PWERM: Probability Weighted Expected Return Method

Use when there are a small number of discrete, plausible outcomes and you can estimate values and probabilities for each.

OPM: Option Pricing Method

Use when outcomes are better represented as a continuous distribution and you need to allocate value across share classes given their rights and preferences.

Hybrid method: scenario-based method plus OPM

Use when part of the future is best represented through discrete scenarios and part through a distribution, which is common as companies approach but have not yet reached a clear liquidity event.

CVM: Current Value Method

Allocates equity value as though the business were to be sold on the measurement date. This is typically most relevant when an exit is imminent and outcomes are relatively narrow.

CVM is typically appropriate only when a near-term liquidity event provides a reasonably observable value anchor and should not be used as a default approach where outcomes remain wide or highly uncertain.

Backsolve: OPM backsolve

Backsolve is a commonly used application within an OPM framework that works backwards from a recent preferred financing price, using the cap table rights and assumptions such as volatility and time to liquidity, to infer implied total equity value and allocate across classes.

Backsolve should be used only when the financing is assessed to be representative of fair value and the key assumptions used in the model, including volatility and time to liquidity, are supportable and documented.

Fund of Funds and LP interests have their own anchors

When valuing fund interests, a common starting point is the reported NAV, with adjustments only when supported by credible market participant evidence, such as relevant secondary market pricing. This aligns with the emphasis on observable inputs and market participant assumptions.

Useful system labels include:

• NAV-based approach for fund interests
• Secondary market discount or premium to NAV, only when supported by credible market evidence

A practical final picklist that stays credible

If you want one set of valuation technique options that works across VC, PE, Fund of Funds and family office portfolios, this picklist is aligned with the approaches above and current private markets guidance.

1. Comparable Company Multiples
2. Comparable Transaction Multiples
3. Calibration to the entry transaction
4. Discounted Cash Flow, company level
5. Discounted Cash Flow, instrument cash flows
6. PWERM
7. OPM
8. Hybrid method, scenario-based plus OPM
9. CVM
10. Backsolve, OPM backsolve
11. Net Assets method
12. Sum of the Parts
13. Available market prices and other observable market inputs
14. NAV-based approach for fund interests
15. Secondary market discount or premium to NAV

Where Taghash Services fits

Taghash Services fits in as the execution layer for the valuation cycle. We run data packs and follow-ups, apply the appropriate technique by instrument and stage and maintain an assumptions register and evidence trail through review and sign-off. The result is fair value marks that hold up under scrutiny and flow cleanly into LP reporting and quarter-end deliverables.

Over December and January, we shipped a set of updates to make everyday work smoother, more connected and far less manual. From richer contact context to more flexible transactions, stronger automation and clearer cross-company insights, these improvements are built for real fund workflows.

Introduced Contact Enrichment

Now you can access smarter contact context without the extra work. When you add a new contact with a valid website, Taghash now enriches the profile automatically using trusted third-party sources. If associated members are found externally, their profiles are enriched too.

You will notice:

• More complete contact profiles: Relevant professional and company details are pulled in automatically.
• Better network visibility: If associated members are found externally, their information is enriched too, helping you understand the wider network.
• Less research, better conversations: Your team spends less time hunting for context and more time engaging with confidence.

Updated SAFE handling 

Here’s to more flexibility with direct divestments. As SAFE instruments do not always follow a clean conversion path, you can now record divestments and returns directly against SAFE transactions.

Key improvements include:

• Direct SAFE divestments: Record divestments and returns directly against SAFE transactions.
• Convert when you want to: Convert SAFE into equity when needed or divest directly for a return or refund.
• Partial divestments: Divest a SAFE investment fully or partially, including one or more SAFE investments.
• One workflow for SAFE and equity: Manage SAFE and equity transactions within the same flow.

Added Transaction Comments

Now the context always stays attached to the transaction because sometimes a transaction needs a quick note to capture the why behind the entry. You can now add comments across all transaction types.

You can:

• Add comments while recording: Including equity and SAFE instruments.
• See comments at a glance: A Comment column in the transaction table shows notes instantly.
• Keep everyone aligned: Better handoffs, clearer decisions and less back and forth.

Launched Zapier Integration

Workflow automation across your tools is made possible. You can now connect Taghash with external applications using Zapier and reduce repetitive steps.

You will notice:

• Triggers from platform events: Set automations based on deal stage changes, category updates and other platform activity.
• Two-way automation: Trigger actions in external apps when something happens in Taghash and update Taghash based on external events like form submissions.
• Practical automations that save time: Create new deals, update deal data and add notes automatically to match your team’s process.

Introduced a new Analytics Tab

Cross-company dashboards are now available in one unified workspace. The new Analytics Tab brings portfolio analytics and cross-company dashboards together so teams can analyse, compare and share insights faster.

Key improvements include:

• Unified dashboard experience: Open multiple dashboards, organize charts easily and pin important dashboards for quick access.
• Smarter search and navigation: Find dashboards and specific charts quickly with built-in search.
• Cross-company analysis: Compare metrics across companies in one dashboard. Standardize metrics using aliases, apply date filters and group data monthly, quarterly or yearly.
• Flexible customization and collaboration: Resize and arrange charts, add notes, duplicate dashboards or charts and move charts across dashboards.
• Easy sharing and export: Download full dashboards as PDFs or export individual charts as Excel, PDF or images. Share via email in a few clicks.

Enhanced LP Transactions

Single-entry support and custom fields are active now as we improved the LP transaction workflow to make small updates easier and to support fund-specific tracking needs.

You can now:

• Add single transactions: Enter individual transactions directly from the transactions view, including folio number, transaction date and description.
• Add custom fields: Capture additional financial or operational data not covered in standard fields.
• Use custom fields in templates: Include custom fields in document templates for automatic data injection into capital call documents.
• Keep bulk uploads compatible: Custom fields work in bulk uploads by adding the custom field columns in your CSV.

Team Note

This month’s release includes improvements across contacts, transactions, automation and analytics. Highlights include Contact Enrichment, flexible SAFE handling, Transaction Comments, Zapier Integration, the new Analytics Tab and upgraded LP transaction workflows with single entry and custom fields. These changes aim to streamline operations, reduce manual work and improve overall data visibility for teams.

— The Taghash Team

SEBI has made digital accessibility a mandatory expectation for SEBI-regulated entities, linked to obligations under the Rights of Persons with Disabilities Act, 2016 and framed as investor protection for access to digital platforms. SEBI then issued compliance guidelines and a later clarification that reshaped near-term reporting obligations and timelines.

At Taghash Services, we help VC funds meet SEBI digital accessibility requirements across fund websites and investor portals. We audit against benchmarks such as WCAG 2.1 AA, translate findings into an execution ready remediation backlog, retest fixes after deployment and deliver a platform-wise readiness and compliance report.

What SEBI requires

Across SEBI’s circular, compliance guidelines and clarification, three practical requirements emerge:

1. Platform-level reporting of readiness and compliance

SEBI’s clarification drives a platform-wise view. Funds should be able to state, for each investor facing a digital platform, whether it is compliant, in progress or pending, with clear next steps. The commonly cited near-term milestone is platform-wise reporting by March 31, 2026, using SEBI’s prescribed format, as reflected in the clarification.

2. Measured against recognised accessibility benchmarks

In practice, audits and remediation are typically aligned with WCAG, with WCAG 2.1 AA being the most frequently used operating benchmark in implementation programs. Accessibility specialists summarising the SEBI programme commonly reference WCAG 2.1 AA in the compliance approach.

3. Compliance is operational and not temporary 

This is not a one-time design refresh. SEBI’s intent is inclusive access across investor-facing digital platforms, including onboarding and KYC flows that can otherwise exclude persons with disabilities.

What funds should treat as in scope

For a VC fund, scope is easiest to define by investor journeys.

If an investor or beneficiary interacts with you digitally and an accessibility barrier could prevent use, treat that platform as in scope. This usually includes:

• Public fund website and disclosure pages
• Investor or LP portal, including login and account management
• Digital onboarding, such as subscription journeys, KYC workflows, forms, uploads, e-sign and OTP flows
• Document libraries, statements, notices and downloadable reports
• Grievance or contact journeys, including “write to us” and complaint routes

This “platform inventory first” approach aligns with SEBI’s platform-wise reporting direction.

How to run an audit that holds up

A compliance grade audit is not only an automated scan. Automated tools catch patterns quickly, but they miss many real-world blockers.

A defensible audit program typically includes three layers:

1. Automated crawl and scan
   Scan the full publicly accessible site or platform to identify broad issue patterns, coverage gaps and risk areas.
2. Manual expert review of unique templates and components
   Manually assess every distinct layout, component and interaction pattern. This focuses effort on what users actually experience, rather than repeating checks across similar URLs.
3. Assistive technology verification
   Test key flows using keyboard-only navigation and screen readers to validate real-world usability.

This approach provides comprehensive, repeatable and defensible coverage, aligning with the expected conduct of accessibility audits under regulatory and enterprise standards.

Remediation: what typically needs fixing on fund sites and portals

Most fixes fall into repeatable buckets. Focus on fixing the system so new pages stay compliant.

Keyboard access and focus management
Every core journey should work without a mouse. Tab order should be logical, focus should be visible and modals should not trap focus.

Forms and onboarding
Inputs need clear labels. Errors should be explained in text, not only colour. Upload, consent and OTP flows must be operable by keyboard and understandable via screen readers.

Navigation and structure
Use meaningful headings and landmarks. Ensure menus, accordions and interactive elements are accessible. Links and buttons should have descriptive names, not “click here”.

Documents and disclosures
Avoid scanned PDFs for investor-facing material. Where documents are part of an investor journey, they need to be readable and navigable for assistive technologies.

Prioritise remediation by investor impact first, then severity. That is what prevents a situation where low-impact issues consume time while critical journeys remain blocked.

Evidence: what to keep ready for reporting, reviews and grievances

Most teams struggle because evidence is scattered.

Since the requirement is platform-level readiness and compliance reporting, funds should maintain an “accessibility compliance file” that supports the report and makes future reviews faster. A practical evidence set includes:

• Platform inventory with owners and vendor details
• Audit scope, methodology and findings
• Issue log with severity, mapping to the benchmark used and fix recommendations
• Remediation tracker with tickets and acceptance criteria
• Retest results after fixes
• The final platform-wise readiness and compliance report in SEBI’s format

This also helps with grievance handling because the fund can show a clear trail of assessment, remediation and verification.

In a nutshell

SEBI’s digital accessibility programme becomes manageable when it is treated as ongoing operating hygiene.

Platform-wise readiness reporting forces clarity on what platforms you own, what you assessed, what is compliant today, what is in remediation and what evidence supports it.

With Taghash Digital Accessibility Service running this as a repeatable process, funds move from one-off fixes to a steady cadence. It keeps investor journeys accessible, reporting clean and evidence-ready when reviews or grievances arise.

About Taghash

Taghash provides an end-to-end platform for venture funds, private equity, fund of funds and other alternative investment funds. Over the last seven years, we have served as the tech arm for top VCs, helping them manage operations across deal flow, portfolio, fund and LP management. 

We also offer a services layer to support execution across data management, legal and compliance, fund administration coordination, trustee and custodian interfacing and valuations and advisory.

Trusted by leading fund managers like Blume Ventures, Kalaari Capital and A91 Partners, we enable our clients to achieve greater success. Click here to book a demo.

Quarterly portfolio reporting looks simple on paper. Pull the latest MIS. Update ownership and investment details. Summarise what changed. Share the report.

In reality, it is one of the most failure-prone fund workflows. Data sits across tools. Numbers move late in the cycle. Definitions drift between teams. Versions multiply over email. Then someone asks a basic question that is hard to answer quickly: what changed, why did it change and where is the supporting backup?

Most teams already have the data. The pain comes from converting that data into a consistent, repeatable portfolio company report every quarter.

Taghash Portfolio reduces reporting friction with template-driven report generation. Upload a Word template with placeholders once. Taghash pulls accurate values from portfolio records and MIS already inside the platform. It then generates a formatted portfolio company update you can download instantly or receive by email.

This is built for funds that want reporting to run like a controlled process, not a quarter-end hassle.

What this feature is

Inside Taghash Portfolio, you can auto-generate portfolio company updates using your own reporting template. The template carries your structure and Taghash fills it with the right data every time.

A template is a Word document that includes:

• Your fund’s standard headings and narrative sections
• Placeholders for key fields like company name, sector, valuation, stake and key updates
• Tables that auto-populate, such as transaction history and quarterly or yearly MIS snapshots

When you click Generate Report in Taghash Portfolio, the flow stays consistent each time:

1. Select the fund
2. Define the “as on” date
3. Upload your template with the correct placeholders
4. Generate the report
5. Download it from Taghash and optionally receive it by email

Every output follows your format. Every field pulls from the platform.

Why this matters for fund teams

Each benefit below maps to a common failure point in quarterly reporting and explains what improves when the workflow becomes template-driven.

1) Reporting supports governance and audit trail

Portfolio reporting influences LP trust, internal decision-making, audit readiness and IC quality. When reporting is inconsistent, teams spend time on follow-ups, rechecks and explanations. 

A static template creates a stable reporting standard. It maintains consistency across quarters and across team members. It also strengthens the audit trail.

2) Consistent structure improves review quality

Portfolio reviews work better when updates are comparable over time. A consistent frame keeps discussions anchored and makes it easier to spot the signal. 

If the structure changes each quarter, it becomes harder to spot the signal. If fields are missing, stakeholders fill gaps with assumptions. If KPIs move without context, the conversation drifts into debate instead of action. Template-driven reporting creates a consistent frame that keeps discussions anchored.

3) MIS adds value when it directly drives the reporting output

MIS is most useful when everyone works from the same numbers. Keeping MIS inside the system reduces inconsistencies and shortens review cycles.If numbers are copied and pasted across tools, inconsistencies show up and reduce confidence. When MIS stays inside the system and flows into reporting, review becomes faster and disputes become easier to resolve.

4) Quarter selection becomes deterministic

A common issue in quarterly packs is a reporting cut-off mismatch. The “as on” date flow helps keep period selection consistent across the team.

One person uses a different “as on” date, another uses a different quarter cut and the pack becomes hard to reconcile. Set the date and Taghash picks the relevant quarters.

5) Templates save time for better judgement

Templates remove repetitive manual work so teams can spend time on the parts that need judgement and context.

As a result, less time is spent on formatting and reconciliation and more time on the work that matters, such as variance explanations, key updates, risks and next steps.

How to generate a portfolio report in Taghash

The steps below reflect the exact workflow a fund team follows inside Portfolio, from template setup to quarterly reuse.

Step 1: Create your Word report template

Start with the structure you already use for LP updates or internal reviews. Insert placeholders for the fields you want Taghash to fill. Keep headings, tables and narrative blocks exactly as you want them to appear.

Step 2: Keep the portfolio and MIS fields clean inside Taghash

A clean dataset makes the report generation stronger and more reliable. Here are the main ways teams set this up:

• Add new fields to match your reporting requirements
• Customise fields such as KPI labels, internal tags and key update sections
• Use the MIS data already uploaded inside Taghash, so reports pull the latest values

Step 3: Generate the report from Portfolio

Once your template is ready, generating the report is a short repeatable flow:

• Click Generate Report
• Choose the fund
• Set the “as on” date
• Upload the template
• Generate and download
• Receive the report by email when needed

Step 4: Reuse the template next quarter

Next quarter, change only the “as on” date. Taghash generates the same layout with updated MIS snapshots and updated portfolio fields. The structure stays stable and comparisons become easier.

Common use cases

This feature fits best wherever the same update format repeats across companies and across quarters. Teams typically use it for:

• Quarterly portfolio company one-pagers for LP reporting
• IC pre-reads and internal portfolio reviews
• Deal team updates where ownership, investment details and MIS snapshots need consistent presentation
• Exit planning notes where the structure stays constant across multiple companies

In a nutshell

Taghash turns quarterly portfolio reporting into a repeatable workflow. Your report format stays consistent across quarters. Your data stays accurate because it is pulled from Taghash MIS and portfolio records. 

Review cycles shorten because version control improves and reconciliation work reduces. Teams spend more time on judgement, narrative clarity and decisions.

About Taghash

Taghash provides an end-to-end platform for venture funds, private equity, fund of funds and other alternative investment funds. Over the last seven years, we have served as the tech arm for top VCs, helping them manage operations across deal flow, portfolio, fund and LP management. 

We also offer a services layer to support execution across data management, legal and compliance, fund administration coordination, trustee and custodian interfacing and valuations and advisory.

Trusted by leading fund managers like Blume Ventures, Kalaari Capital and A91 Partners, we enable our clients to achieve greater success. Click here to book a demo.

Portfolio valuation is a recurring fund workflow. It feeds quarterly reporting, investor communication, audit review and sometimes transaction decisions. The requirement is simple. The fair value conclusion should be consistent, explainable and supported by evidence that can be traced back quickly when questions come up.

Taghash Services supports private market portfolio valuations by running a structured execution process around the valuation work, so the outcome is not just a number but a complete, review-ready file.

Why process matters in valuation

In private markets, fair value is an estimate at a point in time. That estimate becomes defensible only when the method fits the facts, the inputs are current and the judgement calls are documented clearly. Most delays and rework in valuation cycles come from workflow gaps rather than modelling issues. Inputs sit across emails and versions, assumptions are not captured cleanly and supporting evidence is assembled late. That is what makes the quarter close unpredictable.

Our approach is to keep the work repeatable every cycle: define context, collect evidence, apply the right method, document key decisions and close the file cleanly.

Standards and regulatory alignment

Our valuation engagements are aligned with:

• IPEV guidelines for fair value best practices in private markets
• SEBI expectations for AIF portfolio valuation, where relevant
• Companies Act valuation requirements, where applicable to the specific transaction context
• FEMA requirements for non-resident transactions, where relevant, including valuation using an internationally accepted pricing methodology on an arm’s length basis, duly certified by a Chartered Accountant or a SEBI-registered Merchant Banker, as applicable

What we do

We support the full valuation workflow, from input readiness to final deliverables, including coordination with an independent valuer for AIF reporting and, where required for a specific corporate action, obtaining a report from a registered valuer. This is designed for funds and finance teams that want valuations to run on a steady cadence without last-minute evidence chasing.

What you get

Deliverables are built for audit and investor scrutiny while remaining practical for internal use:

1. IPEV-aligned valuation report issued by a registered valuer
2. Summary valuation memo highlighting methodology, key assumptions, and sensitivities
3. Supporting working papers and data references, as required for audit or regulatory review

How the engagement runs

We keep the flow consistent each cycle so teams know what to expect:

1. Confirm the measurement date and purpose, then map the relevant frameworks
2. Build the valuation data pack and validate completeness
3. Apply the appropriate methodology based on stage and available evidence
4. Make assumptions explicit, run sensitivities and document judgement
5. Coordinate with the independent valuer and where required, the registered valuer
6. Finalize the model, evidence file, approvals and closing memo

Inputs we typically need

A valuation moves faster when the data pack is complete. We typically request:

• Latest financials and key operating metrics
• Projections and the assumptions behind them
• Cap table plus rights and preferences
• Details of the last primary round and any secondary transactions
• Material updates since the prior measurement date

Practical boundaries

Standard exclusions typically include:

• Legal opinions or tax advisory
• Audit certification beyond the valuation scope
• Preparing projections or business plans unless separately agreed

Closing

If you want valuations that are consistent, defensible and easy to review, the difference is a clean workflow and a strong evidence trail. Taghash Services provides the execution layer so valuation cycles run predictably, documentation is ready on time and teams spend less senior time rebuilding context each quarter.

About Taghash

Taghash provides an end-to-end platform for venture funds, private equity, fund of funds and other alternative investment funds. Over the last seven years, we have served as the tech arm for top VCs, helping them manage operations across deal flow, portfolio, fund and LP management. 

We also offer a services layer to support execution across data management, legal and compliance, fund administration coordination, trustee and custodian interfacing and valuations and advisory.

Trusted by leading fund managers like Blume Ventures, Kalaari Capital and A91 Partners, we enable our clients to achieve greater success. Click here to book a demo.

If you are a founder raising in 2026, a solo GP can often move from first call to a decision faster than a multi-partner firm, because there is one decision maker.

That person is a solo GP: an individual fund manager running a venture fund with a standard fund structure, outside capital and institutional reporting. One decision maker runs a lean platform with a clear investing thesis.

This blog covers what solo capitalists are, why they are rising and where Taghash fits.

What is a solo capitalist?

A solo capitalist, or solo GP, is a term popularised in 2020. It describes someone who is the sole general partner of a venture fund, the primary investment decision-maker and the name under which LPs invest and founders work.

A solo GP still runs a fund with the usual structures and obligations. The difference is that they choose not to build a large internal team.

Why solo funds have momentum in 2026

Fund operations are now more modular. Specialised administrators and modern systems can handle capital calls and distributions, accounting and audit and LP reporting. That makes it feasible to run an institutional process with low headcount.

This is where a single source of truth matters. Solo funds cannot scale on scattered trackers and inbox-driven follow-ups. They need one place to store fund data, deal context, documents and evidence and stay organised across cycles.

The market has also shifted toward micro funds. Reports show that by 2024, 69% of new VC funds were under $25 million and in the 2024 and 2025 vintages, at least 40% of closed funds were between $1 million and $10 million in committed capital. Smaller funds often pair well with the solo model because one person can deploy and support a concentrated portfolio at seed and pre-seed.

After the 2022 reset, differentiation has mattered more. Many LP conversations now focus on strategy clarity and repeatable edge, rather than broad generalist positioning. Solo GPs fit this profile when their operations and reporting match institutional expectations.

Who becomes a solo GP

In practice, solo GPs tend to come from a few repeatable backgrounds where personal credibility and network can substitute for a large platform.

• Exited founders and operators
• Spin-offs from established firms
• Sector specialists with a narrow focus
• Creator-led investors who turn audience into deal flow and brand

Where Taghash fits for solo GPs

A solo GP can only move fast if the operating stack is disciplined. Taghash positions itself as an end-to-end platform across the full fund lifecycle, combining products plus execution support.

Products 

Taghash supports core workflows in a governed system of record, built to keep fund context organised across cycles.

• Dealflow CRM: Ingest and manage dealflow and relationships in one CRM with custom pipelines, owners, stages and full deal context
• Relationship Management: Maintain a relationship layer across founders, LPs and partners with interaction history as searchable institutional memory
• Portfolio Management: Track portfolio companies with structured MIS and KPI collection, plus ownership and follow-on visibility over time
• Fund Management: Run overall stats across funds and vehicles with organised, auditable fund records and performance context
• LP Reporting: Produce LP reporting from live system data so reporting is consistent, repeatable and reconciliation light
• Branded LP Portal: Offer a branded LP portal for secure, permissioned investor access to updates, reports and documents
• Single source of record: Keep everything connected in a single source of truth so analytics, reporting and decisions stay tied to the same underlying data
• AI copilots via Taghash MCP Server: Enable AI copilots via the Taghash MCP Server to query permissioned live data and generate answers, analysis and outputs without exporting data

Services to support fund ops

For lean teams, Taghash also provides an execution layer to support operations through:

• Data management
• Legal and compliance
• Fund administration support
• Trustee and custodian interfacing
• Valuations and advisory

Taghash MCP integration and responsible AI

Solo GPs want the upside of AI, but they cannot afford tools that live outside the fund’s source of truth.

Taghash’s MCP Server is positioned as a secure bridge that connects live VC and PE data in Taghash directly to AI agents, using Taghash login, permissions and guardrails. Practically, this enables workflows like summarising information into CRM notes, enriching pipeline records, drafting follow-ups and updates and running analysis using governed context from the Taghash workspace.

Why founders choose solo capitalists

For founders, the appeal is mostly about speed, clarity and hands-on support with fewer internal layers.

• One decision maker, so feedback is direct and accountability is clear
• Faster timelines from first call to decision, often within days at seed
• Operator style support on pricing, early GTM, early hires and next round preparation
• Cleaner fund math in micro funds, which can keep ownership discussions more balanced

Why LPs allocate to solo GPs

For LPs, solo funds offer a way to buy targeted exposure to specific theses with a lean cost structure and clear accountability.

• Narrow theses with defined cheque sizes, stage and focus areas
• Lean fixed cost base with outsourced operations
• More granular exposure across themes and regions

For LPs, the operational bar remains institutional. Reporting, governance and audit readiness need to be consistent, even if the team is lean.

Constraints and the rise of solo plus

The solo model concentrates key person risk and creates bandwidth limits as the portfolio grows. Fundraising and compliance can also be demanding.

Many solo GPs choose a solo plus setup, keeping full investment authority while building a slim platform around operations and community. The goal is to stay fast without letting context fragment across people, tools and inboxes.

What 2026 likely looks like

Solo capitalists are increasingly common at the early stage. The winners will be the solo GPs who combine a clear thesis with institutional execution.

Tooling becomes part of the edge. Not as a substitute for judgment, but as the operating layer that keeps decisions, reporting and evidence clean across cycles.

About Taghash

Taghash provides an end-to-end platform for venture funds, private equity, fund of funds and other alternative investment funds. Over the last seven years, we have served as the tech arm for top VCs, helping them manage operations across deal flow, portfolio, fund and LP management. 

We also offer a services layer to support execution across data management, legal and compliance, fund administration coordination, trustee and custodian interfacing and valuations and advisory.

Trusted by leading fund managers like Blume Ventures, Kalaari Capital and A91 Partners, we enable our clients to achieve greater success. Click here to book a demo.