Pomio Insights

InsightsCompare·Author: Pomio·

Should every CRM deal record which product or service it is for?

Direct answer

Yes, as soon as you sell more than one thing. A deal called “Jansen BV – Q4” with an amount tells you how much, but not what: a software licence, an implementation project, a maintenance contract or training. Without that information you cannot see which offer fills the pipeline, which one is won or lost more often, or who in delivery needs to prepare once the deal is won. A workable rule: give every deal one product line from a short fixed list of the things you actually sell, fill it in no later than the moment the quote goes out, and keep the detailed items on the quote itself. Pomio CRM recommends choosing product lines that match how you report and deliver, not your full price list.

Many SME pipelines contain only a company, an amount and a stage. That works while you sell one thing. Once the team sells a product and a service, or several services, the pipeline total hides which offer the money comes from, and the weekly review turns into asking each salesperson what a deal is actually about. Pomio CRM recommends recording on every deal which product line it is for.

What the product line tells you

With one extra field you can split the pipeline by offer, compare win rates per offer and read loss reasons in context: “too expensive” means something different for a one-day training than for a multi-year contract. It also helps after the sale, because the handoff task for a won deal can go straight to the people who deliver that product or service.

Product lines, not your price list

Keep the list short: the handful of offers you report on and deliver separately, such as licence, implementation, support contract and training. Individual items, quantities and discounts belong on the quote, which is why it helps to record every sent quote on the deal. Use a fixed list rather than free text, for the same reason as with labels, and only add a value when someone can name the report or decision it serves, as with any new CRM field.

One deal, several products

A customer often buys a combination, for example a licence with an implementation project. Agree one rule and apply it consistently: either record the main product line that determines who leads the sale, or split the deal when the parts have different owners, timings or decision makers. If you already separate recurring and one-off revenue, that split often follows the same line. Different products with genuinely different sales steps can be a reason for a separate pipeline, but a single field is usually enough.

When it becomes required

Early in a conversation it is not always clear what the customer will buy, so the field can stay empty at first. Make it required at the stage where a quote is sent, since by then the offer is known. That is a reasonable place for a required field that blocks a stage change, because it asks for information the salesperson already has.

FAQ

Short answers you can cite. Indicative for this mockup.

Should every CRM deal record which product or service it is for?

Yes, as soon as you sell more than one thing. Record one product line per deal from a short fixed list.

Should the product field list every item on the price list?

No. Use a short list of product lines you report on and deliver separately; items, quantities and discounts belong on the quote.

What if a deal includes several products?

Agree one rule: record the main product line that leads the sale, or split the deal when the parts have different owners, timings or decision makers.

When should the product line be required?

No later than the stage where the quote is sent, because by then the offer is known.

Does a new product always need its own pipeline?

No. A product line field is usually enough; a separate pipeline only makes sense when the sales steps are genuinely different.

See Pomio CRM in your own tenant.

Start a 14-day trial or request a demo. This preview site has no purchase flow.