Software for firms that service other people's equipment
A customer with a plant in Hillsboro may have others in Washington and Idaho, and would rather have one service partner and one record for all three. Sooner or later that customer asks its Portland-area service firm to look after the Tacoma site too, or the one in Boise. What keeps a firm with ten technicians from saying yes is seldom the technicians. That customer wants a report after every visit and the year's history on request, and a firm assembling those by hand cannot add sites in another state.
The work behind those reports sits in a calendar, a spreadsheet and email. Each customer's agreement sets its own visit schedule, and somebody rereads it to learn what is owed. The plant in Hillsboro, the port and the hospital each expect their report when the visit ends, so technicians write them in the evening. Parts leave the van without leaving the stock sheet. At year's end a customer asks for every visit and every part, and the office digs them out of sent mail. A technician crosses the river twice in a day because nobody saw the two calls together.
We would build the agreements, the schedule, the van stock and the reports into one program, and the customer notices the change first. Their agreement lists the visits owed. Their report is built from what the technician entered on site and reaches them once the technician has signed it. Their history sits on a private page they can open themselves. Parts used come off the van's stock and onto the reorder list. An agreement nearing its end appears on a list with the visits made and the parts used, and the renewal price is yours to set. Field-service products exist, and we look at what you already pay for first. Scope and price are fixed in a brief before building starts. When the customer's Tacoma or Boise plant is added, its visits land in the schedule your dispatcher already opens each morning, and a technician based near that plant files reports as the ten around Portland do.



