Evolving December 10, 2025
MobiFlex, Smart Booking and CRM for Mobile Services
A flexible workflow system for trades and field-based businesses
crm field workflows automation scheduling full-stack
React PostgreSQL FastAPI Python LLMs Google APIs Mapbox Mailgun
1. Context
MobiFlex was designed as a smart booking + CRM system for mobile service businesses, including electricians, cleaners, auto detailers, lawn care, and other field-operation teams who rely on fast, clear communication and consistent job flow.
Traditional CRMs are either:
- Overbuilt (enterprise bloat),
- Underbuilt (simple forms + spreadsheets), or
- Too rigid for the unpredictable nature of field work.
MobiFlex sits directly in the gap:
A flexible workflow system designed around how field work actually runs.
2. The Problem
Field operators deal with constant friction:
- Jobs booked through multiple channels (DMs, calls, texts)
- No centralised customer history
- Manual reminders & follow-ups
- Scheduling conflicts or gaps
- Lost details between booking, job, and payment
These aren’t “software problems.”
They’re systems problems that require a full-stack workflow approach.
3. Constraints
- Users often operate entirely from mobile
- Data needed to remain simple, not overengineered
- Must support irregular schedules (weather delays, travel time, cancellations)
- Needed to integrate with existing habits (Google, SMS, email)
- Budget-limited small businesses where efficiency mattered
4. The System I Designed
A modular workflow system with smart booking, customer history, and automated job handling.
Components
- Smart Booking Form: dynamic intake, reduces back-and-forth
- Customer Profile System: history, notes, preferences, past jobs
- Automated Reminders & Follow-ups
- Job Timeline: booking, confirmation, and completion
- Mobile-first dashboard for field operators
- Admin controls for the business owner
- LLM-Assisted Tools for triaging leads, bookings and operational tasks
How It Works
- Customer submits a smart booking request (or operator enters manually).
- System checks availability + location + job type.
- Customer receives confirmation + reminders automatically.
- Job appears in the mobile dashboard with all relevant info.
- Completion triggers follow-up messages and record updates.
- Entire lifecycle logs into the customer’s history.
It becomes a clear operating surface for the business.
5. Before vs After
| Before | After |
|---|---|
| Bookings scattered across apps | All bookings flow into one system |
| Manual reminders & follow-ups | Automated lifecycle messaging |
| No customer history | Full CRM timeline from first contact onward |
| Scheduling by guessing | Smart scheduling + buffer logic |
| Admin buried in micro-decisions | System-driven workflow |
6. Stack & Architecture
- Neon Postgres for DB, and real-time functionality
- Clerk for authentication
- Next.js / Astro hybrid for brochure site + app dashboard
- LLMs (OpenAI/Anthropic) for generating job descriptions, summaries
- Python microservices for routing logic and data sync
- Google APIs for calendar integration
Architecture emphasizes:
- Modularity
- Field resilience (offline-ish behaviour)
- Minimizing user thinking
- Automating everything that isn’t uniquely human
Project links
- See it live: Visit the MobiFlex marketing site
- Related system: Service Area Map Generator
- Contact: Talk to Blake about booking and CRM systems
7. Impact
- Faster booking flow
- Fewer errors (customer name, address, job details)
- Centralized data and less operational stress
- Operator clarity: “What’s next?” always visible
8. What I’d Build Next (v2)
- Full job photo logging system baked in (like Job Pics)
- Schedule optimisation engine
- Voice-to-job logging (start/end job using speech)
- Multi-operator mode with real-time assignment