Engagement · Pricing & Payment

How we work together, and how payment works
Four-stage payment, with the last stage due only after acceptance

Two things cause the most friction in project-based delivery: unclear scope and money paid too fast. We put both up front — deliverables listed item by item, acceptance criteria tested one by one, and payment tied to milestones. Raise any dissatisfaction before the payment gate, not at the very end.

30%Upfront, kickoff
40%Site entry / staged delivery
20%Completion of agreed services
10%After acceptance

Four ways to engage

Project-based (most common)

Fixed scope, fixed deliverables, fixed timeline. Before signing, we produce a "Scope & Deliverables List" signed by both parties; later scope changes go through change orders, and no extra charge for parts that don't add cost.

Dedicated engineer input

Engaged by the person-day or month, plugged into your dev environment and standups — effectively an external software group. Fits projects where requirements keep changing and scope can't be fixed once.

Long-term retainer

An annual framework agreement with 5 reserved person-days per month, usable across projects; unit prices below single-project rates. Fits companies with multiple machines and ongoing retrofit needs.

Platform engagement

Engaged through integrator subcontracting or third-party platforms, settled under their rules. Fits remote clients starting with a small trial order before moving to direct collaboration.

Payment schedule (standard terms)

30% upfrontPaid after contract effective and scope confirmed; covers scheduling and kickoff
40% on site entryPaid on site entry (or staged-delivery acceptance for remote projects)
20% on service completionPaid after all agreed services are complete and deliverables submitted
10% on acceptancePaid within 10 business days of acceptance and sign-off

Why we hold the last 10% until after acceptance: it's a small amount, but it's proof we stand with you — if the deliverables don't meet the standard in the contract, you can withhold that 10% and we have no grounds to press for it. Conversely, if acceptance passes and payment still drags, we pause subsequent services (also written into the contract, applying to both sides equally).

Remote projects have no "site entry" milestone, so the corresponding 40% is paid against staged deliverables: half on completion of the structure mapping, half on completion of the main delivery. The proportions match on-site projects.

How acceptance criteria are written

No "good quality" or "looks nice" clauses that can't be measured — every criterion maps to an executable action.

Delivery typeAcceptance methodPass criteria
Program refactoringStation-by-station motion verification + item-by-item confirmation of the behavior difference listAll differences in the list confirmed by the client; no new unexpected behavior
DocumentationThe client's maintenance engineer completes one fault-localization using only the docsAble to locate the block and signal without looking at the program
LocalizationScreen-by-screen screenshot comparison + 10% terminology spot-checkNo overflow/truncation; 100% terminology consistency
HMI/SCADA applicationItem-by-item testing against the point list and report definitionsAcquisition accuracy and refresh cycle meet spec; report figures match manual reconciliation
AI pilotComparison against the manually labeled baselineHit rate and false-positive rate within contractually agreed bounds

Terms & conditions

Who owns the intellectual property?

Custom development results (including source code and docs) belong to the client once payment is settled in full. We retain ownership of generic components, templates, and tools, but grant the client a perpetual, royalty-free, transferable license — so switching vendors won't leave you stuck.

What if we need to change requirements?

Go through a change order: state what's added, the schedule impact, and the cost impact, and execute after both sides confirm. Small adjustments that don't affect the deliverables list are free (we reserve about 10% slack in every project).

Who's responsible if something breaks afterwards?

Software deliverables carry a default 90-day warranty: problems caused by defects in our deliverables are fixed free of charge during that period. After the warranty, maintenance is by incident or annual. Problems caused by the client's own changes, third-party changes, or hardware faults are outside warranty, but we can assist in troubleshooting by the hour.

Can you invoice? Do you accept corporate bank transfer?

Yes — we issue VAT invoices (standard or special) and accept corporate bank transfer. With contract, quotation, and acceptance record in order, there's no issue running it through your procurement process.

How is confidentiality handled?

We sign an NDA: programs, drawings, process parameters, and client information are all confidential, and copies are deleted or returned at project close. If needed, we can accept non-compete terms (same city and industry, no similar projects within the agreed scope).

Define the scope first, then talk price

Tell us the equipment models, program size (lines or blocks), and the outcome you want, and we'll produce a "Scope & Deliverables List" and a written quote — no obligation to sign.

+86 133 1955 1131