The contractual engagement between Dimension WebWorx (DWW) and the entities controlled by Gerhard Kriel—Friends of Agriculture (FOA) NPC, KrielTech, and RateTheLeader (RTL) (Pty) Ltd—is defined by a “risk-compounding” architecture. The overlapping nature of these three primary agreements creates an environment where DWW’s operational capital is systematically diverted to subsidize the client’s speculative ventures. By intertwining a pro-bono service level agreement (SLA) with a deferred-payment structure and a high-risk revenue-share model, the client has successfully offloaded 100% of the financial and technical risk onto the developer, vitiating the principle of commercial reciprocity.
Contract Entity | Revenue Model | Payment Structure | IP Rights | Risk Burden |
FOA NPC (SLA) | Non-Revenue | 100% Pro-Bono (incl. CGI/SLA) | Perpetual IP Waiver | Critical: Continuous strategic asset/labor drain. |
KrielTech Entities | Deferred | Contingent on RTL commercialization | KPI Data Access only | High: Capital locked behind third-party success. |
RTL B2B Contract | 10% Net Income Share | 0% Upfront; 0% Milestone-based | Pre-launch Transfer | Existential: Total cost absorption by Supplier. |
The contractual landscape exhibits a profound lack of mutual benefit. The “100% Pro-Bono” clause in the FOA agreement mandates that DWW provide high-end technical services, including complex CGI and web development, for zero financial recovery. Simultaneously, the KrielTech agreement utilizes a “Deferred Payment” structure that ties compensation for multiple entities (AgRetail, FOA Ops) to the success of the RateTheLeader platform. This arrangement systematically strips DWW of operational liquidity, forcing the agency to fund 100% of the development and infrastructure costs while the client retains all capital and provides zero project-specific investment.
The inclusion of a perpetual IP waiver in the FOA SLA represents an unmitigated long-term risk. By relinquishing these rights, DWW is legally barred from repurposing or monetizing the technical architecture developed for the NPC. This effectively creates a “non-compete by theft of IP,” where DWW is prohibited from servicing other agricultural clients using its own developed frameworks, gifting a high-value asset to the client while destroying the developer’s future leverage and asset valuation.
The theoretical imbalances of these contracts have directly translated into a state of severe financial hemorrhaging during project execution.
In a strategic audit, tracking unrecovered costs and “hidden” operational expenses is vital to determining the viability of a partnership. When a client refuses to fund the infrastructure required for their own project, the developer’s role shifts from a strategic partner to an involuntary financier.
As of June 2025, DWW has incurred R134,200 in unreimbursed development costs for the RateTheLeader platform, as codified in Invoice #2025INV0454. These costs include:
Internal assessments indicate that the pro-bono obligations for FOA result in an estimated R280,000 annual loss. This financial strain represents a massive opportunity cost, as senior talent is diverted from revenue-generating accounts to service a client who refuses to meet basic financial obligations.
Evidence from forensic logs and the “Emergency Meeting” transcript reveals a pattern of unfunded infrastructure. DWW incurred over R24,000 in specific license expenses, including Membership Press Pro—a cost the developer noted “broke my back” during the meeting. Furthermore, Source 7 (Printagon Quote QTE121429) confirms that Kriel used DWW as a procurement and branding agent for R6,395 in physical marketing materials (gazebos and banners), further misappropriating technical resources for physical procurement. Despite Kriel’s awareness of Azure Non-Profit limitations (WhatsApp dated 28 May 2025), he intentionally shifted the hosting burden to DWW, leading to an additional R35,000 in integration and infrastructure expenditure.
These financial liabilities are compounded by operational bottlenecks that transform fixed-scope deliverables into indefinite resource drains.
Client-induced “bottlenecking” is a primary risk factor that converts development cycles into “dead-end” resource sinks. By withholding credentials and approvals, the client has frozen the project lifecycle while continuing to expand the work requirements.
The RTL project suffered an 83% rate of missed milestones directly attributable to the client. Primary drivers include the refusal to provide Azure credentials and the failure to approve core functional skeletons (e.g., the “ALFA” version), which paralyzed the deployment pipeline.
An analysis of the client’s “Agenda” (Source 1) reveals a massive, unfunded expansion of scope. DWW was tasked with creating a “link farm” for Kriel’s personal network (ABN) via ten “one-pager” redirects, including:
Item 36 of the Agenda reveals that the developer was forced to “watch videos” to learn the B2B King Plugin, a tool dictated by Kriel despite his lack of technical understanding. Demand for “last-minute integrations” (e.g., Storehub.io) for a platform with zero active users represents a strategic failure, wasting R&D hours on auxiliary features for a non-existent user base.
This operational diversion was not accidental; it served a clear pattern of misappropriating professional talent for personal gain.
The audit identifies a high risk of “Resource Misappropriation,” where DWW’s professional agency time was diverted to enhance Gerhard Kriel’s personal standing rather than fulfilling contracted project goals.
Agenda items 38 and 45 confirm that DWW resources were used for Kriel’s personal brand-building. This includes developing the “Kriel Group Website” via Canva and managing YouTube uploads for old videos. The client explicitly stated these uploads were to prevent others from “stealing my program names,” effectively transforming a web development agency into a free personal trademark-protection service.
The client requested DWW to design logos with “Registered Mark” (®) symbols for his personal portfolio (Item 23). This represents the use of DWW’s professional design talent to provide brand-protection services for Kriel’s personal assets without a corresponding fee structure or commercial justification.
During the “Emergency Meeting,” Kriel attempted to frame the relationship as a “friendship” to avoid professional accountability. This is a classic “Bad Faith Engagement” tactic: Kriel leverages the “friendship” to obtain menial labor—such as Canva designs and video management on memory sticks—only to immediately pivot to a “disappointed client” persona (“I don’t see a product”) once the developer requested payment for incurred costs.
These behavioral patterns culminated in the bad-faith dispute regarding the RTL platform delivery.
Forensic communication logs and meeting transcripts provide an unassailable defense against Kriel’s breach-of-contract allegations.
The client’s claim that he “never saw a product” is demonstrably false. The transcript of the 2-hour and 35-minute demonstration confirms that Kriel was actively “rating” and “messaging” within the system. This proves the system was interactive and functional, not “static” as he later claimed in his termination notice. The developer’s schedule of ALFA and BETA milestones was fulfilled to the extent allowed by Kriel’s own hosting interference.
Kriel claimed he did not expect DWW to “foot running costs.” However, his demand on 1 June 2025 for DWW to deploy RTL on his Azure account—while knowing the account was limited and refusing to fund upgrades—proves he intended to shift the financial burden of hosting to the developer.
DWW issued eight formal delay notices, including critical notices on 14 February 2024 and 9 January 2025. These notices were issued prior to termination and specifically highlighted the bottlenecks. Under the principle of estoppel, Kriel cannot now claim that “pain points were never discussed” as a basis for dispute, as he was formally notified of these issues and failed to rectify them.
A “hard pivot” is required to mitigate the existential liquidity risk posed by the current relationship. The findings of this audit indicate that the partnership has been terminally compromised by the client’s bad-faith tactics.
Future contracts must adhere to a “New Standard” to prevent further exploitation:
Based on the “Verdict: FALSE” findings regarding the client’s claims and the documented unrecovered costs, a continuation of the partnership is not advised. The systemic non-reciprocity and misappropriation of resources constitute a fundamental breach. DWW should proceed with a formal breach-of-contract claim to recover the R134,200 plus interest and dissolve all remaining SLAs with Kriel-affiliated entities.
The risks in these engagements are not merely operational but architectural; immediate and decisive recovery action is the only path to protecting the agency’s long-term solvency.
The RateTheLeader (RTL) engagement was structured as a strategic performance-contingent remuneration model between Dimension WebWorx (DWW), as the Supplier, and Gerhard Kriel/RateTheLeader (Pty) Ltd, as the Client. Under this framework, DWW assumed the initial capital and operational risk of development in exchange for a 10% net revenue share post-commercialization. This agreement was predicated on the Client’s contractual obligation to provide necessary infrastructure and timely approvals to facilitate a global launch.
The following table summarizes the foundational parameters of the engagement:
Parameter | Detail | Reference |
Effective Date | 1 February 2024 | RTL B2B Contract, Preamble |
Revenue Share | 10% of Net Monthly Income | Clause 4.1 / Schedule 4 |
Refundable Advance | R4,000 (Repayable Investment) | Invoice Nr2023INV-347 |
Advance Repayment | Written request required before 28 August 2024 | Schedule 4, Section 6 |
Primary Objective | Fully working website operating globally | Clause 2.4 |
While the framework established a clear path to commercialization, the forensic audit of the project’s execution reveals a systemic failure by the Client to meet core dependencies, shifting the entire financial burden to the Supplier.
The chronological record of the RTL project is essential to identifying the root causes of project stagnation. This audit reconciles documented milestones against actual performance, highlighting the impact of client-induced dependencies.
Date | Milestone/Event | Status/Outcome | Source/Context |
1 Feb 2024 | Contract Effective Date | Project Commencement | B2B Contract Preamble |
5-6 Feb 2024 | NDA Signings | Confidentiality established | NDA Record |
29 Mar 2024 | Alfa Version Target | Missed | Schedule 3 (Prototype/Skeleton) |
17 May 2024 | Beta Version Target | Missed | Schedule 3 (Public Beta Features) |
28 Jun 2024 | Official Launch Target | Missed | Schedule 3 (Go-Live) |
Aug 2024 | Advance Repayment Deadline | No request submitted | Schedule 4, Section 6 |
Feb – April 2025 | Shift to FOA/AgRetail | Strategic Resource Diversion | ARMANDT Discussion Logs |
28 May 2025 | Admission of Hosting Limits | Infrastructure Throttling | WhatsApp (Kriel admits Azure NPO limits) |
1 June 2025 | Formal Termination | Contract Terminated | DWW invokes Clause 10.1 |
Risk Reallocation Analysis The audit identifies 47 documented instances of client-induced delays, directly correlating to an 83% failure rate in milestone achievement. Notably, the forensic analysis accounts for two “hacker” incidents impacting DWW; however, these were handled as controlled variables where DWW successfully restored service, contrasted against three separate delay instances where the Client failed to provide essential instructions. This negligence effectively shifted 100% of the financial risk to DWW, which absorbed over 12 months of development costs (Invoice #2025INV0454) without the Client providing the production environment necessary for revenue generation.
By early 2025, the project reached a critical failure point as RTL resources were systematically diverted to support the Client’s secondary entities, resulting in the total starvation of the RTL development cycle.
Environment stability is a non-negotiable prerequisite for software deployment. The Client’s failure to provide adequate infrastructure represents a material breach of Clause 3.3, which requires the Client to provide “adequate delivery instructions or any other instructions relevant to the supply of the Services.”
The primary bottleneck was the Client’s insistence on using a Non-Profit (NPO) Azure subscription. This environment was inherently restricted, lacking the capacity to support the essential APIs and modules required for the RTL system. A critical breaking point occurred when the Client refused to fund the “Membership Press Pro” license, which was the final essential component requested for compensation to enable the system to function.
Technical Bottlenecks Identified:
This infrastructure negligence rendered the contract untenable, as DWW could not deliver a globally operational product on a restricted, non-commercial server.
Factual grounding is required to refute bad-faith claims made during the termination phase. The following reconciliation addresses the Client’s verbal assertions against the documented forensic record.
Client Claim | Documented Reality | Forensic Verdict |
“DWW failed to deliver despite ample time.” | 83% of missed milestones were caused by client delays and Azure hosting limits (WhatsApp, 28 May 2025). | REFUTED |
“I never expected DWW to pay running costs.” | Invoice #2025INV0454 documents R134,200 in unreimbursed development and running costs. | REFUTED |
“Pain points were never discussed.” | DWW issued 8 formal delay notices (e.g., 14 Feb 2024, 9 Jan 2025) citing project distress. | REFUTED |
Strategic Impact Analysis The emergency meeting transcript reveals a calculated attempt by the Client to use “friendship” to evade contractual accountability. Kriel stated, “I have even gone as far as to think… we have already become friends,” an assertion met with DWW’s clinical rebuttal regarding the necessity of a legal letter to terminate. This breakdown in professional conduct, coupled with the Client’s refusal to fund basic technical requirements, confirms a bad-faith engagement strategy that necessitates immediate legal recovery.
The project suffered from extreme “Scope Creep” where DWW’s “maxed out” manpower was redirected to support Gerhard Kriel’s pro-bono agricultural entities. This diversion occurred while the commercial RTL project was starved of the server funding and approvals required to launch.
The secondary projects that consumed DWW resources include:
Financial Impact of Diversion DWW provided services to FOA at an estimated annual loss of R280,000 in pro-bono labor. While DWW performed high-value Ozow integrations and CGI work for these entities, the Client simultaneously claimed an inability to fund the RTL hosting environment. This represents a strategic diversion of DWW’s capital and labor to benefit the Client’s non-profit interests at the cost of the RTL revenue-share agreement.
Following the formal termination on 1 June 2025, Dimension WebWorx has moved to secure its assets and quantify the Client’s financial liability.
Intellectual Property (IP) Chain of Custody In accordance with the contractual assessment, Dimension WebWorx has asserted full ownership of the RTL IP due to the Client’s material breach and non-payment. The IP has been successfully transferred to and licensed by NorthBright Digital U.S. The Client retains no rights to the source code, data models, or functional architecture of the RTL platform.
Financial Exposure and Liability The Client is currently liable for the following:
Forensic Conclusion The failure of the RateTheLeader project was the direct result of systemic client-side negligence. The Client’s refusal to provide a professional hosting environment, combined with the documented diversion of DWW’s high-value resources to pro-bono entities, constitutes a fundamental breach of the B2B agreement. DWW has fulfilled its professional obligations, while the Client has acted in bad faith to exploit the Supplier’s labor without providing the necessary environment for commercial success.
We use essential cookies to make our site work. With your consent, we may also use non-essential cookies to improve user experience and analyze website traffic. By clicking “Accept,“ you agree to our website’s cookie use as described in our Cookie Policy.