Yuhox Works.
Industry-agnostic project management. Dispatch, work, acceptance, and settlement in one flow.
How to start
Match the workflow first
What is still in development we will not describe as ready. Tell us what you need to do; we will say whether we cover it now.
Trial or a pilot
If a pilot fits, we install it. If it does not, we say so — we do not force a sale.
Buy after it ships
Prices are on the pricing page. We will not put a placeholder number for something not priced yet.
What it solves
Dispatch work, do the work, acceptance, settlement — one job tracked from start to finish. Any industry that assigns work by project, works by work order and gets paid on acceptance runs this process. Yuhox Works drove the industry assumptions out of the core tables; the main process keeps only project, stage, work order, acceptance and settlement. Switching industries means switching templates, not switching systems.
Before and now
| Before | Now |
|---|---|
| Generic tables stuffed with industry-specific data; a new industry means a rewrite | Generic tables keep only what all business types share; industry differences go through configuration and templates |
| The workflow is hardcoded to four stages of one industry | Stages are configurable. Once one industry is working, save it as a template and reuse it for the next |
| Tickets go out; what comes back is a few photos in WeChat | Mobile: take jobs, fill in, photograph, and sign. Files bind to the work order. |
| Settlement is done in Excel; change one cell and the whole sheet recalculates | Settle by project, batch or person; export and book it |
| No signal on site means you cannot fill anything in | Can be filled offline; syncs when back online |
Core capabilities
- 01
Industry-agnostic core
Five tables — project, stage, work order, acceptance, settlement — carry the main process; industry differences go through configuration.
- 02
Field work
Ticket dispatch, mobile fill-in, photos and signatures as a trail.
- 03
Settlement and reconciliation
Settle by project, batch or person; export and book it.
- 04
Template reuse
Once an industry is proven, save it as a template. The next industry uses it as-is.
Who it is for
Engineering retrofit, installation and maintenance firms
Assign work to people, keep an acceptance trail, settle by batch
Project teams that use subcontractors
Subcontract tickets and settlement are counted separately; the books stay clear
Teams that have already switched project tools more than once
Do not want to be locked to an industry template again
Why this one
Five tables carry the main flow
Project, phase, work order, acceptance, settlement. The simpler the skeleton, the less a single industry can pull it off course.
Template reuse
Run one industry through once, save it as a template, and the next similar project applies it directly. That's the real payoff of generalizing the design.
Acceptance records are the settlement evidence
Photos, signatures, and measurements bind to the work order. Settlement does not mean digging through chat history for proof.
Same stack as the company's other systems
The front end and the server side use the same technology choices as Yuhox's other sites, so staff can cover for each other. For a small team that's a real cost.
Same job, two ways
The left column is what most sites do today, without naming any product; the right column is what this skeleton is meant to be.
| Topic | Common practice | Yuhox Works |
|---|---|---|
| Change industry | Generic tables crammed with industry-specific data; a new industry means a rewrite | Five generic tables carry the main process; industry differences go through configuration and templates |
| Field reports | A few photos in WeChat that never match at settlement | Take the job, fill in, photo, sign — on the phone. Files stay bound to the work order |
| Settlement | Reconcile in Excel; one change recomputes the whole sheet | Settle by project, batch or person; export and book it |
| No signal | Cannot fill it in; catch up later | Can be filled offline; syncs when back online |
Key parameters
| Status | In development; there's no externally delivered version yet |
|---|---|
| Form | Web + mobile |
| Deployment environment | Linux x64 + PostgreSQL |
| Frontend | React + Vite + TypeScript |
| Account | Connect to Yuhox unified sign-in |
| Offline | Field work orders can be filled offline |
Up front
Can we use it now?
There's no released version yet. This main process genuinely ran on one business line; after that line stopped we stripped out the industry assumptions and kept the skeleton. If you want to use it, contact us first and we'll build the first phase together around your project.
Our industry is very different from senior care. Will this still work?
If the main flow is generic, it can be used. The real test is whether your work fits this line: project — stage — work order — acceptance — settlement. Where it does not, we will say so rather than force it in.
Can we import existing Excel ledgers?
The plan is two-level import: by project, by work order. Which column maps to which field is one click during import.
Do you need on-premises deployment?
The design already supports single-machine deployment; for data-sensitive projects we recommend on-premises, and we provide deployment documentation.
One account, multiple systems
If you use several Yuhox systems, one account covers them all. No separate accounts or passwords per system.
Walk us through your process
From winning the job to getting paid, who is involved and where it stalls: we walk through it and see whether it fits.