Project study / Pest-control software
A service visit.
A clear record.
A simpler day.
Connecting the office and the technician, from assigning a visit to preserving the work recorded on site.
A study of the application we built and reviewed. Customer adoption and time savings have not been measured.
Discuss a similar workflow →
The brief
Two people. Different jobs. Shared information.
Office staff need to manage customers, schedule visits, assign technicians, and review reports. Technicians need to see their assigned work, register arrival, record findings, and finish the service from a phone.
The product brings those steps together with a desktop interface for the office and a mobile interface for the technician. Each person sees the work relevant to their role.
The working path
Keep the visit connected.
- 01 / Office
Schedule and assign
Create the customer and service location, schedule a visit, and assign a technician.
- 02 / Technician
Record the work
Register arrival, save findings and photos, and record the products used during the visit.
- 03 / Completion
Preserve the record
Record customer acknowledgement and save the completed service revision that the report is based on.
An important decision
Remove steps the first version doesn’t need.
The original inventory design included warehouses and transfers to technicians. Reviewing the interface exposed a simpler need: define a product, enter a quantity, and record how much was used on a visit.
An acceptance-check example, not a customer performance metric.
The simplified flow keeps a company stock balance and usage history while removing warehouse allocation and receipt-confirmation steps from everyday work.
What the work established
A working implementation, with limits made visible.
The project records document working visit flows, permissions checks, service-history preservation, and report inspection. Completed records remain stable when later findings change.
Those checks do not establish long-term field reliability or customer adoption. Production email configuration and physical-device camera testing were among the release issues identified in the implementation history.
Your next step
Does your team have a workflow like this?
Tell me where information gets lost or work gets repeated. We can start with one useful improvement.
Discuss your workflow