Wachir: a pest control operating platform the business owns and can trust.
We are building Wachir’s own field operations platform around the way its pest control teams work. The office application, customer portal and technician app connect recurring visits, site evidence, service reports and invoicing, with English and Arabic support across the operation.
- Client
- Wachir Pest Control
- Sector
- Pest control & field services
- What we built
- A custom bilingual field operations platform
- Headline outcome
- Owned scheduling, reporting and billing in two languages
Every visit produces evidence the office and customer need.
Wachir serves contracted sites including warehouses, restaurants, factories and offices. A visit produces a service report; monitoring devices need regular checks; chemical records must remain traceable. The office needs to know what happened before it can review the report, answer a customer or prepare an invoice.
The existing software left gaps in analytics and customer reporting, while invoicing happened outside the platform. Wachir also needed English and Arabic interfaces, correctly rendered Arabic PDFs and a technician experience designed for unreliable connectivity. Owning the system would let the business shape those workflows itself.
The office, the field and the customer share the record.
Recurring operations and supervisor review
Customer and site records connect to recurring schedules, technician assignment, monitoring devices and a shared report inbox. Supervisors can review service evidence before the next office or customer facing step.
A bilingual platform and report service
The web experience supports English and Arabic with right to left layouts. A self hosted PDF service renders IPM and monitoring reports with correct Arabic shaping, using a bounded queue to handle submission bursts.
Customer visibility and connected billing
The customer portal brings service reports, upcoming visits and invoices into scoped views. Completed jobs connect to invoicing, with a data model designed for ZATCA aligned billing requirements.
Analytics built on validated records
Charts, trends, maps and exports use consistent data checks and Riyadh time calculations. Invalid historical dates are quarantined and counted instead of appearing as misleading chart data.
Ownership includes the data rules underneath.
Access checked at database level
Row level security separates tenant and customer records. Audit triggers capture changes, with database tests checking policies and business rules.
Language treated as a product requirement
English and Arabic strings, right to left screens and PDF rendering are part of the shared design system and quality checks.
A tested mobile foundation
The Expo application establishes technician authentication, secure session storage and bilingual interfaces for the phased rollout of field workflows.
A phased replacement, checked against the operation.
The engagement follows the signed proposal across foundations, core operations, invoicing, portal, migration, analytics and field delivery. The web scope is built; the broader rollout remains phased.
- 01
Build the shared foundation
Establish the data model, access rules, bilingual components and core operations workflows.
- 02
Connect the service journey
Bring scheduling, report review, customer views and invoicing onto the same backend.
- 03
Verify and extend
Check real backend browser flows, database rules and mobile contracts as the remaining rollout progresses.
A working foundation under Wachir’s control.
web screens across operations and the customer portal
interface strings translated in English and Arabic
authentication round trips per dashboard view
Figures describe the project’s documented build snapshot. The engagement is a phased replacement; these are delivered engineering results, not a claim that every planned mobile or migration feature is already live.
A few useful
questions.
Is this a generic field service template?
The platform is built around Wachir’s recurring visits, monitoring devices, chemical records, report review and bilingual operating requirements.
What does Wachir own?
The project is built in Wachir’s repositories on infrastructure it controls. The office application, portal and field foundation share a backend and operational records.
What does your operating software still make the team work around?
From the first proof to a working implementation. We’ll explore the workflow, the systems involved and a practical first build.