Add to Preferred Sources
CRM for BEE consultants is a client system built around the 12-month life of every B-BBEE affidavit and verification certificate, so that each client's route, expiry date and evidence file drive the follow-up. It differs from the general advice in our CRM software in South Africa guide because a BEE consultancy sells a recurring compliance cycle, not a one-off deal.
Most CRM shortlists start with the sales pipeline: lead, proposal, won.
A consultancy that prepares EME affidavits, QSE scorecards and verification files earns most of its revenue after the first "won", on the anniversary. The right system is the one that makes that anniversary impossible to miss, and keeps each client's documents and sensitive ownership data under control. That is the test to apply to any shortlist, especially where several staff work the same client book.
Quick Answer
The best CRM for BEE consultants is whichever one lets you store a certificate expiry date, a client's B-BBEE route and a document checklist against each company, then trigger reminders from that date. Both the sworn affidavit and the verification certificate are valid for 12 months, so renewal tracking has to come before deal stages. Race-derived ownership data is special personal information under POPIA, and section 10 limits what you hold to what is adequate, relevant and not excessive for the purpose.
Jump to
Not sure your renewal book is trackable?
Send us how you currently log client expiry dates and we will talk through it in a free consultation.
Why does a BEE consultancy run on expiry dates rather than deals?
A B-BBEE affidavit or verification certificate stays valid for 12 months from signing or issuance, so every client you serve becomes a renewal that falls due exactly one year later. According to the practitioner guide at Opreg on EME and QSE status, both the affidavit route and the verified-certificate route carry that 12-month life.
Which route a client uses depends on turnover and ownership. The table follows Opreg's description of the routes; the dtic's Codes of Good Practice are the primary authority, so confirm each client against them before you quote.
| Client type (per Opreg) | Evidence that expires | What the system should record |
|---|---|---|
| EME: total annual revenue under R10 million in the most recent reviewed financial year | Sworn affidavit on the dtic's gazetted template, signed before a Commissioner of Oaths | Signing date, turnover band, resulting level |
| QSE: R10 million to R50 million, 51%+ black-owned | Can use a QSE sworn affidavit instead of a verified certificate | Signing date, resulting level, financial year-end |
| QSE: R10 million to R50 million, below 51% black-owned | Verification certificate from a SANAS-accredited agency, after measurement against the QSE scorecard | Certificate date, level, agency, scorecard weak spots |
| Client in a gazetted sector code | Depends on the sector code | Sector code flag, checked before the route is assumed |
The same source notes that sector codes can override the general thresholds, and names construction, ICT, tourism, forestry, agriculture, transport, financial services, property and marketing, advertising and communications as sectors with their own gazetted codes. A sector field on every company record is therefore not optional.
CRM for BEE consultants: which records should you build first?
A system for BEE consultants starts with the company record, because the certificate belongs to the company and a deal belongs to one engagement. Build four object types in this order, and resist adding fields until each is used weekly:
- Company: route (EME, QSE affidavit, QSE verified, sector code), turnover band, financial year-end, current level, expiry date.
- Contacts: the owner, the financial director or bookkeeper, and the person who signs. Several people sit behind one certificate, and the system must link them all to the company.
- Engagements: one per service (affidavit, scorecard review, verification support, skills or supplier-development advice), each with its own fee and status.
- Evidence checklist: the documents you are waiting on, with an owner and a due date.
The expiry date is the field everything else hangs from. As a working rule of thumb rather than a regulatory requirement, set reminders at 90, 60 and 30 days before expiry, which leaves time to collect documents before a client needs the certificate for a tender or a supplier onboarding. Pick your own cadence, but make it automatic.
Key Takeaway
A BEE consultancy's most valuable CRM field is the certificate expiry date on the company record. Reminders, renewal revenue forecasts and "who is about to lapse" lists all come from that single date, so a system that cannot filter and trigger on a date field is the wrong system however good its sales pipeline looks.
Which client fields should a BEE consultancy track?
A BEE consultancy should track only the fields that change what you do next: the route, the expiry, the evidence outstanding and the next action. Everything else can sit in the document folder where it already lives.
| Field | Why it matters |
|---|---|
| Route and sector code | Decides whether the client needs an affidavit or a verified certificate |
| Certificate or affidavit date and expiry | Drives renewal reminders and revenue forecasting |
| Financial year-end | Opreg describes EME status as turnover in the most recent reviewed financial year, so the year-end shows when a client's band could change |
| Current level and target level | Opens a scorecard improvement conversation for clients who want to move up |
| Skills development evidence status | The Synthro guide says the skills pillar needs training invoices and attendance records to be kept |
| Source (referral, tender, search) | Shows which channel brings clients with renewals worth keeping |
On the generic and QSE scorecard, as described in the Synthro SME guide, ownership carries 25 points, management control 19, skills development 20, enterprise and supplier development 40 and socio-economic development 5. A client who is weak on one pillar is an advisory conversation, and a simple pillar-status field lets you see them without opening a spreadsheet. Our CRM lifecycle stages post covers how to name the statuses so reports stay clean.
Wondering whether your pipeline fits a renewal business?
Tell us your client mix and we will map your engagement stages and expiry reminders to a timeline that fits.
How should POPIA shape the way race and ownership data is stored?
POPIA treats information about a person's race or ethnic origin as special personal information, which section 26 says a responsible party may not process, subject to section 27. A BEE file contains race-derived items: shareholder and management demographics, the black-ownership percentage calculated from them, and the identity documents behind both. Even the company-level percentage is derived from race, so treat it with the same care as the underlying data.
The Act itself offers routes through that prohibition. Section 27(1) lists consent and processing necessary for the establishment, exercise or defence of a right or obligation in law among the situations where the prohibition does not apply.
Section 29 states two purposes for which the prohibition on race or ethnic origin does not apply: (a) to identify data subjects, and only when this is essential for that purpose; and (b) to comply with laws and other measures designed to protect or advance persons, or categories of persons, disadvantaged by unfair discrimination.
Which of those bases fits your consultancy is a legal question for your own adviser. Two other sections apply whichever basis you rely on. Section 10 says personal information may only be processed if, given the purpose, it is adequate, relevant and not excessive. Section 19(1) requires appropriate, reasonable technical and organisational measures to prevent unlawful access to it.
In practice, keep the shared record to what drives the next action: the route and the resulting level. Keep the ownership percentage, demographic breakdowns and identity documents in a restricted folder with named access, and if you do store the percentage in the system, apply the same minimality test and field permissions. Our CRM data governance checklist covers access roles and retention in more detail.
Design rule: if a field does not change a reminder, a quote or a document request, it does not belong in the shared system. That is a practical way to meet section 10's "adequate, relevant and not excessive" condition, and it limits what a lost laptop or an over-permissioned colleague can expose.
What five tests should a CRM pass before a BEE consultancy buys it?
A system suits a BEE consultancy if it passes five tests using dummy clients. When you compare CRM software for BEE consultants, run them on each shortlisted product, whether HubSpot, Pipedrive, Zoho or a local option, and on the plan tier you would actually buy: automation and field-level permissions can sit on higher tiers, so confirm on the vendor's own page that your tier includes them.
- Date-triggered reminders. Can you create a custom date field on the company and fire a task or email 90 days before it?
- Many contacts, one company. Can you attach the owner, the bookkeeper and the signatory to one company and see all of them together?
- Several engagements per company. Can one client have an affidavit renewal and a scorecard review open at once, with separate values?
- Permissioned fields. Can you hide sensitive fields and files from staff who do not need them?
- Export. Can you export every record, including custom fields, to a file you can take with you?
A system that passes all five is workable even if it looks plain. For the price and feature comparison of two common options, see HubSpot vs Pipedrive for South African businesses, and for typical cost lines, the CRM software pricing breakdown. We have deliberately left vendor prices out of this post because plan names and limits change; check each vendor's own page on the day you buy.
A CRM for BEE consultancies with several staff on one client book needs the same five tests, with permissions weighted most heavily. Other professional-services practices face the same renewal and document questions: the posts on accounting firms and architects show how the stage design shifts when the client file, not the quote, is the centre.
What pipeline stages fit a BEE engagement?
A BEE engagement moves through stages defined by who holds the next action, so each stage name should say whether you or the client is waiting. A workable sequence has seven stages:
- Enquiry: turnover band and sector code captured.
- Route confirmed: affidavit or verified certificate agreed.
- Quote accepted.
- Awaiting documents: client holds the action.
- In preparation: you hold the action.
- Issued or signed: expiry date is written to the company record.
- Renewal due: opens automatically from the expiry date.
Stage 4 is the stage most exposed to delay, because it depends on someone outside your firm. A report of every client sitting there, sorted by days waiting, shows where to chase first.
What does the system not solve, and where does acquisition fit?
A well-built client system retains clients; it does not create enquiries. Renewals give you a floor, but growth depends on being found by the business owner who has just been told a tender needs a certificate. That is a search and lead-generation problem, which we cover in our post on lead generation for BEE consultants.
Tracking the source on each company record, as in the fields table above, is what links the two, and it turns your renewal list into a channel report as well. Over time you can see whether tender-driven enquiries, referrals or search produce the clients who renew.
Key Takeaway
A client system for a BEE consultancy keeps clients; it does not find them. Record the enquiry source on every company so you can see which channels produce clients who renew, then fund acquisition from that evidence.
Why South African Businesses Choose Growth Pulse Media
Growth Pulse Media, based in Johannesburg, was founded by Dirk van Greuning, who built and scaled a large South African ecommerce business before starting the agency. All work is executed in-house, with a limited client load for senior attention.
Our digital strategy work starts with the commercial question this post asks: which part of the pipeline pays back, and what does it take to protect it? We build around Google Ads, Meta Ads, GA4 and Search Console for acquisition, and leave the choice of client system to your workflow.
Who Is This Not For?
This advice does not suit three situations, where a different step comes first.
A solo consultant with a few dozen clients. A well-structured spreadsheet with a date column and a calendar reminder passes the five tests at no cost. Move to a CRM when reminders start slipping.
A firm that wants the CRM to store the evidence files. Keep documents in a permissioned drive and link to them. A sales system is a poor filing cabinet for sensitive identity and ownership documents.
Anyone expecting software to fix a document-chasing problem. Reminders only help if a person acts on them. If stage 4 stalls because nobody owns the chase, assign an owner before you buy anything.
Ready to turn renewals into a forecast?
Ask for a free audit of how your client data is structured, before you pick a platform.
Frequently Asked Questions
These questions cover the choices a BEE consultancy has to settle before it picks a client system.
What is the best CRM for BEE consultants?
The best CRM for BEE consultants is the one that passes five practical tests: date-triggered reminders, several contacts per company, several engagements per company, permissioned fields and full export. Features beyond those matter less than whether the expiry date drives your follow-up.
Do BEE consultants need a CRM or is a spreadsheet enough?
A spreadsheet with an expiry-date column and calendar reminders is enough for a small client book. A system earns its cost when several people work the same clients, when reminders are being missed, or when you need to forecast renewal revenue.
How long is a B-BBEE certificate valid?
According to Opreg's EME and QSE guide, both a sworn affidavit and a SANAS-accredited verification certificate are valid for 12 months from signing or issuance. That is why the expiry date is the central field in a consultancy's client system.
Is race and ownership data in a client file special personal information under POPIA?
Information about a person's race or ethnic origin is special personal information under section 26 of POPIA, subject to the exceptions in sections 27 and 29. Shareholder demographics and the black-ownership percentage derived from them are race-derived, so handle them with the same care. Section 10 limits processing to what is adequate, relevant and not excessive, and which exception applies to you is a question for a legal adviser.
What fields should a CRM for BEE consultants include?
Include the B-BBEE route, sector code, turnover band, financial year-end, current level, expiry date and outstanding evidence on the company record. Add contacts, engagements and a source field so you can see which channels bring clients who renew.
Build a client system that never misses a renewal
Whether you are on a spreadsheet or comparing HubSpot and Pipedrive, send us your client stages and we will map your expiry-date reminders and acquisition channels. No obligation, and we will get back to you within 24 hours.
