Changelog
A public record of how Prism evolves, what improves, and what changes across the platform over time
Enterprise buyers want more than feature claims. They want evidence that a product is active, improving, and being maintained with discipline. This changelog exists to provide that visibility.
As Prism evolves, this page will record meaningful product changes across the platform, including new capabilities, material workflow improvements, bug fixes, security-related enhancements, and changes that affect day-to-day use. The goal is not to publish noise. It is to maintain a clear public record of product momentum.
Where relevant, entries will explain what changed, why it matters, and which part of the platform it affects. That helps current and prospective customers understand how Prism is developing over time without having to infer progress from screenshots or marketing copy alone.
How We Use This Changelog
Added
New platform capabilities, net-new workflows, or major new surfaces introduced into Prism.
Improved
Enhancements to existing workflows, usability improvements, stronger analytics, better exports, or changes that make the platform more capable or easier to use.
Fixed
Bug fixes, corrected behaviours, reliability improvements, and issues resolved across the product or supporting experience.
Security and Access
Changes related to permissions, authentication, auditability, data handling, and other trust-critical platform improvements where public disclosure is appropriate.
Current Platform Baseline
The core platform areas this changelog will track as Prism develops
Portfolio Intelligence and Scenario Modelling
Current baseline
Prism’s portfolio layer is built around live portfolio visibility, concentration and exposure analysis, currency-aware reporting, and interactive scenario modelling through the Delta Engine. This includes stress-testing workflows, waterfall-style value impact views, and portfolio analytics intended to reduce spreadsheet-heavy analysis cycles.
What future entries will capture
New analytics views, scenario enhancements, new export options, performance improvements, and changes to how portfolio reporting and interpretation work in practice.
Deal Workflow and Relationship Management
Current baseline
Prism connects deal workflow and relationship data through structured entities such as GPs, LPs, funds, assets, contacts, interests, and commitments. The wider operating model is intended to support deal progression, relationship continuity, and more coherent internal workflow across private capital teams.
What future entries will capture
Workflow enhancements, pipeline and relationship management improvements, import and onboarding changes, document handling updates, and improvements to the connected CRM model.
Reporting, Report Packs, and AI-Assisted Workflows
Current baseline
Prism’s reporting direction is built around structured report packs, reusable templates, export-oriented workflows, AI-assisted document extraction, and AI-supported portfolio analysis grounded in platform data. The product is designed to support a cleaner handoff from live operating data into internal and external reporting outputs.
What future entries will capture
Report builder changes, new report sections, scheduling improvements, export improvements, AI-assisted workflow upgrades, and changes to how reporting is previewed, generated, and delivered.
Investor Portal and External Experience
Current baseline
Prism includes an investor-facing portal model designed around LP-linked access, grouped document delivery, notifications, branded presentation, and self-service visibility for external stakeholders. The goal is to provide a better LP experience without weakening internal control or data boundaries.
What future entries will capture
Portal usability improvements, document-centre enhancements, investor notification changes, branded experience updates, and investor-facing analytics or self-service improvements.
Governance, Access, and Control
Current baseline
Prism is positioned around stronger operational structure through role-based access, auditability, approval-oriented workflows, and a more controlled operating model than disconnected spreadsheets and shared tools can provide. Governance is intended to be a visible part of how the platform works, not an afterthought.
What future entries will capture
Access-model improvements, audit-related changes, approval workflow updates, security-relevant platform enhancements, and improvements that strengthen operational trust and control.
Release Principles
Meaningful Updates Over Noise
This page is intended to record changes that matter. Not every minor tweak belongs in a public changelog. Where updates are listed here, they should represent something a customer or evaluator would reasonably care about.
Clear Scope
Entries should explain which part of Prism changed and why the change matters. That is more useful than vague release notes that say something was “improved” without telling the reader what actually changed.
Honest Progress
Prism should not claim finished capability where only partial implementation exists. If a workflow is improving but still developing, the changelog should describe that honestly. Transparency builds more trust than inflated release language.
Public Momentum
For a product serving private capital teams, visible momentum matters. Buyers want confidence that the platform is being maintained, extended, and taken seriously over time. This changelog exists to make that momentum visible.
What Future Entries Should Include
The structure Prism should use as the public changelog becomes more active
Release titles and dates
Each public entry should carry a clear title and publication date so readers can quickly understand chronology. Version labels can be used where helpful, but the wording should remain readable for non-technical buyers as well as product users.
What changed
Each entry should explain the actual change in plain language: new capability, improved workflow, bug fix, security enhancement, reporting upgrade, or portal improvement. Buyers and users should not need to decode engineering shorthand.
Why it matters
The strongest changelog entries explain not only what changed, but why it matters operationally. For Prism, that usually means faster reporting, better data structure, clearer governance, improved investor experience, or reduced manual work.
Affected product areas
Entries should make it clear whether the change affects portfolio intelligence, deal workflow, CRM, reporting, investor portal, exports, access control, or another specific part of the platform. This makes the changelog much easier to scan and far more useful over time.
Why This Matters for Buyers and Customers
For private capital software, a changelog is not a vanity page. It is part of the trust surface around the product. It helps current customers understand what is improving, and it helps prospective buyers see that Prism is an active platform rather than a static marketing promise.
Combined with the platform pages, security content, pricing, FAQ, results, and live demo, a public changelog makes the site feel more complete and more transparent. It shows that the product is being maintained in public, with a willingness to document what changes and why.
That is a small thing visually, but a meaningful thing commercially.
Explore Prism today, then follow how the platform continues to evolve
Open the live demo to see the current platform in action, or get in touch if you want to discuss fit, rollout, or upcoming priorities.