This framework is for anyone who creates on behalf of Sourceworx. Use it as a guide, not a script. Our clients are smart, busy professionals and they will feel the difference between copy that truly understands their world and copy that is just trying to sound impressive. The words should make them feel seen. That is the only brief that matters.
On the creative side: always lead with people and outcomes. Show the impact, not the infrastructure. And keep the breathing room — whitespace is not wasted space.
Ready-to-use messaging for five target verticals across every format - ads, web, print, social media, email and video. Anchored always to one truth: we are the partner that makes technology perform.
Before a single headline gets written for a specific audience, this is the anchor. Everything in this document is a translation of these principles into the language of a specific industry.
"We are the partner that makes technology deliver on its promise - reliably, accountably and in the context of South Africa."
"Your Partner in Performance."
This is not a slogan. It is a contract. Use the full phrase in formal contexts and first introductions. In confident, established contexts, let the word Performance stand on its own.
In each vertical it means something specific - and that specificity is what makes it resonate. Translate the concept. Never dilute it.
Pressure from every direction at once. The SARB wants to see cyber resilience frameworks. The FSCA expects CPD records. The board wants stable IT. The audit committee wants POPIA compliance documented. And somewhere in all of that, there are 150 branches with unreliable network connections and a digital onboarding project that cannot get the FICA workflow right.
Specificity, credentials and evidence - in that order. They have been burned by vendors who over-promised. They respond to confidence, not enthusiasm. They want someone who speaks their regulatory language before being asked to. Name the directive. Name the system. Show them you have been here before.
A system failure in financial services is not an IT problem - it is a compliance event, a reputational event and a revenue event simultaneously. The primary message addresses this existential fear.
We are not a generic IT firm that has read the regulations. We have designed our services around them. This message answers the compliance question before it is asked.
These facts answer the due diligence question when procurement and risk committees evaluate us. They close the conversation.
Switch between formats using the tabs below. Every block is ready to drop into a campaign, brief or design layout.
Measured, assured and precise. This audience distrusts enthusiasm. They respond to competence. Write with the quiet confidence of someone who has resolved a SARB audit finding and a branch network outage in the same week - because we have.
Use regulatory frameworks by name. Reference the SA compliance environment directly. Prefer "reliable" over "excellent". Prefer "demonstrable" over "proven". Prefer "your auditors will see" over "you can trust us".
A minefield of overlapping accountability obligations - the Auditor-General, the portfolio committee, council, COGTA, National Treasury and ultimately the residents who either receive services or do not. A technology failure is not just an IT problem. It is a service delivery failure. A procurement irregularity in a software purchase is an irregular expenditure finding that follows the accounting officer for years.
Level 1 B-BBEE status that protects them in every tender evaluation. Technical knowledge they do not have to explain. Solutions that do not create new compliance problems while solving technology ones. And an honest acknowledgement of the real constraints: tight budgets, load-shedding, connectivity gaps and under-resourced IT teams. Do not pretend these do not exist.
Service delivery performance and audit accountability held together. These are not competing priorities when the technology partner understands both.
B-BBEE Level 1 is a competitive advantage in every public sector tender. MFMA and PFMA alignment means the technology we deploy does not create new compliance problems.
We are not offering a global solution adapted for SA. We are offering one built for SA from the ground up.
Respectful, clear and service-oriented. Never condescending. Government communicators are sophisticated and they recognise when they are being talked down to. Write with the respect due to professionals navigating a genuinely complex mandate.
Reference specific legislation by name and section. Acknowledge real constraints - budget, load-shedding, connectivity, skills shortages. Use the language of accountability (audit findings, irregular expenditure, clean audit) because that is the language of the audience.
Instead use: citizen-centred, accountability-driven, service-delivery-ready
A TVET college principal managing no permanent IT staff, learners from disadvantaged communities and a SETA compliance obligation that requires meticulous evidence management. A university CIO managing tens of thousands of devices across multiple campuses, a globally competitive research network and a POPIA obligation covering extremely sensitive personal information. Both are overwhelmed with too many vendors and not enough IT capacity.
Consolidation. A partner who can handle IT infrastructure and the learning platform under one SLA is genuinely appealing to someone currently managing five separate vendor relationships for the same outcome. Lead with outcomes - more students completing programmes, better evidence proving it - and then show how the technology makes it possible.
The primary message holds the outcome aspiration and the compliance reality together. It also introduces the single-partner consolidation that overwhelmed IT and L&D teams find immediately appealing.
EDVantage is the most distinctive asset in this vertical. This message positions it with the specificity that separates it from every global LMS competitor that is adapted for SA compliance versus built for it.
The supporting message addresses consolidation value: IT infrastructure and learning platform from one partner, with all the coordination efficiency that brings.
Purposeful and human. Education professionals are motivated by impact. Lead with outcomes for learners, not features of software. Use aspirational language grounded in specific compliance reality - the aspiration earns attention, the specificity earns trust.
Start with the learner or the student. Move to the administrator's reality. Then introduce the technology as the bridge between what should happen and what currently does. "More students completing programmes and more evidence that they did" is more powerful than any feature list.
Do not lead with technology features. Do not use corporate language like "driving ROI" or "optimising throughput" - this audience finds it alienating. Speak about people first, systems second.
A technology failure that takes down the production reporting system has an immediate financial cost - every minute of production that cannot be measured or managed is production at risk. A cybersecurity breach that reaches an OT network is not just a data breach. It is a potential safety incident and a MHSA liability simultaneously. They are sceptical of technology vendors who have never been underground.
Operational language. Engineers, not salespeople. Specificity about their environment - shaft sinking schedules, SCADA security, MQA learnership management. The scenario "when a crusher fails at 02:00 and the OEM engineer is in Finland" communicates more understanding than any corporate pitch. Show them you have been in this environment before.
Direct and operational. The cost of downtime is immediate and quantifiable. The performance promise is therefore a production promise, not a technology one.
OT/IT convergence is a rare capability. Remote site management at scale is an operational differentiator. Naming both establishes that we have been in this environment before.
Charter compliance and SLP obligations are real commercial and licence risks. A technology partner who manages them reduces the operational burden meaningfully.
Direct, operational and technically credible. This audience does not respond to marketing language. They respond to precision. Use operational terminology. Reference the specific systems they operate. Quantify wherever possible - hours of downtime, rand per hour, percentage uptime.
"When a crusher fails at 02:00 on a Saturday and the OEM engineer is in Finland" is more powerful than "we provide 24/7 support". The scenario communicates understanding of the actual operational reality. Scenarios beat abstractions in this vertical.
Avoid corporate abstraction. "Digital transformation", "technology ecosystem" and "innovation journey" are noise in this context. Speak in operational outcomes - production targets, safety records, compliance obligations met.
A complex, high-stakes technology challenge that does not fit a standard offering. The organisation going through a merger needing IT transition management. The CFO who needs a Power BI Centre of Excellence. The DG digitising 255 citizen services. They have been through complex technology projects before and they know how badly they can go wrong.
Single accountability. The number one failure mode in complex projects is not technical - it is accountability. Multiple vendors. Nobody owns the outcome. When things go wrong, everyone points at someone else. Sourceworx's breadth - network, security, software development and products all in-house - is the differentiator. That is what this audience is genuinely searching for.
Single-partner accountability is the core promise. This addresses the number one pain in complex IT projects.
Single accountability is only valuable if the partner has genuine depth. We are not a PM layer over subcontractors. We are an engineering organisation with 70-plus people and the track record to prove it.
Complex project buyers often cannot use a standard managed service pricing model. We accommodate the way they need to buy.
Calm, thorough and direct. This audience has usually just survived a difficult experience with a previous vendor. Overconfidence is a red flag to them. Thoughtful, evidence-based confidence is reassuring. Acknowledge complexity and risk before proposing a solution.
Show that you understand the failure modes - vendor finger-pointing, scope creep, post-go-live abandonment. Then explain specifically how your approach prevents each one. Replace vague commitments with specific ones: "We manage the system we build under a long-term SLA. You do not get handed off to a support team that was not part of the build."
Avoid the phrase "partnership approach" - it is overused and meaningless. Replace it with specific commitments. Never say "we will be there for the long term" without explaining what that means structurally.