A lead block for a car aggregator portal
The portal showed prices and sellers but did not accept leads. We added contact buttons, a leasing form, a "notify me when available" subscription, emails to sellers and a "Leads" section in the admin area. It went live 15 days after kickoff.
The problem
The portal collects offers from car dealerships in a single catalog: prices, trim levels, leasing programs. The reader finds a car but could not contact the seller directly from the portal. The owner wanted to turn the catalog into a source of leads for sellers, and paid ones at that: contact buttons should appear only for those who pay for placement.
Before
- The catalog is filled from a spreadsheet rather than by hand, and changes every day.
- Leads were accepted by a single simple form with no delivery: no email went to the seller.
- There was no way to pass a calculation request to leasing companies.
- A visitor who could not find the right trim in stock could only come back later.
- The admin area had neither a list of requests nor statistics by seller.
What we built
- Four ways to contact a paying seller: "Call" (with the phone number), "Request a call", "Send a message", "Book a test drive". Which buttons to show is determined by the spreadsheet: no address for a request type means no button. On a phone the buttons are separate; on a desktop they are gathered into a dropdown menu.
- A leasing calculation request for a specific program: the leasing company receives the car, the price and a sample calculation, and the seller learns about it without the client's personal data.
- A "notify me when available" subscription: the visitor leaves an email, confirms it via a link, and after the next catalog upload receives an email if the trim has come into stock. Unsubscribing takes one click.
- An email queue with retries when mail fails: emails are not lost, and every attempt is logged.
- A "Leads" section in the admin area: a list with filters, a request card (where it came from, the consent text, the status of each delivery), counters by seller, Excel export, and deletion of a request when consent is withdrawn.
- Spam protection: a hidden honeypot field, rate limits, and a check of form completion time.
- Data rules: a seller who is not in the latest upload is not shown in the card or emails, and no leads are sent for them. A lead records the price and the seller at the moment of the request.
- A switch: the block can be turned on with a single flag after checking. Until then the buttons are not visible on the site.
Before launch we ran an independent audit in four parts (code, specification, server, live site) and fixed what it found: the switch turned off only the buttons and not the intake of leads, the rate limit was not atomic, and the honeypot could be triggered by autofill.
Results
- The block is live in production; the client checked the buttons and wrote that everything worked.
- The seller receives a request by email with the car, the price at the moment of the request and the client's details.
- A visitor who did not find the right trim stays in touch through the subscription.
- The portal owner now has statistics of requests by seller: a basis for paid placement.
The client's name is withheld under NDA. Real names and details are shared at the brief.
A similar task?
Describe it briefly — within 1–2 days we'll come back with an analysis and an hourly estimate. If a packaged solution fits, we'll say so honestly.