Where AI is worth doing in Pittsburgh
Pittsburgh has long been an engineering town, and a firm of twenty engineers here bills for design and judgment. The paper around a single project shows where the other hours go. A contractor sends in a submittal. Somebody logs it, routes it to the right engineer and tracks it until it is answered. The project team holds a two-hour coordination meeting, and somebody turns it into minutes with action items and owners. Before the documents go out, a specification is checked against the drawing list for the sheet that was renumbered. Then the next submittal comes in.
With our software in that office, the submittal goes into the log as it comes in, and the log shows what is outstanding and which engineer has it. Minutes are drafted from the recording or the notes, and the engineer who ran the meeting corrects them before they go out. Mismatches between the specification and the drawing list come back as a list for an engineer to resolve. Whether a submittal is acceptable stays the engineer's call, and the engineer still reviews and stamps the work. Before it starts, we and the office put in writing which project folders the software may open, and what it keeps is hosted on hardware we own. The logging, the first draft and the cross-check are routine, and software can carry them. We run our own businesses this way, with court-record lookups and reminder texts handled by software we built, and nobody lost a job.
Other small offices around Greater Pittsburgh carry the same kind of paper: an accounting firm waiting on client documents, a remodeler with estimates to follow up, a health care practice with appointments to confirm. For the engineering office, the change is plainest from the client's end. A plant manager in Ohio asks where a submittal stands and gets an answer taken from the current log. A hospital in West Virginia receives minutes with a name beside every action item. A client in Texas who came by reputation sees a Pittsburgh firm of twenty keep its paper in order.



