# Tempo, Sense Asia

> Tempo builds Sense Asia's fulfillment plan from ERP and legacy exports, flags the orders at risk of a missed date, and puts the plan in front of a planner.

Source: https://www.homodeus.co/tempo | Language: en | Updated: 2026-10-30

---

### The ask

Sense Asia runs supply chain operations. Synchronizing order fulfillment meant reading exports from the ERP and legacy systems by hand, about ten hours of planning a day, with each planner keeping a private file and a private version.

## The plan lived in separate files, and in each planner's head.

### The inputs

The ERP and legacy exports, the orders, inventory, purchase orders and production schedules each sat in a separate place.

### The decision

Each order is a constraint check across three moving quantities: its target date against stock, material arrival and capacity.

### The miss

Orders heading for a late date were not flagged before the date slipped.

## The agent proposes. The planner signs.

### The plan

It reads the ERP and legacy exports and builds one fulfillment plan, with a visual view and a suggested action for each order at risk.

### The signature

The planner approves every plan that goes out. The agent does not release one alone, and the client is not ready to remove that step.

## The blocker was habit, not code.

### Adoption

Planners kept opening their old spreadsheet first, even when the agent was right. Seminars and one-to-one sessions fixed that, not a change to the agent.

## Outcome

Ten hours of stitching exports together each day is now one plan the whole floor shares. Every order heading for a late date is flagged while there is still time to move it, instead of found after it slips.

---

[Site index](https://www.homodeus.co/llms.txt) | [Ask this site](https://www.homodeus.co/api/llms?query=HomoDeus)