The drawing that arrived as a photograph

A customer sends a drawing. Not a file — a photograph of a drawing, taken at an angle, with dimensions handwritten in the margin.

Somebody at a trade stand photographs a spec sheet rather than carrying it home. A business card goes into a jacket pocket. A whiteboard at the end of a good meeting gets snapped by three people and shared to nobody.

All of it is real business. None of it is in any system. It sits in a camera roll until somebody remembers it exists, which is usually one week after it would have been useful.

Real work does not arrive as structured data

Software has a quiet assumption baked into it: that information turns up in the shape the software expects. A form gets filled in. A file gets uploaded to the right place, named properly.

Industry does not work like that, and it never has. An enquiry arrives as a photograph on a phone at half past eight at night. A revision arrives as a scan with a stamp on it. A requirement arrives as a whiteboard.

So the intake is where companies leak. Not the pipeline, not the reporting — the gap between something arriving and something being recorded. Every tool in the building starts working after that gap, which is why nobody has ever fixed it.

How it works, roughly

Happen reads what arrives, in the form it actually arrived in.

• The dimensioned drawing a customer sent as a photo. Read, and filed against the right account.
• The spec sheet photographed at a stand. Same.
• The business card, the whiteboard, the quote, the purchase order, the CV. Read, filed where it belongs, and flagged when something does not match what the record already says.

That last part matters more than the filing. A purchase order that does not match the quotation it refers to is the cheapest problem you will ever solve, and only if you catch it on the day it arrives rather than at invoicing.

Why it stays in your building

Look at what is actually in that pile. Customer drawings. Pricing. Specifications a competitor would like to read. The photographs are often more commercially sensitive than the contract, because they show what is being built before anybody has announced it.

This is exactly the material that has to be read to be useful, and exactly the material that should never leave the site to be read. Both are satisfied by the same decision: the model runs on your own hardware, inside your own network.

And a person still confirms where it landed. Happen reads the photograph and proposes the account; somebody who knows the customer says yes. That part we are not trying to automate.