What we do
We source and supply the technology our clients use — software, hardware, licensing, and the services around them. We do this as part of the practice, not as a sales channel.
The distinction matters. Most providers in this market treat procurement and operations as separate businesses — the people who sell the technology are not the people who have to operate it. We sell what we have tested ourselves, what we can operate properly, and what we are willing to put inside our clients’ environments. The procurement decision and the operational decision are the same decision, taken by the same people, accountable to the same outcome.
When organisations need this
Most clients use procurement work for one of a few reasons:
They have decided on a piece of technology — through their own thinking, through advisory work, or through a recommendation — and they need it sourced, licensed, and delivered. They want the procurement to land cleanly, with the right specification and the right supporting arrangements.
They are running a refresh — workstation replacement, server lifecycle, network upgrade, licensing renewal — and they want a single point of accountability rather than negotiating directly with multiple distributors.
They are bringing a new domain into the practice — a new office, a new system, a new compliance requirement — and they need the technology that supports it sourced as part of a coherent whole.
They are an existing client of ours, and procurement happens naturally as part of the operational relationship. We already know the environment, the constraints, and the trajectory; new procurement folds into the same disciplines.
How we approach the work
Procurement looks like a transaction. The work that makes it succeed is not.
We sell what we operate. Every product on our catalogue is something we have tested in our own environment or in client engagements we operate. If we have not used it, or cannot reasonably support it, we do not sell it. This sounds restrictive — and it is — but it is the discipline that makes our procurement recommendations defensible. We are not the right channel for boutique products we do not understand; we are the right channel for the technology stack we operate every day.
We specify properly, even when it slows us down. Procurement is where small specification mistakes become operational problems three months later — the wrong licence tier, the wrong hardware revision, the wrong support level, the wrong cable category, the missing accessory. We check fitness for purpose, we ask questions that turn a part number into a working solution, and we resist the pressure to convert a request into a quote without understanding the requirement. The result is procurement that lands cleanly, integrates into the environment, and does not produce surprises in operation.
We refuse to sell the wrong thing. If a client asks us to procure a product that is not fit for their purpose, we will say so. We will explain what we recommend instead, and why. If the client wants to proceed with the original choice anyway, that is their decision — but we will not pretend the procurement is the right one when it is not. The honest conversation up front is cheaper than the operational consequence later.
We help even when we cannot supply. Some products we do not stock. Some licensing arrangements we cannot offer. Some procurement requirements (notably empowerment-led procurement at higher B-BBEE levels) we are not positioned for. In any of these cases, we will help the client adjudicate a third-party quote — read it, check what it covers, identify what is missing, and confirm whether the product is fit for the purpose. This is offered whether or not the client ends up buying through us. The procurement decision is theirs; our job is to help them make it well.
What we cover
We organise the catalogue around the practice areas the technology serves rather than around vendor lines. The arrangement reflects how clients actually procure — for a purpose, not for its own sake.
Productivity and collaboration. Microsoft 365 across the licence stack — email, SharePoint, Teams, Copilot, the supporting administrative and security licensing. Microsoft Azure where the workload makes sense. Voice and telephony arrangements through hosted PBX partners.
Security tooling. Endpoint security platforms, including managed detection and response upgrade paths for clients whose threat profile warrants them. SIEM, log management, and security event tooling for the monitoring practice. Vulnerability management licensing where applicable.
Infrastructure — networks and edge. Firewalls, switches, routers, wireless access points, structured cabling components. The networking stack we operate inside client environments, sourced from authorised distribution and specified to integrate with the rest of the environment.
Infrastructure — servers, storage, and virtualisation. Server hardware, storage arrays, tape libraries where relevant, the supporting licensing for operating systems, hypervisors, and management tooling. Hosted infrastructure arrangements through South African hosting providers, including budget colocation where appropriate.
Continuity and recovery. Backup software and licensing for on-premises and cloud workloads. Cloud storage and offsite backup arrangements. Microsoft 365 backup tooling. The supporting licensing and capacity for the continuity practice.
Connectivity. Internet connectivity, dedicated lines, and inter-site connectivity arranged through South African connectivity providers. We do not provide connectivity directly — the underlying infrastructure is operated by specialists — but we manage the relationship and the integration into the client environment.
Specialised arrangements. Document and content collaboration platforms, specialist storage tools, and other technologies we have brought into the catalogue specifically because clients we operate with have needed them.
The full vendor and product list, with current authorisations and partner status, is available on request. We do not maintain a public catalogue page because the list changes — products come in, products go out, partner programmes evolve — and a static page would mislead more than it would inform.
A note on commercial structure
Where we are the vendor reselling a service or product, first response and general requests are included as part of the supply arrangement. Detailed engagement structures — block hours, retainers, project-based arrangements — are described on the Engagement Models page.
A note on B-BBEE positioning
WR360 is currently a B-BBEE Level 4 contributor. Our certificate translates to 100% B-BBEE procurement recognition under the Preferential Procurement element of the Codes of Good Practice — meaning clients can claim 100% of their spend with us towards their own preferential procurement scorecard. Empowerment legislation is evolving; we keep our certification current and update this page as our level changes.
Where a client’s primary procurement requirement is to maximise scorecard recognition through Level 1 or Level 2 suppliers, we may not be the right primary supplier and will say so honestly. Where empowerment is one factor among several and Level 4 contributes acceptably, the conversation is open.
We are clear about this position because the South African procurement market includes providers whose primary value proposition is empowerment level rather than the technical work behind it. That is a legitimate position in some procurement contexts; it is not how we operate. Clients procuring through us are procuring on technical fit, operational consequence, and supplier accountability — with empowerment recognition as a contributing factor.
Who this is for
Organisations that want technology procurement to be informed by the operational consequences of the choice — and want a single accountable supplier for the technology they will be using.
It works for organisations that have lived through the alternative — buying the wrong product because the quote was fast and the recommendation was margin-driven, then discovering the operational consequences later. The cost of those mistakes, paid in rework and downtime, is what procurement-as-a-practice protects against.
It works for organisations that already engage WR360 for operational, advisory, or continuity work. Procurement folds naturally into the relationship, and the procurement decisions are coordinated with the operational decisions because they are made by the same practice.
It works for organisations whose procurement requirements include empowerment recognition at Level 4 — which covers the majority of South African private-sector procurement and a meaningful share of public-sector and large-enterprise procurement that includes empowerment as one factor among several.
It may not be the right primary fit for organisations whose procurement is driven primarily by maximising scorecard recognition through higher-level suppliers — though we are happy to have the conversation about whether Level 4 contributes acceptably alongside other factors.
It does not work for organisations that want a quote-shop relationship with no operational accountability. There are providers in that lane; we are not one of them.
How we work with you
Procurement is delivered as part of the broader practice relationship. For clients on operational, advisory, or continuity engagements, procurement is integrated into the work — we know the environment, we know the constraints, and procurement decisions reflect both.
For clients who engage us specifically for procurement, the work runs as defined-scope sourcing engagements. The shape varies — a single procurement event, a refresh project, an ongoing supply relationship, an adjudication of a third-party quote. We discuss the engagement up front and document what is being procured, on what timeline, with what supporting arrangements.
Where the procurement is part of a broader project (a deployment, a migration, a refresh), the procurement work coordinates with the implementation work. The technology arrives, gets specified into the environment, and gets operated against the rest of the practice.
What it looks like in practice
We apply the same procurement discipline to ourselves. WR360’s own technology stack — service desk, monitoring, documentation, automation, communication, and the rest — is procured on the same principles we recommend to clients. We use what we sell. We have lived with the support arrangements, the licensing complexity, the lifecycle realities, and the operational consequences of the choices. The recommendations are shaped by lived experience, not by sales material.
This is also why our catalogue is narrower than some competitors. We are not the procurement provider with the longest list of products — we are the procurement provider whose list is the technology we know how to operate properly. For clients who value that constraint, the narrower catalogue is a feature.
A few honest things to know
Procurement decisions made well take more time than procurement decisions made fast. We work to land procurement properly rather than to optimise the speed of the quote itself. For most clients this is the right trade-off; for clients with extreme time pressure, it sometimes is not.
We do not pretend to be neutral. Our procurement recommendations reflect what we have tested, what we can operate, and what we have commercial relationships with. We disclose this rather than performing neutrality. Where the right answer for the client is a product we cannot supply, we say so and help them adjudicate it elsewhere.
The procurement market includes products with very different operational realities — some excellent, some adequate, some genuinely poor. Part of the value of procurement-through-the-practice is that we have already filtered for what works. Part of the cost is that the filter sometimes excludes products clients have heard about elsewhere. We will explain why, every time.
We will not adjudicate a quote we are also competing against without disclosing it. If you have brought us your incumbent’s quote and asked us to provide an alternative, that is a different conversation from asking us to read the incumbent’s quote independently. Both conversations are available; the boundary between them is just made explicit.
What this connects to
Procurement does not stand alone. It is one face of the practice.
The Information Security Management System practice frames what is procurable. Where the ISMS requires specific control capabilities, procurement decisions reflect those requirements directly.
Advisory and Architecture is where most significant procurement decisions begin. The advisory question — what should we do, with what trade-offs — comes first. The procurement question — how do we source it — follows.
Technology Operations is where most procurement lands. The technology that operations is responsible for is technology that has gone through the procurement practice. The two are co-designed.
Continuity and Recovery and Monitoring and Response both have procurement components — backup software and licensing for the first, monitoring and security tooling for the second. The procurement supports the practice; the practice operates what is procured.
Want to talk?
The fastest way to start is to tell us what you are looking to procure, what it is for, and what other constraints (timeline, budget, regulatory, empowerment) we should know about up front. We will read it carefully and reply with what we think a useful conversation would look like.