PROCESS // REQUEST TO DEPLOY
Your project moves through
checkpoints.
From request to deployment — four phases and fourteen steps. Each has a deadline, an owner and a document; between phases sit checkpoints where the decision stays with you.
Four phases. Fourteen steps.The decision — always yours.
Each step has a deadline, an owner and a document at the exit. At the end of every phase there's a checkpoint: a place where you compare the facts against the plan and decide whether we go on. And, on a separate line — what this phase needs from you.
For catalog deliveries without integration the same circuit compresses to 1–3 weeks: phases aren't skipped — they get shorter.
Synchronisation
F·01- 01
A request in free form
1 DAY · YouDescribe the task the way you see it — no 40-field briefs. We reply on substance and name the format: catalog, package or custom. At this point you owe us nothing.
→ FORMAT CONFIRMED
- 02
NDA — before the drawings
1–2 DAYS · You + NexumIf selection requires layouts, specs or process data — we sign a standard NDA first. Your documentation lives inside our legal perimeter and is never passed to third parties.
→ SIGNED NDA
- 03
Site discovery
3–7 DAYS · NexumWe collect the facts: layout, flows, labour costs, infrastructure, constraints. For large projects — an engineer on site or a remote scan together with your team.
→ DISCOVERY DOSSIER
- 04
Draft configurations
3–5 DAYS · NexumWe assemble 1–3 solution options with budget ranges and honest assumptions. This is direction alignment, not a quote — so we don't spend a week pricing what you don't need.
→ CONFIGS + RANGE
From you in this phase
- The task in free form — as you can, no briefs
- Layout and site photos — after the NDA is signed
- A contact who knows your operations
≈ 2–4 hours of your time per phase
Checkpoint CP·1
Choosing a direction
You pick one of 1–3 draft configurations — or we part ways. No invoice, no obligations: the phase is free and commits you to nothing.
Contract
F·02- 05
Budget gate
1 DAY · YouWe fix the from–to corridor in which the deal is worth working further. If it doesn't add up — we say so and part ways, burning no one's time.
→ BUDGET AGREEMENT
- 06
Engineering session
1–2 WKS · You + NexumYour engineers and operations against ours: integrations (WMS / POS / BMS / MES), site constraints, acceptance criteria. The spec is born here — not in managers' chats.
→ AGREED SPEC
- 07
Quote + Bill of Materials
5–10 DAYS · NexumFinal configuration: an equipment specification down to serial items, timeline, cost breakdown, service plans. Every line of the estimate is visible — there is no “miscellaneous 15%” with us.
→ QUOTE PDF + BOM
- 08
Contract & payment scheme
1–2 WKS · You + NexumJurisdiction is your choice: UAE, Hong Kong, China or Belarus. Payments — LC, escrow or staged, agreed with both sides' banks. KYC goes both ways: you vet us, we vet you.
→ CONTRACT + KYC
From you in this phase
- A decision on the budget corridor — 1 business day
- Your engineer or operations lead for 1–2 technical sessions
- Documents for mutual KYC
≈ 1–2 business days of your team per phase
Checkpoint CP·2
Signing the contract
Up to this point either side can exit without penalties. After it — figures, timelines, serial numbers and the termination procedure are fixed in the contract.
Production & transit
F·03- 09
Factory order placement
4–10 WKS · FactoryThe order goes to the manufacturer or an authorised partner. You receive a weekly status; serial numbers are fixed in the contract before acceptance — batch substitution is excluded.
→ REPORT + SERIALS
- 10
FAT — acceptance before shipping
2–5 DAYS · NexumOur engineer in Shenzhen runs the batch through a checklist: sampling, tests, firmware, packaging. Video and protocol reach you before shipment — defects turn back where they're cheap to fix.
→ FAT PROTOCOL + VIDEO
- 11
Logistics & customs
2–6 WKS · LogisticsSea, rail or air — we route for deadline and budget. Customs in the destination country, local certification, cargo insurance, warehouse acceptance — inside our perimeter, not on you.
→ EXPORT-IMPORT PACK
From you in this phase
- Nothing operational — production and transit are in our perimeter
- Read the weekly statuses — 10 minutes a week
- Confirm the FAT protocol before shipment
≈ 1 hour of your time a week
Checkpoint CP·3
Batch acceptance before shipment
You see the video and the FAT protocol before the batch leaves China. Defects turn back where they're cheap to fix — not at your warehouse.
Launch & operation
F·04- 12
Installation & commissioning
1–3 WKS · NexumMounting, network and power, route mapping, integrations with your systems, loaded test runs. You accept a working scenario — not boxes on a pallet.
→ COMMISSIONING ACT
- 13
Training the people
3–5 DAYS · NexumOperators, shift leads, duty engineer: typical failures, escalations, procedures. Docs and videos in your team's language; the cheat sheet is one page, not a volume.
→ PROCEDURES + VIDEO
- 14
Handover to service
SLA STARTS · NexumThe project moves onto a service contract: monitoring, scheduled maintenance, consumables, warranty cases handled through us — no Chinese-language correspondence with the factory.
→ SERVICE CONTRACT
From you in this phase
- Site access, power and network per our checklist
- People for training — 3–5 days on the shift schedule
- Acceptance of a working scenario against the spec criteria
≈ 2–3 days of your team per phase
Checkpoint CP·4
Commissioning act
You accept not “boxes on a pallet” but a working scenario against criteria agreed back in the spec. From this day the service SLA switches on.
Σ FULL CYCLE · 10–22 WEEKS
System in operation
From here the service contract takes over: monitoring, SLA, consumables and scheduled maintenance — with no Chinese-language correspondence with the factory.
Response times are part ofthe contract, not courtesy.
The most common fear in China supply is silence after the prepayment. That's why the speed and format of communication are fixed with us just as firmly as price and serial numbers.
First reply — ≤ 1 business day
A request in any form is answered by an engineer, not a bot: we name the format of the task and the next step. If a calculation needs a day, we say so plainly.
One pair for the whole project
A dedicated manager plus a lead engineer from the first call to the handover to service. Both contacts are in the contract, not in a “general support chat”.
Weekly status without reminders
From the moment the order is placed, the production and logistics report comes on its own: photos from the line, percent ready, the nearest milestone.
Escalation — ≤ 24 hours
Any disputed matter is, on your request, raised to a managing partner within a day. The escalation route is written into the contract.
Channels — whichever suit you
Email, Telegram, WhatsApp, video calls. After every meeting — minutes with decisions and deadlines: agreements don't live in the memory of a chat thread.
Languages — Russian and English
All documentation, training and support are in your team's language. We do the Chinese with the factory, and that's not your concern.
HANDOVER · TEAM TRAINING · STEP 13AFTER LAUNCH
The system stays with people who know how to run it
Operators, shift leads and the duty engineer are trained on your site: typical failures, escalations, procedures. The cheat sheet is one page; documentation and videos are in the team's language.
→ PROCEDURES + VIDEO GUIDES
Sea, rail or air — the route is calculated for deadline and budget. Customs, certification and insurance — inside our perimeter.
What can go wrong —and how it's covered.
We don't promise there are no risks — we show the mechanism against each one. On the left, a typical fear of China supply; on the right, what stands between it and your project.
Defects in the batch
FAT acceptance by our engineer in China: tests, firmware, packaging. Video and protocol reach you before shipment — a defect is turned back at the factory.
→ FAT protocol + video
The factory missed the deadline
A weekly production status, a buffer in the project schedule and a late-delivery penalty built into the contract with the supplier.
→ Production report
Substituted configuration
Serial numbers are fixed in the contract before acceptance and checked at FAT and at on-site handover. Batch substitution is excluded by procedure.
→ Serials in the contract
Cargo stuck at customs
Declarations, local certification and insurance are prepared by our broker in advance — the document package is assembled before shipment.
→ Export-import package
Payment risks
A letter of credit, escrow or staged payment against inspection — the scheme is agreed with your bank before signing, not after the prepayment.
→ Contract + mutual KYC
“The robot can't handle the scenario”
Acceptance criteria are fixed in the spec at the technical session, and before handover the system is run through test runs under real load.
→ Commissioning act
Money moves the wayyour bank finds comfortable.
Settlements, guarantees and acceptance are arranged around the customer: country, bank, scale. The four mechanisms we use most often — in one dossier.
Nexum standard B2B deal mechanisms
NDA before any materials change hands
A standard non-disclosure agreement is signed before details are discussed. Customer documentation stays inside our legal perimeter and is not passed to third parties without separate consent.
Letters of credit & escrow
For large projects — a letter of credit (LC), escrow, or payments against inspection and shipping documents. The exact mechanism is fixed in the contract in agreement with the customer's bank.
Credentials audit
Our legal entities are in the public registries of four jurisdictions. Full credentials, licences and statements — on request after NDA, for your security team or an independent auditor.
Bank guarantees
For large contracts we discuss performance guarantees. Availability depends on the customer's country, bank and scale; the final scheme is agreed before signing — not after the prepayment.