A lot of B2B software origin stories follow the same arc: founder spots a market, talks to fifty potential customers, builds an MVP, lands a pilot, iterates. That arc works. It’s not how SalesThumb got started.
SalesThumb’s first customer was a window-tint and detail shop in Florida called Polar Tint. Polar Tint is owned by the same person who founded Roffik. The MVP didn’t get built in a vacuum and then sold — it got built because the shop’s existing tools were costing money every week, and the owner happened to also be a software builder.
That sequence — pain first, software second — turns out to matter a lot. It’s a different kind of advantage than market research can give you, and it shows up in the product in ways we’re still discovering.
The pain that started it
Before SalesThumb existed, Polar Tint ran the same stack a lot of shops run: a calendar app for booking, a separate notepad for quotes, texts for follow-ups, a spreadsheet for inventory, and a generic CRM the previous owner had set up and never quite finished configuring.
The CRM was the real problem. It was built for software sales teams. It had pipelines with stages like “Discovery Call” and “Proposal Sent.” Every time someone walked into the shop and asked “how much for ceramic on a 4Runner?”, the salesperson had to either ignore the CRM and write the quote on paper, or spend two minutes navigating a UI that wasn’t designed for the situation.
Two minutes per quote × twenty quotes a day × six salespeople × five days a week is fifty hours of labor per week burned on tool friction. The decision to build SalesThumb wasn’t “this is a good market opportunity.” It was “if I keep paying the friction tax for one more quarter, I’m going to lose my mind.”
What we built first
The first version of SalesThumb did three things: quote a job from the door (pull up a vehicle, pick a service, get a price — 20 seconds, not two minutes), convert quote to booking (same screen, no re-entry), and track the job through the bay (a pipeline that matched what shops actually do).
We launched it at Polar Tint and watched what happened. Within two weeks, the salespeople stopped using the old CRM entirely — not because anyone forced them to, but because SalesThumb was faster. Within a month, average ticket size went up about 11%. The cause was embarrassingly simple: when quoting takes 20 seconds, salespeople quote three tiers and let the customer pick. When it takes two minutes, they quote one tier (the cheap one) to avoid spending six minutes on every walk-in.
That single insight — the speed of the quote tool affects what gets quoted — has shaped almost every decision in the product since.
Three things it taught us about building for shops
1. Operator-built beats market-researched, by a lot
Every shop owner we’ve shown SalesThumb to has had the same reaction in the first 90 seconds: “this was built by someone who actually does this work.” The screen layouts match the order of operations of an actual shop. The fields in a quote map to the questions a customer actually asks. The pipeline stages match the physical flow of a vehicle through the bays. This is impossible to fake, and generic shop-management software has been pitched at this industry for fifteen years — shop owners can spot a tourist in the first thirty seconds.
2. The speed of a tool changes the behavior it enables
Shop tools aren’t just tools — they’re behavior shaping. A slow quoting tool causes salespeople to under-quote. A clunky booking tool causes front-desk staff to forget bookings. When you understand this, you stop optimizing for “feature completeness” and start optimizing for “what does the salesperson actually do during a real interaction with a customer.” That’s why SalesThumb’s quote-to-book screen is one screen, not a wizard.
3. The first customer’s complaints are the roadmap
Polar Tint complained about everything for the first two months — and almost every complaint shipped within four weeks. “I can’t see today’s bookings on the wall TV” → wall-display mode shipped. “I have to print quotes to hand to the customer” → email-quote-as-PDF shipped. “When a customer reschedules, I have to delete and re-book” → reschedule shipped. These complaints would have been absurd to prioritize via a survey. They’re the kind of thing operators grumble about while doing the work. The only way to hear them is to be in the room.
What’s next
SalesThumb is now on a small set of shops doing tint, detail, PPF, ceramic coating, and (soon) mobile work. The next big chunk is integrations — QuickBooks, Xero, Twilio-backed texting, and review tools (Birdeye, Podium, Google direct). After that: the recruiting, training, and quality-control side of the workflow.
If you run a shop in window film, detailing, PPF, or related work, we’re still small enough to have a real conversation about your stack. Reach out at roffik.com/contact. The earliest customers shape the product the most.
— Sean
