javier.org.uk
Demo · synthetic data

Latticeform

Agents that schedule maintenance before a line stops, using the plant’s own history.

LondonIndustrialFounded 20248 people

Team

74

Plant engineer and a software generalist. Credible on the floor, unproven at selling a second site.

Weight 30

Market

72

Unplanned downtime is priced. Software budgets at this layer are not. That gap is the whole question.

Weight 25

Traction

48

One plant, €150k, a second site ‘verbal’. Too early to score as traction. Score it as a signal.

Weight 25

Moat

57

History of that plant’s failures. Valuable locally, not yet a dataset.

Weight 20

Watch

Screened 2 Oct 2026Pre-written. The replay is simulated.

Summary

Latticeform proposes the week’s maintenance from the plant’s own failure history. One UK site pays €150k. The seed is small. We do not need to hurry, and we should not drop it either: the introduction came from the Kiln network, which has been right once.

Why now

There is no process forcing a decision. The founder is raising because the first plant’s parent wants a second deployment and will not fund it internally.

Product

A scheduler on top of the CMMS the plant already hates. It does not claim to see the future. It claims the Tuesday jobs are in the wrong order. The plant manager agreed, which is the only reference that matters.

Business

Site licence. One logo. Gross margin irrelevant at this scale. A €2m cheque is only sensible after site two is contracted, not ‘verbal’.

Recommendation

Leave it in sourced. Amira asks the parent for a written second-site scope. If it arrives, screen it. If it stays verbal, it stays a note.