CRM for Moscow
truck permits

Task

Before the CRM, everything lived in Excel: every client vehicle has its own permit, inspection card expiry and RNIS status. The owner spent half a day processing her clients by hand — checking deadlines on government sites, calling and messaging each one. Even so, revoked permits were still noticed late, and clients called the office to ask about status. The goal was one system with automated checks against government sites and separate access for the owner, an assistant and the client.

Solution

We built a lightweight server-rendered CRM in Go with no separate frontend: it loads fast, works on a phone and ships as a single Docker container.

• One table of clients and vehicles: VIN, payment, RNIS in three states, zone (MKAD / TTK / Garden Ring), price, permit and inspection dates, internal and client-facing comments
• Scheduled permit, RNIS and inspection checks plus a “Check now” button, with permit history in the vehicle card
• Email and SMS notifications to the client when a permit is issued or revoked, a stop list and per-contact opt-out
• Leads: statuses, extra contacts, callback reminders as a pop-up, bulk handover to an assistant
• Excel / CSV import and export — migrating the old spreadsheets without manual re-entry
• Roles: the admin sees the whole fleet, an assistant only their own clients, a client only their vehicles in the portal
• Search by plate, VIN and phone, filters by permit, onboarding and revocation dates
• Daily database backups, Docker and auto-deploy via GitHub Actions

Results

Managers no longer check deadlines by hand: the CRM checks permits and inspections, highlights expiring and revoked ones and notifies the client. Clients see their vehicles’ status in the portal without calling. Screenshots show a demo instance: companies, plates and contacts are fictional.

Screenshots