Reference builds

How we solve each family of problem.

Five builds with synthetic data. They are neither clients nor finished products: they are how we approach a specific kind of operation.

Quotation Intake

Reference build

Requests arrive by email with drawings attached and nobody knows how many are open.

Flow: Intake → customer, material and deadline extracted → revision check → review → opportunity
Human decision: The bid owner confirms scope and margin before anything is created.
Observable result: A single queue with status, owner and deadline visible.

Reference build

The answer exists, but it lives across SharePoint, inboxes and three people's memory.

Flow: Question → permission-aware search → answer with citations → expert confirmation
Human decision: Nothing ships without a linked source and someone validating it.
Observable result: Answers with checkable provenance and reusable questions.

Reference build

Issues arrive through three channels and priority depends on who shouts loudest.

Reference build

Nobody sees the real state until someone builds a spreadsheet on Friday.

Flow: Process events → consolidated state → exceptions → owner
Human decision: Exceptions escalate to a named person, not to a shared inbox.
Observable result: One view of what is stuck, since when and who owns it.