Implementation & Onboarding

One of the biggest reasons software purchases stall is that the buyer can picture the demo, but not the rollout. They can see the dashboards, the workflow, and the reporting surfaces, but they still do not know what happens after they say yes. How does the system get set up? How does existing data get in? How is SSO configured? What does the first phase of rollout actually look like? Who needs to do what internally?

This page is intended to answer those questions directly. Prism is designed to be a more practical alternative to heavyweight enterprise implementations, but practical does not mean vague. Good onboarding still needs a clear operating plan: a sensible first use case, a structured data migration path, controlled access setup, and realistic expectations about what should be live first.

The aim is not to drag a firm into a year-long implementation programme. It is to get Prism into real use quickly, in a controlled way, with enough structure that the product becomes useful early rather than turning into another half-finished software project.

What a Good Prism Rollout Looks Like

The best Prism rollouts start with a defined use case and a clear path to value. Rather than trying to switch every process at once, the strongest approach is to begin with the workflow that is creating the most immediate friction today.

Start with a Real Workflow

For some firms that will be portfolio oversight and reporting. For others it will be CRM and relationship structure, investor portal delivery, or a more controlled operating model around approvals and reporting. The important point is to start with a workflow that is visible, repetitive, and painful enough that improvement will be felt quickly.

Move in a Controlled First Phase

A good first phase should be small enough to execute cleanly but meaningful enough to prove value. Prism is best introduced through a practical first operating slice, not a broad theoretical transformation with too many moving parts from day one.

Use Early Success to Expand

Once the first use case is live and trusted, firms can expand further into the connected areas of the platform. That is where Prism becomes stronger over time: portfolio views, reporting, relationship data, investor access, and approvals start to reinforce each other because they are operating inside one environment rather than separate tools.

Data Migration Without the Usual Chaos

Data migration is one of the biggest reasons good software fails to become real operating infrastructure. If the path from legacy spreadsheets into the platform is too painful, teams delay the work, half-complete the setup, or lose trust in the result before the rollout has even properly started.

CSV Templates for Core Entities

Prism’s implementation direction includes downloadable CSV templates for core entities such as GPs, LPs, funds, assets, contacts, and commitments. That creates a much more realistic migration path for firms moving away from disconnected spreadsheets or ad hoc trackers.

Validated Bulk Import

The onboarding model is also designed around validated bulk import rather than blind file ingestion. That means checking required fields, numeric values, dates, and field-level issues before changes are applied. A better import process reduces the risk that poor setup becomes the first thing users associate with the platform.

Structured Data Before Wider Expansion

Good implementation is not just about loading everything as fast as possible. It is about bringing in the right records with enough quality that the first live workflow is trustworthy. Once the relationship and reporting foundation is credible, expansion into other areas becomes much easier.

SSO, Identity, and Access Setup

For many firms, implementation is not complete until access is structured properly. Buyers in private capital do not just want a product that works. They want a product that fits their control model.

OIDC-Based SSO Configuration

Prism’s enterprise access model includes tenant-configurable OIDC SSO with support for providers such as Azure AD, Okta, Google Workspace, and other OIDC-compatible identity providers. That means identity can be aligned to the firm’s existing authentication model instead of becoming another unmanaged login surface.

Tenant-Scoped Configuration

SSO in Prism is designed to remain tenant-scoped, with company-specific configuration and controlled user mapping. That matters because identity setup in a multi-tenant platform must be precise. It should strengthen access control, not introduce ambiguity.

Role Setup and Access Boundaries

Implementation also includes defining how internal roles should work in practice. Prism’s operating model assumes clearer role boundaries across administrators, standard users, viewers, and portal-oriented users. Getting this right early makes the rest of the rollout cleaner.

Branding, Investor Access, and External Rollout

For firms using Prism not only as an internal operating platform but also as an investor-facing surface, onboarding also includes external presentation and portal setup.

Tenant Branding

Prism’s onboarding path includes tenant-level branding so firms can apply their own logo, colour treatment, and branded portal presentation. That matters because the investor portal is often one of the most visible parts of the product to external stakeholders.

Portal User Setup Linked to LP Records

Investor access in Prism is designed to be linked back to the underlying LP record, which gives the portal a more controlled and structured access model. During onboarding, that means portal setup is not just a matter of creating generic external users. It is about mapping access properly to the relationship model inside the platform.

External Experience After Internal Confidence

The strongest external rollouts happen after the internal data and reporting workflow are already trusted. That way, when the investor-facing layer is introduced, it is built on a credible internal foundation rather than on data the team is still trying to clean up.

Roles and Responsibilities During Rollout

A smoother implementation usually comes from clear ownership on both sides. Even when the product is easier to deploy than heavyweight incumbents, rollout still works best when responsibilities are defined.

Your Team

Your team usually owns the first-use-case decision, source data preparation, identity-provider information for SSO if required, branding inputs, and the internal operating choices about roles, access, and rollout order.

Prism Configuration and Product Setup

The product side of onboarding centres on making sure the chosen workflow, imported data, access boundaries, and portal configuration are set up coherently so the first live use case works as intended.

Shared Responsibility for Adoption

No software becomes valuable through configuration alone. A successful rollout depends on the system being put into real use quickly enough that the team feels the difference. That is why implementation should always be tied to a live workflow, a real reporting cycle, or a meaningful operating process rather than treated as a background technical task.

Timeline Expectations

Prism is positioned as a faster alternative to enterprise platforms that often require long, expensive implementation projects. But faster does not mean careless. The timeline should still reflect the amount of legacy data, the number of workflows included in the first phase, and whether identity, investor access, and branding are all being rolled out together.

Fast Start, Sensible Scope

The strongest expectation to set is not an inflated promise about every use case being live instantly. It is that a focused first phase can become useful quickly if scope is clear and the source data is ready.

Pilot First, Broader Rollout Second

The product and market-assessment materials both point toward a guided pilot model as a sensible way to evaluate and adopt Prism. A focused pilot with one fund, one LP relationship, one reporting cycle, or one defined workflow usually creates better proof than a much broader rollout attempted too early.

Expansion Should Follow Confidence

Once the first operating slice is live and trusted, the platform can expand further across reporting, investor access, relationship data, and additional workflows. That is where implementation shifts from setup into real operational value.

What Buyers Should Look For During Evaluation

A good implementation page should not only explain how rollout works. It should also help buyers evaluate whether the product is genuinely ready for their operating model.

Can the Data Get In Cleanly?

If migration is still painful, adoption will be painful too. Buyers should look at whether their core records can move into Prism in a controlled way and whether import, validation, and review feel realistic for the team who will actually own the work.

Does Identity Fit the Control Model?

For regulated or security-conscious teams, access setup matters early. Buyers should evaluate whether SSO, role boundaries, and tenant-scoped access feel strong enough to support real internal use rather than just demo convenience.

Does the First Live Workflow Remove Work?

The strongest sign of a good rollout is that an existing burden becomes lighter. That may be reporting, relationship management, investor document delivery, or portfolio review. If the first phase is not removing real work, the implementation scope probably needs to be tightened.