Trade · automotive

A good year on the forecourt.A bad week on Google.

Cars are a considered purchase researched almost entirely before anyone walks in. What they find is your rating, your replies, and whatever you last posted.

Three days on site · three days of analysis · the report is yours either way
12

Open source projects

Public on github.com/JIGGAI

4

AI plugins

Published on npm, free to install

65.3K

AI plugin installs

65,281 to date, per npm

2.8K

AI monthly plugin installs

2,811 in August 2026, per npm

Sound familiar

What we hear in the first hour.

Not a generic list. These are the ones that come up in businesses shaped like yours.

01Reviews

A service went wrong in March and it is still the first review anyone reads.

Reply speed is the only lever you have on an old review. Answered well, it reads as a business that fixes things.

02Escalation

Nobody tells the service manager until a customer mentions it.

Escalation by text within minutes, to the person who can ring them back today rather than next week.

03Repeat

Service reminders go out when someone remembers to run the report.

The most predictable revenue in the building, and the first thing to slip in a busy month.

04Social

Our stock is posted on the portals and nowhere else.

The portals charge for the audience you could be building yourself, and the feed is the cheapest place to build it.

05Multi-site

Every branch handles reviews differently, if at all.

One voice, several sites, with what changes per branch kept to a handful of settings.

The rule

The test drive is not the first impression. The reply to last month’s complaint is.

Which makes response time the number worth moving — ours escalates anything negative by text within minutes and drafts the reply for approval.

What we expect to find

The software already in the building.

We do not arrive with a platform to sell you. We arrive expecting these, and the work is usually in the gaps between them.

01

DMS

Keyloop, Pinewood, CDK, Reynolds. Where sales, service history and the customer record actually live.

02

Google Business Profile

Per site, and usually the most-read page any branch has.

03

Workshop scheduling

Where a job is marked finished — the moment a review request or a follow-up should fire from.

04

Stock and listings

AutoTrader, Cars.com, or the site feed. Where inventory is already structured and rarely reused socially.

05

Customer messaging

Whatever sends MOT and service reminders today, and what record exists of consent.

06

Manufacturer surveys

A separate reputation surface with its own rules, often watched more closely than Google.

A worked example

Getting the service manager to a bad review while it is still fixable.

Roughly what one entry in your report looks like — a real shape, with the numbers changed.

What we saw
Negative reviews found late by whoever happened to look, with no consistent reply and no record of who had seen what. Branch managers learnt about complaints from head office.
What it costs today
On a profile most buyers read before choosing where to service, an unanswered complaint at the top costs you booking enquiries you never hear about — and nobody could say how long any of them had been there.
What we would build
Monitoring across every branch profile, an immediate text and email to the branch manager on anything negative, a drafted reply for approval, and a weekly summary per site with the trend.
How you would know it worked
Time from review posted to manager notified, time to reply published, and share answered per branch. The first of those is what decides whether the customer is recoverable.
And what we would not automate

Offering anything. A reply that promises a refund, a free service or a callback is a commercial commitment, and a system that made one on its own would be committing the branch to something nobody approved.

The arithmetic

What coordination work costs you.

Three numbers you already half-know. Move them until they look like your business.

12

re-keying, chasing status, producing the same document again

6h

on that work specifically, not their whole job

$65

salary, tax, benefits, desk

Coordination work, per year
3,312hours
Plausibly retired by agentic automation
2,484hours

A 75% capture rate. The other twenty-five per cent is judgement, exceptions, and not wanting to look greedy.

1.4
FTE equivalent
$161,460
Per year

This is arithmetic, not a finding. It rests on three numbers you guessed. The assessment replaces all three with numbers we observed — and tells you which of those hours are actually worth automating.

See what a real finding looks like →
What happens

What the six days look like.

The most common question we get is not about AI. It is what these people will actually do in my building.

Assessment · 3 days on site · 3 days analysisNo prep required
  1. Day 1Walk the floorWhoever is on shift

    We start where the work happens, not in a meeting room. Nobody prepares anything, and the first day is mostly watching.

  2. Day 2Sit with the people doing itOps, admin, finance

    Conversations with the roles that touch the work most, and a real task followed end to end — including the parts that happen in a group chat.

  3. Day 3Systems, then a read-backWhoever holds the logins

    What you run, what talks to what, and where a person is currently the integration. We tell you what we saw before we leave, while it is still cheap to correct.

  4. Days 4–6Research and discoveryOur desks, not yours

    Away from your building. We cost the work we watched, model the alternatives, and test the shortlist against your own numbers rather than a framework.

  5. +1 weekOne recommendationPresented in person

    The single change worth making first, specified precisely enough to build — with the ranked analysis behind it and the list of what we would not automate.

Before you ask

The questions this raises.

We have six sites with separate profiles.

Each site gets its own monitoring, its own alert recipients and its own weekly summary, with the drafting voice configured once. Per-site setup is configuration and stays inside the fixed price.

Can it handle manufacturer survey scores too?

Monitoring covers the surfaces you actually appear on, and we confirm which are worth watching for your franchise rather than assuming. Some survey platforms allow no automated access at all, and where that is true we will tell you rather than pretend.

Will it text customers about their MOT?

If they opted in, yes, and consent is checked before every send. If your DMS holds no clear record of consent, that is a finding in itself and worth fixing before any campaign runs.

What about the sales team posting their own stock?

They can keep doing it. The social team plans and drafts the branch feed; it is not there to stop a salesperson posting a car they are proud of.

Start with half an hour.

We'll tell you whether an assessment would pay for itself in an operation like yours. Sometimes the answer is no.