Where AI is worth doing in Portland
A quote request reaches an equipment supplier west of Portland as a drawing, a list of part numbers and a date from one of the large plants. The estimator, one of twenty people at the firm, hunts through old folders for a job like it, works out a price and sends it. If the plant says yes, the equipment goes in and a technician returns on a schedule to service it. Every visit ends with a report in the plant's own format, pieced together from notes and photographs, and it is usually written at night.
Our work changes that job at its slowest points. The request comes to the estimator laid out, the part numbers listed and the closest past jobs open beside the drawing, and the price remains the estimator's to set. After a visit, the technician's notes, readings and photographs come back as a draft report in the plant's layout, which the technician corrects and signs. The list of maintenance visits falling due keeps itself, with nobody watching it. We run our own businesses this way, with court-record lookups and reminder texts handled by software we built, and nobody lost a job. A plant's drawings can come with limits on who sees them. Which ones the software may open is written down with the firm before it opens any, and the firm's records are hosted on hardware we own.
Portland has plenty of small firms whose week repeats like this one, among them makers on the Central Eastside sending the same wholesale answers and shipping updates. The supplier's limit is different: the firm depends on one plant and grows only as fast as that plant buys. Boise, where the same industry builds, is the nearest way out, with Phoenix and Austin after it and customers across the Pacific beyond. A plant in Boise wants its quote and its service report as promptly as the one near Hillsboro gets them. Once software drafts its quotes and its service reports, the same estimator can answer a plant in Boise from the desk where the Hillsboro quotes are priced.



