Build vs list comparison

Build, buy or list for tokenized private markets

A single-deal launch, a branded hosted platform, a client-controlled deployment, or a custom build: the starting point depends on your pipeline, data requirements, integrations, team, and legal structure.

For banks, brokers, wealth platforms, asset owners, issuers, family offices, and partners deciding how much infrastructure and operating responsibility to take on.

Find a launch route Compare the four routes

Compare launch routes

These choices can overlap: one deal can use hosted software, and a client-controlled deployment can carry your brand. Compare the scope and responsibilities as well as the label. No route is a default winner.

Four launch routes: fit, operating responsibility, and information to resolve before commitment.
Route	When to consider it	Operating responsibility	Resolve before commitment
Single-deal launchPrivate Listing Desk	A specific asset, fund, credit facility, or issuer-led opportunity is ready for scoping; a continuing platform business is not yet justified.	Scope onboarding, documents, registry, reporting, and controlled transfers around the deal. Name the sponsor and post-launch servicing owner.	Instrument and vehicle, investor eligibility, payment and custody arrangements, reporting requirements, and servicing after the raise closes.
Branded hosted platformHosted deployment options	You need your own investor experience and repeatable workflows, and a vendor-managed service fits the required integrations and data policies.	The vendor operates the agreed hosting scope. Your team still owns business decisions and assigned operating controls; branding and data rights are contractual.	Hosting region, tenancy, subprocessors, branding limits, support terms, integration scope, and usable data exports at exit.
Client infrastructureClient-controlled deployment	You need control of the deployment environment and can provide an infrastructure team or a defined managed-services arrangement.	Run the platform in your cloud or controlled environment. Allocate security, patching, backups, recovery, and integration maintenance explicitly.	Environment requirements, external data flows, access and key controls, maintenance ownership, software rights, and handover evidence.
Custom buildArchitecture risk pack	Documented requirements cannot be met through configuration or available integrations, and a product and engineering team can maintain the result.	Own requirements, development, assurance, releases, and long-term maintenance. External service dependencies and issuer responsibilities remain.	A tested gap analysis, architecture, integration specifications, staffing, security review, acceptance criteria, and a maintenance plan.

Need more detail on branding, hosting, and contractual rights? Read the white-label platform guide. A custom build is a comparison route, not a claim that every engagement requires bespoke software.

What to decide first

Choose the smallest credible launch that supports the strategy, with named owners for the work after launch.

Deal pipeline: One defined offering or a repeat program? Identify expected vehicles, investor groups, servicing periods, and who owns the investor relationship. Deal count alone does not decide the route.
Data control: Specify access, hosting location, retention, recovery, and export requirements. Distinguish control of the environment from ownership of software and rights to investor records.
Integration requirements: List custody, payments, identity checks, administrator, CRM, and reporting systems. Mark each connection as available, configurable, or requiring development, with evidence rather than assumptions.
Operating team: Name owners for investor support, reconciliations, reporting, rule changes, incidents, and maintenance. A vendor-hosted service does not replace every internal role.
Legal-structure readiness: Identify the instrument, issuer or vehicle, jurisdictions, investor eligibility, and proposed service providers. Qualified counsel must review activity-specific permissions and responsibilities; hosting is not a licensing conclusion.

Not enough information is a valid result

Pause the route decision if the asset, economics, investor eligibility, counsel path, or reporting requirements are unclear, or if nobody owns post-launch operations. Missing data is not a reason to default to custom development.

Resolve the instrument and role map through the legal perimeter memo, or document data, integration, and operating gaps with the architecture risk pack.

A usable decision record

The route to investigate and the requirements that make it a candidate.
The alternatives considered and the unresolved trade-offs.
Missing evidence, who will obtain it, and who can approve the decision.
A role map covering issuer, legal, regulated-partner, custody, advisory, and operating responsibilities.
Acceptance evidence for onboarding, payment reconciliation, register accuracy, reporting, recovery, and handover.

Compare the cost categories

Compare quotes for the same scope and planning period. Separate one-time work, recurring charges, and usage or event-driven costs. Unknown costs remain unquoted, not zero; count bundled services once.

Implementation: Discovery, configuration, migration, training, acceptance testing, and handover; distinguish included setup from custom work.
Software and development: License or subscription, modules, usage allowances, custom engineering, and later changes; state renewal and termination terms.
Hosting and support: Compute, storage, backups, monitoring, incident response, patching, and recovery tests; do not add hosting twice when it is bundled.
Investor checks: Initial verification, screening, rechecks, and additional usage; identify what is included and which provider bills each service.
Integrations: Connector implementation, third-party subscriptions, transaction charges, API use, and maintenance when external systems change.
Audit and assurance: Security review, testing, remediation, and recurring assurance; confirm what existing reports cover.
Administration and specialists: Register maintenance, reconciliations, distributions, investor reporting, counsel, tax, custody, and other scoped external services.
Exit and transition: Data exports, document retention, register handover, migration assistance, and any period of parallel operation.

Review the existing pricing and scope page for commercial context, then confirm current inclusions and exclusions in a written proposal. Delivery depends on documents, integrations, partner onboarding, testing, and approvals; software readiness is not the same as deal readiness.

Boundaries for every route

This comparison supports scoping, not a pricing quote, legal conclusion, or investment recommendation. Asset Haus provides infrastructure and implementation coordination, including coordination with qualified counsel; it is not acting as issuer, broker-dealer, exchange, custodian, investment adviser, or legal counsel.

Owning software does not remove issuer or service-provider obligations. A private listing does not guarantee capital or liquidity. Pause any proposal that relies on guaranteed investment results or unrestricted transferability.

Common questions

Is build vs list the same as build vs buy?

No. First decide whether you need to launch a particular deal or operate a continuing platform. If a platform is needed, hosted software, a client-controlled deployment, and custom development are separate implementation choices.

Can a team start with private listing and later own the platform?

That can be a route, but migration is not automatic. Agree data export, document retention, register handover, software rights, and ongoing servicing before committing. A first deal can help establish operating requirements without proving that a later platform is necessary.

Does white-label mean client-hosted software or source-code ownership?

No. White-label describes branding. Hosting, source-code delivery or escrow, modification rights, and continued use after termination are separate contractual questions. A hosted platform can also be white-label.

Turn the comparison into a scoped decision

Bring the asset or mandate, intended investors, integration requirements, and open questions. Use the assessment or contact the team to discuss the responsibilities and evidence still needed.

Start assessment Email the team