What a kitchen showroom CRM actually has to do

The deal closed three weeks ago. The client paid the deposit, the cabinets were ordered, everyone moved on. Then the client calls to ask when install is, and nobody can answer without digging through an email thread, a folder on someone's desk and a text from the rep.

The sale was tracked. The job wasn't.

Why doesn't a regular CRM fit a kitchen showroom?

Most CRMs are built around a deal that moves through sales stages and ends at "closed won". A kitchen job only begins there. After the signature come the spec sign-off, the deposit, supplier orders, acks, lead times, freight, delivery, install, the punch list and sometimes a remake. A sales CRM has no natural place for any of it.

You can see it in the defaults. HubSpot's default deal pipeline, for example, ends at closed won or closed lost. That's a sensible design for selling software or insurance, where the deal is the product.

In a showroom the deal is a promise. You've promised a door style, a finish, a delivery window and an install day, and you've promised them using cabinets you don't make, from a manufacturer whose ship date you don't control.

So a showroom bolts things on. A custom "Order Placed" stage. A notes field for the ack number. A spreadsheet beside the CRM for supplier balances. A whiteboard for install days. Within a year the CRM holds the leads and everything that actually costs money lives somewhere else. If that sounds familiar, running orders on a spreadsheet covers where that setup tends to crack.

What should a kitchen showroom CRM track on every job?

At minimum: the client, the address, the spec (line, door style, finish, box construction), the sale price, the deposit received, each supplier order with its cost, the ack, the promised ship date, the delivery date, the install date, who owns the job, and the open punch list items. If any of those live outside the system, someone will lose them.

Here's the field list we'd want on every order. Not all of it at once on day one, but all of it by install day.

A sales CRM will happily store some of this as custom fields. The trouble is the supplier rows. One job, four vendors, each with its own cost, payments and balance. That's a list inside a record, and deal-based tools usually aren't set up that way out of the box.

Which job statuses does a kitchen showroom need?

You need statuses that describe where the job physically is, not how likely it is to close. A workable set: New, In Progress (designing and quoting), Order Placed, HOLD, Delivered, Installed, Complete, and Cancelled. HOLD matters more than people expect, because jobs stall on permits, a client's other trades or a backorder.

A few notes on that list.

Order Placed should mean the order is in with the manufacturer, not "the client said yes". Those are weeks apart sometimes.

HOLD is for anything waiting on something outside your control. Put the reason in the job, not in your head.

Installed and Complete are different. Installed means the boxes are on the wall. Complete means the punch list is closed and the balance is paid. It's easy for a job to sit at "installed" for months with one door outstanding and a final payment nobody chased.

Seven or eight statuses is enough. Twenty is a sign someone's using statuses as a to-do list.

How should supplier orders sit inside a job?

Each job needs its own list of supplier orders: who it's from, what was ordered, the cost, what you've paid that supplier and what you still owe. This is what tells you the job's real margin and how much cash is about to go out. Without it, you find out what a job made months after it's done.

Here's a worked example. Say the job sells for $38,000 and has three suppliers.

So the job carries $17,560 over material cost ($38,000 minus $20,440), which is about 46% before your own install labor. And there's $12,700 still to pay out. If the client's balance is due on delivery, you want to know that the fabricator bill and the second cabinet payment land in the same few weeks.

Now multiply by twenty open jobs. That's the number an owner needs on Monday morning, and a deal pipeline won't produce it. The deposit and payment schedule guide goes into how to line client payments up against supplier payments.

Who owns what on a kitchen job?

Every stage needs one named person. In a small showroom one person might own several stages, which is fine, as long as it's written down. The usual gap is the handoff between the designer who sold the job and whoever schedules delivery and install.

If your current software can't show "jobs owned by Maria that are past ship date", you're tracking this in someone's memory.

What should you ask in a kitchen showroom software demo?

Skip the dashboard tour. Bring a real job from last year, ideally a messy one with a change order and a backorder, and ask the vendor to enter it while you watch. How the software handles that one job tells you more than any feature list.

Questions worth asking:

1. Can I add my own fields (cabinet line, door style, finish) myself, or does that take a consultant?
2. Show me one job with three suppliers. Where do I see what I owe each one?
3. Where does the ack go, and how do I mark it as checked?
4. Show me every job delivering in the next two weeks on a calendar.
5. A door arrives damaged after install. How do I log the replacement without opening a whole new job?
6. Can my installer use it on a phone at the job site?
7. Can I see profit and cash owed across all jobs for last quarter?
8. Who imports my current spreadsheet, and what does that cost?

And ask what it costs with your real headcount, including the person who only logs in twice a week.

What are the red flags in kitchen and bath showroom software?

The biggest one is a pipeline that ends at "won" with no real model of the job after it. Close behind: needing paid setup to add a field, supplier costs that live only in an accounting export, no calendar for delivery and install, and per-seat pricing that punishes you for giving the installer a login.

Others we'd watch for:

• The demo is all lead capture and email campaigns. Showrooms mostly don't lose money on lead capture. They lose it between order and install.
• "Integrates with everything" but can't show a single job end to end.
• Long contracts or an annual commitment before you've run a real job through it.
• No way to attach the ack and drawings to the order itself.
• It wants to replace your design software. If you design in 2020 or ProKitchen, keep it. The 2020 Design page covers what that side of the business does and doesn't handle.

So what's the best CRM for a kitchen showroom?

The best one is whichever runs the job after the signature without a second spreadsheet next to it. For a showroom doing a few jobs a month, a general CRM can work if you're disciplined. Past ten or fifteen open jobs, you want software built around orders, suppliers and install dates. Test it with a real job.

There's no single right answer here, and this comparison of showroom software by job lays out what the common tools are actually built for.

We built Salone for this exact gap. Each order has your own fields, a row per supplier with cost and balance owed, delivery and install dates on a shared calendar, and a status board from New to Complete. It doesn't draw kitchens or order from manufacturers for you. It keeps track of the job once you have.

The checklist above works no matter what you pick, though. Before you buy anything, take your three most recent jobs and try to fill in every field in that first table. Wherever you can't, that's what your next system has to fix.