Skip to main content
Customer relationships (CRM)

A relationship that is managed from first contact to closed deal

Pipelines and their stages, customers and contacts, leads and their conversion, activities and follow-up, quotations and approvals, where each lead came from, and revenue forecasting in one system — so “where do we stand with this customer?” has an answer in the system rather than in someone’s memory.

Request a needs analysisSee the sales cycle
  • Clear pipelines and stages
  • Customers and contacts
  • Activities and follow-up
  • Quotations and approvals
  • Revenue forecasting
Odoo · Inventory
Temporary placeholder — slot for the pipeline view

Direct answers

The questions asked first

Does CRM replace our current sales system or integrate with it?

The default is Odoo CRM, because it shares one database with inventory and accounting — a quotation becomes a sales order and then an invoice with no re-keying. If you run a sales system you want to keep, we first inspect its APIs and its ability to exchange customers and orders, then decide: integrate, replace one channel gradually, or keep it and connect reporting. We will not promise an integration before inspecting the interfaces.

How do we know where each lead came from and what each channel returns?

We configure sources and channels (advertising, search, referral, exhibition, direct call) with campaign tags, and connect the website forms to them, so the source is recorded automatically when a lead arrives through a digital channel. Non-digital channels — a call, a visit, a verbal referral — depend on whoever logs them being disciplined, so we make the source field mandatory on the entry form. Without that rule the reporting stays incomplete no matter how good the system is.

Does it support different sales stages per team or product line?

Yes. A separate pipeline can be defined per team or product line, with its own stages and a win probability per stage, plus automation rules that move a deal when a condition is met (a quotation sent, a customer reply). We configure the stages around your actual sales cycle rather than a ready template, because a stage nobody uses corrupts every report built on it.

What actually decides whether a CRM implementation succeeds?

Adoption by the sales team, not the software. A complete CRM with no consistent entry becomes an archive rather than a tool. So we make entry a precondition for the next step where possible — no quotation without an opportunity, no closing without a lost reason — cut the fields down to what is genuinely needed, and build the reports on what actually gets entered. We say that plainly during analysis, because agreeing the operating rule matters more than choosing the fields.

Anatomy

What sales work is made of

Eight elements sharing one set of data, so every call, quotation and lost reason forms part of one picture.

Pipelines and stages

A pipeline per team or product line, with its stages, win probability, and rules that move a deal when a condition is met.

Stages built on your real cycle

Customers and contacts

One record for the company, its branches and the people inside it — address, tax number and history — rather than numbers on each rep’s phone.

One record per customer

Leads and conversion

Capture the lead, qualify it, then convert it to an opportunity or discard it with a recorded reason — instead of a list nobody knows the fate of.

Every lead has a fate

Activities and follow-up

A call, meeting or task with a date and an owner, and a reminder before it is due — so a deal is not forgotten because nobody opened the calendar.

Follow-up has a date and an owner

Quotations and approvals

A quotation with its lines and terms from the same price list, with an approval chain for discounts or terms before it reaches the customer.

No discount without approval

Lead source and channels

A source on every lead and a tag per campaign, with the website forms connected, so you know which channel actually delivers and which one only consumes budget.

The channel known from the start

Revenue forecasting

Open opportunities weighted by each stage’s probability and expected close date — a number built on the pipeline rather than on optimism.

A forecast built on the pipeline

Email, calls and interaction history

Connecting the mailbox and calls so the interaction is recorded on the customer record, letting whoever takes over the account see what happened before them.

History stays with the account

The sales cycle

The sales cycle

Six steps with a clear output each, and one rule: no transition without an entry, and no closing without a reason.

  1. 01

    Capture the lead

    From a website form, a call, an exhibition or a referral — with the source recorded as mandatory and the follow-up owner assigned.

    Output: a lead with an owner and a source

  2. 02

    Qualify

    A first call to understand the need, budget, timeline and decision maker, then converting to an opportunity or discarding it with a written reason.

    Output: a qualified opportunity or an explained discard

  3. 03

    Quote

    Building the quotation from the price list, with discounts and terms inside the rep’s authority or an explicit approval chain.

    Output: an approved, sent quotation

  4. 04

    Negotiate and follow up

    Scheduled and recorded activities for each negotiation round, updating the stage and expected date instead of leaving the deal without a next step.

    Output: a deal with an updated stage and date

  5. 05

    Close

    A won close turns the quotation into a sales order; a lost close records a reason from a defined list — rather than letting the deal quietly disappear.

    Output: a sales order or a lost reason

  6. 06

    After the sale

    Following up delivery and collection, plus renewal or upsell activities with dates, because an existing customer is cheaper than a new one.

    Output: renewal activities and satisfaction follow-up

Controls

Control over the data

Controls that make the reporting trustworthy: who owns a record, who may see what, and who moved a stage and why.

Record ownership and deduplication

Every customer and opportunity has one clear owner, with duplicate detection at entry — so two reps never chase the same customer unaware.

Data visibility rules

Who sees only their own opportunities, who sees their team’s, and who sees every branch — one rule configured once and applied to every screen and report.

A history of who changed what

A stage, amount or close-date change is recorded with the name and time behind it — which is what makes any number reviewable.

A lost reason is mandatory

A deal closed as lost without a reason means the company paid for a lesson and did not learn it — so the reason is required before closing.

Data quality at the point of entry

A few well-chosen mandatory fields, dropdowns instead of free text, and rejection of an invalid phone number — good reporting starts at entry.

Reporting

The reports a sales team gets asked about

What management needs: where the money sits at each stage, what is expected to close, and where the losses teach something.

Pipeline by stage

The count and value of opportunities at each stage, and where deals pile up instead of moving.

Conversion by stage

How many move from each stage to the next, and where the real loss is — not one overall percentage that says nothing.

Expected revenue

The forecast weighted by each stage’s probability and close date, against target, per team and period.

Team performance

Activities, opportunities and wins per rep — for comparison and coaching rather than for blame.

Lost reasons

Losses distributed across price, product, timing and competitor — the report most likely to produce an actual change.

Lead sources and channel return

Where leads came from and where the closed deals actually came from, because the channel bringing the most is not always the most profitable.

Integration

CRM is not an address book

The value shows when a quotation becomes a sales order, a website lead becomes an opportunity, and a closed deal becomes an invoice.

Sales and orders

A won opportunity becomes a sales order with the same lines and prices, so the quotation is never retyped in another system.

Accounting

Invoices and collections show on the customer record, so a rep knows the payment position before asking for a new order.

Website and web forms

Website forms create a lead with its source automatically, instead of enquiries piling up in one person’s inbox.

Email and calendar

Messages and appointments are linked to the customer and opportunity, so the interaction history stays with the account rather than a rep’s mailbox.

Point of sale and eCommerce

Branch and online sales appear on the same customer record, so the customer picture is complete rather than split.

Scope

Delivery scopes

Described scope with no published prices: cost depends on the number of teams, pipelines, users and integrations, and is quoted in a proposal.

نطاق مركّز

Foundation

One pipeline with its stages, customers and contacts, leads, activities and follow-up, and core pipeline reporting.

The right first step for one sales team

النطاق الكامل

Advanced sales

Everything in Foundation plus multiple pipelines, quotations and approvals, lead sources and campaigns, revenue forecasting, and email and website integration.

The common single-entity scope

نطاق ممتد

Multiple teams and branches

Everything above with several teams and branches, visibility rules per level, targets per team, and additional customisation and integrations.

Quoted after the needs analysis

We publish no price before the needs analysis: cost follows the number of teams, pipelines, users and integrations.

FAQ

Questions asked before signing

Direct answers on scope, responsibility and what the system does not do — without inflation.

Does CRM replace our current sales system or integrate with it?

The default is Odoo CRM, because it shares one database with inventory and accounting — a quotation becomes a sales order and then an invoice with no re-keying. If you run a sales system you want to keep, we first inspect its APIs and its ability to exchange customers and orders, then decide: integrate, replace one channel gradually, or keep it and connect reporting. We will not promise an integration before inspecting the interfaces.

How do we know where each lead came from and what each channel returns?

We configure sources and channels (advertising, search, referral, exhibition, direct call) with campaign tags, and connect the website forms to them, so the source is recorded automatically when a lead arrives through a digital channel. Non-digital channels — a call, a visit, a verbal referral — depend on whoever logs them being disciplined, so we make the source field mandatory on the entry form. Without that rule the reporting stays incomplete no matter how good the system is.

Does it support different sales stages per team or product line?

Yes. A separate pipeline can be defined per team or product line, with its own stages and a win probability per stage, plus automation rules that move a deal when a condition is met (a quotation sent, a customer reply). We configure the stages around your actual sales cycle rather than a ready template, because a stage nobody uses corrupts every report built on it.

What actually decides whether a CRM implementation succeeds?

Adoption by the sales team, not the software. A complete CRM with no consistent entry becomes an archive rather than a tool. So we make entry a precondition for the next step where possible — no quotation without an opportunity, no closing without a lost reason — cut the fields down to what is genuinely needed, and build the reports on what actually gets entered. We say that plainly during analysis, because agreeing the operating rule matters more than choosing the fields.

Can our existing customer data be migrated from a file or an old system?

Yes, with a check before migrating: we review the file or export, clean duplicates and unify names and contact numbers, then migrate with a reconciliation pass on the customer count and open value. We say plainly that a file with no tax numbers or incomplete addresses stays incomplete after migration — cleaning is joint work, not magic.

What is typically out of scope in a CRM implementation?

Selling the tool internally to the sales team, deciding the pricing and discount policy on management’s behalf, manually cleaning a very large historical dataset, running the advertising campaigns themselves or buying media, and legal advice on data protection. We configure the system and the rules and train the team; the commercial decision and statutory compliance remain the client’s responsibility.

How do you handle reps who refuse to enter their data?

This is not a software problem and we treat it as an operating rule: cut the fields to the minimum, make entry a precondition for the next step where possible, and tie any commission or report to what was actually entered. We tell management during analysis that the system will reflect what is entered, so unless entry is enforced internally the reports will be incomplete — and that is a management decision, not a technical one.

Request a sales needs analysis

Four details are enough: how many sales teams, how many users, your current lead channels, and the sales system you use today.

  • Reply within one business day
  • Written scope before any commitment
  • Your customer data is not shared with third parties
Services needed

By submitting you agree that we may contact you about your request. We do not share your data with third parties.

Ready for a pipeline where every deal is known?

Tell us how many sales teams and users you have and which channels you use, and we will come back with a delivery plan and a clear scope.

Request a proposal

Related topics

We are a systems implementation and integration company, not a certification body. We configure the pipelines, stages, permissions and reports and train the team; consistent data entry, team adoption and daily use remain the client’s responsibility — and they are what decides the outcome. We announce no conversion or revenue improvement before measuring it against an agreed baseline, and we cannot guarantee data that was never entered.

Or contact us directly