Perfect Fit Auto Parts

Perfect Fit Auto Parts sells genuine and aftermarket car parts across the United States. Most orders start with a phone call. The buyer gives the year, make and model, a specialist checks the exact fit, and the part ships to their door.

So the business needed two things. A website that turns a search into a call or a part request. And a system where the team can answer that call, follow up and take payment without losing anyone.

The website

We designed and built perfectfitautoparts.us. Every button leads to a call or a part request. Nothing sends the buyer away to another shop.

• Pages written from the catalogue. A script reads the parts list and writes a page for each category, each make, and each make with each category. Every page shows real parts, a short buying guide and common questions. Add parts to the list and the next build adds the pages.
• Request a part. A short form for the phone number, the vehicle and the part. A VIN box fills in the vehicle when the buyer has one. The form also carries the text message consent the phone carriers ask for.
• Guides. Articles on choosing a headlight, spotting a failing alternator and knowing when to change brake pads. They answer what buyers search before they buy.
• Ready for search. Clean titles, a sitemap, and structured data for the store, the parts, the breadcrumbs and the questions.

Stack: static pages generated with Node.js from the parts catalogue, hosted on Cloudflare Pages.

Screenshots of the live site, October 2026. Visit perfectfitautoparts.us.

The sales CRM

Every call, text and payment lands in one place. An agent opens a customer and sees the whole story before they speak.

• Leads and callbacks. Each enquiry has an owner, a status and a next step. Callbacks come up when they are due. An agent cannot close or change a sale that belongs to another agent.
• Calls through Dialpad. Click a number to ring the customer from the agent's own Dialpad, and choose which company number shows. When a customer calls in, every agent sees a banner and one taps to take it. After the call, the recording and the summary sit on the call log.
• Texts with photos. Two way text messages through Twilio. Customers often send a photo of the part they need, and it arrives in the same thread. A guard stops the same message going to the same person twice.
• Card payments, kept safe. The team can send a payment link by text, or take a card over the phone in a Stripe or Square card field. The card number goes straight to the payment company. The CRM keeps only the card brand and the last four digits.
• Plain help on a decline. When a card is declined, the CRM says why in plain words and tells the agent not to retry straight away.
• Part Finder. Pick the year, make, model, trim and engine, then type the part or the part number. The finder shows live listings with photos, so the agent can quote while the customer is still on the line. A VIN can be decoded too.
• Old customers brought over. We moved an older customer book into the CRM, graded each contact, and marked the people who must not be contacted.

Stack: a plain JavaScript front end with Netlify Functions and Netlify Blobs, joined to Dialpad, Twilio, Stripe and Square.

The CRM is private to the sales team, so there is no public link.

Search and ads

The catalogue pages give a search for a part and a car somewhere to land. Calls from the website are tracked in Google Ads, so the budget can follow what brings calls. We also made the product films for the brand's YouTube channel. See them on the work page.

What this means for your business

If you sell by phone, the website should bring calls and the CRM should make sure each one is answered and followed up. We build both, and join them to your phone line, your texts and your payments.

Message us on WhatsApp at +92 323 2802832 with what you sell and how you sell it. See our website design and WhatsApp and CRM pages, or the PMC Parts case study.