Simple Simon

What Stevin gets out of Simple Simon

Simple Simon does exactly what the name promises: engineers quickly record their job, hours, materials and photos in a work order while on the move. It is low-friction, and that is why it actually gets used on site, where heavier systems get left alone. But that simplicity stops the moment the order is done. We see service firms stall after completion: a work order that is finished but never invoiced, a customer who gets no update, a happy customer who is never asked for a review when that was exactly the moment. Simple Simon captures the work in the field, but does nothing afterward. Stevin reads the finished orders through the API or an export and turns them into signals with a next step underneath: invoice, update the customer, ask for a review. The owner sees the action before it goes out, Stevin makes sure the order does not stay sitting.

What you pair it with

Choosing Simple Simon gives you fast input in the field, but the whole follow-up side is something you have to arrange yourself, because it is deliberately not in the app. Count on an invoicing system alongside it and something that turns finished orders into actions. The connection runs through the API or an export, so the orders come out. The question is what happens the moment an order is finished. Without something reacting to that, finished orders pile up and you miss both the invoicing and the right moment for a review.

Common mistakes

• →Not turning finished work orders into invoicing, so revenue is delayed.
• →Not giving the customer an update after the job, when a short message makes the difference.
• →Letting the review moment pass because no one has a signal on it.
• →No overview of open service actions, so everything runs on the planner's inbox.