Let’s talk about your project.

A new application, an existing system, or a workflow to improve. Tell us where you want to start.

Phone

Mr. Nie

Prefer to chat here?

Start here. An assistant replies first; Mr. Nie can join.

WeChat
Scan to add Mr. Nie on WeChat

Scan. Let’s talk.

Add Mr. Nie and mention your industry.

On mobile, save the QR image and open it in WeChat.

From your first idea to delivery.

Discuss your business needs

Tell us what you want to build, improve or connect. Together we assess whether project development or embedded FDE support fits your needs.

What should I bring to the first conversation?

Bring a workflow you want to improve, the systems you use and an anonymised sample. We clarify who uses it, where it gets stuck and which results need human approval.

Start with a well-defined use case. Assess interfaces, materials and deployment conditions before agreeing on the pilot scope.

Agree on scope and approach

For development, agree on features, timeline and pricing. For FDE, agree on the scope of discovery, stage objectives and collaboration period before work begins.

How do we agree on scope, costs and data?

The proposal identifies features, deliverables, schedule, acceptance samples and each party’s responsibilities. Changes are assessed for cost and schedule before implementation.

The quotation distinguishes implementation fees from third-party costs such as hosting, model usage and SMS, including who procures them and how they are billed.

Agree on deployment location, access, retention and deletion. Before using an external model, confirm which data will be sent and how it will be anonymised. Local deployment still requires checking external dependencies.

Implement and validate in stages

Confirm the prototype and key workflows, then develop and integrate in stages. Review progress through regular demonstrations and checks using actual business scenarios.

How do we validate a pilot?

Run agreed samples through the entire workflow, including valid inputs, missing information, invalid inputs and human handover. Record results, issues and fixes against the agreed criteria.

To measure efficiency, first record baseline time and quality, then repeat the same task using the same definitions. Keep demo results, deployment checks and sustained usage results distinct.

Deliver and continue

Complete testing, deployment, and handover of source code and documentation. For FDE engagements, continue with SOPs, team adoption and improvements as agreed.

Delivery, acceptance and ongoing support

Agree the handover list for the project: custom source code, dependencies and versions, database schema or migrations, deployment configuration, API and user documentation, and acceptance records. Transfer accounts and secrets through an agreed secure channel.

Check deployment steps, key functions and permissions in the agreed environment. Record passes, outstanding issues and retest results. The checklist below is a starting template.

Ownership of custom work, handover conditions and timing follow the contract. Existing tools, open-source components and third-party services have their own usage and licensing terms.

Agree in writing on the support period, channels, response arrangements and the scope of bug fixes and new features. Ongoing development or FDE support is arranged separately.

Download the delivery and acceptance checklist template