CRM Consultant, South Africa

How South African industrial and corporate suppliers win business

The CRM design starts with how deals are won, and for South African suppliers to industry, mining, government and large corporates, that usually involves more formal steps than a standard sales pipeline assumes.

• Public and private tenders arrive with briefing sessions, closing dates, returnable documents and evaluation criteria that may include preferential procurement scoring.
• RFQs through procurement portals run by large buyers, often with short response windows and repeated rounds for the same items.
• Repeat and contract business from existing accounts, where the job is to protect renewals and grow share rather than to chase new names.
• Distributor and dealer channels for suppliers who sell through others in different provinces or neighboring countries.

Each route needs its own definition of progress. For a tender, it might be that returnables are complete and the bid is submitted. For an RFQ, that a quote has gone out before the deadline. For contract business, that a renewal discussion has started well before expiry.

I document these routes with the people who run them, then decide which need separate pipelines and which can share one. Accounts and contacts are shared across everything, so the same customer is not recorded once by the bid team and again by sales. This is the requirements-led method of my CRM consulting service, adapted to the way South African procurement works.

Compliance documents, credit applications and account opening

Winning a South African customer often means passing their vendor onboarding before the first order. Buyers commonly ask for proof of tax compliance status, a B-BBEE certificate or affidavit, company registration documents and a bank confirmation letter. When any of these expires, payments or new orders can stall, and sales usually finds out last.

I design the CRM to hold these as structured records rather than attachments lost in email: document type, issue and expiry dates, which customers have received the current version and who is responsible for renewal. Reminders go out before expiry, and the account manager sees at a glance which customers need an updated pack. The B-BBEE strategy itself belongs with specialist advisors; the CRM simply keeps the evidence current and visible.

The other direction matters too. When your customer applies for credit with you, the CRM can manage the application: collecting the form, trade references and supporting documents, recording the credit controller's checks and approval, and only then creating the customer in the accounting system with the approved limit and terms. This avoids two common problems: sales promising terms that finance has not approved, and customers being created twice under slightly different names.

The result is a clear account opening process that sales and finance both trust, documented as part of the CRM design and tested before go-live.

POPIA and direct marketing: what the CRM should record

The Protection of Personal Information Act governs how personal information is processed, and it includes specific rules on direct marketing by electronic communication. Broadly, marketing to people who are not existing customers requires their consent, while existing customers can be contacted about similar products provided they were given the chance to opt out. How those rules apply to your business, and to business contacts as opposed to consumers, is for your information officer or legal advisor to confirm.

A CRM design can make the rules easier to follow:

• each contact's source, purpose and relationship to the business, recorded at capture
• consent fields where consent is required, with the date, channel and wording
• an opt-out on every message, reflected in the CRM and every connected email or messaging tool
• role-based access so personal information is seen only by those who need it
• retention rules for prospects who never became customers

Data location is another question to raise early. Many CRM products host data outside South Africa, and POPIA sets conditions for cross-border transfers. I ask each vendor where data is stored and processed and record the answer for your advisor. I do not decide what the Act requires; I make sure whatever your advisor decides can be configured, enforced and audited in the CRM.

Quote to cash with Sage, Xero or an ERP

Most South African businesses that adopt a CRM keep an accounting system alongside it, often Sage, Pastel, Xero or a full ERP. The CRM succeeds or fails on how well it works with that system, so I design the boundary between them with sales and finance together.

The points we settle in that session:

• the home of price lists and customer-specific pricing, which decides where quotes are built
• the moment a prospect turns into a debtor account, and the person who creates it once credit is approved
• VAT on quotes, so the buyer sees the figure that later appears on the tax invoice
• the stock and lead-time information a rep may see before committing to a date
• the delivery, invoicing, payment and overdue information returned to the rep's view of the account

In most designs the ledger side keeps tax invoices, VAT and debtors, and the CRM's role ends at a complete, approved order, after which it only displays progress. VAT treatment of particular supplies is a question for your accountant.

When customers buy through procurement portals, the design also notes which documents must be uploaded to the buyer's portal, by whom, and how that step is recorded on the deal. The technical side of these links, including bank and portal connections, is what I handle as an integration consultant for South African companies.

Choosing a CRM that works through outages and staff turnover

I compare CRM options against the design, not against vendor demos. A South African shortlist might include Zoho CRM, Odoo CRM where Odoo is under consideration as the ERP, HubSpot, Salesforce, Dynamics 365 or the sales features of the system you already run.

Two local factors deserve extra weight. First, outages and connectivity: reps on the road and staff at branches need a mobile app that can capture visits, notes and orders offline and sync when power or signal returns, so I test that behavior rather than accept a brochure claim. Second, staff turnover: when an account manager leaves, the customer history should stay with the business. That argues for shared mailboxes or email logging, recorded calls and messages where appropriate, and a rule that key conversations are captured against the account.

Licensing is often quoted in dollars, which affects running cost when the rand moves, so the comparison shows cost drivers in both currencies. Implementer availability and support hours also count.

Adoption is planned from the start: few mandatory fields, useful mobile views and the dashboards that directors already ask for, such as bids due, pipeline by stage and renewals coming up. The work is delivered remotely, alongside my ERP advice for South African businesses; the South Africa page lists the rest.