How to design your sales process in a CRM: a Pipedrive guide for SME owners

Start from your team's actual sales steps, not from the default pipeline. Before you edit anything, check one assumption: many B2B distributors quote from a price list before writing a formal proposal, and a pipeline that places Proposal before Quote bakes the wrong order into the setup. If your trial's default order does that, change it — don't adapt your team to the software.

This guide gives you a seven-step method to define a 4–7 stage pipeline, choose only the deal fields that drive a decision, and set up two or three automations that remove repeated admin. It ends with a worksheet and a worked B2B distribution example. The 4–7 stage range, the field rule, the two-to-three automation starting point, and the custom-development threshold below form a professional decision framework for SME owners — they are not a measured optimum from Niro Digital's own sales data. Niro Digital describes this blog as field notes on AI automation, custom software, recruiting advertising, and lead generation — written from the work we ship for clients, not from a content calendar.

The quickest way to a pipeline nobody uses is to accept the vendor's defaults. Replace that with a one-hour exercise: ask each salesperson to write the steps a deal actually goes through on separate cards, then order the cards as the work happens. Include the steps that feel messy — the internal handover, the re-quote, the credit check — because they are where the CRM either helps or gets abandoned.

In Pipedrive, each pipeline stage represents a step a deal goes through before it is won or lost, and Pipedrive defines a well-structured pipeline as one that helps track progress, forecast revenue and identify bottlenecks. Pipedrive's own guidance is to list each major step a deal actually goes through and use those as your stages, with "clear and action-oriented" names such as "Meeting scheduled" or "Proposal sent" instead of broad labels like "In progress." Pipedrive's documentation also warns that too many stages make the pipeline harder to scan and reduce adoption and recommends fewer stages; the source we reviewed was cut off before the specific recommended number, so we won't put a number in your mouth. Keep the range at 4–7 stages as a working rule, not a law.

The default order trap: Proposal before Quote

Pipedrive ships with a default sales process (found in the deals tab under pipeline view), which can be edited or replaced; only users with deal admin permissions can set up or edit a pipeline. That default is generic and can get the order wrong for a distributor. In the illustrative B2B distribution workflow used in this guide, the team sends a price-list quote before a formal proposal. The worked example later in this guide places "Quote sent" before "Proposal sent." If your current pipeline has the two reversed, fix that: a stage order that contradicts how you sell is a reason your team stops logging deals.

A pipeline that keeps every stage at 100% reports a number you can't use to plan. Each stage carries a configurable stage probability (the likelihood the deal is won by its expected close date, defaulting to 100% unless changed); a per-deal probability can override the stage probability, and Pipedrive automatically calculates weighted value from the probability. Here, weighted value means a deal's value multiplied by its chance of closing, so an early enquiry at €10,000 with a 10% probability contributes €1,000 to your forecast, not €10,000.

Set each stage probability from your own close-rate history, not from optimism. Then check the pipeline summary box, which reports four metrics — Total value, Number of deals, Value by currency, and Weighted total value (adjusted by stage or deal probability) — and filters let you restrict which deals are included in the totals. If the weighted total nearly equals the total value at every stage, the probabilities were never changed. The fix is one visit to stage settings and a few honest numbers.

The field set is where CRM adoption is won or lost. Every extra required field is a small tax your salespeople pay on every deal. Our rule for SME teams is this: add a custom field only if it drives a decision, a required gate, or a report; use Pipedrive's required-fields feature for stage-specific gates (for example, "Proposal sent") and let "important" fields stay optional context. This is a decision framework, not a measured optimum — it will not tell you which specific fields your business needs.

Before you set required fields, decide which record each piece of information belongs on. Our placement rule: permanent company information belongs on the organisation record, permanent individual contact information on the person record, opportunity-specific commercial information on the deal, and dated next actions in activities. Apply this to the Step 7 worksheet: company name and product category on the organisation; contact person on the linked person record; quote/proposal numbers, requirement summary, revision count and agreed margin on the deal; follow-up dates and handover checklist in activities. Annotate each example field with its record type, so the deal's required fields stay commercial.

First, know what you can and can't change. All Pipedrive items (leads, deals, people, organizations, activities, products, projects) share a structure of default, system and custom fields; default fields cannot be deleted and their names and types cannot be edited, though their visibility can be changed. Creating, editing or deleting custom fields requires the correct global permissions, and custom fields exist so companies can store, organise, filter and manage the information that matters to their own sales process.

Required fields are where you enforce a gate. The required-fields feature lets admins block saving or stage movement: users "won't be able to add or edit new items or move deals until the required fields have been filled in"; it is documented as available on Professional and higher plans — an old plan name. For deal- and lead-type fields, the required rule can be scoped per pipeline and per stage (e.g., a field required only in the "Proposal sent" stage); person, organization and product-type fields are documented as always required and cannot be scoped this way. Pipedrive's Academy training distinguishes required fields (must be filled; set by admins; can vary by pipeline or stage) from important fields (add context and prompt completion but are not mandatory), shown with colour indicators in the deal detail view.

Watch the plan ceiling. Under the old plan tiers (superseded 2025-09-30): Essential 30, Advanced 100, Professional 300, Power 500, Enterprise 1,000 custom fields per company. Current limits on the new tiers were not captured in this run, so check the actual number in your own account before designing around an old tier. The field rule keeps you well under any ceiling if you apply it honestly.

Quotes don't move in a straight line: a buyer asks for a revised quote, then a discount, then a different delivery date. The clean way to model that is to keep the deal in one pipeline. A deal can exist in only one pipeline at a time, and the product allows creating multiple pipelines to reflect different sales processes in the same account. That second half can tempt you into building a separate "negotiation" pipeline — don't.

To handle quote and negotiation loops that do not follow a straight line, keep the deal in a single pipeline (Pipedrive allows a deal in only one pipeline at a time) and model each revision as a stage or as a dated follow-up activity, rather than creating parallel pipelines. For a re-quote, either move the deal back into a "Quote sent" revision stage or create a dated follow-up activity when the quote is sent. If the loop genuinely cannot live in one pipeline, that is an early signal for the custom-development threshold in Step 6. You can read more about that alternative in our Custom CRMs page.

A Pipedrive automation is exactly two parts — a trigger event ("if") and an action event ("then"); triggers can be the creation, update or deletion of a person, organization, activity or deal, or a date trigger such as a contract renewal or event deadline. That trigger/action model is enough to remove repeated admin without making the CRM feel like a robot sending things on your behalf.

Start with the automation Pipedrive itself recommends: scheduling an activity when a deal moves to a specific stage. Pipedrive's own example of a worthwhile automation is "scheduling an activity when a deal moves to a specific stage", framed as replacing repeated administrative tasks so sellers can focus on selling. From there, pick two or three that remove real annoyance. Start automation where it removes repeated admin: for example, schedule an activity when a deal moves to a specific stage (Pipedrive's own example), and keep irreversible or client-facing actions behind a human approval gate.

Know your plan's ceiling before enabling many. Active-automation limits per company on the new plan tiers: Growth 50, Premium 150, Ultimate 250; deactivated automations do not count; if the limit is reached, "some automations may stop running, fail to complete actions or ignore new executions". Under the old plan tiers (superseded 2025-09-30): automation limits per company were Advanced 50, Professional 100, Power 150, Enterprise 250, and if/else conditions per automation were capped at Advanced 1, Professional 5, Power 10, Enterprise 20. The history matters only because tutorials still cite the old numbers.

Niro Digital's published automation doctrine puts the same boundary in stronger terms: "We never trust model output blindly. Every automation ships with deterministic verification checks, budget ceilings, and human approval gates for irreversible actions. We build systems where AI output is treated as a claim that must pass checks before it counts as done." Apply the plain-reading version here: if an action sends something to a customer or can't be undone, don't automate it — make it a task a human approves. If you want to go beyond Pipedrive's native trigger/action model, our AI Automation service covers supervised agent systems with verification gates. Check the Automation overview dashboard (account menu → Tools and apps → Automations → Overview) for automation health, most failed automations, most active automations and automations with no executions, over today / last 7 / last 14 days; global admins see company-wide activity, regular users only their own. This is where you notice an automation silently ignored.

The honest threshold is a professional judgement, not a benchmark: as an inference from Pipedrive's documented constraints, off-the-shelf CRM configuration is likely sufficient when your process fits within Pipedrive's supported pipelines, stage counts, custom-field limits, and automation limits. Custom development earns its cost when the process needs non-linear quote/negotiation loops, per-stage required fields, or automation behaviours that the current plan limits do not support. Read that sentence twice — the limits you met in Steps 2, 3 and 5 are the boundary, not abstract preferences.

To be clear what configuration gets you out of the box: on all four new plan tiers (Lite, Growth, Premium, Ultimate) the documented feature set includes customizable pipelines, custom fields, deal-card customization, deal rotting, data import/export, merge-duplicate-data, the leads inbox, and the products catalog. If your process lives within those features and the plan limits, keep configuring. If it doesn't, custom development is the legitimate option.

Niro Digital is a digital agency founded in late 2023, registered in Croatia and serving primarily the Slovenian market — never describe it as a Slovenian company. Its four main services, in the site's own order, are AI automation, custom software development, recruiting advertising, and lead generation advertising. Custom software development — CRMs, dashboards, employee tools, logistics systems shaped around how the business actually works — is one of those four. The agency's published value Radical Transparency states: "You own your ad accounts and your code." That values statement is the reason this guide tells you not to buy bespoke software when configuration solves the problem. If you do go custom, published indicative ranges live on the pricing page, and a deeper look at the service is on the Custom Software Development page. We won't quote a price here because the right number depends on your actual process.

Before you copy the table, one placement rule decides where each field lives: permanent company information belongs on the organisation record, permanent individual contact information on the person record, opportunity-specific commercial information on the deal, and dated next actions in activities. Each example field below is annotated with the record type that should hold it.

Copy the table and replace the example rows with your team's steps. The example is an explicitly hypothetical template, not drawn from a Niro Digital CRM implementation, so replace it with your own steps. Set each probability from your own close rates; the numbers below are placeholders.

Once the table is filled in, test it for one day with one or two salespeople: log real deals, move them, and watch where the fields or stages feel wrong. Pipedrive's pipeline can be edited or replaced, so don't over-engineer day one — leave the worksheet somewhere you can return to when the process changes. If you want evidence of real custom CRM work before making a bigger decision, the Projects page shows published case studies.

That completes the task: you now have a pipeline draft, a short field list, and two or three automations to start with. If you'd like a second opinion on whether off-the-shelf configuration is enough for your team, bring the worksheet to an intro consultation and we'll review it with you before the trial ends.

Book an intro consultation about CRM implementation.