Marketplace

Deployment marketplace intake

A structured intake for Hong Kong financial institutions and enterprises that need project scoping, engineer matching, delivery governance, and acceptance standards.

Structured brief
Delivery governance
Acceptance criteria
1
Project brief
Scope, data, risk, timeline
3
Review layers
Business, security, delivery
0
Fake matching claims
No unauthorised logos
90
Roadmap horizon
Typical delivery planning
Intake

What the marketplace captures

The MVP focuses on scoping and governance. It does not list fabricated experts or invented partner institutions.

Project brief

Capture business scenario, desired outcome, timeline, available data, and internal stakeholders.

Scenario and scope
Budget and timeline

Capability fit

Map the project to diagnosis, knowledge-base, agent workflow, security, or managed operation capabilities.

Required roles
Delivery risk

Governance setup

Define approval flow, data boundaries, milestone reviews, acceptance criteria, and documentation.

Review gates
Acceptance plan

Follow-up record

Marketplace submissions enter the lead system for qualification, notes, status updates, and export.

Lead scoring
Admin pipeline
Workflow

From marketplace intake to delivery decision

The intake flow is designed to qualify demand before any engineer or delivery claim is made.

01

Submit structured project brief

02

Review risk, data, and scope

03

Confirm capability and delivery model

04

Move to diagnosis or proposal

Next Step

Marketplace entry points

Use the request form for project intake, diagnosis for paid scoping, and engineer path for capability context.

Submit request

Create a lead for project qualification.

Open

Paid diagnosis

Turn the brief into a roadmap and budget.

Open

FDE Engineers

Understand the delivery capability framework.

Open
Enterprise Procurement Route

Start with non-sensitive context, then move into an accepted AI deployment route

FDE.HK connects intake, diagnosis, solution design, delivery, and managed operations into one enterprise buying path for business, technology, compliance, and management teams.

Non-sensitive first
Sensitive materials wait until NDA, permission, and data boundaries are confirmed
Diagnose before build
Clarify scenarios, users, data, budget, and acceptance criteria first
Accepted delivery
Plans, workflows, training, operations, and acceptance checklists stay traceable