Tokenization partner for law firms
Asset Haus works on technical implementation and coordination alongside counsel advising private-market issuers, sponsors, funds and operators. Your firm keeps the legal mandate and remains responsible for legal advice; the client keeps its operating decisions.
Start with the requirements your client needs to put into operation. Agree what passes from counsel to implementation, what evidence comes back, and who can approve each step.
Bring a mandate and its requirements
- Mandate and decision owners
- Client objective, proposed instrument, relevant jurisdictions and investor audience, named counsel and the client's operating lead. Mark open questions rather than treating assumptions as approved.
- Documented requirements
- Versions of terms and workflow instructions cleared for sharing: admission conditions, consent powers, transfer restrictions, record-keeping and reporting requirements. Counsel identifies what is final and what still needs review.
- Operating and technical context
- Existing systems, intended record keeper, appointed service providers, sample data formats and integration constraints. The client confirms access and who may approve technical changes.
Begin with a non-confidential summary. Share client documents only after the parties agree permissions and handling arrangements; do not assume that a technical collaboration establishes privilege. The legal perimeter memo is a scoping resource for counsel, not a legal opinion.
How counsel's instructions become an accepted operating workflow
This is a collaboration model to scope, not a standard package or a promise of launch. Product fit, service-provider readiness and the parties' approvals determine the work.
Qualify the collaboration
Counsel and the client outline the mandate; Asset Haus reviews the infrastructure fit. Agree contacts, confidentiality, information-sharing permissions and the proposed scope before detailed materials pass between teams.
Handoff: A scoped brief with owners, exclusions, missing inputs and a proceed, defer or no-fit decision.
Translate counsel's requirements
Counsel supplies approved requirements and unresolved legal questions. Asset Haus maps those instructions to proposed user journeys, permissions, records and integration requirements for review.
Handoff: A requirements-to-workflow map tied to document versions; gaps return to the responsible adviser or client owner.
Agree delivery and acceptance
The parties confirm what can be configured, what requires integration or further work, and what remains outside the engagement. The client appoints operational approvers and agrees acceptance scenarios.
Handoff: An agreed implementation scope, dependency list and test plan. Open legal questions are not silently converted into software defaults.
Review the implementation evidence
Within the agreed scope, Asset Haus prepares the technical implementation and test evidence. Counsel reviews whether the mapped requirements reflect its instructions; client operations checks the whole workflow, start to finish.
Handoff: Recorded findings, corrections and separate legal, technical and operational approvals. A passed software test is not legal clearance.
Hand over and manage changes
The client authorizes launch after the agreed gates are met. Name the owners for support, record corrections and exceptions. Later document or policy changes return through legal review, impact assessment and testing as applicable.
Handoff: An accepted configuration baseline, operating handover and agreed escalation and change-control process.
For a detailed map of instructions, money, records and exceptions, see the private-market operating workflow guide.
Define the outputs and their dependencies together
A scoped engagement could include the following. Deliverables, reviewers, exclusions and acceptance criteria must be agreed before work begins; none replaces counsel's advice or the client's approvals.
Collaboration brief and role map
Potential outputA shared scope identifying counsel, client, Asset Haus and appointed providers, with decision owners and open dependencies.
Required input or boundaryConfirmed mandates, client consent to introductions and a named owner for each unresolved decision.
Requirements and implementation pack
Potential outputA proposed mapping from approved documents to workflows, permissions, records and interfaces, with explicit product gaps.
Required input or boundaryCounsel-reviewed instructions, document version control and technical discovery. No assumption that every requirement is a standard feature.
Review and acceptance evidence
Potential outputAgreed test scenarios, results, exception records and a sign-off log linking requirements to the implementation.
Required input or boundaryClient and counsel reviewers, usable test data and provider access. Legal opinions and external assurance remain separate workstreams.
Operating handover
Potential outputAn agreed runbook covering responsibilities, reporting, escalation, record access and change requests after launch.
Required input or boundaryAppointed operating owners and agreed support scope. Continuing legal advice, administration, custody and other third-party services are not assumed to be included.
Separate advice, implementation and operation
Keep their own roles and mandates
- Law firm
- Client
- Appointed providers
Asset Haus, within the agreed scope
- Technical implementation
- Workflow mapping
- Delivery coordination
- Law firm
- Legal advice, legal documents and opinions within its engagement, including the relevant legal and regulatory analysis. Counsel reviews the interpretation of its instructions, not a blanket assurance of software performance.
- Asset Haus
- Agreed technical implementation, workflow mapping and delivery coordination. Asset Haus does not replace counsel, give legal or tax advice, or act as issuer, broker, custodian, placement agent, investment adviser or exchange through this collaboration.
- Client and appointed providers
- Operating decisions and the services assigned to them: investor admission, cash handling, record keeping, administration and reporting as applicable. Each mandate and approval must be identified; a software configuration does not transfer responsibility.
No capital raise, liquidity or regulatory approval is guaranteed. Technical acceptance does not authorize a regulated activity, and a partner relationship does not extend another party's permissions.
Partnership model or specific client project: where to start
This page is for law firms agreeing how to collaborate with an infrastructure provider. For a client's structure, documents and implementation dependencies, use legal setup and licensing coordination. That workstream coordinates preparation with qualified counsel; it does not make Asset Haus the legal adviser.
For a single proposed private launch, review the Private Listing Desk, a closed private-market launch workflow, not a public exchange or retail marketplace. For broader collaboration planning, use the partner playbook.
Partnership questions
- Does Asset Haus provide legal advice or opinions?
- No. The law firm retains the legal advisory role under its own engagement. Asset Haus provides technical implementation and coordination within the agreed scope; it does not make legal or regulatory determinations.
- How is the client relationship handled?
- Client contacts, introductions, information sharing and each party's mandate should be agreed at the outset. The proposed collaboration keeps counsel responsible for legal advice and Asset Haus responsible for its agreed technical work; commercial and support arrangements are scoped privately.
- What if a requirement cannot be implemented as proposed?
- Record the gap and return it to the relevant decision owner. Any alternative needs the appropriate counsel and client review before the implementation scope changes. An unresolved requirement can mean deferring the work rather than assuming support or approval.
Discuss the handoff for your next mandate
Outline your firm's role, the client's objective and the implementation questions. Use a non-confidential summary; detailed materials can follow once sharing arrangements and scope are agreed. The team replies by email within one business day.