Software for the firms that keep Baltimore running
The person who calls a Baltimore facilities firm is responsible for a building: a hospital engineer, a campus facilities manager, a downtown property manager, someone at the port. That person needs to report a fault once, with the site and the equipment, and to hear who is coming. Afterwards they want something to show their own managers: who attended, when, what was done, and a signature. What reaches them instead can be a paper sheet that got to the contractor's office days after the repair.
Behind that call, requests arrive by phone and email and whoever is free gets sent. The firm may have a dozen technicians and no single list of their work. For such a firm we would build one work-order system in place of the phone notes, the inbox and the paper. A request is entered once, with its site, equipment and urgency. The office chooses the technician, who opens the job on a phone and sees that site's history. A photograph and a signature close the job. The invoice is drawn from that record and goes out only after someone in the office has approved it. Each client has a private page listing its open and closed requests. Where a product the firm already pays for does this, we build only what is missing. Scope and price are fixed in a brief before building starts.
Here is how a job in Wilmington would run. A client whose Baltimore buildings the firm already maintains has a property there, and its manager emails about a failed pump. The request is logged in Baltimore, and the office sends a technician up the road with that building's history on a phone. A photograph and the manager's signature close the job, the invoice follows from the record, and the client sees the Wilmington pump on the private page that lists its Baltimore requests. Between the first email and the invoice, the only thing that happened in Wilmington was the repair. A Washington building is handled the same way, as is the work of a firm that cleans, moves or maintains.



