Respond to inquiries and requests
Auditor requests, investor questions, regulatory inquiries, RFP responses. PitCrew pulls the data from your connected systems, assembles the response package, and logs every step for your evidence trail.
Book a DiagnosticThe Problem
Every request starts a scavenger hunt across your systems
Whether it's an SEC examiner, an LP asking about performance, or a due diligence questionnaire, your team drops everything to manually pull data from multiple systems.
Hours spent on a single auditor request
An examiner asks for 12 months of trade data cross-referenced with compliance reviews. Someone opens four systems, exports data, formats it, and hopes nothing was missed.
RFP/DDQ responses take weeks
A 200-question due diligence questionnaire arrives. Your team copies answers from last time, updates the numbers manually, and prays the formatting holds.
Regulatory inquiries create fire drills
A regulator asks about a specific transaction from 18 months ago. Finding the original documents, the approval chain, and the compliance review takes days of digging.
Investor questions compete with real work
LP capital account inquiries, performance questions, K-1 status updates. Each one interrupts someone's actual workflow for 30-60 minutes of data gathering.
How It Works
From incoming request to response package in four steps
Classify the request
PitCrew reads the incoming request, identifies what data is needed, and maps it to your connected systems. Examiner request, DDQ, investor inquiry, or internal audit.
Pull from connected systems
The Skill queries your CRM, document management, compliance systems, custodian, and portfolio platforms. No manual exports. Every data point is sourced and timestamped.
Assemble the response
Data is organized into the format the requester expects. Tables, narratives, supporting documents. Cross-referenced against your policies and prior responses for consistency.
Review and send with evidence trail
Your team reviews the assembled package, makes any edits, and approves. PitCrew logs who requested what, when it was assembled, which sources were used, and when it was delivered.
Use Cases
Where firms use Respond to Inquiries
SEC/FINRA examination response
Examiner sends a document request list. PitCrew pulls the evidence from your systems, organizes it by line item, and produces a response package with data lineage for every document.
RFP and DDQ completion
Due diligence questionnaires from prospects, consultants, or counterparties. PitCrew populates answers from your firm's knowledge base, flags questions that need manual review, and tracks version history.
Investor/LP inquiries
Capital account questions, performance reporting, K-1 status, distribution schedules. PitCrew assembles the answer from your fund accounting and investor relations systems.
Regulatory and compliance requests
Form ADV amendments, blue sky filings, annual compliance questionnaires. PitCrew pulls current data, compares against prior filings, and flags what changed.
Internal audit support
When your internal audit or compliance team needs to verify a process, PitCrew assembles the evidence package: policies, procedures, execution logs, and exception documentation.
Counterparty due diligence
Incoming due diligence from banks, prime brokers, or fund administrators. PitCrew maintains a response library and updates answers with current data for each request.
Integrations
Pulls data from the systems your firm already uses
Respond to Inquiries queries your existing platforms directly. No CSV exports, no manual data gathering.
40+ integrations available. If your system has an API, PitCrew can connect to it.
Frequently asked questions
Last updated:
What types of inquiries can PitCrew handle?
Any structured request where the answer lives in your connected systems. SEC/FINRA exam requests, DDQs, investor reporting inquiries, regulatory filings, internal audit requests, and counterparty due diligence.
Does PitCrew send responses automatically?
No. PitCrew assembles the response package and routes it to your team for review. Nothing goes out without human approval. You control the final send.
How does PitCrew handle repeat questions?
The Skill maintains a response library. When a similar question comes in, PitCrew pulls the prior answer, checks if the underlying data has changed, and presents both the updated answer and what changed since last time.
What if the data isn't in a connected system?
PitCrew flags it. The response package clearly marks which answers were sourced from connected systems (with data lineage) and which require manual input from your team.
How does this help with SEC exams specifically?
Examiners typically send a document request list with 20-50 line items. PitCrew maps each item to your systems, pulls the evidence, organizes it by line item number, and produces a production package with a cover index and data lineage for every document.
Stop treating every request as a fire drill
15-minute diagnostic call. We review your inquiry workflows and show you exactly where Respond to Inquiries fits.
Book a Diagnostic