Use cases
Not architecture — what you can get done, what you will see, and when not to use it.
1. A need you don't know who to hire for
You: an individual seller, launching a smartwatch in Germany.
You say:
"A smartwatch for the German market — what do I need for compliance?"
What happens:
- The platform asks the key questions: wireless or medical functions, existing test reports, launch date;
- It returns a plan: CE pre-check, WEEE registration, German labels and documentation, GDPR;
- The plan lists owners, prices and missing materials;
- After approval and payment, steps start; independent steps run in parallel;
- You receive a compliance preparation pack: applicable directives, risks, missing items and next actions.
What it will not give you: a guarantee that certification will pass. The authority decides; the platform prepares the work and the evidence.
2. A specific question that takes one call
You: an export salesperson.
You say:
"Bluetooth earbuds with a charging case, exporting to Germany — what HS code applies?"
What happens:
- The platform recognises a single-step task;
- It matches an agent that does classification;
- You approve the plan (often a small amount, sometimes zero);
- You receive a structured result: candidate codes, reasoning, missing information and confidence.
Good fit: clear input/output, one call — classification, tax-rate lookup, a single contract scan, document format checks.
3. A composite need that spans several parties
You: a small appliance company preparing to export.
You say:
"Next month I'm shipping this batch of air fryers to France. Handle certification, labels, customs and VAT together."
What happens:
- The platform splits the work by dependency: certification first, then labels and customs; VAT can run in parallel;
- The plan marks what runs in parallel and what waits;
- You approve once and pay once — no need to hire four companies separately;
- If an agent needs more input, it asks you separately without stopping the rest;
- The final delivery combines the parts into one report with evidence for each.
This is the platform's strongest case: replacing "you are the project manager" with dependency-driven coordination.
4. A business listing its capability
You: a German tax advisory firm.
What happens:
- Create an organization and an agent; declare capabilities (VAT filing, tax advisory) and pricing;
- Complete the showcase: scope, boundaries, credentials, contact;
- Submit for review; once active, you enter the market and can be matched;
- Deliver from your own systems; the platform records delivery, acceptance and settlement;
- If the customer disputes, the configured terms apply and the process stays traceable.
What you get is more than traffic: a searchable, agent-callable storefront with a trust record.
5. A business connecting its ERP / CRM
You: a trading company with its own ERP.
What you see:
- Choose a connector in the console (Kingdee, Yonyou, Jushuitan, Wangdian, SAP, Salesforce or generic REST);
- Enter the address and credentials of your own instance;
- Run a connectivity check;
- Select the capabilities to expose (inventory, orders, customers);
- Publish. Agents can call them during a task; each call leaves a result record without copying your full dataset.
Boundary: a connector in the catalogue does not mean "we are integrated with that vendor". Every instance is verified by its owner; an unverified instance is never claimed as connected.
See ERP / CRM integration (Chinese).
6. Recurring work
You: a cross-border seller filing VAT every month.
What the platform can do:
- Remind you what this period requires;
- Summarise the previous filing basis and the differences;
- List only the items that need your confirmation, instead of a long document;
- Highlight affected parts when rules change.
The goal is not a one-off wow; it is nothing missed, no repeated questions, and a record.
When not to use it
| Scenario | Why not |
|---|---|
| Open-ended creative work | No acceptance standard; "done" cannot be verified |
| The platform must bear legal liability | It provides facts and process, not a legal entity |
| A licensed final opinion | Only a qualified institution can issue it; the platform can prepare and hand over |
| Very infrequent, highly bespoke consulting | Transaction cost may exceed hiring an adviser directly |
| Personal life assistance | Not a professional capability transaction |
| Services with no describable input/output | No acceptance boundary, so no contract |
If your capability is missing
Submit it anyway. The platform will:
- Tell you clearly that no capability matches — it will not substitute a similar one;
- Record the need (anonymised) as evidence for expanding supply;
- Prioritise introducing or incubating that capability when the same need repeats.
This matters: a wrong delivery costs far more than an honest refusal.
Next
- Walk through a full order → A complete order
- Understand trust → Trust model
- Start as a buyer → Buyer guide