Multi-tenant ERP and CRM
PotholeDoctor
An ERP and CRM for a paving-repair contractor, covering the whole job from lead to completion certificate.

cat README.md: overview
PotholeDoctor runs a paving-repair business end to end: leads, estimates, proposals, invoices, work orders, materials, crew scheduling and completion certificates.
Every company gets its own subdomain and PostgreSQL schema. A Next.js proxy resolves the tenant and refreshes tokens, and Laravel switches to that tenant’s schema and checks permissions on every request. The backend is split into modules (CRM, estimates, invoices, work orders, inventory, tasks and more), so each part of the business can grow on its own.
What I built
- Lead pipeline with stages, sources and interest levels, turning into customer records with contacts, addresses, notes, documents, email and SMS
- Estimates priced from map take-offs: staff draw and measure the repair areas on Google Maps
- Proposals and invoices that customers review, approve and sign through a public link, with no account needed, plus history, email and reopen or void
- Work orders with services, tasks, notes and job photos, ending in a completion certificate
- Inventory across warehouses: products with bulk edit and QR codes, purchase orders and shipments, stock adjustments and material jobs
- Vendors, partners, couriers and salespeople, with rebate credits, commissions and salesperson rankings
- Scheduling and tasks on a calendar, with reminders sent through queues on Horizon and RabbitMQ
- Company settings for service templates, labor costs, payment terms, taxes, units, and contract and message templates
- Roles and permissions per company, staff accounts, OTP password reset and in-app notifications
- Excel exports across customers, invoices, work orders, inventory and tasks