SCSS IP Theft and Public Warning

SCSS Consulting: A Case Study in Failed Software Delivery and Unacceptable Conduct

Overview

Our Company engaged SCSS Consulting Pty Ltd to design and build a Patient and Admin Portal—a core platform intended to support patient onboarding and management, pharmacy workflow integration, repeat medication ordering, document generation (including letters of attestation), delivery address updates, and online transactions. This portal was business-critical: it directly affected clinical operations, customer experience, patient safety workflows, and our ability to scale.

The engagement was governed by a Software Development Agreement and multiple Statements of Work executed across several months in 2025. The project scope, delivery expectations, and milestones were documented. Despite this, SCSS Consulting failed to deliver any functioning software, including:

• a working prototype,

• a testable staging environment,

• a usable minimum viable product (MVP), or

• a production-ready system.

This is not a complaint about “quality” or “timelines.” It is a case of non-delivery.

The Contracted Work

SCSS Consulting was contracted to develop:

1. A patient portal with secure login and account management.

2. Repeat medication ordering and administration features.

3. Integration pathways to pharmacy dispensing workflows.

4. Secure handling of patient-related information and operational data.

5. A scalable architecture fit for healthcare-related use cases.

6. Documentation, handover, and access to code repositories and environments.

Our team cooperated fully. We provided process maps, workflows, content, clinical and administrative requirements, and significant operational knowledge to enable the build. We also made ourselves available for meetings, feedback loops, and clarifications.

What Was Delivered

After nearly 6 month of engagement, what we received was effectively nothing that could be used. We did not receive:

• a demonstrable product,

• a stable build,

• a working portal,

• a meaningful prototype,

• credible deployment pathways, or

• complete and verifiable handover materials suitable for another developer to continue.

Where progress was claimed, it was not substantiated through functioning deliverables. The gap between commitments and outcomes was severe and persistent.

Concerns Regarding Intellectual Property and Misuse of Knowledge

In addition to non-delivery, we have serious concerns about inappropriate conduct related to intellectual property (IP), confidential information, and business know-how shared during the engagement.

We shared operational workflows, portal logic, user journeys, integration approaches, and proprietary processes that took considerable time and cost to develop. This knowledge was provided for one purpose only: to build the contracted solution for us. We now believe that certain behaviours during and after the engagement created a risk that our IP and internal knowledge may have been misused, repurposed, or leveraged outside the agreed scope, without permission and without proper attribution or contractual basis.

To be clear: we are not publishing confidential materials here. We are publishing a warning based on our experience of conduct that we consider inconsistent with professional standards and the obligations typically expected under a software services agreement, including confidentiality and proper handling of client information.

Parties Identified

SCSS Consulting Pty Ltd
ABN: 82 672 801 599

Principal contact: Sachit Adhikari
Listed locations: Nepal | Australia
Publicly associated with: CEO of Cannabiz Elite (as represented in public channels)

Why We Are Publishing This Warning

We are publishing this statement to:

• alert other businesses—especially healthcare, pharmacy, and regulated-service operators—of the risks we experienced,

• encourage proper due diligence before engaging software contractors, and

• discourage behaviour that undermines trust in professional software delivery.

We strongly recommend that any organisation considering SCSS Consulting:

1. Require verifiable demonstrations of working software at every milestone.

2. Ensure code is committed to a client-owned repository from day one.

3. Use escrow or milestone-based payment tied to objective acceptance criteria.

4. Confirm jurisdiction, enforceable contract terms, and dispute mechanisms.

5. Limit disclosure of sensitive operational knowledge until delivery capability is proven.

Our Position

We stand by the importance of ethical delivery, accountability, and respect for client confidentiality and IP. We consider the outcome of this engagement unacceptable. We will take all necessary steps to protect our operations, our patients, our partners, and our proprietary materials.

If you believe you have had a similar experience involving SCSS Consulting Pty Ltd or related entities, we encourage you to document your interactions carefully and seek independent legal advice.

This notice reflects our experience and is published in the public interest.