Sales CRM and field planning
A modular CRM for account managers: customer records, visit planning on a map, quote follow-ups and performance reporting, built on top of existing business data.
Anonymised professional work. Company names, internal systems, data and code are left out on purpose.
- My role
- Scoped the system and wrote the specification, designed a shared design system for its modules, and built the modules and their APIs.
- Type
- Professional, UI/UX
- Technologies
- PHPSQL ServerJavaScriptLeafletOpenStreetMap
Overview
A sales workspace that gives account managers one place to see their customers, plan visits, record interactions and follow quotes through to sales.
The problem
Customer, sales and quote information was spread across existing business systems and spreadsheets, with no shared view of coverage, follow-ups or which areas to visit next.
Architecture
Server-rendered PHP pages with JSON endpoints. The CRM keeps its own SQL Server database and reads sales and quote history from the company's existing systems.
- Existing business data
- CRM database
- JSON APIs
- Module screens and maps
Approach
- Built each module on prototype data first to check the flow with the people who'd use it, then connected it to real APIs one section at a time.
- Defined a shared design system so every module looks and behaves the same while keeping its own styles scoped.
- Specified dashboards that only use real numbers people can drill into: no invented metrics or composite scores.
Key features
- Customer directory with filters, bulk actions and data-quality flags
- Visit planning on a live map, filtered by distance
- Prospect capture with map-based address lookup
- Quote tracking with follow-up and conversion views
- Performance view from assigned customers through to sales