A system covering the commercial cycle of an occupational health and safety company: from the proposal to the contract and the work order. A modern architecture, with a REST API and a React front end kept separate.
The challenge
The clinic's operations were already sorted. What was still manual was what comes before them: the negotiation. Proposals built in a spreadsheet, approval by email, the contract typed in again, and the work order emerging disconnected from what had actually been sold. The result is the classic mismatch — what was promised in the proposal, what is written in the contract and what the operation actually performs are three slightly different things, and the difference only surfaces at invoicing.
The solution
Higia chains proposal, contract and work order into a single flow. The services quoted in the proposal become the services in the contract, which in turn determine the work orders carried out — with no re-typing and no divergence. Each stage has its own tracking screen and dashboard: open proposals and their approval stage, active contracts by company and address, work orders in progress and a sales summary. Technically it is the most modern project of the set: a REST API with token authentication and an independent React front end, which cleanly separates domain from presentation and lets the two evolve at different paces. The domain is isolated in its own library, with an audit trail on every main entity.
Results
From nothing to operating in six months, with 25 domain entities, 11 endpoint groups and 77 database versions. The first system in the group built as a separate API plus front end, serving as the architecture reference for the ones that follow.