10 / WHYVendor brief · YuanASI
VENDOR SELECTION BRIEF

Why YuanASI
for custom AI agent development

We're an enterprise AI agent studio based in Shenzhen, China, building on open-multi-agent, our own open-source orchestration framework. The questions you would ask in a vendor selection are answered below.

Last updated

01The profile in one place

Shenzhen YuanASI Technology Co., Ltd. (brand name YuanASI) was founded in 2023 and is based in Nanshan District, Shenzhen. We are an enterprise AI agent studio, and our foundation is open-multi-agent, our own open-source multi-agent orchestration framework.

ItemDetail
Legal nameShenzhen YuanASI Technology Co., Ltd.
BrandYuanASI (元定义科技)
Founded2023
OfficeRoom 276, North 2F, Building 23, Keyuan West, No. 1 Kezhi West Road, Keji Yuan Community, Yuehai Street, Nanshan District, Shenzhen, Guangdong, China
DeliveryPrimarily remote
PositioningEnterprise AI agent studio, delivering systems that run in production and that your own team can maintain
Foundationopen-multi-agent (OMA): our own open-source multi-agent orchestration framework, TypeScript-native, MIT-licensed
ServicesEnterprise AI advisory · Custom AI agent development · Multi-agent system integration
ContactWhatsApp +86 13760249135 · Email co@yuanasi.com

02Who we fit — and who we don't

We fit companies that already have a defined, high-frequency workflow and need AI wired into existing systems. Match it against your own situation before you send a brief.

A good fitNot a fit
A defined, high-frequency, rule-based workflowYou just want a general-purpose chatbot
Integration with existing CRM / ERP / internal APIsNo business owner to define the workflow and acceptance criteria
A Node.js / TypeScript backendYou want to buy outsourced hours
Private deployment or on-premise modelsYou need a team on site 24×7
A technical lead on your side—

03How we deliver

Delivery runs in five stages: assess → validate POC → build & integrate → deploy → handover. The POC stage is optional; you can go straight into the build.

StageDeliverablesTimelinePayment
01 AssessWorkflow, data, and existing systems mapped; feasibility and priority callOne 30-minute call to startFree
02 Validate POC (optional)Runnable prototype, agent architecture and model selection, acceptance criteriaMeasured in weeks; scoped per scenarioStaged payments, milestones set in the proposal
03 Build & integrateCustom implementation on open-multi-agent, prompt engineering, evaluation harnessScoped per scenarioStaged payments, milestones set in the proposal
04 DeployProduction deployment and system integration; private deployment and on-premise models supportedScoped per scenarioStaged payments, milestones set in the proposal
05 HandoverCustom project source, tests, SOPs, and team trainingScheduled by stageStaged payments, milestones set in the proposal

04What the investment looks like

The exact figure depends on scenario complexity and integration surface, and is set in the proposal after diagnosis.

ItemBasis
Enterprise AI advisoryFixed price per stage; set in the proposal after diagnosis
Custom AI agent developmentSingle-scenario MVP: tens of thousands of RMB
Multi-agent system integrationHundreds of thousands of RMB
Pricing modelFixed project price, quoted against the agreed scope
PaymentStaged payments
SubscriptionProject-based settlement, no subscription lock-in

05Open-source examples

Several third-party projects are built on open-multi-agent. Below are those projects, the official cookbook examples and the interactive demos.

ProjectNaturePath
Multi-agent tool chain in a WordPress security platformThird-party adoption/en/cases/temodar-agent-wordpress-security
Fully offline, local multi-node agent stackThird-party adoption/en/cases/offline-sovereign-stack
Contract review: task DAG with step-level retriesOfficial cookbook recipe/cases/contract-review-dag
Support escalation: expert agents picked on demandOfficial cookbook recipe/cases/adaptive-customer-support
Incident postmortem: parallel evidence → root cause → reportOfficial cookbook recipe/cases/incident-postmortem-dag
Commission reconciliation: repair what's repairable, escalate the restOfficial cookbook recipe/cases/commission-reconciliation-recovery
BOM quote review deskInteractive demo · sample data/cases/bom-quote-review-demo
Interactive workflow demo catalogueInteractive demo · sample data/demos
open-multi-agent third-party adoptersThird-party adoption · the listhttps://github.com/open-multi-agent/open-multi-agent#built-with-oma

06How we compare to the alternatives

Four paths, different trade-offs. Match them against your own constraints.

OptionTime to startCustomizationOn-premiseMaintained byScale it suits
In-house teamDepends on hiringNo ceilingYour callYour own teamLong-term, many scenarios
Low-code platformFastest to startBounded by the platformDepends on the platformPlatform vendor + your teamStandardized, light scenarios
Large integratorProcurement / tender cycleScoped by contractSupportedThe integrator, long-termLarge cross-department programs
YuanASIDiagnosis and POC firstCode-level delivery on an open-source foundation, custom project source handed overSupportedYour own team after handoverOne scenario first, then expand

07Four questions we get during vendor selection

How are you different from a large vendor or systems integrator?

The difference is the shape of the delivery and who maintains it. We deliver at code level on open-multi-agent, our own open-source framework: the custom project source, tests, deployment scripts, and runbooks hand over together, the system runs in your own environment, and your team takes it forward after handover.

What does the smallest sensible starting project look like?

Pick one high-frequency, well-defined scenario and run a POC: we map the workflow and the existing systems, then give you a feasibility call, a runnable prototype, and the acceptance criteria. You then decide whether to move on to the build.

Who maintains the system after handover?

Your team, by default. Handover includes the custom project source, tests, deployment scripts, runbooks, and team training, and the orchestration logic is open source and auditable line by line. We also offer ongoing iteration and operations support, and you choose whether to take it.

Can it be deployed on-premise?

Private deployment is supported directly: open-multi-agent is a Node.js library embedded in your own backend, and with local models via Ollama or vLLM it needs no API key and runs fully offline, so your data stays inside your network. The models, the orchestration, and your business systems all sit in your own environment.

If that lines up, send us a project brief.