Who receives an invitation?
Define selection, confidentiality and eligibility rules before outreach.
02.02 / CO-INVESTMENTAPPLICATION PATTERN
ONE DEAL.ONE CONTEXT.ONE CONTROLLED JOURNEY.
Bring the opportunity, selected audience, evidence, allocation and subscription process into one deal-specific experience.
01 / THE PATTERN
Deal-specific offerings
A co-investment journey is narrower than a general product shelf but operationally demanding. Timing, confidentiality, capacity and eligibility need to remain synchronized from invitation through closing.
A focused operating journey for a manager presenting a defined co-investment opportunity.THE OPERATING PRINCIPLEBring the opportunity, selected audience, evidence, allocation and subscription process into one deal-specific experience.
02 / OPERATING BLUEPRINT
Three parts that have to remain connected.
The pattern becomes operational when product logic, customer context and specialist responsibilities share explicit state and hand-offs.
01
Invitation boundary
Control who can discover and access the opportunity and under which conditions.
02
Deal room context
Keep approved evidence, terms, questions and acknowledgements attached to the opportunity.
03
Allocation workflow
Coordinate indications, commitments, final allocations and payment hand-offs.
03 / ROUTE TO IMPLEMENTATION
Move from the pattern to a controlled operating journey.
Use the parent operating model as the backbone, then adapt its evidence, approvals and providers to this application.
- 01
Structure
Define the investment proposition, terms, issuer or vehicle and target audience.
- 02
Evidence
Assemble product documents and the approvals required for launch readiness.
- 03
Publish
Expose the approved product through a controlled branded experience.
- 04
Subscribe
Coordinate investor onboarding, eligibility, orders and payment hand-offs.
- 05
Service
Operate holdings, communications and lifecycle events after issuance.
04 / DECISIONS BEFORE CONFIGURATION
Resolve the operating questions before selecting technology.
How does capacity resolve?
Establish allocation authority and handling for oversubscription or changes.
What becomes the holding?
Confirm the legal instrument, register process and post-close servicing model.
05 / RESPONSIBILITY BOUNDARY
One journey.
Distinct responsibilities.
Valuya DA holds the application and operating context together. It does not collapse product ownership or regulated services into the software provider.
Product + relationship
Commercial intent, brand, governance and the customer relationship.
Application + orchestration
Connected product, investor, subscription and lifecycle context.
Specialist responsibilities
Regulated and technical services required by the configured product.
The software can coordinate a deal journey but does not determine whether an opportunity may be offered or allocated to an investor.
FROM OPERATING MODEL TO CONFIGURED SOFTWARE
Test the pattern against your product, providers and responsibilities.
Start with one bounded journey. Make ownership and exceptions explicit. Then configure the platform around the operating reality.
Request a demo ↗