Where AI is worth doing in Philadelphia
Philadelphia's largest customers are institutions: hospital systems, universities and corporations. One small firm that sells to them is a printer in Camden whose biggest account is a university across the river. A department there emails a purchase order as a PDF, and someone in the printer's office retypes the order number, the items and the delivery date onto a job ticket. Once the work is delivered, the invoice has to show that order number exactly, because the university's portal rejects it when it does not. The same month, the university wants its supplier form renewed and a current insurance certificate sent.
The software we would build for that printer reads the PDF the department emailed and fills in the job ticket. By delivery the invoice is drafted with the order number as the university wrote it, set out the way its portal asks. The certificate that expires next month appears on a list with its renewal packet prepared. The first build covers that one account, and the result is set beside how the work is done now. We run our own businesses this way, with court-record lookups and reminder texts handled by software we built, and nobody lost a job. The printer's owner chooses which steps may go out unreviewed. Anything with a price on it waits for a person in the office, and so does any order the software is unsure it read correctly.
The same paperwork sits in offices across the region: at wholesalers and manufacturers, and at caterers, cleaners and repair firms with a hospital or campus account. Such a firm once added a distant institution by sending a salesperson and keeping an office hand who knew that customer's forms by heart. Today a purchasing office in New York can find the Camden printer online, and what its forms and portal require is held in the software, not in one clerk's memory. A firm that struggled to keep two hospital accounts in order can bid for a third in New Jersey, a university in Delaware or a system in New York.



