Field Sales Mapping & Optimised Route Creation

Cliente Freelancer · Remoto · Remoto · freelance · mid · 10–9000 CAD

Publicada el 2026-07-15

Descripción de la oferta

Brief B: Field Sales Mapping & Route Optimisation Tool Job title: Build an Interactive Map & Route Planner for Field Sales Reps Project type: Full‑stack web application (admin map + routing engine) Timeline: 4–5 weeks Engagement: Fixed-price or hourly Overview This application is the “legs” of our sales operation. It consumes a live feed of scored, classified construction leads (provided by a separate intake API) and displays them on an interactive map. An admin can filter leads by score, plan an optimised daily driving route for a rep, export the route as a CSV, and receive visit outcomes back (either via API or CSV re‑upload) to keep the map clean. Core features Admin map dashboard Secure login for the admin. Pull all active leads from the intake system API (GET /leads). Display them on a map (Leaflet or Mapbox) colour‑coded by score (green ≥ 80, yellow 50‑79, red < 50). Filter by minimum score (slider). Click a marker to see full lead details (owner, contractor, phones, project address, score). Automatically hide leads that have been marked as visited (via outcome API). Route planning wizard Admin inputs: starting address (often rep’s home), available time in hours, optional end address. Admin sets a default stop duration (e.g., 15 minutes) – adjustable. System selects the highest‑scored leads that can be visited within the time budget, using: Google Distance Matrix to get drive times between all selected stops. A greedy or optimised TSP selection/ordering algorithm. Display the route on the map with estimated arrival times. Allow admin to manually add/remove stops and re‑optimise. Export the final route as a CSV spreadsheet with columns: Proposal Date, Project Address, Owner name/phone/email, Contractor name/phone/email, Project Details, (optional) Project Type – in visit order. The exported CSV will be ingested by our existing sales‑rep software. Visit outcome feedback loop Support two methods of updating visit results: API integration – the rep’s software calls a simple endpoint on this system (or the intake system) to record the outcome and mark the lead as visited. CSV re‑upload – the rep fills in a “Status” column in the same CSV, and the admin re‑uploads it. The tool processes statuses like: “Calling Queue”, “Acquire Number”, “Measurement Booked”, “No Interest”. Upon outcome recording, the lead is removed from the active map and flagged as completed so it never reappears. Optional nice‑to‑haves Basic historical reporting (visits per day, conversion rates by region). Multi‑rep support (assign routes to different reps), but MVP is single rep. GPS-based actual stop duration tracking (future phase). Technical requirements Frontend: JavaScript, Leaflet (free) or Mapbox GL JS. Clean, responsive UI. Backend: Python (Flask/FastAPI) or Node.js. Must integrate with the intake API. Database: Can use a lightweight store (SQLite for simplicity, or the same PostgreSQL as intake, but not required to share). Google Maps APIs: Directions API (with optimize:true), Distance Matrix, Geocoding (for start/end points). Deployment: Docker or simple deployment instructions. I’ll host on a cloud VM. Integration with the intake system This tool will rely on the intake API (described in a separate brief). You will need to assume that API is live and returns JSON in a documented format. I can provide a mock server if the intake system is not ready. The outcome recording can be done either directly to the intake system (if it accepts POST outcomes) or to your own endpoint, which will then forward to the intake API. We can agree on the simplest approach. Deliverables Working admin web application deployed and accessible. Route planner with CSV export that matches the required format. Integration with the intake API (or mock). Source code, README, deployment guide. Short user guide (can be a video walkthrough). Skills needed Full‑stack development with map/routing applications (must have demonstrable experience). Google Maps Directions API with waypoint optimisation. Backend algorithm for TSP/greedy subset selection. Ability to connect to external REST APIs. Experience with field sales or logistics tools is a plus. Budget & Timeline Timeline: 4–5 weeks. How to apply (both briefs) Please include: Your understanding of the project in your own words. Links to 1–2 similar projects (especially with map + routing for Brief B, or ETL/scoring for Brief A). Your proposed tech stack. Estimated hours and total cost. Earliest start date. I’m ready to start immediately with the right candidate. If you can build both parts (intake + mapping), please mention that – I may award both to one person/team to reduce integration overhead.

Skills

Fuente original: freelancer

Análisis JobHunter