autoVISUS — the CRM dealerships never had
CRM for car dealerships
A small dealership runs vehicles, clients, quotes and sales on spreadsheets and WhatsApp. Generic CRMs do not speak the language of the business: trade-ins, commissions, negotiation stages, brand catalogues. The vertical ones are expensive and heavy. autoVISUS is the middle: built around what a car salesperson actually does.
Recorded on a demo dealership with a real month of data: 4 sales, €60,950 invoiced, 14 proposals, 27 clients and 22 vehicles in stock. No sound.
Eleven reminders, so no follow-up is lost
This is what the application exists for. A dealership does not lose sales for lack of clients — it loses them because nobody called back. autoVISUS does not wait for you to remember: it raises the reminder when the thing happens, and asks again if it goes unanswered.
Booked commitments
- A test drive or visit is coming up
- Warns you ahead of time, at two moments of your choosing — whichever of the two arrives first is the one that fires.
- The next day: what happened?
- The day after a test drive or a visit, it asks how it went. This one opens the bell by itself instead of waiting to be found, and closes as soon as you move the client's stage or write a note. Close it without answering and it goes quiet for that day, then comes back tomorrow.
The deal moving
- The client changed stage
- Every stage of the negotiation has its own reminders, each with its own delay: confirm the visit the next day, call two days into waiting for a decision. You can have more than one per stage.
- After the sale closes
- Post-sale contact, thirty days later by default — and the number is yours to change.
- The sold vehicle is arriving
- When the expected arrival date comes within the notice you set, so you can tell the client before they ask.
- The reminder you set yourself
- A date, a title, and it sits in the bell like all the others.
When the car does not come back
- The test drive ran past its end
- The car went out and has not returned. The alert goes to the salesperson who registered it and to every manager of the dealership, and repeats every day the test drive stays open.
- Two test drives on the same car
- Someone took a car already promised to another drive, after being warned. Only managers are told — the person who did it already knows, it was their call.
Keeping the house in order
- The client's birthday
- Once per client per year. It is the cheapest excuse there is for a phone call.
- The dealership's licence is running out
- Goes to the dealership's managers and to whoever administers the platform, before anyone is locked out.
- A field only a manager can fix is missing
- A colleague tried to issue a PDF and the dealership's address or contact was missing. They press notify the manager and it arrives — once, even if they press it ten times.
How they behave
Four states per reminder: pending, done, snoozed and ignored. Snoozing forces you to pick the new date, because a postponement without a date is forgetting under another name.
The bell shows how many are overdue, and the count updates by itself.
A digest of your reminders by email, at the time and cadence you choose — for the days you do not open the application.
A second email, weekly or monthly, about results rather than tasks: new clients, sales, commissions and each goal's progress.
Every email goes in the language of whoever receives it, never that of whoever sent it.
Twenty minutes. No commitment, and no agency preamble.
A salesperson's day, covered end to end
- 01
Stock and vehicles
Inventory with a catalogue of brands, models, versions and colours. Vehicle states, purchase and sale price, and the margin calculated — when the cost is recorded. When it is not, the system tells you the margin is unknown instead of counting it as zero.
- 02
Clients and pipeline
Negotiation stage and temperature per client, lead source, last interaction. A visual pipeline showing where each deal is, and search that finds someone by name, phone or plate.
- 03
Proposals and sales
Proposals with history, loss reasons when they don't close, and conversion to a sale when they do. The sale date comes from the business, never from the server clock — an automatic date falsifies the record.
- 04
Team and commissions
Several salespeople per dealership, with invitations and permissions. Per-person statistics: revenue, number of sales, proposals. Commissions are private — they never appear on screens shared between colleagues.
- 05
Leads and test drives
A public capture page per dealership, leads landing straight in the system, and a test-drive record showing what is happening right now and what already happened.
- 06
Goals and figures
Personal and team targets on the dashboard, progress through the month, and warnings when information is missing for a figure to be right.
Designed, and not built yet
Separated on purpose. Nothing on this list works today — it is designed, decided and waiting to be built. We would rather tell you now than in a demo.
- 01
Calendar
not built yet
One screen, not two. You see your own events by default and can overlay the whole dealership's, one colour per salesperson, with a filter to narrow it to one person. Arrival and delivery dates, test drives, visits and birthdays land there on their own.
- 02
Adding a vehicle by photographing its registration document
not built yet
Instead of typing fifteen fields: plate, chassis number, make, model, first-registration date, fuel, displacement and power come in filled and you confirm them. The owner's details are not extracted — whoever sold the car to the dealership has no business being in the vehicle's record. The two document formats in circulation, the paper booklet and the card mandatory since August 2020, are different cases and treated as such.
- 03
Three years after the sale
not built yet
A reminder to whoever made the sale when the vehicle reaches the typical replacement age. It fires once, never every year, and the number of years is set per dealership.
- 04
What to do next
not built yet
Five clients in order of real urgency, with the reason written beside each — stalled twenty-five days at the decision stage, test drive at three this afternoon. A booked deadline always comes before a client going cold, and a birthday never outranks either.
Multi-dealership, two languages, licensed
What's included
- 01
Each dealership is isolated: none can see another's data, guaranteed in the database design rather than in the hope of whoever writes the query.
- 02
Interface in Portuguese and English, served from the API — no text welded into the code.
- 03
Licensing per dealership, with team invitations and roles. The admin role bypasses the checks, and that is written in the documentation instead of hidden.
- 04
Tests running against the real database, not against imitations: 586 on the server, 107 on the interface and 65 full journeys in a real browser, plus a check that all 1,112 translations exist in both languages. Measured 20 August 2026.
- 05
The test data deliberately exceeds the screens' limits — more than one page of everything, because a screen only tested with ten rows was never tested.
- 06
Running it locally is one command: the whole stack comes up in Docker.
Who it's for
Dealerships with one to ten salespeople who have lost track of stock and proposals.
Anyone who wants the real margin per sale and the commission per salesperson.
Groups with more than one dealership that need them kept apart.
And who it isn't
Anyone who just wants a website with the cars: a site costs less and is enough.
Anyone needing certified invoicing — we don't do that; it integrates with those who do.
The right-hand column exists because saying no in time saves money on both sides. If you are in it, we will tell you in the first conversation.
What happens after you write
- 01
A person replies, not an autoresponder.
- 02
We ask the questions that are missing — no commitment, no mandatory meeting.
- 03
You get a proposal with a figure, a timeline, and what is excluded.
