Michael ZhaoAPAC / WEB3 / EARLY STAGE
FIELD NOTE / 05 / Market entry

Put Institutional Constraints on the Product Roadmap

Interest can be abundant while procurement stays still. Compliance, custody, integration, budget, and ownership determine whether an institutional user can proceed.

Measure commitment, not enthusiasm

A conversation, pilot, and procurement review require different investments from a potential user.

Record the next resource a counterparty will commit: data, security review time, integration work, or an accountable buyer. Interest without ownership can remain conversational.

Draw the decision chain

Users, information security, legal, compliance, procurement, and budget owners may each control a gate.

Knowing their evidence requirements early exposes duplicated work, interface gaps, and unclear responsibility.

CHECKPOINTS+Problem owner and budget+Regulatory perimeter+Security and data requirements+Custody or settlement dependency+Procurement and integration capacity

Classify regulatory work

Regulation may limit geography, customer type, supported assets, or data handling. A generic risk label gives a product team no direction.

Separate questions requiring legal interpretation, licensing, and product controls. Each has a different owner and timeline.

Productise repeated constraints

A bespoke feature can teach the company or distract it. The key question is whether the constraint repeats across the target segment and whether resolving it shortens future adoption.

Institutional readiness means making the product easier to validate, approve, and operate continuously.