Kapintelligence by Kapnative
Integrations and implementation

Start with secure upload. Integrate where it creates value.

You can run a complete fund review before any integration exists. Everything below is optional, and every delivery method carries an honest availability status.

01

Secure upload

Documents go into your workspace directly. No connector, no data-warehouse project, no core-system change.

02

Your templates

Your DDQ, policy tests and memo format are loaded as configuration, not as a development request.

03

Integrate later

SSO, APIs and document-store connectors are added when they remove real friction, not to justify the platform.

Integration matrix

What exists today, and what does not.

Four statuses, used literally. Planned means planned: it is not available, and we will say so in the meeting too.

Live In production with customers
By configuration Available, set up per customer
Beta Working with early customers
Planned Not available today
Secure document upload
Drag-and-drop or bulk upload into a tenant-scoped workspace. The first-value path.
Live
Excel and CSV import
Agreed workbook formats for cash flows, positions and reference data.
Live
SharePoint and OneDrive
Pull documents from an existing document store into a fund workspace.
Beta
Outlook intake
Forward manager reports and notices straight into the correct fund.
Beta
Data-room provider connectors
Direct connection to third-party VDR platforms.
Planned
Named users with role-based access
Roles, fund assignments and administrator rights.
Live
Multi-factor authentication
Enforced per tenant.
Live
SSO / SAML
Enterprise identity provider integration, configured per customer.
By configuration
SCIM user provisioning
Automated joiner, mover and leaver handling.
Planned
Excel workbook export
Portfolio data, model outputs and DDQ exports with source columns retained.
Live
Document export
IC memo and DDQ in your house format, with sources and validation states.
Live
REST API
Approved portfolio data and validation states for BI tools and internal systems.
By configuration
Scheduled delivery
Recurring workbook or API delivery on your reporting calendar.
By configuration
CRM connectors
Two-way sync with commercial and relationship systems.
Planned
RMS / portfolio system sync
Write approved data back into an investment management system.
Planned
Licensed market datasets
Benchmark and reference data alongside your own evidence.
Planned

No third-party logo appears on this page. A logo implies a supported, tested integration, and we only show those once they are live for customers.

Implementation

Prove value on one fund before touching the operating model.

Two paths, depending on which module you start with. Both begin with secure upload and your own templates.

One fund, your DDQ and your IC format. The objective is a reviewed output your committee would accept, not a configured system.
Week 0 Scope Choose the fund, the workflow, the success measures, the users and the security-review path.
Week 1 Configure Load your DDQ, policy tests, knock-out criteria, memo format and model methodology; calibrate the outputs together.
Week 2 Run Process one real data room; review coverage, sources, calculations and gaps with the analyst who owns the fund.
Week 3-4 Validate Complete human review, compare against your manual baseline and decide on wider rollout.
A recommended pilot narrative, not a guaranteed schedule. Timing depends on data-room completeness, manager response times and your own review steps.
What you do not need
No core-system replacement, and no migration before first value. No data-warehouse project to start a fund review. No custom development: templates and criteria are configuration. No commitment to integrations you have not tested.
What your IT and security teams do need to do
A security review: architecture, hosting, subprocessors, DPA and TOMs. A decision on identity: named users to begin with, SSO when you want it. Named administrators for your tenant, and an offboarding process. Sign-off on where exported data may live once it leaves the platform.

We plan this in week 0 rather than claiming that no IT project is involved.

Tell us what your stack looks like.

We will tell you which parts are worth integrating, which are not, and what the first four weeks would actually involve.