Every customer who says "it only makes the noise sometimes" is a bug report with no repro steps. Good service advisors fix that by going on the test drive with them.
Founders, when's the last time you watched a user hit your bug live?
Your cancel flow shouldn't lead with a discount. It should ask "what did we miss?"
When a customer leaves a shop, the advisor who calls to ask that learns more than any coupon ever will. Do you actually read your churn reasons?
Still working on a missed-call text-back for service departments.
A lot of calls come in before 9 AM, before anyone is at the desk to pick up.
Shop folks: what would that text need to say so the customer waits for you instead of calling the next shop?
Hot take: vibe coding won't kill SaaS any more than YouTube killed mechanics.
Everyone can watch the brake job video.
Most people still pay someone to own it when it starts squealing again.
The most dangerous sentence at a service desk: "Oh, it's been doing that for a while."
The SaaS version is a customer saying "that's been broken for months."
It doesn't mean it's fine. It means they stopped telling you.
What's the free multipoint inspection of your SaaS?
The free thing you do that quietly creates most of your paid work.
At the dealership it costs the customer nothing, and it books more repairs than any ad we run.
@heyshrutimishra Approve or reject in 44ms is great until it's rejecting a warranty claim. In a service drive the decision was never the hard part. Explaining the "reject" to the person standing in front of you is. Who's building that half?
Your changelog is your service history.
People trust a used car with every oil change documented. Users trust a product that shows what got fixed and when.
Do you actually read changelogs before paying for a tool?
Hot take: the best SaaS onboarding is a walkaround.
At a dealership you walk the car with the customer before you touch it, so nobody's surprised later.
Most onboarding skips straight to handing over the keys.
What's the check engine light in your SaaS? The one number that tells you something's wrong before customers start complaining. In the service lane it's comebacks: the same car back within 30 days. What's yours?
Service advisor rule that works for SaaS support: never just say "it's fixed." Say what you found, what you did, and how they'll know it's working. Customers don't trust fixes. They trust explanations.
At the shop, the fastest way to earn trust is to show the customer the worn out brake pad.
What's the SaaS version of that? Changelogs? Before and after screenshots? Showing the bug you fixed?
What actually makes you trust a tool?
Every customer at my service desk says "just do whatever it needs." Then they see the estimate.
SaaS version: "we'd totally pay for this" on a discovery call, then silence at the pricing page.
Ask for the card before you build. Words are free. Estimates aren't.
@jasonlk The other 90% isn't a no, it's a wrong shop. Like asking a BMW dealer for a $40 oil change: nobody's wrong, the math just doesn't fit. Find the 10% whose math matches yours and stop arguing with the menu board.
@tdinh_me AI having taste is the easy part. Hearing "can you make the logo pop more" for the fourth time and still smiling while the invoice clears is the actual job. Your career's safe until it learns to nod politely.
Founders: what's the support ticket you get every single week that the product itself should have prevented?
In a service drive it's "the light came back on." What's the SaaS version?