Automotive and compliance · Operational Leverage Systems
A fixed regulatory deadline, met across every location
The operator
A multi-location dealership operator needed to satisfy a new regulatory requirement across every store by a fixed date. The operator knew exactly how the sales process worked in practice, including the steps staff would skip under pressure.
What stood in the way
The requirement applied to live transactions across several locations. A partial solution would have created audit exposure rather than reducing it, and the deadline could not move.
Why the obvious fix would have failed
No vendor product matched the process the group actually ran. A manual procedure would have depended on consistent behavior at the busiest moment of the sale, which is precisely where consistency fails.
What changed the approach
Compliance had to become a byproduct of the existing workflow rather than an extra step. That meant instrumenting the systems staff already used and recording evidence automatically.
What Was Built
The system
Production middleware integrated with the systems already in use across locations
Automatic, audit-traceable logging of every relevant transaction
Exception handling and escalation for cases requiring a human decision
Monitoring and alerting suited to a regulated process
System architecture
Inbound Webhook Events
CRM events and dealership consent directives received via authenticated endpoints
Transactional Outbox
- ▪All events persisted to PostgreSQL before delivery
- ▪Decouples ingestion from downstream delivery
- ▪Guarantees zero data loss under degraded conditions
Cron-Driven Processor
Claims pending entries on a short interval, in configurable batches with exponential backoff retry
Tag-Based Location Routing
Contact tags restrict routing using an intersection model, which prevents over-routing to unintended locations
Bidirectional Sync
- ▪Consent events fanned out to dealership locations
- ▪Inbound Do Not Contact directives from AWS SNS signature-verified
- ▪DNC flags written back to GHL contacts in real time
Transactional outbox pattern ensures zero data loss under degraded conditions across both integration directions.
The outcome
What changed for the business.
Compliance evidence produced without adding steps for front-line staff
Audit questions answerable from system records rather than recollection
Consistent handling across locations rather than store-by-store variation
How it holds up
- Middleware deployed to production across all in-scope locations inside the regulatory window
- Full transaction logging with an auditable trail
- Automated handling of the volume the group processes in normal operation
On the business result
This engagement did not include a measured revenue or margin outcome, so we do not state one. The operating change above is documented.
Figures from this engagement are with the partner for verification and written approval. We do not publish them before that is complete, even when we have them internally.
Our Role
What PillarTek was accountable for.
More Work
Other engagements.
Recognize your own constraint here?
Tell us what you are running into. We will be direct about whether this experience transfers to your situation.