An agency CRM running three surfaces from one codebase
A domestic-staff agency running on paper and WhatsApp. The office, the field staff and the partners had no shared system, so the same booking existed in three different states depending on who you asked.
Three groups, no shared record
The office worked from paper. Field staff worked from WhatsApp. Partners worked from whatever they had last been sent. Nobody was wrong, exactly, but there was no single record of a booking, so reconciling the week was somebody's whole Thursday.
What we built
Three surfaces from one codebase: a web admin for the office, a mobile app for field staff, and a REST API for partners. Leads are captured from WhatsApp directly. A family-matching engine handles placement. Contracts are generated as PDFs and signed electronically, billing recurs on its own, and clock-in and clock-out are GPS-verified with live tracking and route optimisation.
Why one codebase and not three
Three surfaces usually means three projects, three release cycles and three interpretations of the same business rule. Sharing the codebase means a change to how a placement works lands everywhere at once. It costs more discipline up front and much less maintenance afterwards, which is the trade worth making for an agency that will keep changing its process.
Stack
React for the web admin, React Native for the staff app, Node and Express behind both. Stripe for recurring billing, Google Maps for tracking and routing, and the WhatsApp Cloud API for lead capture.
Want the same thing looked at in your business?
We map the process, find the part worth automating first, and give you a written scope with the phases separated. No obligation, and you keep the plan.