CRM examples: how teams actually use one

What counts as a CRM example?

A useful CRM example names the records, the stages and the document at the end; a screenshot shows none of that. People who search for CRM examples usually want one of two things. Some are early: which products exist, and roughly what each is for. Others already know what CRM is and want to see a process, with the records named, before committing a team to it. Vendors usually answer only the second question, and only with their own customers.

This page answers both. The five workflows come first, because a product name means nothing until you know which workflow you are buying it for; the products follow, with no ranking and no prices. The workflows are illustrative: composites of how sales teams commonly work, not Senitix CRM customer stories, so they carry no results and no figures. A number attached to an anonymous example is decoration.

Inbound lead to closed deal

This is the workflow every product in the category claims, which is exactly why it is worth writing down. The steps are the same everywhere. The differences are in the joins between them.

In records, the workflow is six steps.

• A request arrives (a web form, the sales inbox, a phone call, a badge scan at a trade show) and becomes a lead with its source recorded.
• Someone qualifies it: is there a real organization, a real need, somebody who can sign, and a date the customer is working toward?
• Qualified, the lead becomes three linked records: an account for the organization, a contact for the person, and a deal for the possible sale.
• The deal sits on a pipeline whose stages are named after observable events. “Demo booked” means there is a meeting in a calendar. “Proposal sent” means a priced document reached the customer.
• Calls, meetings and email land on the deal as they happen, because the mailbox is connected rather than copied from.
• It closes won or lost, and a loss carries a reason picked from a short list, so the reasons can be counted later.

Two things usually go wrong here, and both are configuration rather than software. Stages get named after internal feelings (“warm,” “interested”), so nobody can say what has to happen for a deal to leave one. And a request sits unowned, because nobody was told it arrived. In Senitix CRM, an automation can set the owner the moment a lead is created, either a named rep or spread across the team; on plans with no automations, someone sets it by hand. Dedicated assignment rules, such as routing by territory, are coming soon.

The tool that runs it: any sales CRM with a lead record, a deal pipeline and two-way mailbox sync. Nearly all of them qualify, so judge them on how many clicks the conversion takes, and on whether an email you sent from your own mail client reaches the record without help. In Senitix CRM, Gmail, Google Calendar, Microsoft Outlook, Microsoft Calendar and any IMAP/SMTP mailbox can be connected, so mail sent from your own client reaches the record; web forms that create the lead directly are coming soon.

Quote to invoice

The moment a price is written down is where CRMs stop resembling each other. Up to that point most of them are a list of deals with notes attached. After it, they are either a system that produces the commercial document or a system that hands the job to a spreadsheet.

The deal reaches the point where the customer wants a number. Line items come from a product catalog rather than being typed, with quantities, a discount and a validity date. The customer asks for two items to be removed: that produces a second version of the quote, not an edit to the first, so both are on the record when somebody asks later what was originally offered. A discount past an agreed threshold routes for approval before it is sent. The approved quote goes out as a PDF. When the deal is won, the quote becomes a contract or an order, and the order becomes an invoice, with the line items traveling rather than being retyped.

In Senitix CRM, a quote keeps numbered versions with a PDF, and approvals, contracts, orders and invoices follow from it; plan details are on the pricing page. The honest gap: saved email templates for the covering message are coming soon, so that message is written each time. Senitix AI can draft it from the record, but a template you save and reuse is not there yet.

The tool that runs it: a CRM that carries products and prices into a document and keeps that document versioned. A pipeline tool with a quoting add-on and a system that owns the whole chain behave very differently on the day a customer asks for a revision, so test this one with your own price list. What to check in quoting, approvals and the documents that follow them is covered in CRM features.

Renewal and repeat purchase

Nobody submits an inquiry for a renewal. A date does. A support contract, a service plan, an annual license, a maintenance agreement: the work starts because a field is approaching, which makes this the first workflow a CRM has to begin on its own.

The second pipeline is the part teams skip and then regret. Renewal stages are not new-business stages. “Qualification” is meaningless for a customer you already have; the stage that matters is the one where somebody has said they are reviewing alternatives. Running both motions through one set of stages produces a board nobody trusts, and a forecast that mixes two very different probabilities.

In records, it is four things.

• The account or the contract record carries the end date as a field, not as a note.
• An automation raises a task ahead of that date, assigned to whoever owns the account.
• The renewal opens as a deal on its own pipeline, separate from new business.
• One report answers one question every month: what is due next quarter, and which of it is at risk.

The tool that runs it: a CRM that runs more than one pipeline and can automate against a date field. Plenty of entry-level products give you one pipeline and stop, which is fine right up until the second motion arrives: check before you commit, not after. In Senitix CRM, a team can run several pipelines, each with its own stages, and a date-based automation can open the renewal task before the date arrives. The habits that keep a renewal board honest are covered in CRM best practices.

Dealer and channel orders

Manufacturers and wholesale distributors rarely sell one deal at a time to a stranger. They sell again and again to known dealers, resellers and contractors, each on its own discount tier, and the record shape changes accordingly.

The dealer is an account, with an ordering contact attached and a tier that decides price. Orders repeat, so the pipeline is short and largely administrative: requested, priced, confirmed, shipped, invoiced. The catalog and the tier produce the price, which means nobody is quoting from memory. Documents (the order confirmation, the packing slip, the signed dealer agreement) sit on the account rather than in somebody’s folder.

The complication is that the order is often placed somewhere else: a portal, a spreadsheet emailed in, or the ERP the finance team already runs. At that point this stops being a CRM question and becomes an integration one. Two facts are worth having before you design it: in Senitix CRM, that bridge runs through a connected app Senitix registers rather than a self-serve API a developer signs up for and calls directly, so it starts as a conversation about the specific integration, not a read of the API docs; and outgoing webhooks are coming soon. CRM integration covers sync direction, matching keys and the rest.

The tool that runs it: a CRM with a product catalog and price books, a short second pipeline or an order record, and an integration path your ERP can actually use. In Senitix CRM, a dealer tier can be its own price book, and an accepted quote continues into a standard order record; volume discount schedules and customer-specific contracted prices are not available yet. One rule outranks the software: both systems have to agree on which record is the dealer, or the discount tier drifts and nobody notices until a credit memo goes out. The same motion is set out sector by sector on CRM for wholesale distributors and CRM for manufacturers.

Applicant intake

A partner or reseller program application, a membership application at a trade association, enrollment in a paid training program, a new vendor being onboarded. None of these is a sale, and all of them are the same shape as one: a person or a company arrives, is assessed against criteria, moves through stages, and is either accepted or not.

The applicant is a lead with the program as a field on it. The stages are renamed to the process (inquiry, application started, documents received, interview, decision, onboarded), and the vocabulary above them has to move with them, because a team that reads “deal value” on an applicant record stops trusting the screen. Documents live on the record: the application itself, a W-9 or a certificate of insurance, the signed agreement. Consent is a field rather than an assumption, because follow-up calls and email are regulated, in the US by the TCPA and CAN-SPAM, among other rules.

The tool that runs it: a general CRM whose stages, fields and labels you can rename out of sales vocabulary, with document storage on the record. In Senitix CRM, files attach to any record, and custom fields and custom objects carry the vocabulary the process needs; web forms that would let an applicant start the record themselves are coming soon. Purpose-built partner-portal and membership products arrive already fitted; the trade is that a fitted product resists being bent when the process changes, which it will.

The five workflows side by side

Read down the last column: it is a shortlist of trial tasks, more useful than any feature comparison, because each row is something a product either does or visibly does not. Read down the middle column and you get the other lesson: all five sit on the same handful of record types, so the CRM database underneath them barely changes.

Workflow	Records it runs on	The question that decides the tool
Inbound lead to closed deal	Lead, account, contact, deal, activities, email	Does an email you sent reach the record without anyone copying it there?
Quote to invoice	Deal, product catalog, quote versions, approval, order, invoice	Does a revision create a version, or overwrite the first quote?
Renewal and repeat purchase	Account, a second pipeline, a date field, automation, reports	Can you run more than one pipeline, and automate against a date?
Dealer and channel orders	Account, contact, catalog and discount tier, a short order pipeline, API	Do both systems agree on which record is the dealer?
Applicant intake	Lead, renamed stages, documents, a consent field, custom object	Can the labels leave sales vocabulary behind entirely?

Examples of CRM software, without a ranking

The other half of this search wants product names. Here they are, without a ranking: a ranking from a vendor tells you about the vendor rather than about you. Each entry says what the product is built around and the first thing an evaluation should check. No prices: vendors change them on their own schedule, and a figure copied here would go stale without anyone noticing.

• Salesforce: built for complex enterprise sales, with deep customization and a large app marketplace. Check the implementation scope, and who will administer it a year in.
• HubSpot: sells marketing, sales and service as separate hubs on one platform, which suits teams consolidating all three. Check what each added hub and each extra seat costs at the size you will be.
• Zoho CRM: one part of a wide suite of business applications from the same vendor. Check cross-app licensing, and how much interface a rep has to learn.
• Pipedrive: built around a visual sales pipeline for sales-first teams. Check whether the workflows around the pipeline are included or sold as add-ons.
• Senitix CRM (ours): built for small and mid-size teams that want the pipeline, the quote and, in time, the contract, order and invoice on one record. Check which plan each capability starts on and whether anything you need is still labeled coming soon. It runs in a web browser, with no native mobile app yet.

Those five are not the whole category. Sector-specific products exist for real estate, construction, field service and many other trades; they arrive fitted, at the cost of bending later. Many teams also weigh a CRM against the accounting system they already own, which compares two different jobs: one keeps the ledger of billed work, the other the work not yet won. If you are running an actual shortlist rather than reading about one, how to choose the best CRM is the page for that.

How do you turn an example into your own setup?

Pick the one that costs you money today. Not the most interesting one: the one where work is currently going missing. Then write it out the way the sections above are written: which records exist, what has to be true before a stage advances, and what document comes out. That page is your configuration brief, and it beats any vendor’s onboarding checklist.

Then configure that workflow and nothing else. The second one goes in after the first is genuinely in use, which is later than anyone plans for. CRM implementation sets out the sequence; benefits of CRM is the page to send to whoever approves the budget; and if the shortlists you are reading lean on AI claims, AI CRM covers what a daily digest, a drafted email and a next-action suggestion really are. What Senitix CRM puts on one record, and what it does not yet, is set out on the product page, and what each plan includes is on plans and pricing.