Structuring an RWA Concept and Defining Requirements

Turning a broad, unsettled concept into an MVP scope.

Industry: Finance / RWA (real-world asset tokenization)
Duration: About 3 months (concept structuring through completion of MVP requirements)
Team: 1 consultant + legal coordination (Netsujo)
Scope: Concept structuring, defining open questions, technical validation, requirements definition, regulatory review
Technologies: Blockchain selection, smart contracts, alignment with Japan’s Financial Instruments and Exchange Act / Payment Services Act

Background

A business aiming to launch a new RWA (real-world asset) service found that the breadth of its concept had outpaced its ability to reconcile the technical scope with the business scope.

Fundamental questions — what to tokenize, which regulations apply, how secondary trading should be designed — remained unresolved even as the client moved toward engaging a development vendor. The concept was too broad to determine what not to build, and the preconditions for starting development had never come together.

The challenges

Business: unresolved questions on asset scope, issuer model (self-issued vs. platform-based), and whether secondary trading would exist meant the MVP scope could not be defined.
Technical: blockchain choice (public vs. consortium), smart-contract constraints, and whether a crypto-asset exchange license would be required were all unverified.
Organizational: how multiple regulations — the Financial Instruments and Exchange Act, the Payment Services Act — applied to each other had not been mapped, and who owned legal-response priorities was undecided.

Our approach

In RWA, regulation directly constrains business design. Running technical validation and legal analysis separately risks one conclusion invalidating the other’s design, so we ran structured discovery conversations to put the concept into words in parallel with checking technical feasibility.

Structured discovery with the business owner: turning the concept into words and setting priorities
Defining the concept: drawing the line between what to do and what not to do
Technical validation: blockchain selection, checking smart-contract constraints
Requirements definition: fixing the MVP scope against both technical constraints and regulation
Regulatory review: identifying which regulations applied and the priority order for addressing them

We scored each idea on three axes — legally viable, technically feasible, business impact — to structure agreement among stakeholders.

Results

Key takeaways

Turned an ambiguous concept into a defined MVP scope, ready for development to begin
Identified the applicable regulatory scope and clarified legal-response priorities
Confirmed the blockchain selection and smart-contract design direction
Moved into the development phase without rework after MVP requirements were finalized

Before / after

Before: A broad, unsettled concept — unclear what to tokenize or which regulations applied — left decisions stalled and the preconditions for engaging a development vendor unmet.
After: A fixed MVP scope, technical design direction, and legal-response priorities, ready to move into development, plus an evaluation framework the client kept in-house for future prioritization decisions.

Who this fits

An RWA concept exists, but technical and business scope are not yet reconciled
The regulatory scope is unclear, blocking the start of development
Want an outside party to define requirements and structure open questions before briefing a development vendor
Need to settle secondary-market and exchange-license questions early
Want a partner who digs into individual open questions, not a generic proposal from a large vendor

To talk through a similar RWA concept-structuring or requirements-definition project.