From field planning to invoicing: one connected operations platform.
A custom system for coordinating distributed field work, while keeping planning, execution evidence, customer records and invoicing in sync.
Planning, fieldwork, customer updates and invoicing lived in separate places. Changes in one system did not reliably show up in the others, so office staff spent time reconciling the day by hand.
Build one operations platform with clear data ownership, background sync and interfaces per role. Not another spreadsheet bolted onto an existing tool.
What I built
- Work-order and intervention management for office and field roles.
- Queued constraint-based route planning (vehicle routing with time windows) using Python and OR-Tools.
- Webhook-driven synchronization with batched jobs and clear ownership rules between systems.
- Draft invoice generation tied to completed operational work.
- Separate interfaces for administration, field workers and customers.
Planning, execution evidence and invoicing sat in one maintainable platform instead of a chain of disconnected tools. I am not inventing savings figures here. The outcome is structural: one place that is authoritative for the operational day.
Custom software
Internal tools, integrations and domain models when SaaS stops fitting.
Read more →Need an operations system that matches how your teams work?
Tell me what you’re trying to build, automate or fix. A few lines is enough.
I read everything myself. No newsletter, no CRM sequence.