← The journalSALES / FIELD GUIDE

Why your CRM belongs inside your ERP

When leads, quotations, orders and invoices share one record, sales stops guessing about stock, credit and margin.

Pedestrians in Shibuya with directional camera-motion blur.SALES / SUNDIAL
Photography: Ayumi Kubo / Unsplash ↗ · Sundial motion treatment
THE PRACTICAL TAKEAWAY

A CRM that cannot see stock, credit and invoices gives sales half the picture. Put the pipeline on the same record as the order.

The problem with a separate CRM

Most growing companies buy a CRM first and an ERP later, or the other way round, and then spend years connecting them. The sales team lives in one tool, finance and operations live in another, and a sync job sits in the middle copying customers, products and prices back and forth.

That sync job is where the trouble starts. A customer's address is updated in the CRM but not in the ERP, so the invoice goes to the old office. A salesperson quotes a product that was discontinued last month because the item list in the CRM is a copy from the previous quarter. A deal is marked won, but nobody can see that the customer has three overdue invoices until the order is already being picked.

None of these are dramatic failures. They are small daily costs: a phone call to finance, a revised quotation, an apology to a customer. Over a year they add up to a sales team that does not fully trust its own numbers.

What changes when the CRM is part of the ERP

In Sundial's Sales & CRM module, the lead, the opportunity, the quotation, the sales order, the delivery and the invoice are records in the same database. There is no copy of the customer and no copy of the item master. When something changes, everyone sees the same change.

In practice, that gives a salesperson answers that a standalone CRM cannot give without an integration project:

  • Can we deliver? The quotation shows the stock available in each warehouse and what is already committed to other orders.
  • Can they pay? The customer record shows outstanding receivables, overdue amounts and the credit limit set by finance.
  • Is this deal any good? Item prices, pricing rules and valuation rates sit next to each other, so the margin on a quotation is visible before it is sent.
  • What did they buy last time? Past orders, returns and support issues are on the customer record, not in someone's inbox.

The pipeline becomes a forecast you can plan against

When opportunities live in the ERP, the pipeline stops being a sales-only report. Operations can see which items appear in late-stage opportunities and decide whether to build or buy ahead. Finance can see expected order values alongside confirmed orders and receivables, and shape the cash view accordingly.

This only works if the pipeline is honest. A few habits help:

  • Record the items and quantities on the opportunity, not just a deal value. A number without items cannot inform purchasing or production.
  • Use a small number of clear stages with written exit criteria, so "proposal sent" means the same thing for every salesperson.
  • Close lost opportunities with a reason. Over time, lost reasons tell you more about pricing and lead times than any survey.

From won deal to order without retyping

The moment a quotation is accepted, it becomes a sales order with one action. Customer, items, prices, taxes, payment terms and delivery dates carry over exactly as agreed. From there, the order drives the rest of the flow: a pick list for the warehouse, a work order if the item is made to order, a delivery note when it ships and an invoice when it is billed.

Because each step is linked to the one before it, you can open any invoice and trace it back to the quotation and the original lead. When a customer disputes a price, the answer is two clicks away instead of a search through email threads.

Contracts, renewals and repeat business

Many businesses earn most of their revenue from customers they already have. Keeping contracts, recurring orders and support history in the same system as sales makes renewal work far more practical. A salesperson preparing for a renewal can see what the customer bought, what they returned, which support issues they raised and whether invoices were paid on time.

That context changes the conversation. Instead of starting with a discount, the team can start with what went well, what went wrong and what the customer needs next year.

What to check before you move your CRM

Moving sales into the ERP is not free. Salespeople are used to a tool built only for them, and an ERP that feels heavy will be ignored. Before you switch, check a few things:

  • Can a salesperson log a call, update a stage and create a quotation from a phone in under a minute? Sundial's workspace is designed for exactly this, on desktop and phone.
  • Can you set permissions so sales sees credit status and stock but not cost prices or payroll? Role-based access is part of the platform.
  • Can you import open leads and opportunities with their history, not just a contact list?

We are also building Sundial so that routine pipeline work can be handed to an AI agent: drafting a follow-up after a quotation goes quiet, or flagging opportunities whose items are short on stock, with a person approving every step. That is the direction of the product; the foundation is having one record to work from.

Where to start

Start with the flow from quotation to invoice, because that is where the separate-system cost is highest. Bring in customers, items and price lists first, then open opportunities, then historical orders. Once the team quotes from the same place finance invoices from, the case for keeping a separate CRM tends to disappear on its own.

If you want to see how it feels, try the demo with sample data for Kestrel Workspace, or talk to us about your current setup.