A CRM works by tying customer requests and conversations to a shared record. When a request comes in, someone opens a lead record. As the lead is qualified it becomes an opportunity. The team prepares a quote for that opportunity and an accepted quote turns into a sale. After the sale, follow-up continues on the customer card. The pipeline and reports a manager sees are the sum of those records.

That is why "how do you use a CRM" is mostly a question of habit: reps update the record after every contact and managers review those records once a week to make decisions. For a definition of CRM, see What is CRM?; for what a CRM does and how it differs from ERP, see CRM vs ERP. Below you will find the three things every record needs and the path a request takes from first record to post-sale follow-up, then how the team uses the system each day and the manager each week, the first weeks of setup and the most common mistakes.

1. How a CRM works: owner, status and next step

In a CRM, the unit of work is the record. Leads, customers, opportunities, quotes, sales and appointments are separate record types that link to each other: under a customer card you can see the opportunities opened with that customer, the quotes sent and the sales closed. The system becomes useful when every open record answers the questions below.

  • Owner: Who is handling this record? A request with no clear owner is one everyone sees and nobody calls.
  • Status: What stage is the record waiting in? When every status means the same thing to everyone, lists like "waiting on a quote" or "to call this week" become reliable.
  • Next step: What happens next and when? This lives on the record as a dated reminder or task.

Reports feed on these same fields. If a rep never logged a call, the manager cannot see it in a report; if nobody updated the status, the pipeline shows last month's picture. How much value you get from a CRM depends on your team's logging habits as much as on the software's features.

In XON CRM, each of these record types has its own module: leads live in Lead Management, customer cards in Contact Management and revenue-bearing deals in Opportunity Management. Notes, reminders, tasks and next actions live inside each record, so the current status is visible without switching across tools.

2. From first record to sale: the path of one request

Take a hypothetical example. An HR manager at a company fills in the web form of a consultancy that runs sales and communication training for businesses, asking for a price on training for the sales team. The steps below show the path this request takes through the CRM. The Professional Services page covers how consulting, agency and legal teams use XON CRM.

Step 1: the request is recorded

The sales team records the request as a lead and fills in its source (web form), the service it concerns (sales training), its status ("new") and the owning rep.

In XON CRM's Lead Management, source, status and related product or service are separate fields on every lead. Because requests from web forms, phone calls, events or referrals end up in the same structure, the team can see at a glance where a new record came from, what it is about and how quickly it needs a response.

Step 2: first call and qualification

The rep calls the HR manager the same day. During the call she learns which team needs the training and when, as well as who makes the decision. She writes it into a note. Once a second call with the decision maker is set for the following week, she moves the status to "engaged" and attaches a reminder to the call date.

Qualification is the step where you decide whether a request carries a real chance of a sale. The team sets its own criteria; need, timing and access to the decision maker are common ones. If there is no chance, the rep closes the record with a reason instead of deleting it. Those closed records later help show which sources bring qualified requests.

In XON CRM, a lead record keeps notes, planned calls, qualification criteria and the owner in the same flow. Status steps can also be adapted to your sales language. In Reminders, you can set a reminder on the related record for steps such as a return call or a post-quote check.

Step 3: an opportunity is opened

In the second call, the decision maker says the company wants training for the sales teams at two branches and asks for a quote. With the need and the decision maker now clear, the rep sets the lead status to "converted," opens an opportunity and fills in the expected value, the estimated close date and the stage ("quote preparation"). From here on the deal shows up in the pipeline and the manager can see which month it is expected to close.

In Opportunity Management, steps such as discovery calls, needs analysis, quote preparation, approval waiting and closing can be followed inside the opportunity record. Next to expected value and estimated close date, the same record can hold budget status, competitor information and access to decision makers, so the team can judge how mature the deal is more accurately.

Step 4: the quote is prepared and revised

The rep prepares and sends a quote covering training scope, duration, price and payment terms. She moves the opportunity stage to "approval waiting" and sets a date for the expected response. To stay within budget, the customer asks to start with one branch only, so the rep sends a second version with a narrower scope and notes on the quote why the scope changed. When the second branch comes up months later, anyone who opens the record can see what was discussed in the first quote.

In Quote Management, the record shows who received the quote, which version is current and when a response is expected. When the price or scope changes, the reason stays on the record, so the team has a reference point for the same customer or similar work later. How an accepted quote connects to the sale and the invoice is the subject of From Quote to Invoice.

Step 5: the sale closes

The customer accepts the second version. The rep closes the opportunity as won and opens the sales record, which holds the contract status, training date, payment plan and invoice details. The trainers and the finance team start work from the same record, without emailing the rep for details.

Had the opportunity been lost, the rep would have closed it too, this time with a loss reason: price, timing, choosing another provider or the need going away. As loss reasons pile up, you can see at which stage and why deals are lost.

In Sale Management, when work turns into a sale, the quote, customer context, service scope and commercial terms stay connected. When the sales record includes contract status and the implementation start, post-sale operations do not begin with missing context.

Step 6: post-sale follow-up

The relationship does not end with the training. Follow-up moves to the customer card. The card holds the purchased service and the notes from the review call after the training; collection is tracked on the sales record. The rep sets a reminder a few months out for the second branch. When that date arrives, she calls the customer. If the need is confirmed, she opens a new opportunity and the flow starts again from step 3.

In Contact Management, the context of calls, quotes and sales tied to the same customer stays intact; the relationship history does not disappear if the owning rep changes. Once open requests and buying patterns are visible, cross-sell and renewal opportunities are easier to spot. We discussed how to structure post-sale follow-up inside a CRM in Post-Sale Operational Blindness.

3. How does the team use the CRM every day?

Daily use comes down to short updates spread across the day. These are the moments when a sales rep touches the CRM most.

  • Starting the day: She goes through reminders and tasks dated today and the new requests assigned to her. New requests go first, because the longer the first reply takes, the more likely the other side starts looking at alternatives.
  • After every call: She enters the note, status and next step as soon as the call ends.
  • When sending a quote: She links the quote to its opportunity and sets a response date. A quote with no date often gets forgotten unless the customer calls.
  • In the field: Before a meeting she checks the customer history on her phone. After it, she checks her open tasks. XON CRM presents core flows in a calmer mobile layout, so teams can keep track of clients, deals and tasks while moving between meetings.
  • Closing the day: She either finishes the tasks dated today or moves them to a new date, so the list starts clean the next morning.

For teams that work by appointment (clinics, consultancies, service teams), the calendar sits at the center of the daily screen. In Appointment Management, busy hours, open slots and conflict risk can be monitored on the same screen. When the appointment record includes customer notes and previous conversations next to the time and assigned staff, the team arrives better prepared.

4. How does the manager use the CRM each week?

Managers spend most of their CRM time reading records. The weekly sales meeting can run straight from the CRM screen without a separate spreadsheet, which keeps the numbers discussed in the meeting the same as the numbers in the system. These are the main points to check in a weekly review.

  • Unowned records and records with no next step: Records with no owner, no first contact or no dated next step go to the top of the list.
  • Overdue opportunities: For deals still open past their estimated close date, the manager and the rep either update the date or discuss whether the deal is still alive.
  • Deals stuck in one stage: An opportunity that has sat in the same stage for weeks often points to a blocker. The decision maker may have changed, the budget may have been postponed or the quote may have gone unanswered.
  • Sources: The manager looks at which channels bring qualified requests and how many requests turn into opportunities. That answer is on hand when the marketing budget comes up.
  • Loss reasons: If the same reason keeps repeating in lost deals, a decision is due on price, quote content or follow-up speed.

In a team that works with task assignments and reminders, a sales manager can see in XON CRM which records are waiting, which ones are moving and where the process slows down. Detailed Reports turns information collected across modules into reports you can act on. You can also assess a team on follow-up speed, appointment conversion, collection discipline or quote success alongside total sales.

5. The first weeks of setup: flow, status glossary, data and roles

This section covers the usage decisions to make in the first weeks after you switch to a CRM. The timing of that switch is the subject of Ditching Excel and Scattered Spreadsheets.

  1. Write down the flow: Where do requests come from, who makes first contact, at what point does a request count as an opportunity and who prepares and approves the quote? The answers define your CRM stages. XON CRM starts the same way: the first step is aligning the current sales and operational workflow, then setting up the right structure for your team and onboarding through real usage scenarios.
  2. Build a status glossary: Write one sentence per status that says what it means and when a record moves into it. For "converted," that might be "need and decision maker are known, a quote has been requested." Set a short, fixed list of loss reasons too, since free-text reasons are hard to group in a report. In XON CRM, pipeline stages, task flows, customer fields, team ownership and workspace views can be adapted to the way your organization already works.
  3. Clean the data, then import it: Old lists tend to contain the same customer several times or the same detail split across two columns. If you merge duplicates and map fields before the import, the pipeline starts clean on day one. The Import Tool makes it easier to load customer and lead records in bulk from Excel-based files. When columns are mapped clearly to target fields, fewer problems come from wrong matching. Missing, duplicate or non-standard records can also be noticed earlier.
  4. Define roles: Will reps see only their own records or the whole team's? Who can change prices and which fields can finance access? In User Roles, permissions are set by module, action and target. When users see only the modules and fields relevant to their work, screens become easier to understand.
  5. Start with few fields, then review: Too many required fields make forms long. Long forms can lead to incomplete or careless records. Keeping required fields to a minimum in the first weeks also makes it easier for the team to build the logging habit. Within a few weeks you will see which fields people actually use; missing ones can be added then. The XON CRM team takes the same approach after go-live: it learns from live usage and keeps optimizing workflows.

6. Common CRM usage mistakes

  • Leaving records for the evening: Logging calls in a batch at the end of the day means some details get lost. A note entered right after the call may be short, but it is accurate.
  • Leaving the next step empty: If an open record has no dated next step, it never lands on anyone's daily list and only surfaces in the weekly review.
  • Everyone using statuses differently: If one rep calls a record "engaged" and another calls the same kind of record "to be called again," the pipeline report stops reflecting reality. A status glossary exists to prevent this.
  • Updating the quote outside the CRM: If a revision happens over email and the CRM keeps the old version, the person who closed the sale and the person preparing the invoice end up looking at different amounts.
  • Treating the CRM as a reporting tool for managers only: If reps get nothing from the system that makes their own work easier, they delay logging. Once reminders, a template-based quote structure and customer history start saving them time, data entry becomes a habit.

Conclusion: start with one flow

The quickest way to see how a CRM would work in your business is to move one sales flow into it from start to finish. Try tracing your most recent closed sale through the steps in section 2: where did the request come from, who made the first reply and which version of the quote was accepted? If those answers are scattered across email threads and people's memory, start with the first two steps in section 5: write down your own flow and build its status glossary.

You can bring the flow and status glossary you wrote down to a live demo, where we can cover XON CRM setup and your workflow design in the same conversation.