01
The context
The group wanted a single entry point for its internal processes, reachable with company accounts: requests and approvals, supplier purchasing, vehicles, deliveries.
02
The problem
Each process has its own forms, approval rules and people. The platform had to cover dozens of business domains and keep evolving without interrupting modules already in use.
03
What we built
A modular intranet on a domain driven architecture. Each module is described in a detailed specification, then built with Claude Code and reviewed by our engineers. A shared approval engine runs the approval workflows of every module.
-
01 · REQUESTRequest created Business form
-
02 · WORKFLOWApproval workflow Process rules
-
03 · APPROVALApproval by role The right manager Approve
-
04 · TRACKINGStatus updated Lifecycle tracked
- Configurable approval workflow engine, shared by every module
- Supplier prequalification with HSE questionnaires and an approval cycle
- Fleet management and delivery logistics tracking
- New version deployed alongside the old one, on the same database
04
The intranet modules
Each module of this intranet is a reference in its own right: one business process, its rules, its users.
-
Requests approved by email, with no trail and no reminders
A workflow engine shared by every module: steps, roles and conditions set per process, a history of every decision and a single page of pending actions.
Outcome : Every request follows a known path, and every approver sees what is waiting for them.
See the module : Approval workflows -
Qualify suppliers before working with them
Configurable HSE and business questionnaires, supporting documents, an approval workflow, then a supplier evaluation once the work is done.
Outcome : A complete, current file for every supplier, available to purchasing.
See the module : Supplier prequalification and evaluation -
Purchases tracked in exports and spreadsheets
Purchase requests, item and project codification, purchase orders and payment terms, with the exports finance expects.
Outcome : Purchases across the group follow one codification and one workflow.
See the module : Purchasing and purchase orders -
Track vehicles, their maintenance and their fuel use
Vehicle records, preventive and corrective maintenance, fuel entries with mandatory evidence and a tank capacity check.
Outcome : Every refuel is backed by evidence and tied to its vehicle.
See the module : Fleet and fuel -
Know where every shipment stands
Delivery tracking from request to receipt, lifecycle statuses, and adjustments driven by feedback from field testers.
Outcome : Every delivery has a status and an owner.
See the module : Logistics and delivery tracking -
Sales forecasts calculated differently by each team
An opportunity pipeline, win probability set by status, a high confidence flag and a monthly breakdown of expected revenue.
Outcome : Every subsidiary calculates its pipeline with the same rules.
See the module : Sales opportunity tracking -
HR requests scattered across forms and emails
Leave requests and balances following each subsidiary’s rules, performance reviews and objectives, and employee offboarding.
Outcome : Employees make their HR requests in one place.
See the module : Human resources -
Site inspections filled in on paper
Site inspections and work permits, variants per subsidiary, and an offline mobile app for field teams.
Outcome : Inspections are entered in the field, even without a network. Rollout in progress.
See the module : HSE: inspections and work permits -
One more account to manage for every internal tool
Sign in with company accounts through the directory, roles and scopes per subsidiary, and Active Directory account audits.
Outcome : Employees sign in with their usual account.
See the module : Accounts and access
05
The results
Teams have one platform for their internal processes. Modules go to production one at a time: the old and new versions run side by side, so migration happens without downtime.