Scattered requests
Requests arrive by email, chat, spreadsheets and phone, and no one sees the whole queue.
San Francisco · Irvine · New York · Hong Kong
HZ Tech is a forward-deployed engineering (FDE) consultancy. Our engineers work inside your operation to find the problems worth solving, build AI into the workflow and turn what repeats into standard products. Our work spans logistics, manufacturing and trade.
How we engage
Product figures from live deployments; partner figures from the customer's public information
The real problem looks the same in every industry: software, data and people's work are cut off from one another.
Requests arrive by email, chat, spreadsheets and phone, and no one sees the whole queue.
Rate sheets, price lists and specifications come in different formats and keep changing.
Bookings, filings and orders are spread over portals and partner systems — air-cargo bookings and customs filings are typical.
ERP, TMS, WMS, finance and quality systems don't talk to each other.
Staff copy, clean and re-key the same data between systems.
Management has to reprocess data before it can see how the business is doing.
Across current industry research and our live product work, the signal is consistent: value appears when data, workflow and action are designed as one operating system.
of surveyed shippers had adopted at least one transportation AI use case
Logistics surveyhad deployed at least one surveyed AI or digital use case in warehousing
Logistics surveyof surveyed manufacturers reported achieving all targets from AI initiatives
Manufacturing surveySources: McKinsey 2026 State of Digital Logistics Survey; BCG 2025 manufacturing survey. Different samples and questions; figures are directional and not directly comparable.
Enterprise adoption is no longer the strongest signal of advantage. Recent logistics research shows digital tools moving into the operating core, while manufacturing research shows a wide gap between deploying use cases and achieving their intended targets.
More tools will not resolve a weak operating model. Value depends on whether teams can move from detection to decision and from decision to execution without losing context, ownership or control.
Traditional software records what has already happened. The emerging operating layer must assemble the current context, make the next decision legible and route an approved action back into the workflow.
A supply chain cannot be coordinated if rates, bookings, documents and milestones disagree. A factory cannot be optimized if orders, batches, capacity and quality evidence are separated. The operating record is the substrate on which useful intelligence runs.
Logistics and manufacturing share a delivery discipline: observe the work, structure the record, embed intelligence, operate and improve. But they do not share the same ontology, event model or decision cadence.
Logistics follows the supply chain across organizational boundaries. Manufacturing follows an order and batch through controlled production stages. A generic workflow removes the context that makes the system valuable.
External research frames the market view. Live product repositories and operating documentation ground the functional case work.
Methodology note. External survey figures use different samples and definitions and should be read directionally. Product-scope figures describe implemented system structure; they are not customer outcome claims.
Three technology inflection points and one shift in awareness are converging on the same timeline.
Since the “DeepSeek moment”, open-source models have matched closed models on many benchmarks and token costs have fallen sharply — enterprise AI went from unaffordable to affordable.
A new generation of models such as GPT-5.3 and Claude Opus 4.1 has matured long-horizon planning and tool use, taking agents from demos into real workflows.
Models such as Claude Fable 5, GPT-5.6 and Kimi K3 make it realistic for agents to embed reliably into a vertical industry's systems, data and collaboration ecosystem.
With domestic models like Doubao and general-purpose agents like WorkBuddy now widespread, managers and frontline staff have used AI first-hand — the question has shifted from “should we use AI?” to “how do we bring AI into our own business?”
The first wave of enterprise AI made information easier to find and content faster to create. The next wave is harder—and more valuable. It must understand the record of work, recognize the decision in front of an operator and connect that decision to a controlled action.
A chatbot can sit above fragmented systems. An operating product cannot. In logistics, it needs the current supply-chain record, rate, document, milestone and partner status. In manufacturing, it needs the order, specification, batch, production stage and quality evidence. Without that context, intelligence may sound convincing while remaining operationally irrelevant.
The durable advantage will not come from adding intelligence to the edge of an old process. It will come from digitizing the work deeply enough that intelligence can participate in the process—reliably, traceably and under human control.
Not “Can AI answer?” What happens next?
Technology is no longer the biggest barrier. The biggest barrier is now ecosystem integration and the ability to actually deploy intelligent operations inside enterprises.
Whoever has real scenarios, industry understanding and a delivery method stands on the right side of the divide. That is why HZ Tech chose the FDE path: we work inside our customers' operations, one industry at a time.
Solve concrete customer problems like an FDE team; build repeatable standard products like a SaaS company.
Interview frontline roles and observe real work
Split into steps, inputs/outputs and acceptance criteria
Validate the workflow quickly with AI-assisted development
Iterate on real data, keeping human approval and rollback
Consolidate into standard products — agentic systems, skills, MCPs — to cut deployment cost
A useful industrial system does not stop at insight. It connects three layers of work and makes the transition between them explicit.
Structure the documents, master data, transactions, physical events and exceptions that define the current state.
Supply the rules, history, constraints and evidence needed to produce a reviewable recommendation.
Route the approved decision into the system, portal, message or operator queue that can move the work.
Design principleThe shorter the distance between signal and controlled action, the more valuable the system becomes.
An engagement can start at any stage, and every stage ends with something your team can use.
We go on site to map the workflow, data and decisions, and size the problems worth solving.
You getA prioritized problem map with measurable targets
We build a working prototype with AI-assisted development and test it on your real data.
You getA usable prototype, validated against those targets
Our engineers join your team and wire the solution into the live process, with human approval and rollback.
You getA solution running in your operation
We turn what repeats into a standard product, then keep improving and supporting it.
You getA maintained product with regular iterations
We coach your team to use AI tools well and to own the workflow.
You getA team that runs and extends the system itself
Every product starts in a customer's live operation and is validated there before it becomes a standard capability. Our deepest engagement is with a large integrated logistics group; in manufacturing, we connect a textile producer's work from order to shipment.
A leading integrated logistics service group in South China
Source: public information on the customer's websiteExplore how the same delivery discipline becomes a different operating system in logistics and manufacturing.
| Logistics & supply chain | Manufacturing | |
|---|---|---|
| Primary unit of truth | The supply chain | The production order and batch |
| Work crosses | Customers, forwarders, carriers, customs, warehouses and drivers | Planning, materials, production stages, quality and shipping |
| Critical evidence | Rates, bookings, documents, milestones, handoffs and physical events | Specifications, work orders, lots, stage status, tests and deviations |
| Decision window | Quote, route, book, declare, move and recover | Plan, sequence, inspect, explain and correct |
| Failure to avoid | A fast answer built on stale or fragmented supply-chain data | A recommendation detached from capacity, process or quality context |