Where AI is worth doing in Ann Arbor
Ann Arbor has a great many small technical companies for a city its size, and yours is probably built like many of them: a dozen people, a product already in customers' hands, nobody whose whole job is operations. So support falls to whoever wrote the feature. The same handful of questions comes in every week, the documentation holds the answers, and each reply takes a slice of a developer's morning. The offices around you have their own version: a research firm, a property office and a dental practice each answer a repeating message and chase the same follow-up, about a report, a lease date or an appointment.
For your company we would build a drafting tool that works inside the help desk you already use, or by email where it offers no connection. An incoming message is matched to the passage in your documentation that answers it, and the reply arrives as a draft for one of your team to send. A message that describes a real fault gets no reply from the software; it is marked for an engineer, and a question about a price or a promised date always goes to a person. Release notes are assembled from the work completed, and the weekly numbers from the systems you already use. You decide which kinds of reply may go without a reader; a plain one, such as a link to the right page, can earn that once you have seen enough drafts. We run our own businesses this way, with court-record lookups and reminder texts handled by software we built, and nobody lost a job.
Your team and your product cover very different ground. The team may never drive past Ypsilanti for work, yet customers write from California, Germany and Japan while Ann Arbor is asleep. With drafts waiting each morning and the plainest replies already sent, a customer in Japan is answered from the same documentation as one in Saline, and twelve people can keep up with a customer list growing on other continents. The engineers go back to the product.



