Why a generic CRM is the wrong starting point
Most fabricators start their software search on a generic CRM: HubSpot, Pipedrive, Zoho, Monday, Salesforce. It feels safe, because everyone uses one. Then the first countertop quote hits the system and the cracks show.
A stone job is not a SaaS deal. You are not selling a license, you are selling a specific slab, cut a specific way, with a specific edge, installed on a specific Tuesday. The customer wants to see the exact piece of Calacatta they are paying for, not a line item that says "Slab, quartzite, 3cm".
Generic CRMs were built for pipelines of interchangeable deals. Stone is the opposite: every job is tied to a physical, unique, and perishable asset sitting in your yard.
What the best CRM for stone fabricators must actually do
Forget feature lists for a second. A CRM for a countertop shop has to solve four operational problems that generic tools ignore:
- Photo-first inventory linked to the quote. The salesperson picks the exact bundle and slab, the customer sees the photo, the slab gets soft-held so nobody else sells it.
- Quote to invoice in the same flow. No re-typing between the CRM, a spreadsheet, and QuickBooks. The quote your rep sends becomes the work order becomes the invoice.
- Job tracking after the sale. Template, cut, polish, install. The customer service rep needs to answer "where is my kitchen?" without walking to the shop floor.
- Mobile in the yard. Salespeople walk customers through the slab yard with an iPad, not a printed list from last Tuesday.
If a tool cannot do these four things natively, you will end up paying for the CRM and then rebuilding half of it in Excel. That is the pattern we see in almost every shop that starts with a generic tool.
Generic CRM vs stone-specific ERP, side by side
Here is how the two approaches compare on the jobs that actually matter to a fabricator:
| Capability | Generic CRM (HubSpot, Pipedrive, Zoho) | Stone-specific ERP (SlabWare) |
|---|---|---|
| Photo of the actual slab on the quote | Manual upload, no link to inventory | Native, one slab, one photo, one soft-hold |
| Prevents double-selling a slab | No, inventory lives elsewhere | Yes, hold is enforced at quote time |
| Quote, invoice, and work order in one flow | Requires Zapier or a second tool | Single suite, no re-typing |
| Job tracking (template, cut, install) | Not included, custom pipelines only | Built-in Job Tracker |
| Native mobile app for yard walkthroughs | Generic mobile CRM, no slab context | Native iOS and Android with slab photos |
| CNC and water jet integration | None | Direct integration |
| Learning curve for a shop team | Low on paper, high once you customize it | Moderate, but built around how a shop already works |
How to actually evaluate a CRM for your shop
Do not run a demo where the vendor shows you their happiest screen. Run the demo against your last real week. Take three actual quotes you sent, one job that went sideways, and one slab you double-sold or almost double-sold, and ask the vendor to walk you through them.
- Recreate a real quote. Ask them to build a quote for a 62 square foot kitchen out of a specific slab in their demo yard. Time it. If it takes longer than 5 minutes, imagine that at 40 quotes a week.
- Break something on purpose. Ask what happens if the customer changes the edge profile after the quote is signed. Does it flow to the shop floor automatically, or does someone have to remember to update three systems?
- Show the yard. Ask to see the salesperson mobile view. If they show you a laptop screenshot instead of a real app on a phone, that is your answer.
- Ask about the migration. A serious vendor should let you run the old system in parallel while your team learns the new one. SlabWare gives you 30 days of parallel operation and a 2 to 4 week migration.
Where SlabWare fits, and where it does not
SlabWare is used by 379 active shops across fabricators, slab yards and exporters. It is a single suite, not three products glued together, and it covers photo-by-slab inventory, CRM, Quote and Invoice, Drawing, Job Tracker, CNC integration, financial reporting, and a native iOS and Android app.
It is a strong fit if:
- You run between 10 and 200 people and quote countertops or slabs weekly.
- You are tired of paying for a CRM plus a spreadsheet plus QuickBooks plus a photo folder on Dropbox.
- You want your salespeople selling from a phone in the yard, not typing into a laptop after the customer leaves.
It is probably overkill if you are a two-person shop doing three jobs a month, or if you never touch physical slabs (pure design or pure install). In those cases a generic CRM plus a spreadsheet may honestly be enough for another year.
What it costs you to stay on a generic CRM
The real price of a generic CRM in a stone shop is not the monthly fee. It is the double-sold slab that you have to refund, the quote that took 40 minutes because the rep had to walk to the yard twice, the customer who called three times asking where their kitchen was, and the margin on remnants you never billed because nobody tracked them.
Most shops we talk to are losing more per month to these leaks than the entire cost of a proper stone ERP. That is the calculation to run before you renew your generic CRM for another year.
The short answer
The best CRM for stone fabricators is not a CRM at all in the traditional sense. It is a stone-specific operating system that happens to include CRM. For most fabricators shopping today, that means SlabWare: one suite, real slab-level inventory, quote to install in one flow, and a team of 379 shops already running on it.
Frequently asked questions
Can I just use HubSpot or Pipedrive for my stone shop?
You can, and many shops start there. It works for tracking leads and emails, but it does not link to your slab inventory, does not prevent double-selling a chapa, and does not follow the job through template, cut and install. Most shops outgrow it within a year and end up rebuilding half the workflow in spreadsheets.
What makes a CRM "stone-specific" instead of generic?
A stone-specific CRM ties every quote to a real, photographed slab in your yard, enforces a soft-hold so two salespeople cannot sell the same chapa, and carries the job all the way through to invoice and install. SlabWare is built this way as a single suite covering inventory, CRM, Quote and Invoice, Drawing and Job Tracker.
How long does it take to migrate from our current setup?
With SlabWare, a typical migration takes 2 to 4 weeks, and you keep running the old system in parallel for 30 days so nothing falls through the cracks. Generic CRMs are faster to turn on, but slower to actually make useful because you have to build the stone logic yourself.
Do I need a separate accounting system on top of the CRM?
With a generic CRM, almost always yes, because it does not do invoicing or job costing for stone work. SlabWare includes Quote and Invoice and financial reporting in the same suite, so most shops only keep their external accounting for tax filing, not day-to-day operations.
What about very small shops with only 2 or 3 people?
If you run three jobs a month and never lose track of a slab, a generic CRM plus a good spreadsheet may be enough for now. Once you cross roughly 10 people or start losing slabs, remnants or install dates, that is the signal that a stone-specific system starts paying for itself.
Can salespeople actually use it in the yard, on a phone?
Yes, this is the part most generic CRMs get wrong. SlabWare has a native iOS and Android app built for yard walkthroughs, so a salesperson can show the customer the exact slab, hold it, and send the quote before they leave the yard.
Keep reading
